docHub Recipe Book
Per FVW v6 §11, this is the per-app (level 1) Recipe Book for docHub the App.
Files in this folder
| File | Purpose |
|---|---|
recipe.md | Human-readable recipe (what docHub is, what it uses, how to adopt it) |
lineage.json | Machine-readable lineage (faces, chips, modules, decisions) |
codex.md | Final shape of docHub the App |
trace.md | (TBD) History of changes — what's been added/changed/removed and why |
Per-module Recipe Books (level 2)
For each of docHub's 5 modules, a per-module Recipe Book will live at:
mavis/prompts/recipe-book/mavis/decisions/recipe-book/mavis/lanes/recipe-book/mavis/plans/recipe-book/mavis/reports/recipe-book/
These don't exist yet — they need to be created when each module is formalized (currently they're aspirational folders per D-066).
Why a Recipe Book
Per FVW v6 §11.1:
A Recipe Book is the operating manual for a specific app, module, or addon. It records:
- What the scope uses (chips, fragments, modules, names)
- What the scope is by default (base recipe, with no customisations)
- What the scope is in practice (final recipe, with customisations)
- What the scope's shape is (final codex, the Codex entry for this scope)
- Why the scope is the way it is (diffs, the recorded history of changes)
docHub the App:
- Uses: anchor-bar, doc-hub, Tabler icons, FreshCards substrate (cards geometry + CardChipSystem)
- Default recipe: 9 user / 16 dev / 38 mavis files, 3 faces, 5 aspirational modules
- Final recipe: same as default (no customisations yet)
- Codex shape: see
codex.md - History: see
trace.md(TBD)