Format-as-analogy-generator
The observation that a file format is not just storage — it seeds analogies and behaviors. The per-memo-file layout (one memo per file, vs a single ledger) seeded unexpected parallel-PR patterns: two sessions could each issue a memo without a merge conflict, which made parallel fan-outs structurally cheaper than they would have been with a shared ledger.
Where named
MEMO-2026-05-06-3vvg. Builds on the per-memo migration in issue #210.
Detail
When the memo corpus was a single memo_index.md ledger, two parallel sessions issuing memos would race on edits to the same file. Resolving the race meant either serializing memo issuance (losing parallelism) or post-hoc merging (losing the simple “one PR per memo” workflow). After issue #210 split the ledger into one file per memo, parallel issuance became free.
The “analogy generator” framing is that the format change wasn’t just operational. It made parallel fan-outs expectable. Once two instances could issue memos without colliding, the chain found reasons to actually run two instances in parallel — the eight afternoons (accidental) and the laughing-davinci dispatch (deliberate). The format had implicitly licensed a behavior the chain went on to do.
Links to this page
The committee ratified the transition design. The companion follow-on PR (#90) implemented it. The per-memo layout has now produced an unexpected second-order effect — what the chain came to call format-as-analogy-generator: the per-file layout seeded a parallel-PR pattern that recurred at N=3, making it large enough to name as a structural property.