---
name: sideop-ledger
description: Runs a project's change log and document revision ledger — when a change of direction earns a numbered entry, the entry format, how a tracked document's revision number bumps, and the weekly after-action review. Trigger when the user says the plan changed, asks to log a decision, edits a tracked document, or asks for the weekly review. Never invent numbers; log only what the user reports.
---

# Ledger

## Job
Keep an honest record of what changed, why, and what it cost, so the user can always answer "why did we do that?" from the file, not from memory.

## What earns an entry
A numbered change-log entry is written only for a **change of direction**: a decision that replaces a prior plan, cadence, format, tool, price or rule. Routine work, small edits and status updates do not get entries; they go in the weekly review.

Ask before writing: "Does this replace something we decided earlier?" If no, it isn't an entry.

## Entry format
Every entry has the same five parts, in this order:

1. **Planned** — what the plan said before this change.
2. **What happened** — the real events and real numbers that prompted it. No estimates.
3. **What changed** — the new plan, stated plainly, and which tracked documents it touches.
4. **Why** — written by the user, in the user's own words. Leave this line blank and ask for it. Do not draft it unless asked.
5. **What it cost** — time, money, posts or work thrown out.

Entries are numbered in order and dated. Nothing is edited after the fact; a later entry corrects an earlier one.

## Tracked documents and revisions
- A tracked document is one listed in the ledger table: [YOUR DOC 1], [YOUR DOC 2], … Each has a revision number, starting at Rev 1 the day it enters the ledger.
- Any change to a tracked document's meaning bumps its Rev by one and adds a dated line to that document's revision history saying what changed. Fixing a typo does not bump the Rev.
- When one document changes, name every other tracked document that says the same thing, so none goes stale.
- The ledger table holds: document, current Rev, date, and a one-line summary of each Rev.

## Weekly after-action review
Run on the same day each week. Ask the user one at a time:
1. What did you plan this week?
2. What actually happened? (Real numbers only, from the user.)
3. Why the difference?
4. What do you keep doing?
5. What do you change? (If this replaces a prior decision, it becomes a change-log entry.)
6. Hours spent this week, as reported.

Write it in five short sections plus the hours line, and end with next week's top three.

## Rules
- Real numbers only. If the user hasn't reported a number, write [not reported].
- The user writes every Why.
- Date everything.

## Install
Replace the [YOUR DOC] placeholders with your tracked document names. Add the file to the project that owns those documents; ask for it by name.