Make the system tell the truth about what is closed.

Proof Ledger turns the queue into an execution memory: 36 proof slots, expected evidence, actual evidence, closeout questions, and the next action if the proof failed.

Simple layer. If there is no proof, the loop is still open. Open the ledger, close one slot, then decide whether to continue, validate, sell, publish, park, or cut.

The generator reads Action Queue, Daily Run Log, Guide Router, Watchtower, Cashflow, Pipeline, Relationship, Presence, Project Portfolio, Client Delivery, Company, Learning, Life Compass, and Weekly Review.

Run the ledger

node work/life-os-proof-ledger.mjs
# or
node work/life-os.mjs proofs

# then open:
outputs/life-os-command-center/life-os-proof-ledger.md

Read the slots

36 proof slotsEach slot has source, area, command, file, expected proof, actual proof, and close question.

20 revenue slotsCash, pipeline, relationships, and delivery proofs keep business movement visible.

7 session slotsAgent sessions get a real outcome instead of another open tab.

7 review promptsThe closeout review forces proof, decision, privacy, and next action.

Close one loop

1. Open the #1 proof slot.
2. Execute only that action.
3. Write the actual proof.
4. Pick the decision: continue, validate, sell, publish, park, or cut.
5. If it failed, write the blocker and the smaller next proof.

Import into the cockpit

outputs/life-os-command-center/life-os-proof-ledger-import.json

Proof from this run: Proof Ledger writes 36 proof slots, 36 open slots, 20 revenue slots, 7 session slots, 7 closeout prompts, and 12 cockpit captures.

Guardrails

The ledger does not send messages, publish, buy, delete, or control apps. Do not paste secrets or private messages into proof fields. A failed action counts as proof only when it names the real blocker and the smaller next correction.