Roadmaps, capability maps and design slices

pack:roadmaps-and-slices-v1

specs/roadmaps-and-slices.pack.sdp.md

Where the design stands

49 members in authored reading order; no unresolved members.
1 member held below their stated next rung: Roadmap views read releases, baselines and phases from git and the graph (1 unmet clause).
No members waiting only for their author's statement.
174 design entries and 43 pinned declarations.
2 open questions and 1 blocking question.
22 members with an implementation binding.
3 members with a design reference.
43 outside Specs the Pack rests on; 10 outside Specs rest on the Pack; no outside Specs verify it; no outside Specs supersede it.

Maturity map

Rows: stated readiness, idea to ready. Columns: floor reached, none to ready. Each mark counts one member; above 100 members a cell is solid. Floor none is distinct from idea.

Outlined diagonal: matches. Right of diagonal: floor above statement. Left of diagonal: statement above floor.

Maturity map as text

Counts by stated readiness and floor reached. To the right the floor exceeds the statement; to the left the statement exceeds the floor.
Stated rung / floor reached	floor none	floor idea	floor scoped	floor defined	floor ready
stated idea	—	—	—	—	—
stated scoped	—	—	1	—	—
stated defined	—	—	—	—	—
stated ready	—	—	—	—	48

stated scoped, floor scoped · 1 member

Roadmap views read releases, baselines and phases from git and the graph · spec:consumers.projections-model.roadmap-views · scoped floor scoped

stated ready, floor ready · 48 members

The engine's accepted set covers its significant abstractions and only those · spec:protocol.significant-units-review · ready floor ready
The engine's architectural roles each name one pattern · spec:protocol.role-vocabulary · ready floor ready
The architecture page lists each component's significant units by role · spec:consumers.spec-studio.lenses.architecture.unit-register · ready floor ready
The capability map reads every epic and its refinement descendants · spec:consumers.capability-map · ready floor ready
Capability epics keep kind independent of altitude · spec:decisions.epics-of-any-kind · ready floor ready
The Protocol organizes its own features in capability epics · spec:protocol.capability-epics · ready floor ready
Bound examples execute their authored steps · spec:extraction.executable-examples · ready floor ready
The capability map page makes refinement readable by epic · spec:consumers.spec-studio.capability-map-page · ready floor ready
The Studio chooses diagram kinds from graph values · spec:consumers.spec-studio.diagram-kinds · ready floor ready
A diagram preserves readable labels before zoom · spec:consumers.spec-studio.diagram-kinds.legibility · ready floor ready
Edges route around boxes with deterministic orthogonal paths · spec:consumers.spec-studio.diagram-kinds.edge-routing · ready floor ready
A diagram offers Mermaid source as copyable text · spec:consumers.spec-studio.diagram-kinds.mermaid-source · ready floor ready
A dependency drawing shows the declared footing of a Spec set · spec:consumers.spec-studio.diagram-kinds.dependency · ready floor ready
A refinement drawing follows the capability map · spec:consumers.spec-studio.diagram-kinds.capability-tree · ready floor ready
A Spec set draws the architecture it touches · spec:consumers.spec-studio.diagram-kinds.scoped-architecture · ready floor ready
The maturity map is drawn as a grid of counts · spec:consumers.spec-studio.diagram-kinds.maturity-picture · ready floor ready
A requirement drawing separates intent from realization and verification · spec:consumers.spec-studio.diagram-kinds.requirement-trace · ready floor ready
A slice reads a Pack as one design, with the architecture it touches and what each member needs next · spec:consumers.design-slice · ready floor ready
Outside components stop at the touched components' neighbors · spec:consumers.design-slice.outside-components · ready floor ready
Members rest on a chain · spec:consumers.design-slice.chain · ready floor ready
A shaping decision comes before its member · spec:consumers.design-slice.decision-backlink · ready floor ready
A cycle shares a depth · spec:consumers.design-slice.dependency-cycle · ready floor ready
An example folds without lending its readiness · spec:consumers.design-slice.folded-example · ready floor ready
An example with its own dependency stays unfolded · spec:consumers.design-slice.independent-example · ready floor ready
An unanchored component design stays visible · spec:consumers.design-slice.component-absent · ready floor ready
An anchor alone does not realize a component design · spec:consumers.design-slice.component-unrelated · ready floor ready
A realized component matches its declared values · spec:consumers.design-slice.component-matching · ready floor ready
A realized component keeps its differing layer and uses apart · spec:consumers.design-slice.component-differing · ready floor ready
An unreadable declared layer stays visible · spec:consumers.design-slice.component-unreadable · ready floor ready
A prerequisite reaches its satisfying component · spec:consumers.design-slice.outside-satisfied · ready floor ready
An unbound prerequisite invents no component · spec:consumers.design-slice.outside-unbound · ready floor ready
An outside prerequisite names the member it holds · spec:consumers.design-slice.outside-holding · ready floor ready
A slice page shows a Pack's design as one whole · spec:consumers.spec-studio.slice-page · ready floor ready
A roadmap states advisory priority in the graph · spec:decisions.roadmap-priority · ready floor ready
A roadmap orders the next bodies of work, and the graph says what each still needs · spec:consumers.roadmap · ready floor ready
Built work stays on the roadmap · spec:consumers.roadmap.built-work · ready floor ready
A ready unbound part needs building · spec:consumers.roadmap.buildable-part · ready floor ready
A complete part waits for a statement · spec:consumers.roadmap.statement-part · ready floor ready
An unfinished part needs design · spec:consumers.roadmap.design-part · ready floor ready
A binding below ready remains drift · spec:consumers.roadmap.drifting-part · ready floor ready
A descendant without evidence names its holding clause · spec:consumers.roadmap.missing-evidence · ready floor ready
A descendant question holds the entry for design · spec:consumers.roadmap.blocking-part · ready floor ready
A descendant names its outside parent · spec:consumers.roadmap.outside-parent · ready floor ready
Waiting statements keep dependency order against roadmap places · spec:consumers.roadmap.statement-order · ready floor ready
The roadmap page shows the upcoming work in priority order, split by what it needs · spec:consumers.spec-studio.roadmap-page · ready floor ready
A roadmap renders as the forward section of a pull request description · spec:consumers.roadmap.memo · 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 · ready floor ready
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 · ready floor ready

Mermaid source

Preferred syntax: block. Fixed categorical cells; membership appears in comments.

Mermaid source for maturity map

block-beta
  columns 6
  axis["Stated / floor"]
  h0["none"]
  h1["idea"]
  h2["scoped"]
  h3["defined"]
  h4["ready"]
  r0["idea"]
  c00["0"]
  c01["0"]
  c02["0"]
  c03["0"]
  c04["0"]
  r1["scoped"]
  c10["0"]
  c11["0"]
  c12["1"]
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.scoped.scoped: spec:consumers.projections-model.roadmap-views · Roadmap views read releases, baselines and phases from git and the graph
  c13["0"]
  c14["0"]
  r2["defined"]
  c20["0"]
  c21["0"]
  c22["0"]
  c23["0"]
  c24["0"]
  r3["ready"]
  c30["0"]
  c31["0"]
  c32["0"]
  c33["0"]
  c34["48"]
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:protocol.significant-units-review · The engine's accepted set covers its significant abstractions and only those
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:protocol.role-vocabulary · The engine's architectural roles each name one pattern
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.lenses.architecture.unit-register · The architecture page lists each component's significant units by role
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.capability-map · The capability map reads every epic and its refinement descendants
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:decisions.epics-of-any-kind · Capability epics keep kind independent of altitude
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:protocol.capability-epics · The Protocol organizes its own features in capability epics
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:extraction.executable-examples · Bound examples execute their authored steps
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.capability-map-page · The capability map page makes refinement readable by epic
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.diagram-kinds · The Studio chooses diagram kinds from graph values
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.diagram-kinds.legibility · A diagram preserves readable labels before zoom
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.diagram-kinds.edge-routing · Edges route around boxes with deterministic orthogonal paths
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.diagram-kinds.mermaid-source · A diagram offers Mermaid source as copyable text
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.diagram-kinds.dependency · A dependency drawing shows the declared footing of a Spec set
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.diagram-kinds.capability-tree · A refinement drawing follows the capability map
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.diagram-kinds.scoped-architecture · A Spec set draws the architecture it touches
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.diagram-kinds.maturity-picture · The maturity map is drawn as a grid of counts
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.diagram-kinds.requirement-trace · A requirement drawing separates intent from realization and verification
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice · A slice reads a Pack as one design, with the architecture it touches and what each member needs next
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.outside-components · Outside components stop at the touched components' neighbors
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.chain · Members rest on a chain
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.decision-backlink · A shaping decision comes before its member
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.dependency-cycle · A cycle shares a depth
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.folded-example · An example folds without lending its readiness
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.independent-example · An example with its own dependency stays unfolded
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.component-absent · An unanchored component design stays visible
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.component-unrelated · An anchor alone does not realize a component design
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.component-matching · A realized component matches its declared values
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.component-differing · A realized component keeps its differing layer and uses apart
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.component-unreadable · An unreadable declared layer stays visible
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.outside-satisfied · A prerequisite reaches its satisfying component
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.outside-unbound · An unbound prerequisite invents no component
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.design-slice.outside-holding · An outside prerequisite names the member it holds
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.slice-page · A slice page shows a Pack's design as one whole
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:decisions.roadmap-priority · A roadmap states advisory priority in the graph
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.roadmap · A roadmap orders the next bodies of work, and the graph says what each still needs
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.roadmap.built-work · Built work stays on the roadmap
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.roadmap.buildable-part · A ready unbound part needs building
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.roadmap.statement-part · A complete part waits for a statement
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.roadmap.design-part · An unfinished part needs design
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.roadmap.drifting-part · A binding below ready remains drift
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.roadmap.missing-evidence · A descendant without evidence names its holding clause
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.roadmap.blocking-part · A descendant question holds the entry for design
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.roadmap.outside-parent · A descendant names its outside parent
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.roadmap.statement-order · Waiting statements keep dependency order against roadmap places
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.spec-studio.roadmap-page · The roadmap page shows the upcoming work in priority order, split by what it needs
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:consumers.roadmap.memo · A roadmap renders as the forward section of a pull request description
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.ready: spec:decisions.roadmap-over-plans · Plan and review files stop carrying the delivery record once the roadmap and the pull request do
  %% diagram.pack:roadmaps-and-slices-v1.maturity.cell.ready.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
  %% Accessible count table: diagram.pack:roadmaps-and-slices-v1.maturity.text

Framing

How a corpus reads where it stands and what comes next, drawn from the graph. First the architecture the views stand on: a review of which engine units are significant enough to anchor, and the meaning of each role they carry. Then the capability map, epics with their features and stories, and the Protocol's own capabilities stated as epics. Then the diagrams the graph has data for, and the design slice, a Pack read as one design with the architecture it touches. Last the roadmap: the decision that lets the graph hold an advisory priority, the roadmap reading and its page and memo, and the decision that lets the roadmap replace the Protocol's numbered plans.

Changed since the base

Compared with the base graph base b5e0a8b. Read the diff.

Base input: schema 0.12.0, 456 Specs.

Changed members

None.

Added members

None.

Pack membership

No membership or order change.

Members

1. The engine's accepted set covers its significant abstractions and only thosebehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:protocol.significant-units-review

Design

1 design entry · no pinned declarations

Decisions

Bindings are optional, plural, and may reference a design · stated ready
Architectural significance is annotated where it is realized · stated ready

Open questions

None.

Implementation binding: present

impl:protocol.structural-self-binding · realizes the declared significant-unit set and its structural self-binding · test/self-hosting-oracle/structural-edges.ts:76

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

2. The engine's architectural roles each name one patternmodel · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding none

spec:protocol.role-vocabulary

Design

5 design entries · no pinned declarations

Decisions

Architectural significance is annotated where it is realized · stated ready

Open questions

None.

Implementation binding: present

impl:protocol.role-vocabulary · asserts realization of the role vocabulary in the engine anchors' pinned roles · test/self-hosting-graph.test.ts:143

Design reference: none

Verifier binding: none

3. The architecture page lists each component's significant units by rolebehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.lenses.architecture.unit-register

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: present

impl:protocol.studio-unit-register · renders component source bindings and role-grouped recorded units · src/projections/studio/pages/architecture-register.ts:7 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

4. The capability map reads every epic and its refinement descendantsbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.capability-map

Design

10 design entries · 4 pinned declarations

Decisions

Capability epics keep kind independent of altitude · stated ready

Open questions

None.

Implementation binding: present

impl:protocol.capability-map-recipe · asserts realization of The capability map in docs/agent-surface/recipes.md · test/recipes.test.ts:7602 · role projection

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

5. Capability epics keep kind independent of altitudedecision · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding none

spec:decisions.epics-of-any-kind

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: present

impl:protocol.capability-map-recipe · asserts realization of The capability map in docs/agent-surface/recipes.md · test/recipes.test.ts:7602 · role projection

Verifier binding: none

6. The Protocol organizes its own features in capability epicsbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:protocol.capability-epics

Design

5 design entries · no pinned declarations

Decisions

Capability epics keep kind independent of altitude · stated ready

Open questions

None.

Implementation binding: present

impl:protocol.capability-epics · asserts realization of the capability epics in the shipped corpus's refinement · test/recipes.test.ts:8173

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

7. Bound examples execute their authored stepsbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding none

spec:extraction.executable-examples

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: present

impl:protocol.delivery-facts · computes delivery facts from resolving binding edges · src/graph/delivery-facts.ts:65 · role decider · component component:protocol.graph · layer domain · context protocol
impl:protocol.example-runner · plans and executes a bound example against the caller's world · src/runner/index.ts:108 · role service · component component:protocol.runner · layer application · context protocol
impl:protocol.example-runner-adapter · registers one test per example and owns the fresh world lifecycle · src/adapters/vitest.ts:32 · role adapter · component component:protocol.adapters · layer adapter · context protocol
impl:protocol.example-testing-helpers · adapter-lifecycle and oracle-comparison helpers for bound examples · src/testing/index.ts:50 · role adapter · component component:protocol.testing · layer adapter · context protocol
impl:protocol.executable-contracts · derives step and example-space contracts from the graph · src/codegen/contracts.ts:647 · role projection · component component:protocol.codegen · layer application · context protocol
impl:protocol.runnable-modules · derives and publishes runnable registrar modules from the graph · src/codegen/contracts.ts:658 · role projection · component component:protocol.codegen · layer application · context protocol

Design reference: none

Verifier binding: none

8. The capability map page makes refinement readable by epicbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.capability-map-page

Design

6 design entries · 1 pinned declaration

Open questions

None.

Implementation binding: present

impl:protocol.studio-capabilities-page · renders epic evidence, refinement and unreached Specs from the capability map · src/projections/studio/pages/capabilities-page.ts:78 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-filter · filters build-rendered rows through their recorded attributes · src/studio-elements/filter.ts:25 · role interaction · component component:protocol.studio-elements · layer edge · context protocol
impl:protocol.studio-frame · renders Studio navigation, page rails and composing controls · src/projections/studio/pages/frame.ts:6 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-index-page · renders Pack disclosures and filterable Spec rows · src/projections/studio/pages/index-page.ts:8 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

9. The Studio chooses diagram kinds from graph valuesbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.diagram-kinds

Design

37 design entries · 1 pinned declaration

Decisions

The engine lays out every Studio diagram as static SVG when the page set is built · stated ready

Open questions

None.

Implementation binding: present

impl:protocol.studio-architecture-lens · renders recipe component rows and planned designs as architecture and member diagrams · src/projections/studio/pages/architecture-page.ts:50 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-capability-diagrams · places refinement occurrences and bounded branches from the capability map · src/projections/studio/diagrams/capability.ts:101 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-diagram-layout · title-first box placement, wrapping and band sizing for desktop and phone · src/projections/studio/diagrams/layout.ts:140 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-diagram-source · escaped Mermaid flowchart and mindmap source in placed box order · src/projections/studio/diagrams/mermaid.ts:13 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-diagrams · deterministic grid and band layouts with bounded folds and full text equivalents · src/projections/studio/diagrams/svg.ts:73 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-maturity-map · places resolved Pack members by their stated rung and floor in authored order · src/projections/studio/pages/maturity-map.ts:7 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-requirement-diagram · folds requirement bindings by relation direction and claim and serializes exact relations · src/projections/studio/diagrams/requirement.ts:12 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-slice-architecture · selected component grid with distinct planned identities and complete unit edges · src/projections/studio/diagrams/slice.ts:219 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-slice-dependencies · supplied depth bands with protected boundary boxes and lossless text · src/projections/studio/diagrams/slice.ts:10 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

10. A diagram preserves readable labels before zoomcontract · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.diagram-kinds.legibility

Design

6 design entries · 3 pinned declarations

Open questions

None.

Implementation binding: present

impl:protocol.studio-diagram-element · adds view-box pan, zoom and pinch to build-rendered SVG without changing its layout · src/studio-elements/diagram.ts:23 · role interaction · component component:protocol.studio-elements · layer edge · context protocol
impl:protocol.studio-diagram-layout · title-first box placement, wrapping and band sizing for desktop and phone · src/projections/studio/diagrams/layout.ts:140 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-diagrams · deterministic grid and band layouts with bounded folds and full text equivalents · src/projections/studio/diagrams/svg.ts:73 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

11. Edges route around boxes with deterministic orthogonal pathscontract · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.diagram-kinds.edge-routing

Design

6 design entries · 1 pinned declaration

Open questions

None.

Implementation binding: present

impl:protocol.studio-diagram-routing · port, channel and overflow-rail edge routes around boxes and labels · src/projections/studio/diagrams/routing.ts:38 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-diagrams · deterministic grid and band layouts with bounded folds and full text equivalents · src/projections/studio/diagrams/svg.ts:73 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

12. A diagram offers Mermaid source as copyable textbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.diagram-kinds.mermaid-source

Design

6 design entries · no pinned declarations

Decisions

The shipped projections stay frozen · stated ready
The engine lays out every Studio diagram as static SVG when the page set is built · stated ready

Open questions

None.

Implementation binding: present

impl:protocol.studio-diagram-source · escaped Mermaid flowchart and mindmap source in placed box order · src/projections/studio/diagrams/mermaid.ts:13 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-diagrams · deterministic grid and band layouts with bounded folds and full text equivalents · src/projections/studio/diagrams/svg.ts:73 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

13. A dependency drawing shows the declared footing of a Spec setbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.diagram-kinds.dependency

Design

6 design entries · 2 pinned declarations

Open questions

None.

Implementation binding: present

impl:protocol.studio-slice-dependencies · supplied depth bands with protected boundary boxes and lossless text · src/projections/studio/diagrams/slice.ts:10 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

14. A refinement drawing follows the capability mapbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.diagram-kinds.capability-tree

Design

5 design entries · 1 pinned declaration

Open questions

None.

Implementation binding: present

impl:protocol.studio-capability-diagrams · places refinement occurrences and bounded branches from the capability map · src/projections/studio/diagrams/capability.ts:101 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-diagram-source · escaped Mermaid flowchart and mindmap source in placed box order · src/projections/studio/diagrams/mermaid.ts:13 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

15. A Spec set draws the architecture it touchesbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.diagram-kinds.scoped-architecture

Design

5 design entries · 1 pinned declaration

Open questions

None.

Implementation binding: present

impl:protocol.studio-slice-architecture · selected component grid with distinct planned identities and complete unit edges · src/projections/studio/diagrams/slice.ts:219 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

16. The maturity map is drawn as a grid of countsbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.diagram-kinds.maturity-picture

Design

6 design entries · 1 pinned declaration

Open questions

None.

Implementation binding: present

impl:protocol.studio-maturity-map · places resolved Pack members by their stated rung and floor in authored order · src/projections/studio/pages/maturity-map.ts:7 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

17. A requirement drawing separates intent from realization and verificationbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.diagram-kinds.requirement-trace

Design

8 design entries · 1 pinned declaration

Open questions

None.

Implementation binding: present

impl:protocol.studio-requirement-diagram · folds requirement bindings by relation direction and claim and serializes exact relations · src/projections/studio/diagrams/requirement.ts:12 · role projection · component component:protocol.projections · layer edge · context protocol
impl:protocol.studio-requirement-view · selects Spec refiners, verifying examples and their recorded bindings · src/projections/studio/pages/requirement-view.ts:8 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

2 verifiers, 2 enabled · no verifying examples, 0 enabled

18. A slice reads a Pack as one design, with the architecture it touches and what each member needs nextbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.design-slice

Design

18 design entries · 15 pinned declarations

Decisions

Bindings are optional, plural, and may reference a design · stated ready
Architectural significance is annotated where it is realized · stated ready

Open questions

None.

Implementation binding: present

impl:protocol.design-slice-recipe · realizes the design slice in the shipped recipe catalog · test/self-hosting-design-slice.test.ts:148 · role projection

Design reference: present

impl:protocol.studio-slice-answer · full design slice answer consumed by the page and drawings · src/projections/studio/slice-answer.ts:1 · role contract · component component:protocol.projections · layer edge · context protocol

Verifier binding: present

15 verifiers, 15 enabled · 14 verifying examples, 14 enabled

19. Outside components stop at the touched components' neighborsexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.outside-components

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

20. Members rest on a chainexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.chain

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

21. A shaping decision comes before its memberexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.decision-backlink

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

22. A cycle shares a depthexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.dependency-cycle

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

23. An example folds without lending its readinessexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.folded-example

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

24. An example with its own dependency stays unfoldedexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.independent-example

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

25. An unanchored component design stays visibleexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.component-absent

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

26. An anchor alone does not realize a component designexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.component-unrelated

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

27. A realized component matches its declared valuesexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.component-matching

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

28. A realized component keeps its differing layer and uses apartexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.component-differing

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

29. An unreadable declared layer stays visibleexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.component-unreadable

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

30. A prerequisite reaches its satisfying componentexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.outside-satisfied

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

31. An unbound prerequisite invents no componentexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.outside-unbound

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

32. An outside prerequisite names the member it holdsexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.design-slice.outside-holding

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

33. A slice page shows a Pack's design as one wholebehavior · ready floor ready · 1 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.slice-page

Design

12 design entries · no pinned declarations

Open questions

non-blocking · question.exportCarriesSlice · line 38 · specs/consumers/spec-studio.slice-page.sdp.md:38 · 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

Implementation binding: present

impl:protocol.studio-slice-page · design slice summaries, member needs, architecture comparisons and boundary tables · src/projections/studio/pages/slice-page.ts:25 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

34. A roadmap states advisory priority in the graphdecision · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding none

spec:decisions.roadmap-priority

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: present

impl:protocol.pack-aggregate · Pack aggregate and model references · src/model/pack.ts:23 · role contract · component component:protocol.model · layer domain · context protocol
impl:protocol.pack-member-order · keeps manifest member order on the Pack node · src/extract/derive.ts:153 · role extractor · component component:protocol.extract · layer application · context protocol

Verifier binding: none

35. A roadmap orders the next bodies of work, and the graph says what each still needsbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.roadmap

Design

13 design entries · 10 pinned declarations

Decisions

A roadmap states advisory priority in the graph · stated ready

Open questions

None.

Implementation binding: present

impl:protocol.roadmap-recipe · realizes the roadmap in the shipped recipe catalog · test/roadmap.test.ts:20 · role projection

Design reference: none

Verifier binding: present

10 verifiers, 10 enabled · 9 verifying examples, 9 enabled

36. Built work stays on the roadmapexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.roadmap.built-work

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

37. A ready unbound part needs buildingexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.roadmap.buildable-part

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

38. A complete part waits for a statementexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.roadmap.statement-part

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

39. An unfinished part needs designexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.roadmap.design-part

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

40. A binding below ready remains driftexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.roadmap.drifting-part

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

41. A descendant without evidence names its holding clauseexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.roadmap.missing-evidence

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

42. A descendant question holds the entry for designexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.roadmap.blocking-part

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

43. A descendant names its outside parentexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.roadmap.outside-parent

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

44. Waiting statements keep dependency order against roadmap placesexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.roadmap.statement-order

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

45. The roadmap page shows the upcoming work in priority order, split by what it needsbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.spec-studio.roadmap-page

Design

5 design entries · no pinned declarations

Open questions

None.

Implementation binding: present

impl:protocol.studio-roadmap-page · renders roadmap needs, holding parts and the shared Markdown memo · src/projections/studio/pages/roadmap-page.ts:168 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

46. A roadmap renders as the forward section of a pull request descriptionbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:consumers.roadmap.memo

Design

11 design entries · no pinned declarations

Open questions

None.

Implementation binding: present

impl:protocol.roadmap-memo-recipe · realizes the roadmap memo in the shipped recipe catalog · test/roadmap.test.ts:27 · role projection
impl:protocol.studio-roadmap-page · renders roadmap needs, holding parts and the shared Markdown memo · src/projections/studio/pages/roadmap-page.ts:168 · role projection · component component:protocol.projections · layer edge · context protocol

Design reference: none

Verifier binding: present

2 verifiers, 2 enabled · no verifying examples, 0 enabled

47. Plan and review files stop carrying the delivery record once the roadmap and the pull request dodecision · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding none

spec:decisions.roadmap-over-plans

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: none

Verifier binding: none

48. The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requestsbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present

spec:protocol.roadmap-replaces-plans

Design

3 design entries · 2 pinned declarations

Decisions

Plan and review files stop carrying the delivery record once the roadmap and the pull request do · stated ready

Open questions

None.

Implementation binding: present

impl:protocol.roadmap-practice · realizes the roadmap handbook and its current-record gate · test/check-self-hosting-gates.test.ts:52 · role validator

Design reference: none

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

49. Roadmap views read releases, baselines and phases from git and the graphmodel · scoped floor scoped · next rung defined: waits on 1 unmet clause · 1 open, 1 blocking questions · implementation binding none · verifier binding none

spec:consumers.projections-model.roadmap-views

Next rung defined waits on 1 unmet clause:

no-blocking-open-questions · Spec has no blocking open question in intent.openQuestions.

Design

No design entries · no pinned declarations

Open questions

blocking · question.releaseReader · line 22 · specs/consumers/projections-model.roadmap-views.sdp.md:22 · 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 release

Implementation binding: none

Design reference: none

Verifier binding: none

Boundary

Rests on (43)

Spec	Stated rung	Implementation binding	Joined members
Design work reads its answers from catalog recipes `spec:consumers.agent-surface.design-recipes`	ready	present	dependsOn: spec:consumers.design-slice
Register questions stay executable graph recipes `spec:consumers.agent-surface.register-recipes`	ready	present	dependsOn: spec:consumers.roadmap.memo
Views speak binding language, never the internal fact name `spec:consumers.binding-language-views`	ready	present	dependsOn: spec:consumers.spec-studio.capability-map-page, spec:consumers.spec-studio.slice-page
A context bundle is composed per invocation within a stated budget `spec:consumers.context-bundle`	ready	present	dependsOn: spec:consumers.design-slice
Derived readiness renders beside the stated rung and warns in one direction `spec:consumers.derived-readiness-banner`	ready	present	dependsOn: spec:consumers.spec-studio.slice-page
The next body of work is planned from the graph, not from a prose index `spec:consumers.graph-first-planning`	ready	present	refines: spec:consumers.roadmap
A change proposal is addressed, based and checked before it lands `spec:consumers.intent-composition.proposal`	ready	present	dependsOn: spec:protocol.roadmap-replaces-plans
Recipe 49 renders a change proposal as the Markdown memo a person reviews `spec:consumers.intent-composition.proposal.memo`	ready	present	dependsOn: spec:consumers.roadmap.memo, spec:protocol.roadmap-replaces-plans
The Pack context carries the Pack's design `spec:consumers.pack-design`	ready	present	refines: spec:consumers.design-slice
Projections fan out from one graph without becoming truth stores `spec:consumers.projections-model`	ready	present	refines: spec:consumers.capability-map, spec:consumers.projections-model.roadmap-views
The readiness planner orders the statements a person can make `spec:consumers.readiness-planner`	ready	present	dependsOn: spec:consumers.design-slice, spec:consumers.roadmap
A Pack is read from a named perspective `spec:consumers.review-perspectives`	ready	present	dependsOn: spec:consumers.design-slice
The Spec Studio is a static HTML workbench over the one graph `spec:consumers.spec-studio`	ready	present	refines: spec:consumers.spec-studio.slice-page, spec:consumers.spec-studio.roadmap-page
The Studio renders from the reader's values and embeds only what its script reads `spec:consumers.spec-studio.data`	ready	present	dependsOn: spec:consumers.spec-studio.diagram-kinds.requirement-trace, spec:consumers.spec-studio.roadmap-page
A page takes each recipe answer from the recipe's shipped body `spec:consumers.spec-studio.data.recipe-answers`	ready	present	dependsOn: spec:consumers.spec-studio.slice-page
A diagram is laid out from graph values into SVG with a text equivalent `spec:consumers.spec-studio.diagrams`	ready	present	refines: spec:consumers.spec-studio.diagram-kinds, spec:consumers.spec-studio.diagram-kinds.legibility, spec:consumers.spec-studio.diagram-kinds.edge-routing dependsOn: spec:consumers.spec-studio.slice-page
The index says where the corpus stands and narrows every Spec `spec:consumers.spec-studio.index-page`	ready	present	dependsOn: spec:consumers.spec-studio.capability-map-page
Five lenses read the graph as Packs, capabilities, architecture, tests and evidence `spec:consumers.spec-studio.lenses`	ready	present	refines: spec:consumers.spec-studio.capability-map-page
The architecture lens draws components by context and layer, the planned beside the built `spec:consumers.spec-studio.lenses.architecture`	ready	present	refines: spec:consumers.spec-studio.lenses.architecture.unit-register dependsOn: spec:consumers.spec-studio.diagram-kinds.scoped-architecture
A Pack page shows the Pack's design as one card per member `spec:consumers.spec-studio.pack-page`	ready	present	dependsOn: spec:consumers.spec-studio.slice-page
A few custom elements filter, search, open and copy on a rendered page `spec:consumers.spec-studio.page-elements`	ready	present	dependsOn: spec:consumers.spec-studio.diagram-kinds.mermaid-source
`sdp studio` publishes the Studio as one page set `spec:consumers.spec-studio.publisher`	ready	present	dependsOn: spec:consumers.spec-studio.roadmap-page
The Studio reads on a phone as on a desktop `spec:consumers.spec-studio.responsive`	ready	present	dependsOn: spec:consumers.spec-studio.diagram-kinds.legibility
The Studio's shell frames every page with navigation, a rail and a canvas `spec:consumers.spec-studio.shell`	ready	present	dependsOn: spec:consumers.spec-studio.roadmap-page
Bindings are optional, plural, and may reference a design `spec:decisions.anchor-binding-grain`	ready	none	decidedBy: spec:protocol.significant-units-review, spec:consumers.design-slice
Architectural significance is annotated where it is realized `spec:decisions.architectural-annotation`	ready	none	decidedBy: spec:protocol.significant-units-review, spec:protocol.role-vocabulary, spec:consumers.design-slice
One Spec carries named delivery coordinates `spec:decisions.one-primitive`	ready	none	dependsOn: spec:decisions.epics-of-any-kind
Packs have a Markdown manifest carrier `spec:decisions.pack-markdown-carrier`	ready	none	refines: spec:decisions.roadmap-priority
Planning truths live in ruled graph homes `spec:decisions.planning-truths-placement`	ready	none	refines: spec:decisions.roadmap-priority, spec:decisions.roadmap-over-plans
The shipped projections stay frozen `spec:decisions.shipped-projections-frozen`	ready	none	decidedBy: spec:consumers.spec-studio.diagram-kinds.mermaid-source
The engine lays out every Studio diagram as static SVG when the page set is built `spec:decisions.studio-diagram-renderer`	ready	none	decidedBy: spec:consumers.spec-studio.diagram-kinds, spec:consumers.spec-studio.diagram-kinds.mermaid-source
Resolving bindings confer direct delivery facts `spec:extraction.delivery-facts`	ready	present	dependsOn: spec:consumers.capability-map
Carrier reification derives the one graph `spec:extraction.derive-graph`	ready	present	dependsOn: spec:extraction.executable-examples
An open question may name who decides it, its links, a provisional reading and a re-entry trigger `spec:model.open-question-fields`	ready	present	dependsOn: spec:consumers.design-slice, spec:consumers.spec-studio.slice-page, spec:consumers.roadmap
Components are designed ahead of their code `spec:model.planned-architecture`	ready	present	dependsOn: spec:consumers.spec-studio.diagram-kinds.scoped-architecture, spec:consumers.design-slice
A rule or flow entry may carry a key that addresses it `spec:model.rule-keys`	ready	present	dependsOn: spec:consumers.design-slice
Architecturally significant units are annotated where they are realized `spec:model.structural-patterns`	ready	present	dependsOn: spec:protocol.significant-units-review
CI run records are joined to verifiers in a view `spec:observation.run-evidence`	ready	present	dependsOn: spec:protocol.roadmap-replaces-plans
The Protocol authors and validates itself `spec:protocol.self-hosting`	ready	present	refines: spec:protocol.capability-epics, spec:protocol.roadmap-replaces-plans
The engine's structural self-binding covers its architecturally significant units `spec:protocol.structural-self-binding`	ready	present	refines: spec:protocol.significant-units-review, spec:protocol.role-vocabulary
The floor names what blocks the floor's next rung `spec:validation.next-rung-floor`	ready	present	dependsOn: spec:consumers.roadmap
Stated readiness must clear its floor `spec:validation.readiness-floor`	ready	present	dependsOn: spec:consumers.capability-map, spec:protocol.capability-epics
A ready Spec rests only on settled dependencies `spec:validation.typed-dependency-floor`	ready	present	dependsOn: spec:consumers.roadmap

Rested on by (10)

Spec	Stated rung	Implementation binding	Joined members
A Pack has a Markdown manifest carrier `spec:carrier.markdown-pack-authoring`	ready	present	decidedBy: spec:decisions.roadmap-priority
Designs are compared between a base commit and the working tree at entry grain `spec:consumers.design-diff`	ready	present	decidedBy: spec:decisions.roadmap-priority
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	present	dependsOn: spec:consumers.spec-studio.diagram-kinds.maturity-picture
A Spec page shows one Spec in collapsible panels, in a fixed order `spec:consumers.spec-studio.spec-page`	ready	present	dependsOn: spec:consumers.spec-studio.diagram-kinds.requirement-trace
The upgrade kit shows a corpus what it could adopt `spec:consumers.upgrade-kit`	ready	present	dependsOn: spec:consumers.capability-map, spec:consumers.roadmap
A bound example runs its contract steps against a fresh world `spec:extraction.example-runner`	ready	present	refines: spec:extraction.executable-examples
The build derives step and space contracts from graph examples `spec:extraction.executable-contracts`	ready	present	refines: spec:extraction.executable-examples
A Pack node keeps its members in authored order `spec:extraction.pack-member-order`	ready	present	decidedBy: spec:decisions.roadmap-priority
A Pack is a truth-free review aggregate `spec:model.pack-aggregate`	ready	present	decidedBy: spec:decisions.roadmap-priority
The Protocol removes its frozen plans, review reports and superseded concept material `spec:protocol.delivery-record-cleanup`	idea	none	refines: spec:protocol.roadmap-replaces-plans decidedBy: spec:decisions.roadmap-over-plans

Verified by (0)

None.

Superseded by (0)

None.

Members with no verifier binding

The graph records bindings and never runs. Decision records are left out: a decision never needs a verifier binding. The runs page, the tests lens and the Spec pages of the Specs their files verify show the run records as external evidence from test files.

The engine's architectural roles each name one pattern · spec:protocol.role-vocabulary · stated ready
Bound examples execute their authored steps · spec:extraction.executable-examples · stated ready
Roadmap views read releases, baselines and phases from git and the graph · spec:consumers.projections-model.roadmap-views · stated scoped

Findings

None.

Composing (0)

Composing needs the script.