Decisions

Architecture decision records. Each one states a context, a decision, and the consequences accepted with it. A record is never edited to reflect a change of mind. It is superseded by a later record.

Decisions about the blog series rather than the code live in a separate repository, because they govern the writing rather than this implementation.

Records

• ADR-0001: The documentation stack. Why this site is pinned on both sides, and what to watch.
• ADR-0002: An unresolved parent is recorded as absent, never inferred. Why 95 preparations stay unresolved, and why raising that number by guessing fails a test.
• ADR-0003: Culinary terms carry a language tag and are never translated. Why mole is not "sauce", and what that costs.
• ADR-0004: Source material is committed, derived output is not . Why a clone runs offline, and what may enter the corpus.
• ADR-0005: Four layers and no runtime dependencies. What the structure buys against what arrives next.
• ADR-0006: Storage arrives in stages. Why each store waits for the previous one to fail, and why SQLite rather than DuckDB.
• ADR-0007: The source decides what counts as a sauce. Why the catalogue fell from 166 entries to 124, and why an ambiguous base resolves to nothing.
• ADR-0008: A parent may be any catalogued preparation. Why derived rose from 29 to 50, and which runs of words count as statements.