Ledger
The versioning system — every change classified, stamped, and recorded.
A system that changes every day needs to know what changed, how much it matters, and what to call the new state. Ledger is the part of LifeOS that answers all three. Every change is classified, stamped with a version, written into a record, and rolled up into one number for the whole system. Nothing drifts, because there is one authority that decides what version a change is.
Why it exists
Version numbers rot when they’re typed by hand. One doc says 8.2, another says 8.2.0, a third never got bumped at all, and soon nobody trusts any of them. The fix isn’t discipline, it’s a single owner: one system that reads the change, decides the level, and writes every number so they always agree.
It also keeps the language honest. A fix is not a feature, and a feature is not a breaking change. Ledger holds that line so “what version is this” always means the same thing.
How it works
Every version is three levels — Major.Feature.Patch. A patch is a fix. A feature is something new and additive. A major is a structural or breaking change, and it never happens without a real conversation first.
The system carries two layers of number. The whole OS has one rolled-up version, and each part — the Algorithm, the memory system, every skill, every hook — carries its own. A change to one part bumps that part and rolls up into the whole, so the two never disagree.
Where it fits
Ledger sits at the end of a change, not the start. You build the thing; Ledger names what you built. It stamps the private repos and tags them, and it stops there. Cutting a release and publishing it to the world are separate, more careful steps on purpose — stamping a version is not the same as shipping it to everyone.
That separation is the whole point. Private-sync, cut, and publish are three different acts with three different levels of care, and Ledger owns only the first one.