Record the decision, proof, blocker, and next action before you move on.

Decision Proof Journal is the local-only, mutable memory for the Life OS. It stores manual, sanitized notes after a real session: 1 event so far, 8 proof slots, 7 review prompts, and 10 import captures for the cockpit.

Simple layer. Guided Work Session gets you through one focused loop. Decision Proof Journal preserves what actually happened so tomorrow starts from evidence, not another blank plan.

The operator command calls work/life-os-decision-proof-journal.mjs and rewrites decision-proof-journal.md, decision-proof-journal.json, decision-proof-journal-events.json, and decision-proof-journal-import.json. Events are stored locally and sanitized before output.

Run the journal

node work/life-os.mjs journal --area session \
  --decision "Closed session X" \
  --proof "File Y updated" \
  --next "Verify Y tomorrow"

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

Use the seven fields

arealife, session, revenue, project, content, learning, or proof.

decisionThe decision you can re-open later without reconstructing the whole context.

proofFile, command, screenshot, local artifact, result, or reproducible blocker.

nextThe next concrete action after the proof.

statusclosed, blocked, open, or parked.

link/blockerOptional sanitized pointer or blocker detail.

Review with proof slots

The 8 proof slots cover session proof, money proof, Proof Ledger close, project decision, presence proof, daily closeout, diagnostic proof, and resource proof. The 7 review prompts ask what closed, what blocked, what moved money, what should be parked, and what becomes tomorrow's one action.

Import into the cockpit

decision-proof-journal-import.json contains 10 import captures plus a small project, pipeline rows, learning prompts, and rhythm rows. Export your browser state before importing because the cockpit import replaces current localStorage.

Guardrails

Do not paste raw emails, DMs, bank data, credentials, tokens, private client material, or unsanitized paths. If proof is missing, mark a blocker instead of pretending the loop is closed.