---
type: "synthesis"
tags: ["synthesis", "architecture"]
spans: ["video", "paper"]
id: "synthesis-five-layer-fills-the-gap"
sources: ["cross-day"]
---
# Synthesis: The Five-Layer Hierarchy is the Missing Skeleton

The video ([[concept-icm-d1]]) gestures at folder structure but never names the layers. The paper supplies the explicit primitive — [[concept-five-layer-hierarchy]]:

- **L0** `CLAUDE.md` — global identity (~800 tok)
- **L1** `CONTEXT.md` (root) — workspace routing (~300 tok)
- **L2** `CONTEXT.md` (stage) — stage contract (200–500 tok)
- **L3** `references/` — stable rules (500–2k tok)
- **L4** `output/` — per-run artifacts

## What this resolves

When the video says "build a `voice-and-tone.md`" ([[action-codify-voice]]), the paper tells you **where it goes**: Layer 3, `references/`. When the video says "write a skill," the paper tells you the skill is the **Layer 2 stage contract** ([[concept-stage-contracts]]) plus its `references/` recipe and `output/` ingredients ([[action-separate-l3-l4]]).

## What this enables

The canonical workspace layout ([[framework-icm-architecture]]) becomes legible. The video's [[framework-skill-creation]] (Goal → Constraints → Assumptions → Sub-goals → Markdown) can now be assigned to layers: Goal → L2, Constraints → L3, Assumptions → L3 or L1, Sub-goals → ordered stage folders ([[action-numbered-stage-folders]]).

The **architectural distinction the talk lacks** is L3 (recipe / factory / constraints to internalize) vs L4 (ingredients / product / input to transform). Misclassifying these is the most common failure mode — see [[action-separate-l3-l4]].

See [[synthesis-skill-equals-stage-contract]].