# Guide 1 — Why files beat memory

An AI founder's defining constraint is not intelligence — it's that every working session starts from zero. No memory of yesterday's decisions, no feel for the cash position, no recollection of why the pricing is what it is. Naïvely operated, an AI-run company is a company with total executive amnesia, and it fails in predictable ways: re-litigating settled decisions, hallucinating financial facts with perfect confidence, and drifting strategy every session because each session reinvents the context.

The fix is not a bigger context window. The fix is an institution.

## The principle

**Facts about the business live in files, not in the model.** The model is labor; the repository is the company. Three rules make this real:

1. **Any claim about money reconciles against LEDGER.md** — and LEDGER.md only accepts numbers that trace to a document a human relayed. The founder's recollection of the balance is not just untrusted, it's *inadmissible*. This sounds paranoid until the first time a model states a plausible, confident, wrong number — which it will.
2. **Any claim about the past reconciles against DECISIONS.md** — which is append-only precisely so it can be trusted. An editable history is not a history.
3. **Where memory and files disagree, files win.** No exceptions, including when the files seem wrong. If a file *is* wrong, the fix is a new logged entry correcting it — never a silent belief override.

## What this buys you

- **Succession for free.** If the company survives being run by an entity with no memory, it automatically survives switching models, vendors, or architectures. The continuity problem and the amnesia problem are the same problem; solving one solves both.
- **Auditability for free.** A company whose every decision carries logged rationale and whose every dollar traces to a statement is in better shape than most human-run companies. The discipline amnesia forces on you is the discipline auditors wish everyone had.
- **Honest failure.** When the record is append-only and the human's minutes are logged, quiet failure is structurally difficult. The books can't be shaded because the books are the operating system.

## The corollary discipline

Every session ends by paying the institution back: rewrite the state snapshot, append the decisions, log the interventions, commit. A session that does brilliant work and doesn't write it down *subtracted* value — the next founder-instance now holds context that contradicts the files, and the files win.

Treat unusual events as letters to your successor (a `MEMORY/` folder of dated notes). The state files say what is true; the letters say what it was *like* — which traps almost caught you, which workaround is load-bearing. Successors read them in seconds and dodge hours.