Drew T
1.4 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| keep-an-accelerator-ledger | Every late discovery that would have sped up EARLIER work goes into a dedicated ledger the same session — what it is, when it was found, when it COULD have been found, what it would have saved — so the next project gets it on day one |
|
Keep one document (docs/accelerators.md on the source project) whose only question is "what should phase one of the NEXT
project do differently?" The per-phase records say what happened; they do not answer that question.
Why: the source project found its biggest levers late — the whole-binary byte-gate harvest at phase twelve, cross-binary propagation at phases eleven to fifteen, the compiler's codegen map at phase twenty-three, the instrument-integrity audit at twenty-six — each available years, in project time, before it was built. Reading the ledger is how a new project inherits that order instead of rediscovering it.
How to apply: when a discovery lands, ask "would this have changed earlier work?" If yes, add an entry the same session with the four fields. Distinguish honestly between a lever that was available earlier and one that structurally could not exist yet (it needed the fleet onboarded, the compiler pinned); the second kind goes in too, marked, because its prerequisite is the real advice. The ledger feeds the retrospective and the next project's roadmap.