Skip to content

Every record names the commit, the branch and the episode that made it

The ledger records every durable event with its task and its head; identity fields on any record are computed from git and refused when authored; a closed session is an immutable record of what one episode produced; the person's prompts are captured by the provider's hooks; and retention is capped by policy rather than by forgetting.

Who did what, under which task, at which commit, in which session is a ledger the tool writes and a person can read back, not a memory of a conversation.

status
stable
exposed through
area
observability
cost
for
enterprise
engineering-lead

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; the ledger records the events that a cost model would need, and the economics document says what honest measurement would take. 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.

The commands that run it

  • majordomus history inspect · read-only

    Read the append-only ledger back, filtered by task, event or time.

  • majordomus session begin

    Open, inspect and close one execution episode.

  • majordomus capture work

    Record the person's raw prompts from a provider hook as a record with its renderings, draw the episode boundary from the provider's own lifecycle hooks, install those hooks, and report what each provider actually does here.

  • majordomus watch inspect · read-only

    What has drifted since the last update — policy, projections, state, retention.

The objects it is made of

Kinds of the layer. Each is a schema, a source class and a file on disk; the number beside it is what this repository holds today, counted at build time.

  • session11

What it answers

Operational moments from the Why catalogue that name one of this feature's mechanisms. Nothing here was assigned: a moment appears because it names a rule, a command, a capability or a claim this feature also names.

The rules that hold it

What is guaranteed

Executable use cases