Design slice: Roadmaps, capability maps and design slices

pack:roadmaps-and-slices-v1

The design as a whole

49 members; 23 example members counted in their parents.
56 relations among members; deepest depth 4; 0 cycles.
1 member held below their stated next rung; 0 waiting only for their author.
43 outside Specs the slice rests on; 0 hold a member; 10 outside Specs rest on it.
12 components touched: 9 through members' code, 7 through what the slice rests on, 0 named by member designs; 2 outside components shown for context.
0 member component designs; 0 realized; 0 of those match.
7 decisions in scope; 0 state below ready.
2 open questions; 1 blocking.

Members read with the ones others rest on first. The columns count the design each member carries beside its rung; they never judge whether it is enough. This page records no review and approves nothing.

How the members rest on each other

Declared relations by depth

Depths are structural, never phases, dates or priority. Dashed relations order nothing. The text keeps every member and original relation.

The diagram as text

spec:protocol.significant-units-review: The engine's accepted set covers its significant abstractions and only those, depth 2, stated ready, floor ready
spec:protocol.role-vocabulary: The engine's architectural roles each name one pattern, depth 1, stated ready, floor ready
spec:consumers.spec-studio.lenses.architecture.unit-register: The architecture page lists each component's significant units by role, depth 1, stated ready, floor ready
spec:consumers.capability-map: The capability map reads every epic and its refinement descendants, depth 2, stated ready, floor ready
spec:decisions.epics-of-any-kind: Capability epics keep kind independent of altitude, depth 1, stated ready, floor ready
spec:protocol.capability-epics: The Protocol organizes its own features in capability epics, depth 3, stated ready, floor ready
spec:extraction.executable-examples: Bound examples execute their authored steps, depth 1, stated ready, floor ready
spec:consumers.spec-studio.capability-map-page: The capability map page makes refinement readable by epic, depth 3, stated ready, floor ready
spec:consumers.spec-studio.diagram-kinds: The Studio chooses diagram kinds from graph values, depth 1, stated ready, floor ready
spec:consumers.spec-studio.diagram-kinds.legibility: A diagram preserves readable labels before zoom, depth 2, stated ready, floor ready
spec:consumers.spec-studio.diagram-kinds.edge-routing: Edges route around boxes with deterministic orthogonal paths, depth 2, stated ready, floor ready
spec:consumers.spec-studio.diagram-kinds.mermaid-source: A diagram offers Mermaid source as copyable text, depth 2, stated ready, floor ready
spec:consumers.spec-studio.diagram-kinds.dependency: A dependency drawing shows the declared footing of a Spec set, depth 2, stated ready, floor ready
spec:consumers.spec-studio.diagram-kinds.capability-tree: A refinement drawing follows the capability map, depth 3, stated ready, floor ready
spec:consumers.spec-studio.diagram-kinds.scoped-architecture: A Spec set draws the architecture it touches, depth 2, stated ready, floor ready
spec:consumers.spec-studio.diagram-kinds.maturity-picture: The maturity map is drawn as a grid of counts, depth 2, stated ready, floor ready
spec:consumers.spec-studio.diagram-kinds.requirement-trace: A requirement drawing separates intent from realization and verification, depth 2, stated ready, floor ready
spec:consumers.design-slice: A slice reads a Pack as one design, with the architecture it touches and what each member needs next, depth 1, stated ready, floor ready
spec:consumers.design-slice.outside-components: Outside components stop at the touched components' neighbors, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.chain: Members rest on a chain, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.decision-backlink: A shaping decision comes before its member, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.dependency-cycle: A cycle shares a depth, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.folded-example: An example folds without lending its readiness, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.independent-example: An example with its own dependency stays unfolded, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.component-absent: An unanchored component design stays visible, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.component-unrelated: An anchor alone does not realize a component design, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.component-matching: A realized component matches its declared values, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.component-differing: A realized component keeps its differing layer and uses apart, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.component-unreadable: An unreadable declared layer stays visible, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.outside-satisfied: A prerequisite reaches its satisfying component, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.outside-unbound: An unbound prerequisite invents no component, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.design-slice.outside-holding: An outside prerequisite names the member it holds, depth 2, stated ready, floor ready; example folded into spec:consumers.design-slice
spec:consumers.spec-studio.slice-page: A slice page shows a Pack's design as one whole, depth 3, stated ready, floor ready
spec:decisions.roadmap-priority: A roadmap states advisory priority in the graph, depth 1, stated ready, floor ready
spec:consumers.roadmap: A roadmap orders the next bodies of work, and the graph says what each still needs, depth 2, stated ready, floor ready
spec:consumers.roadmap.built-work: Built work stays on the roadmap, depth 3, stated ready, floor ready; example folded into spec:consumers.roadmap
spec:consumers.roadmap.buildable-part: A ready unbound part needs building, depth 3, stated ready, floor ready; example folded into spec:consumers.roadmap
spec:consumers.roadmap.statement-part: A complete part waits for a statement, depth 3, stated ready, floor ready; example folded into spec:consumers.roadmap
spec:consumers.roadmap.design-part: An unfinished part needs design, depth 3, stated ready, floor ready; example folded into spec:consumers.roadmap
spec:consumers.roadmap.drifting-part: A binding below ready remains drift, depth 3, stated ready, floor ready; example folded into spec:consumers.roadmap
spec:consumers.roadmap.missing-evidence: A descendant without evidence names its holding clause, depth 3, stated ready, floor ready; example folded into spec:consumers.roadmap
spec:consumers.roadmap.blocking-part: A descendant question holds the entry for design, depth 3, stated ready, floor ready; example folded into spec:consumers.roadmap
spec:consumers.roadmap.outside-parent: A descendant names its outside parent, depth 3, stated ready, floor ready; example folded into spec:consumers.roadmap
spec:consumers.roadmap.statement-order: Waiting statements keep dependency order against roadmap places, depth 3, stated ready, floor ready; example folded into spec:consumers.roadmap
spec:consumers.spec-studio.roadmap-page: The roadmap page shows the upcoming work in priority order, split by what it needs, depth 4, stated ready, floor ready
spec:consumers.roadmap.memo: A roadmap renders as the forward section of a pull request description, depth 3, stated ready, floor ready
spec:decisions.roadmap-over-plans: Plan and review files stop carrying the delivery record once the roadmap and the pull request do, depth 2, stated ready, floor ready
spec:protocol.roadmap-replaces-plans: The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests, depth 4, stated ready, floor ready
spec:consumers.projections-model.roadmap-views: Roadmap views read releases, baselines and phases from git and the graph, depth 3, stated scoped, floor scoped
Outside this scope: spec:consumers.agent-surface.design-recipes: Design work reads its answers from catalog recipes, stated ready, floor ready
Outside this scope: spec:consumers.agent-surface.register-recipes: Register questions stay executable graph recipes, stated ready, floor ready
Outside this scope: spec:consumers.binding-language-views: Views speak binding language, never the internal fact name, stated ready, floor ready
Outside this scope: spec:consumers.context-bundle: A context bundle is composed per invocation within a stated budget, stated ready, floor ready
Outside this scope: spec:consumers.derived-readiness-banner: Derived readiness renders beside the stated rung and warns in one direction, stated ready, floor ready
Outside this scope: spec:consumers.graph-first-planning: The next body of work is planned from the graph, not from a prose index, stated ready, floor ready
Outside this scope: spec:consumers.intent-composition.proposal: A change proposal is addressed, based and checked before it lands, stated ready, floor ready
Outside this scope: spec:consumers.intent-composition.proposal.memo: Recipe 49 renders a change proposal as the Markdown memo a person reviews, stated ready, floor ready
Outside this scope: spec:consumers.pack-design: The Pack context carries the Pack's design, stated ready, floor ready
Outside this scope: spec:consumers.projections-model: Projections fan out from one graph without becoming truth stores, stated ready, floor ready
Outside this scope: spec:consumers.readiness-planner: The readiness planner orders the statements a person can make, stated ready, floor ready
Outside this scope: spec:consumers.review-perspectives: A Pack is read from a named perspective, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio: The Spec Studio is a static HTML workbench over the one graph, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio.data: The Studio renders from the reader's values and embeds only what its script reads, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio.data.recipe-answers: A page takes each recipe answer from the recipe's shipped body, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio.diagrams: A diagram is laid out from graph values into SVG with a text equivalent, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio.index-page: The index says where the corpus stands and narrows every Spec, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio.lenses: Five lenses read the graph as Packs, capabilities, architecture, tests and evidence, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio.lenses.architecture: The architecture lens draws components by context and layer, the planned beside the built, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio.pack-page: A Pack page shows the Pack's design as one card per member, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio.page-elements: A few custom elements filter, search, open and copy on a rendered page, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio.publisher: sdp studio publishes the Studio as one page set, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio.responsive: The Studio reads on a phone as on a desktop, stated ready, floor ready
Outside this scope: spec:consumers.spec-studio.shell: The Studio's shell frames every page with navigation, a rail and a canvas, stated ready, floor ready
Outside this scope: spec:decisions.anchor-binding-grain: Bindings are optional, plural, and may reference a design, stated ready, floor ready
Outside this scope: spec:decisions.architectural-annotation: Architectural significance is annotated where it is realized, stated ready, floor ready
Outside this scope: spec:decisions.one-primitive: One Spec carries named delivery coordinates, stated ready, floor ready
Outside this scope: spec:decisions.pack-markdown-carrier: Packs have a Markdown manifest carrier, stated ready, floor ready
Outside this scope: spec:decisions.planning-truths-placement: Planning truths live in ruled graph homes, stated ready, floor ready
Outside this scope: spec:decisions.shipped-projections-frozen: The shipped projections stay frozen, stated ready, floor ready
Outside this scope: spec:decisions.studio-diagram-renderer: The engine lays out every Studio diagram as static SVG when the page set is built, stated ready, floor ready
Outside this scope: spec:extraction.delivery-facts: Resolving bindings confer direct delivery facts, stated ready, floor ready
Outside this scope: spec:extraction.derive-graph: Carrier reification derives the one graph, stated ready, floor ready
Outside this scope: spec:model.open-question-fields: An open question may name who decides it, its links, a provisional reading and a re-entry trigger, stated ready, floor ready
Outside this scope: spec:model.planned-architecture: Components are designed ahead of their code, stated ready, floor ready
Outside this scope: spec:model.rule-keys: A rule or flow entry may carry a key that addresses it, stated ready, floor ready
Outside this scope: spec:model.structural-patterns: Architecturally significant units are annotated where they are realized, stated ready, floor ready
Outside this scope: spec:observation.run-evidence: CI run records are joined to verifiers in a view, stated ready, floor ready
Outside this scope: spec:protocol.self-hosting: The Protocol authors and validates itself, stated ready, floor ready
Outside this scope: spec:protocol.structural-self-binding: The engine's structural self-binding covers its architecturally significant units, stated ready, floor ready
Outside this scope: spec:validation.next-rung-floor: The floor names what blocks the floor's next rung, stated ready, floor ready
Outside this scope: spec:validation.readiness-floor: Stated readiness must clear its floor, stated ready, floor ready
Outside this scope: spec:validation.typed-dependency-floor: A ready Spec rests only on settled dependencies, stated ready, floor ready
spec:consumers.capability-map decidedBy spec:decisions.epics-of-any-kind · declared
spec:consumers.design-slice.chain refines spec:consumers.design-slice · declared
spec:consumers.design-slice.component-absent refines spec:consumers.design-slice · declared
spec:consumers.design-slice.component-differing refines spec:consumers.design-slice · declared
spec:consumers.design-slice.component-matching refines spec:consumers.design-slice · declared
spec:consumers.design-slice.component-unreadable refines spec:consumers.design-slice · declared
spec:consumers.design-slice.component-unrelated refines spec:consumers.design-slice · declared
spec:consumers.design-slice.decision-backlink refines spec:consumers.design-slice · declared
spec:consumers.design-slice.dependency-cycle refines spec:consumers.design-slice · declared
spec:consumers.design-slice.folded-example refines spec:consumers.design-slice · declared
spec:consumers.design-slice.independent-example refines spec:consumers.design-slice · declared
spec:consumers.design-slice.outside-components refines spec:consumers.design-slice · declared
spec:consumers.design-slice.outside-holding refines spec:consumers.design-slice · declared
spec:consumers.design-slice.outside-satisfied refines spec:consumers.design-slice · declared
spec:consumers.design-slice.outside-unbound refines spec:consumers.design-slice · declared
spec:consumers.projections-model.roadmap-views dependsOn spec:consumers.roadmap · declared — the roadmap view the owner asked for is the roadmap reading, its page and its memo
spec:consumers.roadmap decidedBy spec:decisions.roadmap-priority · declared
spec:consumers.roadmap.blocking-part refines spec:consumers.roadmap · declared
spec:consumers.roadmap.buildable-part refines spec:consumers.roadmap · declared
spec:consumers.roadmap.built-work refines spec:consumers.roadmap · declared
spec:consumers.roadmap.design-part refines spec:consumers.roadmap · declared
spec:consumers.roadmap.drifting-part refines spec:consumers.roadmap · declared
spec:consumers.roadmap.memo refines spec:consumers.roadmap · declared
spec:consumers.roadmap.missing-evidence refines spec:consumers.roadmap · declared
spec:consumers.roadmap.outside-parent refines spec:consumers.roadmap · declared
spec:consumers.roadmap.statement-order refines spec:consumers.roadmap · declared
spec:consumers.roadmap.statement-part refines spec:consumers.roadmap · declared
spec:consumers.spec-studio.capability-map-page dependsOn spec:consumers.capability-map · declared — the page and index filter render the capability map's answer
spec:consumers.spec-studio.capability-map-page dependsOn spec:consumers.spec-studio.diagram-kinds · declared — the refinement drawing shares the Studio's diagram layout and accessible text contract
spec:consumers.spec-studio.capability-map-page refines spec:consumers.capability-map · declared — the page is the capability map's reading for a person
spec:consumers.spec-studio.diagram-kinds.capability-tree dependsOn spec:consumers.capability-map · declared
spec:consumers.spec-studio.diagram-kinds.capability-tree refines spec:consumers.spec-studio.diagram-kinds · declared
spec:consumers.spec-studio.diagram-kinds.dependency dependsOn spec:consumers.design-slice · declared
spec:consumers.spec-studio.diagram-kinds.dependency refines spec:consumers.spec-studio.diagram-kinds · declared
spec:consumers.spec-studio.diagram-kinds.edge-routing refines spec:consumers.spec-studio.diagram-kinds · declared — arrows that cover no label serve the readable drawings the diagram kinds state
spec:consumers.spec-studio.diagram-kinds.legibility refines spec:consumers.spec-studio.diagram-kinds · declared — readable labels are part of the outcome the diagram kinds state
spec:consumers.spec-studio.diagram-kinds.maturity-picture refines spec:consumers.spec-studio.diagram-kinds · declared
spec:consumers.spec-studio.diagram-kinds.mermaid-source refines spec:consumers.spec-studio.diagram-kinds · declared
spec:consumers.spec-studio.diagram-kinds.requirement-trace refines spec:consumers.spec-studio.diagram-kinds · declared
spec:consumers.spec-studio.diagram-kinds.scoped-architecture dependsOn spec:consumers.design-slice · declared
spec:consumers.spec-studio.diagram-kinds.scoped-architecture refines spec:consumers.spec-studio.diagram-kinds · declared
spec:consumers.spec-studio.roadmap-page dependsOn spec:consumers.roadmap · declared — the page renders the roadmap reading
spec:consumers.spec-studio.roadmap-page dependsOn spec:consumers.roadmap.memo · declared — the page carries the roadmap memo for a description's author to copy
spec:consumers.spec-studio.roadmap-page refines spec:consumers.roadmap · declared — the page is the roadmap's reading for a person
spec:consumers.spec-studio.slice-page dependsOn spec:consumers.design-slice · declared — the page renders the slice's answer
spec:consumers.spec-studio.slice-page dependsOn spec:consumers.spec-studio.diagram-kinds.dependency · declared — the dependency drawing given the slice's order is a drawing kind, which owns layout, folding and the text equivalent
spec:consumers.spec-studio.slice-page dependsOn spec:consumers.spec-studio.diagram-kinds.scoped-architecture · declared — the scoped architecture drawing is a drawing kind, which owns layout, folding and the text equivalent
spec:consumers.spec-studio.slice-page refines spec:consumers.design-slice · declared — the page is the design slice's reading for a person
spec:decisions.epics-of-any-kind refines spec:consumers.capability-map · declared, orders nothing — settles which Specs the capability map reads as epics
spec:decisions.roadmap-over-plans dependsOn spec:decisions.roadmap-priority · declared — plan files give up forward planning only once a roadmap holds priority in the graph
spec:protocol.capability-epics decidedBy spec:decisions.epics-of-any-kind · declared
spec:protocol.capability-epics dependsOn spec:consumers.capability-map · declared — the capability map exposes the corpus's authored refinement
spec:protocol.roadmap-replaces-plans decidedBy spec:decisions.roadmap-over-plans · declared
spec:protocol.roadmap-replaces-plans dependsOn spec:consumers.roadmap · declared — the Protocol reads its own next work from its roadmap
spec:protocol.roadmap-replaces-plans dependsOn spec:consumers.roadmap.memo · declared — each description's forward section is the roadmap memo
spec:protocol.significant-units-review dependsOn spec:protocol.role-vocabulary · declared
spec:consumers.design-slice dependsOn spec:consumers.agent-surface.design-recipes · declared — decisions in scope read the decision register's rows
spec:consumers.roadmap.memo dependsOn spec:consumers.agent-surface.register-recipes · declared — the deferred items come from the open-question register
spec:consumers.spec-studio.capability-map-page dependsOn spec:consumers.binding-language-views · declared — aggregate rows use the same binding labels as Spec pages
spec:consumers.spec-studio.slice-page dependsOn spec:consumers.binding-language-views · declared
spec:consumers.design-slice dependsOn spec:consumers.context-bundle · declared — a slice takes its scope as the bundle does, and builds a Spec list's boundary the same way
spec:consumers.spec-studio.slice-page dependsOn spec:consumers.derived-readiness-banner · declared
spec:consumers.roadmap refines spec:consumers.graph-first-planning · declared — a roadmap is advisory reading of the graph for choosing the next work
spec:protocol.roadmap-replaces-plans dependsOn spec:consumers.intent-composition.proposal · declared — a review's findings against Specs travel as a checked change proposal
spec:consumers.roadmap.memo dependsOn spec:consumers.intent-composition.proposal.memo · declared — the memo writes its code spans by the proposal memo's markup rules
spec:protocol.roadmap-replaces-plans dependsOn spec:consumers.intent-composition.proposal.memo · declared — the pull request carries a review's proposal as its memo
spec:consumers.design-slice refines spec:consumers.pack-design · declared — a slice reads a Pack's design as one whole, with its architecture and open decisions beside it
spec:consumers.capability-map refines spec:consumers.projections-model · declared — the capability map projects authored refinement without introducing a grouping
spec:consumers.projections-model.roadmap-views refines spec:consumers.projections-model · declared
spec:consumers.design-slice dependsOn spec:consumers.readiness-planner · declared — members rest on each other as the statement queue reads the four typed relations, and a cycle reports in its shape
spec:consumers.roadmap dependsOn spec:consumers.readiness-planner · declared — the statements waiting on a person follow the statement queue's order
spec:consumers.design-slice dependsOn spec:consumers.review-perspectives · declared — a slice read for one concern takes the members a perspective selects
spec:consumers.spec-studio.slice-page refines spec:consumers.spec-studio · declared
spec:consumers.spec-studio.roadmap-page refines spec:consumers.spec-studio · declared
spec:consumers.spec-studio.diagram-kinds.requirement-trace dependsOn spec:consumers.spec-studio.data · declared
spec:consumers.spec-studio.roadmap-page dependsOn spec:consumers.spec-studio.data · declared
spec:consumers.spec-studio.slice-page dependsOn spec:consumers.spec-studio.data.recipe-answers · declared — the build evaluates the slice recipe once for each Pack, and the page reads that answer
spec:consumers.spec-studio.diagram-kinds refines spec:consumers.spec-studio.diagrams · declared
spec:consumers.spec-studio.diagram-kinds.legibility refines spec:consumers.spec-studio.diagrams · declared
spec:consumers.spec-studio.diagram-kinds.edge-routing refines spec:consumers.spec-studio.diagrams · declared
spec:consumers.spec-studio.slice-page dependsOn spec:consumers.spec-studio.diagrams · declared — both drawings keep the diagram contract, bound and text equivalent included
spec:consumers.spec-studio.capability-map-page dependsOn spec:consumers.spec-studio.index-page · declared — the Epic filter extends the index's Specs filters
spec:consumers.spec-studio.capability-map-page refines spec:consumers.spec-studio.lenses · declared — the Capabilities page is a lens that reads refinement
spec:consumers.spec-studio.lenses.architecture.unit-register refines spec:consumers.spec-studio.lenses.architecture · declared
spec:consumers.spec-studio.diagram-kinds.scoped-architecture dependsOn spec:consumers.spec-studio.lenses.architecture · declared
spec:consumers.spec-studio.slice-page dependsOn spec:consumers.spec-studio.pack-page · declared — each member links to its card on the Pack page, whose element id is the member's id
spec:consumers.spec-studio.diagram-kinds.mermaid-source dependsOn spec:consumers.spec-studio.page-elements · declared
spec:consumers.spec-studio.roadmap-page dependsOn spec:consumers.spec-studio.publisher · declared — an entry's element id carries the name the page set gives its roadmap's Pack page
spec:consumers.spec-studio.diagram-kinds.legibility dependsOn spec:consumers.spec-studio.responsive · declared
spec:consumers.spec-studio.roadmap-page dependsOn spec:consumers.spec-studio.shell · declared
spec:protocol.significant-units-review decidedBy spec:decisions.anchor-binding-grain · declared
spec:consumers.design-slice decidedBy spec:decisions.anchor-binding-grain · declared — the code a design builds on is reached through the design's own relations, never through a reference from that code
spec:protocol.significant-units-review decidedBy spec:decisions.architectural-annotation · declared
spec:protocol.role-vocabulary decidedBy spec:decisions.architectural-annotation · declared
spec:consumers.design-slice decidedBy spec:decisions.architectural-annotation · declared — a touched component carries the layer and context its anchor states
spec:decisions.epics-of-any-kind dependsOn spec:decisions.one-primitive · declared — kind and altitude are independent named coordinates on the one primitive
spec:decisions.roadmap-priority refines spec:decisions.pack-markdown-carrier · declared — opens the closed Pack manifest envelope to one optional field, `order`
spec:decisions.roadmap-priority refines spec:decisions.planning-truths-placement · declared — narrows the refusal of recorded work order for one case, the advisory priority of a roadmap
spec:decisions.roadmap-over-plans refines spec:decisions.planning-truths-placement · declared — narrows what a plan file may still carry once a roadmap holds priority
spec:consumers.spec-studio.diagram-kinds.mermaid-source decidedBy spec:decisions.shipped-projections-frozen · declared
spec:consumers.spec-studio.diagram-kinds decidedBy spec:decisions.studio-diagram-renderer · declared — every new kind is laid out by the engine at build time as the renderer decision rules
spec:consumers.spec-studio.diagram-kinds.mermaid-source decidedBy spec:decisions.studio-diagram-renderer · declared
spec:consumers.capability-map dependsOn spec:extraction.delivery-facts · declared — rollups count direct bindings without conferring facts on ancestors
spec:extraction.executable-examples dependsOn spec:extraction.derive-graph · declared — executable contracts read the one graph rather than another carrier path
spec:consumers.design-slice dependsOn spec:model.open-question-fields · declared — each question in scope carries its fields
spec:consumers.spec-studio.slice-page dependsOn spec:model.open-question-fields · declared
spec:consumers.roadmap dependsOn spec:model.open-question-fields · declared — the questions waiting on a person are selected by their decider field
spec:consumers.spec-studio.diagram-kinds.scoped-architecture dependsOn spec:model.planned-architecture · declared
spec:consumers.design-slice dependsOn spec:model.planned-architecture · declared — planned components and differing designs come from the realization comparison
spec:consumers.design-slice dependsOn spec:model.rule-keys · declared — each member's rule count is the count rule coverage reports
spec:protocol.significant-units-review dependsOn spec:model.structural-patterns · declared
spec:protocol.roadmap-replaces-plans dependsOn spec:observation.run-evidence · declared — an arc's acceptance reads run records as evidence from test files at their recorded commit
spec:protocol.capability-epics refines spec:protocol.self-hosting · declared
spec:protocol.roadmap-replaces-plans refines spec:protocol.self-hosting · declared
spec:protocol.significant-units-review refines spec:protocol.structural-self-binding · declared — states what the independently reviewed accepted set must contain and exclude
spec:protocol.role-vocabulary refines spec:protocol.structural-self-binding · declared — names what each role value the engine's significant units carry means
spec:consumers.roadmap dependsOn spec:validation.next-rung-floor · declared — an entry's stated next rung and the clauses that hold it come from the one floor evaluator
spec:consumers.capability-map dependsOn spec:validation.readiness-floor · declared — each node reads the existing floor beside the author's statement
spec:protocol.capability-epics dependsOn spec:validation.readiness-floor · declared — reparenting preserves the floor of each existing ready child
spec:consumers.roadmap dependsOn spec:validation.typed-dependency-floor · declared — what an entry rests on is read through the relations the ready floor reads

Mermaid source

Copyable source; the Studio draws static SVG. See the full text equivalent for every original relation and folded member.

Preferred syntax: flowchart. Chosen syntax: labelled flowchart, preserving exact relations, claims and folds.

Mermaid source for Declared relations by depth

flowchart TB
  subgraph depth0["Depth 4"]
    n0["2 members at depth 4, folded"]
  end
  subgraph depth1["Depth 3"]
    n1["6 members at depth 3, folded"]
  end
  subgraph depth2["Depth 2"]
    n2["11 members at depth 2, folded"]
  end
  subgraph depth3["Depth 1"]
    n3["7 members at depth 1, folded"]
  end
  subgraph depth4["Outside this scope"]
    n4["30 outside Specs, dependsOn, folded"]
    n5["11 outside Specs, refines, folded"]
    n6["4 outside Specs, decidedBy, folded"]
  end
  %% folded diagram.pack:roadmaps-and-slices-v1.dependencies.fold.4: spec:consumers.spec-studio.roadmap-page, spec:protocol.roadmap-replaces-plans
  %% folded diagram.pack:roadmaps-and-slices-v1.dependencies.fold.3: spec:protocol.capability-epics, spec:consumers.spec-studio.capability-map-page, spec:consumers.spec-studio.diagram-kinds.capability-tree, spec:consumers.spec-studio.slice-page, spec:consumers.roadmap.memo, spec:consumers.projections-model.roadmap-views
  %% folded diagram.pack:roadmaps-and-slices-v1.dependencies.fold.2: spec:protocol.significant-units-review, spec:consumers.capability-map, spec:consumers.spec-studio.diagram-kinds.legibility, spec:consumers.spec-studio.diagram-kinds.edge-routing, spec:consumers.spec-studio.diagram-kinds.mermaid-source, spec:consumers.spec-studio.diagram-kinds.dependency, spec:consumers.spec-studio.diagram-kinds.scoped-architecture, spec:consumers.spec-studio.diagram-kinds.maturity-picture, spec:consumers.spec-studio.diagram-kinds.requirement-trace, spec:consumers.roadmap, spec:decisions.roadmap-over-plans
  %% folded diagram.pack:roadmaps-and-slices-v1.dependencies.fold.1: spec:protocol.role-vocabulary, spec:consumers.spec-studio.lenses.architecture.unit-register, spec:decisions.epics-of-any-kind, spec:extraction.executable-examples, spec:consumers.spec-studio.diagram-kinds, spec:consumers.design-slice, spec:decisions.roadmap-priority
  %% folded diagram.pack:roadmaps-and-slices-v1.dependencies.outside.dependsOn: spec:consumers.agent-surface.design-recipes, spec:consumers.agent-surface.register-recipes, spec:consumers.binding-language-views, spec:consumers.context-bundle, spec:consumers.derived-readiness-banner, spec:consumers.intent-composition.proposal, spec:consumers.intent-composition.proposal.memo, spec:consumers.readiness-planner, spec:consumers.review-perspectives, spec:consumers.spec-studio.data, spec:consumers.spec-studio.data.recipe-answers, spec:consumers.spec-studio.diagrams, spec:consumers.spec-studio.index-page, spec:consumers.spec-studio.lenses.architecture, spec:consumers.spec-studio.pack-page, spec:consumers.spec-studio.page-elements, spec:consumers.spec-studio.publisher, spec:consumers.spec-studio.responsive, spec:consumers.spec-studio.shell, spec:decisions.one-primitive, spec:extraction.delivery-facts, spec:extraction.derive-graph, spec:model.open-question-fields, spec:model.planned-architecture, spec:model.rule-keys, spec:model.structural-patterns, spec:observation.run-evidence, spec:validation.next-rung-floor, spec:validation.readiness-floor, spec:validation.typed-dependency-floor
  %% folded diagram.pack:roadmaps-and-slices-v1.dependencies.outside.refines: spec:consumers.graph-first-planning, spec:consumers.pack-design, spec:consumers.projections-model, spec:consumers.spec-studio, spec:consumers.spec-studio.diagrams, spec:consumers.spec-studio.lenses, spec:consumers.spec-studio.lenses.architecture, spec:decisions.pack-markdown-carrier, spec:decisions.planning-truths-placement, spec:protocol.self-hosting, spec:protocol.structural-self-binding
  %% folded diagram.pack:roadmaps-and-slices-v1.dependencies.outside.decidedBy: spec:decisions.anchor-binding-grain, spec:decisions.architectural-annotation, spec:decisions.shipped-projections-frozen, spec:decisions.studio-diagram-renderer
  n3 -.->|"refines (orders nothing) · declared — settles which Specs the capability map reads as epics"| n2
  %% count: 1; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.1 to diagram.pack:roadmaps-and-slices-v1.dependencies.fold.2
  n3 -->|"decidedBy · declared (4 relations)"| n6
  %% count: 4; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.1 to diagram.pack:roadmaps-and-slices-v1.dependencies.outside.decidedBy
  n3 -->|"dependsOn · declared (9 relations)"| n4
  %% count: 9; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.1 to diagram.pack:roadmaps-and-slices-v1.dependencies.outside.dependsOn
  n3 -->|"refines · declared (6 relations)"| n5
  %% count: 6; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.1 to diagram.pack:roadmaps-and-slices-v1.dependencies.outside.refines
  n2 -->|"decidedBy (2), dependsOn (4), refines (7) · declared"| n3
  n2 -->|"decidedBy · declared (4 relations)"| n6
  %% count: 4; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.2 to diagram.pack:roadmaps-and-slices-v1.dependencies.outside.decidedBy
  n2 -->|"dependsOn · declared (12 relations)"| n4
  %% count: 12; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.2 to diagram.pack:roadmaps-and-slices-v1.dependencies.outside.dependsOn
  n2 -->|"refines · declared (6 relations)"| n5
  %% count: 6; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.2 to diagram.pack:roadmaps-and-slices-v1.dependencies.outside.refines
  n1 -->|"decidedBy, dependsOn (2), refines (2) · declared"| n3
  n1 -->|"dependsOn (6), refines (2) · declared"| n2
  n1 -->|"dependsOn · declared (11 relations)"| n4
  %% count: 11; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.3 to diagram.pack:roadmaps-and-slices-v1.dependencies.outside.dependsOn
  n1 -->|"refines · declared (4 relations)"| n5
  %% count: 4; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.3 to diagram.pack:roadmaps-and-slices-v1.dependencies.outside.refines
  n0 -->|"decidedBy, dependsOn (2), refines · declared"| n2
  n0 -->|"dependsOn · declared (2 relations)"| n1
  %% count: 2; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.4 to diagram.pack:roadmaps-and-slices-v1.dependencies.fold.3
  n0 -->|"dependsOn · declared (6 relations)"| n4
  %% count: 6; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.4 to diagram.pack:roadmaps-and-slices-v1.dependencies.outside.dependsOn
  n0 -->|"refines · declared (2 relations)"| n5
  %% count: 2; diagram.pack:roadmaps-and-slices-v1.dependencies.fold.4 to diagram.pack:roadmaps-and-slices-v1.dependencies.outside.refines

What each member needs next

Member	Depth	Rung	Next rung	Design carried	Code
The engine's architectural roles each name one pattern `spec:protocol.role-vocabulary` model	1	ready floor ready		0 rules5 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound	1 implementing0 referencing
The architecture page lists each component's significant units by role `spec:consumers.spec-studio.lenses.architecture.unit-register` behavior	1	ready floor ready		5 rules, 5 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound	1 implementing0 referencing
Capability epics keep kind independent of altitude `spec:decisions.epics-of-any-kind` decision	1	ready floor ready		0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound	0 implementing1 referencing
Bound examples execute their authored steps `spec:extraction.executable-examples` behavior	1	ready floor ready		4 rules, 4 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound	6 implementing0 referencing
The Studio chooses diagram kinds from graph values `spec:consumers.spec-studio.diagram-kinds` behavior	1	ready floor ready		5 rules, 5 keyed37 entries1 declarations0 questions1 decisions0 of 0 verifying examples bound	9 implementing0 referencing
A slice reads a Pack as one design, with the architecture it touches and what each member needs next `spec:consumers.design-slice` behavior	1	ready floor ready		18 rules, 18 keyed18 entries15 declarations0 questions2 decisions14 of 14 verifying examples bound	1 implementing1 referencing
14 example members folded in Outside components stop at the touched components' neighbors `spec:consumers.design-slice.outside-components` example · ready floor ready Members rest on a chain `spec:consumers.design-slice.chain` example · ready floor ready A shaping decision comes before its member `spec:consumers.design-slice.decision-backlink` example · ready floor ready A cycle shares a depth `spec:consumers.design-slice.dependency-cycle` example · ready floor ready An example folds without lending its readiness `spec:consumers.design-slice.folded-example` example · ready floor ready An example with its own dependency stays unfolded `spec:consumers.design-slice.independent-example` example · ready floor ready An unanchored component design stays visible `spec:consumers.design-slice.component-absent` example · ready floor ready An anchor alone does not realize a component design `spec:consumers.design-slice.component-unrelated` example · ready floor ready A realized component matches its declared values `spec:consumers.design-slice.component-matching` example · ready floor ready A realized component keeps its differing layer and uses apart `spec:consumers.design-slice.component-differing` example · ready floor ready An unreadable declared layer stays visible `spec:consumers.design-slice.component-unreadable` example · ready floor ready A prerequisite reaches its satisfying component `spec:consumers.design-slice.outside-satisfied` example · ready floor ready An unbound prerequisite invents no component `spec:consumers.design-slice.outside-unbound` example · ready floor ready An outside prerequisite names the member it holds `spec:consumers.design-slice.outside-holding` example · ready floor ready
A roadmap states advisory priority in the graph `spec:decisions.roadmap-priority` decision	1	ready floor ready		0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound	0 implementing2 referencing
The engine's accepted set covers its significant abstractions and only those `spec:protocol.significant-units-review` behavior	2	ready floor ready		7 rules, 7 keyed1 entries0 declarations0 questions2 decisions0 of 0 verifying examples bound	1 implementing0 referencing
The capability map reads every epic and its refinement descendants `spec:consumers.capability-map` behavior	2	ready floor ready		9 rules, 9 keyed10 entries4 declarations0 questions1 decisions0 of 0 verifying examples bound	1 implementing0 referencing
A diagram preserves readable labels before zoom `spec:consumers.spec-studio.diagram-kinds.legibility` contract	2	ready floor ready		2 rules, 2 keyed6 entries3 declarations0 questions0 decisions0 of 0 verifying examples bound	3 implementing0 referencing
Edges route around boxes with deterministic orthogonal paths `spec:consumers.spec-studio.diagram-kinds.edge-routing` contract	2	ready floor ready		5 rules, 5 keyed6 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound	2 implementing0 referencing
A diagram offers Mermaid source as copyable text `spec:consumers.spec-studio.diagram-kinds.mermaid-source` behavior	2	ready floor ready		5 rules, 5 keyed6 entries0 declarations0 questions2 decisions0 of 0 verifying examples bound	2 implementing0 referencing
A dependency drawing shows the declared footing of a Spec set `spec:consumers.spec-studio.diagram-kinds.dependency` behavior	2	ready floor ready		5 rules, 5 keyed6 entries2 declarations0 questions0 decisions0 of 0 verifying examples bound	1 implementing0 referencing
A Spec set draws the architecture it touches `spec:consumers.spec-studio.diagram-kinds.scoped-architecture` behavior	2	ready floor ready		4 rules, 4 keyed5 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound	1 implementing0 referencing
The maturity map is drawn as a grid of counts `spec:consumers.spec-studio.diagram-kinds.maturity-picture` behavior	2	ready floor ready		4 rules, 4 keyed6 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound	1 implementing0 referencing
A requirement drawing separates intent from realization and verification `spec:consumers.spec-studio.diagram-kinds.requirement-trace` behavior	2	ready floor ready		3 rules, 3 keyed8 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound	2 implementing0 referencing
A roadmap orders the next bodies of work, and the graph says what each still needs `spec:consumers.roadmap` behavior	2	ready floor ready		17 rules, 17 keyed13 entries10 declarations0 questions1 decisions9 of 9 verifying examples bound	1 implementing0 referencing
9 example members folded in Built work stays on the roadmap `spec:consumers.roadmap.built-work` example · ready floor ready A ready unbound part needs building `spec:consumers.roadmap.buildable-part` example · ready floor ready A complete part waits for a statement `spec:consumers.roadmap.statement-part` example · ready floor ready An unfinished part needs design `spec:consumers.roadmap.design-part` example · ready floor ready A binding below ready remains drift `spec:consumers.roadmap.drifting-part` example · ready floor ready A descendant without evidence names its holding clause `spec:consumers.roadmap.missing-evidence` example · ready floor ready A descendant question holds the entry for design `spec:consumers.roadmap.blocking-part` example · ready floor ready A descendant names its outside parent `spec:consumers.roadmap.outside-parent` example · ready floor ready Waiting statements keep dependency order against roadmap places `spec:consumers.roadmap.statement-order` example · ready floor ready
Plan and review files stop carrying the delivery record once the roadmap and the pull request do `spec:decisions.roadmap-over-plans` decision	2	ready floor ready		0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound	0 implementing0 referencing
The Protocol organizes its own features in capability epics `spec:protocol.capability-epics` behavior	3	ready floor ready		4 rules, 4 keyed5 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound	1 implementing0 referencing
The capability map page makes refinement readable by epic `spec:consumers.spec-studio.capability-map-page` behavior	3	ready floor ready		8 rules, 8 keyed6 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound	4 implementing0 referencing
A refinement drawing follows the capability map `spec:consumers.spec-studio.diagram-kinds.capability-tree` behavior	3	ready floor ready		3 rules, 3 keyed5 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound	2 implementing0 referencing
A slice page shows a Pack's design as one whole `spec:consumers.spec-studio.slice-page` behavior	3	ready floor ready		17 rules, 17 keyed12 entries0 declarations1 questions0 decisions0 of 0 verifying examples bound	1 implementing0 referencing
A roadmap renders as the forward section of a pull request description `spec:consumers.roadmap.memo` behavior	3	ready floor ready		7 rules, 7 keyed11 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound	2 implementing0 referencing
Roadmap views read releases, baselines and phases from git and the graph `spec:consumers.projections-model.roadmap-views` model	3	scoped floor scoped	next defined: `no-blocking-open-questions` · Spec has no blocking open question in intent.openQuestions.	0 rules0 entries0 declarations1 questions, 1 blocking0 decisions0 of 0 verifying examples bound	0 implementing0 referencing
The roadmap page shows the upcoming work in priority order, split by what it needs `spec:consumers.spec-studio.roadmap-page` behavior	4	ready floor ready		13 rules, 13 keyed5 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound	1 implementing0 referencing
The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests `spec:protocol.roadmap-replaces-plans` behavior	4	ready floor ready		11 rules, 11 keyed3 entries2 declarations0 questions1 decisions0 of 0 verifying examples bound	1 implementing0 referencing

The architecture it touches

Anchored components and member designs

Arrows: uses (anchored).

The diagram as text

component:protocol.adapters: external runtime and source adapters, anchored, layer adapter, context protocol; satisfies members spec:extraction.executable-examples; references members none; code for rests on none; member designs none
component:protocol.cli: entry points, shared build and publication, anchored, layer edge, context protocol; satisfies members none; references members none; code for rests on spec:consumers.spec-studio, spec:consumers.spec-studio.publisher; member designs none
component:protocol.codegen: contracts and registrar output, anchored, layer application, context protocol; satisfies members spec:extraction.executable-examples; references members none; code for rests on none; member designs none
component:protocol.extract: the carrier and source pipeline, anchored, layer application, context protocol; satisfies members none; references members spec:decisions.roadmap-priority; code for rests on spec:extraction.derive-graph, spec:model.open-question-fields, spec:model.rule-keys, spec:model.structural-patterns; member designs none
component:protocol.graph: the one graph and its semantic decisions, anchored, layer domain, context protocol; satisfies members spec:extraction.executable-examples; references members none; code for rests on spec:extraction.delivery-facts, spec:extraction.derive-graph; member designs none
component:protocol.model: the authored contracts and stable ids, anchored, layer domain, context protocol; satisfies members none; references members spec:decisions.roadmap-priority; code for rests on none; member designs none
component:protocol.projections: read-only output, layout and owned publication, anchored, layer edge, context protocol; satisfies members spec:consumers.spec-studio.lenses.architecture.unit-register, spec:consumers.spec-studio.capability-map-page, spec:consumers.spec-studio.diagram-kinds, spec:consumers.spec-studio.diagram-kinds.legibility, spec:consumers.spec-studio.diagram-kinds.edge-routing, spec:consumers.spec-studio.diagram-kinds.mermaid-source, spec:consumers.spec-studio.diagram-kinds.dependency, spec:consumers.spec-studio.diagram-kinds.capability-tree, spec:consumers.spec-studio.diagram-kinds.scoped-architecture, spec:consumers.spec-studio.diagram-kinds.maturity-picture, spec:consumers.spec-studio.diagram-kinds.requirement-trace, spec:consumers.spec-studio.slice-page, spec:consumers.spec-studio.roadmap-page, spec:consumers.roadmap.memo; references members spec:consumers.design-slice; code for rests on spec:consumers.binding-language-views, spec:consumers.derived-readiness-banner, spec:consumers.projections-model, spec:consumers.spec-studio, spec:consumers.spec-studio.data, spec:consumers.spec-studio.data.recipe-answers, spec:consumers.spec-studio.diagrams, spec:consumers.spec-studio.index-page, spec:consumers.spec-studio.lenses, spec:consumers.spec-studio.lenses.architecture, spec:consumers.spec-studio.pack-page, spec:consumers.spec-studio.publisher, spec:consumers.spec-studio.responsive, spec:consumers.spec-studio.shell, spec:model.structural-patterns, spec:observation.run-evidence; member designs none
component:protocol.reader: the typed graph contract and body evaluator, anchored, layer application, context protocol; satisfies members none; references members none; code for rests on spec:consumers.pack-design, spec:validation.next-rung-floor; member designs none
component:protocol.runner: provider-neutral example execution, anchored, layer application, context protocol; satisfies members spec:extraction.executable-examples; references members none; code for rests on none; member designs none
component:protocol.studio-elements: optional browser behavior and proposal handoff, anchored, layer edge, context protocol; satisfies members spec:consumers.spec-studio.capability-map-page, spec:consumers.spec-studio.diagram-kinds.legibility; references members none; code for rests on spec:consumers.intent-composition.proposal, spec:consumers.intent-composition.proposal.memo, spec:consumers.spec-studio.diagrams, spec:consumers.spec-studio.page-elements, spec:consumers.spec-studio.responsive; member designs none
component:protocol.testing: the generated registrar runtime, anchored, layer adapter, context protocol; satisfies members spec:extraction.executable-examples; references members none; code for rests on none; member designs none
component:protocol.validate: one finding currency and ordered checks, anchored, layer domain, context protocol; satisfies members none; references members none; code for rests on spec:model.rule-keys, spec:validation.next-rung-floor, spec:validation.readiness-floor, spec:validation.typed-dependency-floor; member designs none
component:protocol.import: canonical conversion with a fidelity boundary, outside scope, anchored, layer application, context protocol
component:protocol.notation: the leaf step codec, outside scope, anchored, layer domain, context protocol
component:protocol.adapters uses component:protocol.runner · anchored
impl:protocol.example-runner-adapter uses impl:protocol.example-runner · anchored
component:protocol.cli uses component:protocol.adapters · anchored
component:protocol.cli uses component:protocol.codegen · anchored
component:protocol.cli uses component:protocol.extract · anchored
component:protocol.cli uses component:protocol.graph · anchored
impl:protocol.stamp-command uses impl:protocol.schema-version · anchored
component:protocol.cli uses component:protocol.import · anchored
component:protocol.cli uses component:protocol.model · anchored
component:protocol.cli uses component:protocol.projections · anchored
impl:protocol.vault-command uses component:protocol.projections · anchored
component:protocol.cli uses component:protocol.reader · anchored
component:protocol.cli uses component:protocol.validate · anchored
component:protocol.codegen uses component:protocol.graph · anchored
component:protocol.codegen uses component:protocol.notation · anchored
component:protocol.codegen uses component:protocol.reader · anchored
component:protocol.codegen uses component:protocol.validate · anchored
component:protocol.extract uses component:protocol.graph · anchored
impl:protocol.derive-graph uses impl:protocol.delivery-facts · anchored
component:protocol.extract uses component:protocol.model · anchored
component:protocol.extract uses component:protocol.notation · anchored
component:protocol.extract uses component:protocol.validate · anchored
component:protocol.graph uses component:protocol.model · anchored
component:protocol.graph uses component:protocol.notation · anchored
component:protocol.import uses component:protocol.extract · anchored
component:protocol.import uses component:protocol.validate · anchored
component:protocol.projections uses component:protocol.extract · anchored
impl:protocol.gherkin-view uses impl:protocol.gherkin-kind-policy · anchored
component:protocol.projections uses component:protocol.graph · anchored
component:protocol.projections uses component:protocol.model · anchored
component:protocol.projections uses component:protocol.notation · anchored
component:protocol.projections uses component:protocol.reader · anchored
impl:protocol.studio-recipes uses api:protocol.evaluate-body · anchored
impl:protocol.studio-recipes uses impl:protocol.reader · anchored
impl:protocol.vault-notes uses impl:protocol.reader · anchored
component:protocol.projections uses component:protocol.validate · anchored
component:protocol.reader uses component:protocol.graph · anchored
impl:protocol.reader uses impl:protocol.delivery-facts · anchored
component:protocol.reader uses component:protocol.model · anchored
component:protocol.reader uses component:protocol.notation · anchored
component:protocol.reader uses component:protocol.validate · anchored
impl:protocol.reader uses impl:protocol.next-rung-floor · anchored
component:protocol.runner uses component:protocol.notation · anchored
component:protocol.studio-elements uses component:protocol.projections · anchored
component:protocol.studio-elements uses component:protocol.reader · anchored
component:protocol.testing uses component:protocol.adapters · anchored
component:protocol.testing uses component:protocol.runner · anchored
component:protocol.validate uses component:protocol.graph · anchored
impl:protocol.authored-honesty-delivery-facts uses impl:protocol.delivery-facts · anchored
component:protocol.validate uses component:protocol.model · anchored
component:protocol.validate uses component:protocol.notation · anchored
impl:protocol.structural-self-binding implements spec:protocol.significant-units-review; no component
impl:protocol.role-vocabulary implements spec:protocol.role-vocabulary; no component
impl:protocol.capability-map-recipe implements spec:consumers.capability-map; no component
impl:protocol.capability-map-recipe references spec:decisions.epics-of-any-kind; no component
impl:protocol.capability-epics implements spec:protocol.capability-epics; no component
impl:protocol.design-slice-recipe implements spec:consumers.design-slice; no component
impl:protocol.roadmap-recipe implements spec:consumers.roadmap; no component
impl:protocol.roadmap-memo-recipe implements spec:consumers.roadmap.memo; no component
impl:protocol.roadmap-practice implements spec:protocol.roadmap-replaces-plans; no component

Mermaid source

Copyable source; the Studio draws static SVG.

Preferred syntax: block; flowchart fallback because block cannot carry edge claims and counts.

Mermaid source for Anchored components and member designs

flowchart TB
  n0["entry points, shared build and publication, anchored, layer edge, context protocol · component:protocol.cli"]
  n1["read-only output, layout and owned publication, anchored, layer edge, context protocol · component:protocol.projections"]
  n2["optional browser behavior and proposal handoff, anchored, layer edge, context protocol · component:protocol.studio-elements"]
  n3["contracts and registrar output, anchored, layer application, context protocol · component:protocol.codegen"]
  n4["the carrier and source pipeline, anchored, layer application, context protocol · component:protocol.extract"]
  n5["the typed graph contract and body evaluator, anchored, layer application, context protocol · component:protocol.reader"]
  n6["provider-neutral example execution, anchored, layer application, context protocol · component:protocol.runner"]
  n7["outside scope, 1 components, application, folded"]
  %% folded outside.protocol.application: component:protocol.import
  n8["the one graph and its semantic decisions, anchored, layer domain, context protocol · component:protocol.graph"]
  n9["the authored contracts and stable ids, anchored, layer domain, context protocol · component:protocol.model"]
  n10["one finding currency and ordered checks, anchored, layer domain, context protocol · component:protocol.validate"]
  n11["outside scope, 1 components, domain, folded"]
  %% folded outside.protocol.domain: component:protocol.notation
  n12["external runtime and source adapters, anchored, layer adapter, context protocol · component:protocol.adapters"]
  n13["the generated registrar runtime, anchored, layer adapter, context protocol · component:protocol.testing"]
  n12 -->|"uses · anchored (2 unit edges)"| n6
  %% count: 2; component:protocol.adapters to component:protocol.runner
  n0 -->|"uses · anchored"| n12
  %% count: 1; component:protocol.cli to component:protocol.adapters
  n0 -->|"uses · anchored"| n3
  %% count: 1; component:protocol.cli to component:protocol.codegen
  n0 -->|"uses · anchored"| n4
  %% count: 1; component:protocol.cli to component:protocol.extract
  n0 -->|"uses · anchored (2 unit edges)"| n8
  %% count: 2; component:protocol.cli to component:protocol.graph
  n0 -->|"uses · anchored"| n9
  %% count: 1; component:protocol.cli to component:protocol.model
  n0 -->|"uses · anchored (2 unit edges)"| n1
  %% count: 2; component:protocol.cli to component:protocol.projections
  n0 -->|"uses · anchored"| n5
  %% count: 1; component:protocol.cli to component:protocol.reader
  n0 -->|"uses · anchored"| n10
  %% count: 1; component:protocol.cli to component:protocol.validate
  n0 -->|"uses · anchored"| n7
  %% count: 1; component:protocol.cli to outside.protocol.application
  n3 -->|"uses · anchored"| n8
  %% count: 1; component:protocol.codegen to component:protocol.graph
  n3 -->|"uses · anchored"| n5
  %% count: 1; component:protocol.codegen to component:protocol.reader
  n3 -->|"uses · anchored"| n10
  %% count: 1; component:protocol.codegen to component:protocol.validate
  n3 -->|"uses · anchored"| n11
  %% count: 1; component:protocol.codegen to outside.protocol.domain
  n4 -->|"uses · anchored (2 unit edges)"| n8
  %% count: 2; component:protocol.extract to component:protocol.graph
  n4 -->|"uses · anchored"| n9
  %% count: 1; component:protocol.extract to component:protocol.model
  n4 -->|"uses · anchored"| n10
  %% count: 1; component:protocol.extract to component:protocol.validate
  n4 -->|"uses · anchored"| n11
  %% count: 1; component:protocol.extract to outside.protocol.domain
  n8 -->|"uses · anchored"| n9
  %% count: 1; component:protocol.graph to component:protocol.model
  n8 -->|"uses · anchored"| n11
  %% count: 1; component:protocol.graph to outside.protocol.domain
  n1 -->|"uses · anchored (2 unit edges)"| n4
  %% count: 2; component:protocol.projections to component:protocol.extract
  n1 -->|"uses · anchored"| n8
  %% count: 1; component:protocol.projections to component:protocol.graph
  n1 -->|"uses · anchored"| n9
  %% count: 1; component:protocol.projections to component:protocol.model
  n1 -->|"uses · anchored (4 unit edges)"| n5
  %% count: 4; component:protocol.projections to component:protocol.reader
  n1 -->|"uses · anchored"| n10
  %% count: 1; component:protocol.projections to component:protocol.validate
  n1 -->|"uses · anchored"| n11
  %% count: 1; component:protocol.projections to outside.protocol.domain
  n5 -->|"uses · anchored (2 unit edges)"| n8
  %% count: 2; component:protocol.reader to component:protocol.graph
  n5 -->|"uses · anchored"| n9
  %% count: 1; component:protocol.reader to component:protocol.model
  n5 -->|"uses · anchored (2 unit edges)"| n10
  %% count: 2; component:protocol.reader to component:protocol.validate
  n5 -->|"uses · anchored"| n11
  %% count: 1; component:protocol.reader to outside.protocol.domain
  n6 -->|"uses · anchored"| n11
  %% count: 1; component:protocol.runner to outside.protocol.domain
  n2 -->|"uses · anchored"| n1
  %% count: 1; component:protocol.studio-elements to component:protocol.projections
  n2 -->|"uses · anchored"| n5
  %% count: 1; component:protocol.studio-elements to component:protocol.reader
  n13 -->|"uses · anchored"| n12
  %% count: 1; component:protocol.testing to component:protocol.adapters
  n13 -->|"uses · anchored"| n6
  %% count: 1; component:protocol.testing to component:protocol.runner
  n10 -->|"uses · anchored (2 unit edges)"| n8
  %% count: 2; component:protocol.validate to component:protocol.graph
  n10 -->|"uses · anchored"| n9
  %% count: 1; component:protocol.validate to component:protocol.model
  n10 -->|"uses · anchored"| n11
  %% count: 1; component:protocol.validate to outside.protocol.domain
  n7 -->|"uses · anchored"| n4
  %% count: 1; outside.protocol.application to component:protocol.extract
  n7 -->|"uses · anchored"| n10
  %% count: 1; outside.protocol.application to component:protocol.validate

Components the slice touches

Component	Layer and context	Reached through
`component:protocol.adapters` external runtime and source adapters	adapter · protocol	Members its code satisfies: Bound examples execute their authored stepsMembers its code references: noneWhat the slice rests on, realized here: noneMember designs naming it: none
`component:protocol.cli` entry points, shared build and publication	edge · protocol	Members its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:consumers.spec-studio, spec:consumers.spec-studio.publisherMember designs naming it: none
`component:protocol.codegen` contracts and registrar output	application · protocol	Members its code satisfies: Bound examples execute their authored stepsMembers its code references: noneWhat the slice rests on, realized here: noneMember designs naming it: none
`component:protocol.extract` the carrier and source pipeline	application · protocol	Members its code satisfies: noneMembers its code references: A roadmap states advisory priority in the graphWhat the slice rests on, realized here: spec:extraction.derive-graph, spec:model.open-question-fields, spec:model.rule-keys, spec:model.structural-patternsMember designs naming it: none
`component:protocol.graph` the one graph and its semantic decisions	domain · protocol	Members its code satisfies: Bound examples execute their authored stepsMembers its code references: noneWhat the slice rests on, realized here: spec:extraction.delivery-facts, spec:extraction.derive-graphMember designs naming it: none
`component:protocol.model` the authored contracts and stable ids	domain · protocol	Members its code satisfies: noneMembers its code references: A roadmap states advisory priority in the graphWhat the slice rests on, realized here: noneMember designs naming it: none
`component:protocol.projections` read-only output, layout and owned publication	edge · protocol	Members its code satisfies: The architecture page lists each component's significant units by role, The capability map page makes refinement readable by epic, The Studio chooses diagram kinds from graph values, A diagram preserves readable labels before zoom, Edges route around boxes with deterministic orthogonal paths, A diagram offers Mermaid source as copyable text, A dependency drawing shows the declared footing of a Spec set, A refinement drawing follows the capability map, A Spec set draws the architecture it touches, The maturity map is drawn as a grid of counts, A requirement drawing separates intent from realization and verification, A slice page shows a Pack's design as one whole, The roadmap page shows the upcoming work in priority order, split by what it needs, A roadmap renders as the forward section of a pull request descriptionMembers its code references: A slice reads a Pack as one design, with the architecture it touches and what each member needs nextWhat the slice rests on, realized here: spec:consumers.binding-language-views, spec:consumers.derived-readiness-banner, spec:consumers.projections-model, spec:consumers.spec-studio, spec:consumers.spec-studio.data, spec:consumers.spec-studio.data.recipe-answers, spec:consumers.spec-studio.diagrams, spec:consumers.spec-studio.index-page, spec:consumers.spec-studio.lenses, spec:consumers.spec-studio.lenses.architecture, spec:consumers.spec-studio.pack-page, spec:consumers.spec-studio.publisher, spec:consumers.spec-studio.responsive, spec:consumers.spec-studio.shell, spec:model.structural-patterns, spec:observation.run-evidenceMember designs naming it: none
`component:protocol.reader` the typed graph contract and body evaluator	application · protocol	Members its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:consumers.pack-design, spec:validation.next-rung-floorMember designs naming it: none
`component:protocol.runner` provider-neutral example execution	application · protocol	Members its code satisfies: Bound examples execute their authored stepsMembers its code references: noneWhat the slice rests on, realized here: noneMember designs naming it: none
`component:protocol.studio-elements` optional browser behavior and proposal handoff	edge · protocol	Members its code satisfies: The capability map page makes refinement readable by epic, A diagram preserves readable labels before zoomMembers its code references: noneWhat the slice rests on, realized here: spec:consumers.intent-composition.proposal, spec:consumers.intent-composition.proposal.memo, spec:consumers.spec-studio.diagrams, spec:consumers.spec-studio.page-elements, spec:consumers.spec-studio.responsiveMember designs naming it: none
`component:protocol.testing` the generated registrar runtime	adapter · protocol	Members its code satisfies: Bound examples execute their authored stepsMembers its code references: noneWhat the slice rests on, realized here: noneMember designs naming it: none
`component:protocol.validate` one finding currency and ordered checks	domain · protocol	Members its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:model.rule-keys, spec:validation.next-rung-floor, spec:validation.readiness-floor, spec:validation.typed-dependency-floorMember designs naming it: none

Member component designs

None.

Outside the slice, shown for context and not counted as touched

component:protocol.import · canonical conversion with a fidelity boundary · anchored · a touched component uses it; it uses a touched component
component:protocol.notation · the leaf step codec · anchored · a touched component uses it

Units bound to a member and to no component

impl:protocol.structural-self-binding implements The engine's accepted set covers its significant abstractions and only those
impl:protocol.role-vocabulary implements The engine's architectural roles each name one pattern
impl:protocol.capability-map-recipe implements The capability map reads every epic and its refinement descendants
impl:protocol.capability-map-recipe references Capability epics keep kind independent of altitude
impl:protocol.capability-epics implements The Protocol organizes its own features in capability epics
impl:protocol.design-slice-recipe implements A slice reads a Pack as one design, with the architecture it touches and what each member needs next
impl:protocol.roadmap-recipe implements A roadmap orders the next bodies of work, and the graph says what each still needs
impl:protocol.roadmap-memo-recipe implements A roadmap renders as the forward section of a pull request description
impl:protocol.roadmap-practice implements The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests

Decisions in scope

Decision	Rung	In the slice	Shapes	Questions
Bindings are optional, plural, and may reference a design `spec:decisions.anchor-binding-grain` refines spec:decisions.shipped-projections-frozen	ready floor ready	outside	The engine's accepted set covers its significant abstractions and only those, A slice reads a Pack as one design, with the architecture it touches and what each member needs next	0 open, 0 blocking
Architectural significance is annotated where it is realized `spec:decisions.architectural-annotation` refines spec:decisions.shipped-projections-frozen	ready floor ready	outside	The engine's accepted set covers its significant abstractions and only those, The engine's architectural roles each name one pattern, A slice reads a Pack as one design, with the architecture it touches and what each member needs next	0 open, 0 blocking
Capability epics keep kind independent of altitude `spec:decisions.epics-of-any-kind`	ready floor ready	member	The capability map reads every epic and its refinement descendants, The Protocol organizes its own features in capability epics	0 open, 0 blocking
Plan and review files stop carrying the delivery record once the roadmap and the pull request do `spec:decisions.roadmap-over-plans` refines spec:decisions.planning-truths-placement	ready floor ready	member	The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests	0 open, 0 blocking
A roadmap states advisory priority in the graph `spec:decisions.roadmap-priority` refines spec:decisions.pack-markdown-carrier, spec:decisions.planning-truths-placement	ready floor ready	member	A roadmap orders the next bodies of work, and the graph says what each still needs	0 open, 0 blocking
The shipped projections stay frozen `spec:decisions.shipped-projections-frozen`	ready floor ready	outside	A diagram offers Mermaid source as copyable text	0 open, 0 blocking
The engine lays out every Studio diagram as static SVG when the page set is built `spec:decisions.studio-diagram-renderer` refines spec:decisions.studio-web-components	ready floor ready	outside	The Studio chooses diagram kinds from graph values, A diagram offers Mermaid source as copyable text	0 open, 0 blocking

Open questions in scope

blocking · question.releaseReader · spec:consumers.projections-model.roadmap-views · Does a reader need release or baseline views that the roadmap, the recipes and git tags do not serve?Decider: ownerProvisional: Keep release and baseline views deferred; the trigger opens this question and does not authorize either view's build.Trigger: the first published releaseHolds: Roadmap views read releases, baselines and phases from git and the graph
non-blocking · question.exportCarriesSlice · spec:consumers.spec-studio.slice-page · Does a Pack export also carry the Pack's slice page?Decider: delegatedProvisional: no; the export keeps the Pack page and its members, and the slice page stays one link away in the page set

Where the slice meets the rest

Rests on (43)

Spec	Rung	Implementation binding	Joined members	Holds
Design work reads its answers from catalog recipes `spec:consumers.agent-surface.design-recipes`	ready floor ready	present	dependsOn: A slice reads a Pack as one design, with the architecture it touches and what each member needs next	none
Register questions stay executable graph recipes `spec:consumers.agent-surface.register-recipes`	ready floor ready	present	dependsOn: A roadmap renders as the forward section of a pull request description	none
Views speak binding language, never the internal fact name `spec:consumers.binding-language-views`	ready floor ready	present	dependsOn: The capability map page makes refinement readable by epic, A slice page shows a Pack's design as one whole	none
A context bundle is composed per invocation within a stated budget `spec:consumers.context-bundle`	ready floor ready	present	dependsOn: A slice reads a Pack as one design, with the architecture it touches and what each member needs next	none
Derived readiness renders beside the stated rung and warns in one direction `spec:consumers.derived-readiness-banner`	ready floor ready	present	dependsOn: A slice page shows a Pack's design as one whole	none
The next body of work is planned from the graph, not from a prose index `spec:consumers.graph-first-planning`	ready floor ready	present	refines: A roadmap orders the next bodies of work, and the graph says what each still needs	none
A change proposal is addressed, based and checked before it lands `spec:consumers.intent-composition.proposal`	ready floor ready	present	dependsOn: The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests	none
Recipe 49 renders a change proposal as the Markdown memo a person reviews `spec:consumers.intent-composition.proposal.memo`	ready floor ready	present	dependsOn: A roadmap renders as the forward section of a pull request description, The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests	none
The Pack context carries the Pack's design `spec:consumers.pack-design`	ready floor ready	present	refines: A slice reads a Pack as one design, with the architecture it touches and what each member needs next	none
Projections fan out from one graph without becoming truth stores `spec:consumers.projections-model`	ready floor ready	present	refines: The capability map reads every epic and its refinement descendants, Roadmap views read releases, baselines and phases from git and the graph	none
The readiness planner orders the statements a person can make `spec:consumers.readiness-planner`	ready floor ready	present	dependsOn: A slice reads a Pack as one design, with the architecture it touches and what each member needs next, A roadmap orders the next bodies of work, and the graph says what each still needs	none
A Pack is read from a named perspective `spec:consumers.review-perspectives`	ready floor ready	present	dependsOn: A slice reads a Pack as one design, with the architecture it touches and what each member needs next	none
The Spec Studio is a static HTML workbench over the one graph `spec:consumers.spec-studio`	ready floor ready	present	refines: A slice page shows a Pack's design as one whole, The roadmap page shows the upcoming work in priority order, split by what it needs	none
The Studio renders from the reader's values and embeds only what its script reads `spec:consumers.spec-studio.data`	ready floor ready	present	dependsOn: A requirement drawing separates intent from realization and verification, The roadmap page shows the upcoming work in priority order, split by what it needs	none
A page takes each recipe answer from the recipe's shipped body `spec:consumers.spec-studio.data.recipe-answers`	ready floor ready	present	dependsOn: A slice page shows a Pack's design as one whole	none
A diagram is laid out from graph values into SVG with a text equivalent `spec:consumers.spec-studio.diagrams`	ready floor ready	present	refines: The Studio chooses diagram kinds from graph values, A diagram preserves readable labels before zoom, Edges route around boxes with deterministic orthogonal pathsdependsOn: A slice page shows a Pack's design as one whole	none
The index says where the corpus stands and narrows every Spec `spec:consumers.spec-studio.index-page`	ready floor ready	present	dependsOn: The capability map page makes refinement readable by epic	none
Five lenses read the graph as Packs, capabilities, architecture, tests and evidence `spec:consumers.spec-studio.lenses`	ready floor ready	present	refines: The capability map page makes refinement readable by epic	none
The architecture lens draws components by context and layer, the planned beside the built `spec:consumers.spec-studio.lenses.architecture`	ready floor ready	present	refines: The architecture page lists each component's significant units by roledependsOn: A Spec set draws the architecture it touches	none
A Pack page shows the Pack's design as one card per member `spec:consumers.spec-studio.pack-page`	ready floor ready	present	dependsOn: A slice page shows a Pack's design as one whole	none
A few custom elements filter, search, open and copy on a rendered page `spec:consumers.spec-studio.page-elements`	ready floor ready	present	dependsOn: A diagram offers Mermaid source as copyable text	none
`sdp studio` publishes the Studio as one page set `spec:consumers.spec-studio.publisher`	ready floor ready	present	dependsOn: The roadmap page shows the upcoming work in priority order, split by what it needs	none
The Studio reads on a phone as on a desktop `spec:consumers.spec-studio.responsive`	ready floor ready	present	dependsOn: A diagram preserves readable labels before zoom	none
The Studio's shell frames every page with navigation, a rail and a canvas `spec:consumers.spec-studio.shell`	ready floor ready	present	dependsOn: The roadmap page shows the upcoming work in priority order, split by what it needs	none
Bindings are optional, plural, and may reference a design `spec:decisions.anchor-binding-grain`	ready floor ready	none	decidedBy: The engine's accepted set covers its significant abstractions and only those, A slice reads a Pack as one design, with the architecture it touches and what each member needs next	none
Architectural significance is annotated where it is realized `spec:decisions.architectural-annotation`	ready floor ready	none	decidedBy: The engine's accepted set covers its significant abstractions and only those, The engine's architectural roles each name one pattern, A slice reads a Pack as one design, with the architecture it touches and what each member needs next	none
One Spec carries named delivery coordinates `spec:decisions.one-primitive`	ready floor ready	none	dependsOn: Capability epics keep kind independent of altitude	none
Packs have a Markdown manifest carrier `spec:decisions.pack-markdown-carrier`	ready floor ready	none	refines: A roadmap states advisory priority in the graph	none
Planning truths live in ruled graph homes `spec:decisions.planning-truths-placement`	ready floor ready	none	refines: A roadmap states advisory priority in the graph, Plan and review files stop carrying the delivery record once the roadmap and the pull request do	none
The shipped projections stay frozen `spec:decisions.shipped-projections-frozen`	ready floor ready	none	decidedBy: A diagram offers Mermaid source as copyable text	none
The engine lays out every Studio diagram as static SVG when the page set is built `spec:decisions.studio-diagram-renderer`	ready floor ready	none	decidedBy: The Studio chooses diagram kinds from graph values, A diagram offers Mermaid source as copyable text	none
Resolving bindings confer direct delivery facts `spec:extraction.delivery-facts`	ready floor ready	present	dependsOn: The capability map reads every epic and its refinement descendants	none
Carrier reification derives the one graph `spec:extraction.derive-graph`	ready floor ready	present	dependsOn: Bound examples execute their authored steps	none
An open question may name who decides it, its links, a provisional reading and a re-entry trigger `spec:model.open-question-fields`	ready floor ready	present	dependsOn: A slice reads a Pack as one design, with the architecture it touches and what each member needs next, A slice page shows a Pack's design as one whole, A roadmap orders the next bodies of work, and the graph says what each still needs	none
Components are designed ahead of their code `spec:model.planned-architecture`	ready floor ready	present	dependsOn: A Spec set draws the architecture it touches, A slice reads a Pack as one design, with the architecture it touches and what each member needs next	none
A rule or flow entry may carry a key that addresses it `spec:model.rule-keys`	ready floor ready	present	dependsOn: A slice reads a Pack as one design, with the architecture it touches and what each member needs next	none
Architecturally significant units are annotated where they are realized `spec:model.structural-patterns`	ready floor ready	present	dependsOn: The engine's accepted set covers its significant abstractions and only those	none
CI run records are joined to verifiers in a view `spec:observation.run-evidence`	ready floor ready	present	dependsOn: The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests	none
The Protocol authors and validates itself `spec:protocol.self-hosting`	ready floor ready	present	refines: The Protocol organizes its own features in capability epics, The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests	none
The engine's structural self-binding covers its architecturally significant units `spec:protocol.structural-self-binding`	ready floor ready	present	refines: The engine's accepted set covers its significant abstractions and only those, The engine's architectural roles each name one pattern	none
The floor names what blocks the floor's next rung `spec:validation.next-rung-floor`	ready floor ready	present	dependsOn: A roadmap orders the next bodies of work, and the graph says what each still needs	none
Stated readiness must clear its floor `spec:validation.readiness-floor`	ready floor ready	present	dependsOn: The capability map reads every epic and its refinement descendants, The Protocol organizes its own features in capability epics	none
A ready Spec rests only on settled dependencies `spec:validation.typed-dependency-floor`	ready floor ready	present	dependsOn: A roadmap orders the next bodies of work, and the graph says what each still needs	none

Rested on by (10)

Spec	Rung	Implementation binding	Joined members	Holds
A Pack has a Markdown manifest carrier `spec:carrier.markdown-pack-authoring`	ready floor ready	present	decidedBy: A roadmap states advisory priority in the graph	none
Designs are compared between a base commit and the working tree at entry grain `spec:consumers.design-diff`	ready floor ready	present	decidedBy: A roadmap states advisory priority in the graph	none
A Pack page's maturity map places every member by its stated rung and its floor `spec:consumers.spec-studio.pack-page.maturity-map`	ready floor ready	present	dependsOn: The maturity map is drawn as a grid of counts	none
A Spec page shows one Spec in collapsible panels, in a fixed order `spec:consumers.spec-studio.spec-page`	ready floor ready	present	dependsOn: A requirement drawing separates intent from realization and verification	none
The upgrade kit shows a corpus what it could adopt `spec:consumers.upgrade-kit`	ready floor ready	present	dependsOn: The capability map reads every epic and its refinement descendants, A roadmap orders the next bodies of work, and the graph says what each still needs	none
A bound example runs its contract steps against a fresh world `spec:extraction.example-runner`	ready floor ready	present	refines: Bound examples execute their authored steps	none
The build derives step and space contracts from graph examples `spec:extraction.executable-contracts`	ready floor ready	present	refines: Bound examples execute their authored steps	none
A Pack node keeps its members in authored order `spec:extraction.pack-member-order`	ready floor ready	present	decidedBy: A roadmap states advisory priority in the graph	none
A Pack is a truth-free review aggregate `spec:model.pack-aggregate`	ready floor ready	present	decidedBy: A roadmap states advisory priority in the graph	none
The Protocol removes its frozen plans, review reports and superseded concept material `spec:protocol.delivery-record-cleanup`	idea floor idea	none	refines: The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requestsdecidedBy: Plan and review files stop carrying the delivery record once the roadmap and the pull request do	none

Verified by (0)

None.

Superseded by (0)

None.

Composing (0)

Composing needs the script.