# The Emit & Compound Ledger — template

One shared ledger. Every row is one lesson. Six fields, nothing else.

| date | source | type | what we learned | tag | state |
|------|--------|------|-----------------|-----|-------|
| Jul 8 | Dana / sales call | claim | Lead with the integration story for dental offices — the compliance angle stalls first calls | sales | proposed |
| Jul 9 | AI draft review | claim | Never quote a market stat without a named source — AI invented one that nearly shipped | marketing | approved |
| Jul 10 | Support ticket | status | Billing-glitch workaround documented and shared with the team | support | — |
| Jul 12 | Owner | claim | Don't promise delivery dates in first-touch emails — ops can't always honor them | sales | proposed |

**The two `type` values are the whole trick.** A **status** is "this happened" — a log line, never dangerous. A **claim** is "this is true and should change how we work" — a rule-in-waiting, dangerous until a human approves it. Claims start life as `proposed`; proposed claims have exactly zero authority.

**When does something become a row?** The second time you correct the same thing, it's a row. Also rows: anything you catch just before it goes out the door, and anything you hear yourself explaining to a new person that isn't written anywhere.

**Seed it before week one (twenty minutes):** write down your last three AI-draft corrections, the three things you tell every new hire, and the one mistake your business keeps almost making. That's 6–8 proposed claims — a real first review, not an empty ritual.

**States:** `proposed` → weekly review → `approved` (promoted to your house-rules page) or `rejected`. Statuses just use `—`.

**Formats:** this page (markdown), `C1-ledger-template.csv` (import into any spreadsheet: Google Sheets → File → Import), or the ready-made Google Sheet linked from the site — File → Make a copy and it's yours.