What it does
Every command that changes durable state appends one event to the ledger, with the task and
the head it happened at, from a closed vocabulary. majordomus history reads it back and
validates it; watch reports drift between policy, projections, state and git with the
command that reproduces each finding. A closed session record names the branch, the commit
it started from, the one it ended at, the commits between, the paths changed and every
record the episode produced, all derived; the working copy is named by a hash, never by a
path on somebody's machine.
That is the foundation for tracing a change from the provider and model class that made it, through the session and the task, to the commit and the decision it rests on — as data a program can read, on every surface.
What it does not do
It measures no tokens and no cost itself; the ledger records the events a cost model needs, and the economics subsystem, which measures tokens only in matched runs, says what it does and does not measure. It makes no compliance claim: what it provides is a trail with computed identities, and what an organisation does with it is the organisation's.