add-build-ledgerlisted

# Build Ledger — Execution Discipline <!-- uses: - skill: add-commit - mention: /add-framework--done --> Layer-neutral. Governs HOW execution is recorded and when it may continue. WHAT a given layer validates belongs to that layer's own skill, which the executing command selects per F-block. ## When to Use - Planned mode, before the first F-block. - Re-entering a build — every entry, not only after a crash. ## When NOT to Use - Unplanned/direct mode. No F-blocks, no ledger. --- ## F-Block Identity **One F-block = one item of the plan's Execution Order.** Ids are `F1`, `F2`, … in every layer, each carrying the layer tag the plan gave it. There is no separate internal `S<n>` series. Legacy plans on disk using `S<n>` keep their ids — read them, do not renumber them. --- ## The Ledger **Path:** `docs/plans/<plan-basename>--ledger.md` — the plan's basename with `--ledger.md` appended. **Why it is mandatory:** it carries the rulings, and a diff cannot show a decision. **During the build the ledger reaches nobody on its own.** `docs/plans/` is gitignored, so every `Ruling:` line must be carried out of it and into the completion report — that report is how a decision reaches a human while the work is still changeable, and nothing later replaces it. **After close-out the ledger itself survives.** `/add-framework--done` copies it to `docs/deliveries/<plan-basename>/ledger.md` and commits it with the delivery-index entry, so the raw rulings reach `main` before anything r