Faion umbrella

Single entry point for the entire faion knowledge + workflow stack. Auto-invokes on a wide range of triggers — see description above for the full routing surface.

Routing

When invoked, decide what the user needs and read the right entry point:

Signal	Read
Methodology question	L1: `knowledge/domains.xml` → pick ≤3 domains → L2: `knowledge/<domain>/INDEX.xml` → leaf: `knowledge/<tier>/<group>/<name>/AGENTS.md`
"How to do X" — concrete task with steps	L1: `playbooks/taxonomy.xml` (11 goal categories) → L2: `playbooks/by-goal/<goal>/INDEX.xml` → leaf: `playbooks/<goal>/<slug>/AGENTS.md` + `content/01-playbook.xml`
Build / run it, not read about it — "build a research-first product", "run this SDD feature", "write and translate an article", "audit and fix this tree"	L2: `recipes/INDEX.xml` → leaf: `recipes/<name>/<name>.card.md`. Supporting: `fragments/INDEX.xml` (the role prompts a recipe composes) · `tools/INDEX.xml` (scripts to run instead of writing one)
Workflow needed (brainstorm / SDD batch / improver / media pipeline / agent pool)	`workflows/AGENTS.md` to pick + load

A task that names a deliverable and a pipeline to produce it routes to recipes, not into the methodology corpus: a methodology tells you what good looks like, a recipe is the thing that runs.

Methodology layout (v3, post-F-066):