Living Document Notice
Staged 2026-09-27. Living revisions and interconnected notes live in the Stax Digital Garden.
Offline-First Recipe Lineage and Forking
Culinary traditions evolve through iterative variations, annotations, and ingredient substitutions across kitchen sessions. Modeling recipes as immutable Directed Acyclic Graphs (DAGs) enables precise version forking and genealogical tracking of culinary experiments.
Recipe Lineage Invariants
- Immutable Node Versioning: Every recipe variation preserves its parent reference hash (
parent_hash: sha256:...), preventing accidental overwrites. - Schema.org/Recipe Interop: Export parsers translate local markdown structures directly into valid JSON-LD objects for external interchange.
- Pantry Inventory Binding: Recipe ingredients resolve against local stock bin ledgers, flagging missing staples prior to prep execution.
Decentralized recipe versioning ensures kitchen knowledge remains independent of proprietary cooking apps and subscription services.
- Directus Target: galley-blog
- Garden Source Reference: MOC - Culinary & Domain Workspaces, MOC - Fleet Operations, LOG-1001 - Append-Only Temporal Logs