Design slice: Design iteration

pack:design-iteration-v1

The design as a whole

11 members; 0 example members counted in their parents.
2 relations among members; deepest depth 2; 0 cycles.
0 members held below their stated next rung; 0 waiting only for their author.
26 outside Specs the slice rests on; 0 hold a member; 33 outside Specs rest on it.
10 components touched: 6 through members' code, 8 through what the slice rests on, 0 named by member designs; 4 outside components shown for context.
0 member component designs; 0 realized; 0 of those match.
8 decisions in scope; 0 state below ready.
0 open questions; 0 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:consumers.agent-surface.answer-shapes: Recipe answers fit an agent's context and explain their misses, depth 1, stated ready, floor ready
spec:model.rule-keys: A rule or flow entry may carry a key that addresses it, depth 1, stated ready, floor ready
spec:model.open-question-fields: An open question may name who decides it, its links, a provisional reading and a re-entry trigger, depth 1, stated ready, floor ready
spec:model.relation-reasons: An authored relation may carry its reason, depth 1, stated ready, floor ready
spec:consumers.design-diff: Designs are compared between a base commit and the working tree at entry grain, depth 1, stated ready, floor ready
spec:consumers.context-bundle: A context bundle is composed per invocation within a stated budget, depth 1, stated ready, floor ready
spec:consumers.review-perspectives: A Pack is read from a named perspective, depth 1, stated ready, floor ready
spec:consumers.intent-composition.proposal: A change proposal is addressed, based and checked before it lands, depth 2, stated ready, floor ready
spec:model.enrichment-lifecycle: Enrichment keeps one Spec while its detail changes, depth 1, stated ready, floor ready
spec:consumers.impact-graph.curation-assist: File-level imports show where curation is missing, depth 2, stated ready, floor ready
spec:consumers.impact-graph: Mechanical code structure stays inferred and apart from curated intent, depth 1, stated ready, floor ready
Outside this scope: spec:consumers.agent-surface: Agents script a visible typed graph, stated ready, floor ready
Outside this scope: spec:consumers.agent-surface.address-and-cycle-recipes: Address resolution and dependency cycles stay executable graph recipes, stated ready, floor ready
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.evaluation-sink: The evaluation sink runs one body and prints its return, stated ready, floor ready
Outside this scope: spec:consumers.agent-surface.recipe-parameters: Recipes take parameters as data and ship as runnable files, stated ready, floor ready
Outside this scope: spec:consumers.edit-model: Views compose scoped intent instead of patching canonical source, stated ready, floor ready
Outside this scope: spec:consumers.intent-composition: Composed intent hands off on one proposal shape, 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:decisions.adopt-the-nouns: Delivery nouns remain familiar without workflow gates, stated ready, floor ready
Outside this scope: spec:decisions.agent-front-door: The agent front door is one evaluation sink over the exported reader, 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.checked-mentions: A Spec id written in prose is a checked mention, 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.prose-ownership: Prose belongs to typed graph owners, stated ready, floor ready
Outside this scope: spec:decisions.roadmap-priority: A roadmap states advisory priority in the graph, 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:extraction.contract-declarations: Pinned declarations give an adopter a derived module to typecheck, 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:extraction.determinism: Committed source derives byte-identical output, stated ready, floor ready
Outside this scope: spec:extraction.entry-locations: The graph records where each addressable entry is written, stated ready, floor ready
Outside this scope: spec:model.core-model: The Protocol models delivery with one enrichable Spec, stated ready, floor ready
Outside this scope: spec:model.open-question-keys: An open question may carry a key that addresses it, 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.relations: Specs declare typed directed relations, stated ready, floor ready
Outside this scope: spec:model.spec-sections: Spec sections carry typed detail and direct verifier semantics, stated ready, floor ready
spec:consumers.impact-graph.curation-assist refines spec:consumers.impact-graph · declared
spec:consumers.intent-composition.proposal dependsOn spec:consumers.design-diff · declared
spec:consumers.agent-surface.answer-shapes refines spec:consumers.agent-surface · declared
spec:consumers.context-bundle refines spec:consumers.agent-surface · declared
spec:consumers.intent-composition.proposal dependsOn spec:consumers.agent-surface.address-and-cycle-recipes · declared — the check resolves entry-address scopes through address resolution
spec:consumers.agent-surface.answer-shapes dependsOn spec:consumers.agent-surface.design-recipes · declared
spec:consumers.context-bundle dependsOn spec:consumers.agent-surface.design-recipes · declared
spec:consumers.agent-surface.answer-shapes dependsOn spec:consumers.agent-surface.evaluation-sink · declared — a caller runs a shipped body, and wraps it in its own body, through the evaluation sink
spec:consumers.design-diff dependsOn spec:consumers.agent-surface.recipe-parameters · declared — the base graph is supplied as recipe-parameter data, including the KEY=@PATH file form
spec:consumers.intent-composition.proposal dependsOn spec:consumers.edit-model · declared
spec:consumers.intent-composition.proposal refines spec:consumers.intent-composition · declared
spec:consumers.review-perspectives dependsOn spec:consumers.pack-design · declared
spec:consumers.design-diff refines spec:consumers.projections-model · declared
spec:consumers.review-perspectives refines spec:consumers.projections-model · declared
spec:consumers.impact-graph refines spec:consumers.projections-model · declared
spec:model.open-question-fields decidedBy spec:decisions.adopt-the-nouns · declared — question fields describe the question without adding workflow state or gates
spec:consumers.context-bundle decidedBy spec:decisions.agent-front-door · declared
spec:consumers.impact-graph.curation-assist decidedBy spec:decisions.architectural-annotation · declared
spec:model.rule-keys decidedBy spec:decisions.checked-mentions · declared — rule addresses join the address law it rules
spec:model.open-question-fields decidedBy spec:decisions.planning-truths-placement · declared — a deferral's re-entry trigger rides its own blocking question, the home that decision rules
spec:model.relation-reasons decidedBy spec:decisions.prose-ownership · declared — the relation owns its reason as typed prose
spec:consumers.design-diff decidedBy spec:decisions.roadmap-priority · declared
spec:model.rule-keys decidedBy spec:decisions.shipped-projections-frozen · declared — keys stay off the frozen projections, which read the rule text unchanged
spec:model.enrichment-lifecycle dependsOn spec:extraction.contract-declarations · declared — a slimming candidate is a pinned declaration
spec:consumers.impact-graph dependsOn spec:extraction.derive-graph · declared
spec:consumers.design-diff constrainedBy spec:extraction.determinism · declared — equal sources derive equal graphs, so a difference records a source change
spec:model.rule-keys dependsOn spec:extraction.entry-locations · declared — adds rows to the location table
spec:model.open-question-fields dependsOn spec:extraction.entry-locations · declared — adds rows to the location table
spec:model.enrichment-lifecycle refines spec:model.core-model · declared
spec:model.open-question-fields refines spec:model.open-question-keys · declared
spec:model.rule-keys dependsOn spec:model.open-question-keys · declared
spec:consumers.impact-graph.curation-assist dependsOn spec:model.planned-architecture · declared — the report uses the component-design convention to identify unrealized planned components
spec:model.relation-reasons refines spec:model.relations · declared
spec:model.rule-keys refines spec:model.spec-sections · declared

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 2"]
    n0["A change proposal is addressed, based and checked before it lands, stated ready, floor ready, 0 example members folded in · spec:consumers.intent-composition.proposal"]
    n1["File-level imports show where curation is missing, stated ready, floor ready, 0 example members folded in · spec:consumers.impact-graph.curation-assist"]
  end
  subgraph depth1["Depth 1"]
    n2["9 members at depth 1, folded"]
  end
  subgraph depth2["Outside this scope"]
    n3["7 outside Specs, refines, folded"]
    n4["11 outside Specs, dependsOn, folded"]
    n5["8 outside Specs, decidedBy, folded"]
    n6["1 outside Specs, constrainedBy, folded"]
  end
  %% folded diagram.pack:design-iteration-v1.dependencies.fold.1: spec:consumers.agent-surface.answer-shapes, spec:model.rule-keys, spec:model.open-question-fields, spec:model.relation-reasons, spec:consumers.design-diff, spec:consumers.context-bundle, spec:consumers.review-perspectives, spec:model.enrichment-lifecycle, spec:consumers.impact-graph
  %% folded diagram.pack:design-iteration-v1.dependencies.outside.refines: spec:consumers.agent-surface, spec:consumers.intent-composition, spec:consumers.projections-model, spec:model.core-model, spec:model.open-question-keys, spec:model.relations, spec:model.spec-sections
  %% folded diagram.pack:design-iteration-v1.dependencies.outside.dependsOn: spec:consumers.agent-surface.address-and-cycle-recipes, spec:consumers.agent-surface.design-recipes, spec:consumers.agent-surface.evaluation-sink, spec:consumers.agent-surface.recipe-parameters, spec:consumers.edit-model, spec:consumers.pack-design, spec:extraction.contract-declarations, spec:extraction.derive-graph, spec:extraction.entry-locations, spec:model.open-question-keys, spec:model.planned-architecture
  %% folded diagram.pack:design-iteration-v1.dependencies.outside.decidedBy: spec:decisions.adopt-the-nouns, spec:decisions.agent-front-door, spec:decisions.architectural-annotation, spec:decisions.checked-mentions, spec:decisions.planning-truths-placement, spec:decisions.prose-ownership, spec:decisions.roadmap-priority, spec:decisions.shipped-projections-frozen
  %% folded diagram.pack:design-iteration-v1.dependencies.outside.constrainedBy: spec:extraction.determinism
  n2 -->|"constrainedBy · declared — equal sources derive equal graphs, so a difference records a source change"| n6
  %% count: 1; diagram.pack:design-iteration-v1.dependencies.fold.1 to diagram.pack:design-iteration-v1.dependencies.outside.constrainedBy
  n2 -->|"decidedBy · declared (7 relations)"| n5
  %% count: 7; diagram.pack:design-iteration-v1.dependencies.fold.1 to diagram.pack:design-iteration-v1.dependencies.outside.decidedBy
  n2 -->|"dependsOn · declared (10 relations)"| n4
  %% count: 10; diagram.pack:design-iteration-v1.dependencies.fold.1 to diagram.pack:design-iteration-v1.dependencies.outside.dependsOn
  n2 -->|"refines · declared (9 relations)"| n3
  %% count: 9; diagram.pack:design-iteration-v1.dependencies.fold.1 to diagram.pack:design-iteration-v1.dependencies.outside.refines
  n1 -->|"refines · declared"| n2
  %% count: 1; spec:consumers.impact-graph.curation-assist to diagram.pack:design-iteration-v1.dependencies.fold.1
  n1 -->|"decidedBy · declared"| n5
  %% count: 1; spec:consumers.impact-graph.curation-assist to diagram.pack:design-iteration-v1.dependencies.outside.decidedBy
  n1 -->|"dependsOn · declared — the report uses the component-design convention to identify unrealized planned components"| n4
  %% count: 1; spec:consumers.impact-graph.curation-assist to diagram.pack:design-iteration-v1.dependencies.outside.dependsOn
  n0 -->|"dependsOn · declared"| n2
  %% count: 1; spec:consumers.intent-composition.proposal to diagram.pack:design-iteration-v1.dependencies.fold.1
  n0 -->|"dependsOn · declared (2 relations)"| n4
  %% count: 2; spec:consumers.intent-composition.proposal to diagram.pack:design-iteration-v1.dependencies.outside.dependsOn
  n0 -->|"refines · declared"| n3
  %% count: 1; spec:consumers.intent-composition.proposal to diagram.pack:design-iteration-v1.dependencies.outside.refines

What each member needs next

Member	Depth	Rung	Design carried	Code
Recipe answers fit an agent's context and explain their misses `spec:consumers.agent-surface.answer-shapes` behavior	1	ready floor ready	5 rules10 entries2 declarations0 questions0 decisions0 of 0 verifying examples bound	1 implementing2 referencing
A rule or flow entry may carry a key that addresses it `spec:model.rule-keys` rule	1	ready floor ready	7 rules10 entries6 declarations0 questions2 decisions0 of 0 verifying examples bound	3 implementing0 referencing
An open question may name who decides it, its links, a provisional reading and a re-entry trigger `spec:model.open-question-fields` rule	1	ready floor ready	12 rules, 2 keyed7 entries1 declarations0 questions2 decisions1 of 1 verifying examples bound	2 implementing0 referencing
An authored relation may carry its reason `spec:model.relation-reasons` rule	1	ready floor ready	7 rules5 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound	2 implementing0 referencing
Designs are compared between a base commit and the working tree at entry grain `spec:consumers.design-diff` behavior	1	ready floor ready	11 rules8 entries4 declarations0 questions1 decisions0 of 0 verifying examples bound	1 implementing0 referencing
A context bundle is composed per invocation within a stated budget `spec:consumers.context-bundle` behavior	1	ready floor ready	19 rules, 9 keyed17 entries7 declarations0 questions1 decisions2 of 2 verifying examples bound	1 implementing0 referencing
A Pack is read from a named perspective `spec:consumers.review-perspectives` behavior	1	ready floor ready	8 rules, 1 keyed4 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound	1 implementing0 referencing
Enrichment keeps one Spec while its detail changes `spec:model.enrichment-lifecycle` model	1	ready floor ready	0 rules2 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound	1 implementing0 referencing
Mechanical code structure stays inferred and apart from curated intent `spec:consumers.impact-graph` behavior	1	ready floor ready	1 rules, 1 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound	1 implementing0 referencing
A change proposal is addressed, based and checked before it lands `spec:consumers.intent-composition.proposal` contract	2	ready floor ready	9 rules7 entries2 declarations0 questions0 decisions0 of 0 verifying examples bound	2 implementing0 referencing
File-level imports show where curation is missing `spec:consumers.impact-graph.curation-assist` behavior	2	ready floor ready	11 rules7 entries4 declarations0 questions1 decisions0 of 0 verifying examples bound	3 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:consumers.impact-graph.curation-assist, spec:consumers.impact-graph; 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 spec:consumers.impact-graph.curation-assist; references members none; code for rests on spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sink, spec:consumers.agent-surface.recipe-parameters, spec:extraction.determinism; member designs none
component:protocol.extract: the carrier and source pipeline, anchored, layer application, context protocol; satisfies members spec:model.rule-keys, spec:model.open-question-fields, spec:model.relation-reasons; references members none; code for rests on spec:extraction.derive-graph, spec:extraction.determinism, spec:extraction.entry-locations, spec:model.open-question-keys; member designs none
component:protocol.graph: the one graph and its semantic decisions, anchored, layer domain, context protocol; satisfies members none; references members none; code for rests on spec:extraction.derive-graph; member designs none
component:protocol.import: canonical conversion with a fidelity boundary, anchored, layer application, context protocol; satisfies members none; references members none; code for rests on spec:model.open-question-keys; member designs none
component:protocol.model: the authored contracts and stable ids, anchored, layer domain, context protocol; satisfies members none; references members none; code for rests on spec:model.core-model, spec:model.open-question-keys, spec:model.relations, spec:model.spec-sections; member designs none
component:protocol.projections: read-only output, layout and owned publication, anchored, layer edge, context protocol; satisfies members none; references members none; code for rests on spec:consumers.projections-model; member designs none
component:protocol.reader: the typed graph contract and body evaluator, anchored, layer application, context protocol; satisfies members none; references members spec:consumers.agent-surface.answer-shapes; code for rests on spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sink, spec:consumers.pack-design, spec:extraction.contract-declarations, spec:extraction.entry-locations; member designs none
component:protocol.studio-elements: optional browser behavior and proposal handoff, anchored, layer edge, context protocol; satisfies members spec:consumers.intent-composition.proposal; 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 spec:model.rule-keys; references members none; code for rests on spec:model.open-question-keys, spec:model.spec-sections; member designs none
component:protocol.codegen: contracts and registrar output, outside scope, anchored, layer application, context protocol
component:protocol.notation: the leaf step codec, outside scope, anchored, layer domain, context protocol
component:protocol.runner: provider-neutral example execution, outside scope, anchored, layer application, context protocol
component:protocol.testing: the generated registrar runtime, outside scope, anchored, layer adapter, 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.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.notation · 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.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.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.answer-shape-recipes implements spec:consumers.agent-surface.answer-shapes; no component
impl:protocol.authoring-grammar-recipes references spec:consumers.agent-surface.answer-shapes; no component
impl:protocol.authoring-grammar-recipes implements spec:model.rule-keys; no component
impl:protocol.authoring-grammar-recipes implements spec:model.open-question-fields; no component
impl:protocol.authoring-grammar-recipes implements spec:model.relation-reasons; no component
impl:protocol.design-diff-recipe implements spec:consumers.design-diff; no component
impl:protocol.context-bundle-recipe implements spec:consumers.context-bundle; no component
impl:protocol.perspective-filter-recipe implements spec:consumers.review-perspectives; no component
impl:protocol.proposal-schema-and-recipe implements spec:consumers.intent-composition.proposal; no component
impl:protocol.slimming-recipe implements spec:model.enrichment-lifecycle; no component
impl:protocol.curation-recipe implements spec:consumers.impact-graph.curation-assist; 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["the carrier and source pipeline, anchored, layer application, context protocol · component:protocol.extract"]
  n4["canonical conversion with a fidelity boundary, anchored, layer application, context protocol · component:protocol.import"]
  n5["the typed graph contract and body evaluator, anchored, layer application, context protocol · component:protocol.reader"]
  n6["outside scope, 2 components, application, folded"]
  %% folded outside.protocol.application: component:protocol.codegen, component:protocol.runner
  n7["the one graph and its semantic decisions, anchored, layer domain, context protocol · component:protocol.graph"]
  n8["the authored contracts and stable ids, anchored, layer domain, context protocol · component:protocol.model"]
  n9["one finding currency and ordered checks, anchored, layer domain, context protocol · component:protocol.validate"]
  n10["outside scope, 1 components, domain, folded"]
  %% folded outside.protocol.domain: component:protocol.notation
  n11["external runtime and source adapters, anchored, layer adapter, context protocol · component:protocol.adapters"]
  n12["outside scope, 1 components, adapter, folded"]
  %% folded outside.protocol.adapter: component:protocol.testing
  n11 -->|"uses · anchored (2 unit edges)"| n6
  %% count: 2; component:protocol.adapters to outside.protocol.application
  n0 -->|"uses · anchored"| n11
  %% count: 1; component:protocol.cli to component:protocol.adapters
  n0 -->|"uses · anchored"| n3
  %% count: 1; component:protocol.cli to component:protocol.extract
  n0 -->|"uses · anchored (2 unit edges)"| n7
  %% count: 2; component:protocol.cli to component:protocol.graph
  n0 -->|"uses · anchored"| n4
  %% count: 1; component:protocol.cli to component:protocol.import
  n0 -->|"uses · anchored"| n8
  %% 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"| n9
  %% count: 1; component:protocol.cli to component:protocol.validate
  n0 -->|"uses · anchored"| n6
  %% count: 1; component:protocol.cli to outside.protocol.application
  n3 -->|"uses · anchored (2 unit edges)"| n7
  %% count: 2; component:protocol.extract to component:protocol.graph
  n3 -->|"uses · anchored"| n8
  %% count: 1; component:protocol.extract to component:protocol.model
  n3 -->|"uses · anchored"| n9
  %% count: 1; component:protocol.extract to component:protocol.validate
  n3 -->|"uses · anchored"| n10
  %% count: 1; component:protocol.extract to outside.protocol.domain
  n7 -->|"uses · anchored"| n8
  %% count: 1; component:protocol.graph to component:protocol.model
  n7 -->|"uses · anchored"| n10
  %% count: 1; component:protocol.graph to outside.protocol.domain
  n4 -->|"uses · anchored"| n3
  %% count: 1; component:protocol.import to component:protocol.extract
  n4 -->|"uses · anchored"| n9
  %% count: 1; component:protocol.import to component:protocol.validate
  n4 -->|"uses · anchored"| n10
  %% count: 1; component:protocol.import to outside.protocol.domain
  n1 -->|"uses · anchored (2 unit edges)"| n3
  %% count: 2; component:protocol.projections to component:protocol.extract
  n1 -->|"uses · anchored"| n7
  %% count: 1; component:protocol.projections to component:protocol.graph
  n1 -->|"uses · anchored"| n8
  %% 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"| n9
  %% count: 1; component:protocol.projections to component:protocol.validate
  n1 -->|"uses · anchored"| n10
  %% count: 1; component:protocol.projections to outside.protocol.domain
  n5 -->|"uses · anchored (2 unit edges)"| n7
  %% count: 2; component:protocol.reader to component:protocol.graph
  n5 -->|"uses · anchored"| n8
  %% count: 1; component:protocol.reader to component:protocol.model
  n5 -->|"uses · anchored (2 unit edges)"| n9
  %% count: 2; component:protocol.reader to component:protocol.validate
  n5 -->|"uses · anchored"| n10
  %% count: 1; component:protocol.reader 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
  n9 -->|"uses · anchored (2 unit edges)"| n7
  %% count: 2; component:protocol.validate to component:protocol.graph
  n9 -->|"uses · anchored"| n8
  %% count: 1; component:protocol.validate to component:protocol.model
  n9 -->|"uses · anchored"| n10
  %% count: 1; component:protocol.validate to outside.protocol.domain
  n12 -->|"uses · anchored"| n11
  %% count: 1; outside.protocol.adapter to component:protocol.adapters
  n6 -->|"uses · anchored"| n7
  %% count: 1; outside.protocol.application to component:protocol.graph
  n6 -->|"uses · anchored"| n5
  %% count: 1; outside.protocol.application to component:protocol.reader
  n6 -->|"uses · anchored"| n9
  %% 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: File-level imports show where curation is missing, Mechanical code structure stays inferred and apart from curated intentMembers 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: File-level imports show where curation is missingMembers its code references: noneWhat the slice rests on, realized here: spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sink, spec:consumers.agent-surface.recipe-parameters, spec:extraction.determinismMember designs naming it: none
`component:protocol.extract` the carrier and source pipeline	application · protocol	Members its code satisfies: A rule or flow entry may carry a key that addresses it, An open question may name who decides it, its links, a provisional reading and a re-entry trigger, An authored relation may carry its reasonMembers its code references: noneWhat the slice rests on, realized here: spec:extraction.derive-graph, spec:extraction.determinism, spec:extraction.entry-locations, spec:model.open-question-keysMember designs naming it: none
`component:protocol.graph` the one graph and its semantic decisions	domain · protocol	Members its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:extraction.derive-graphMember designs naming it: none
`component:protocol.import` canonical conversion with a fidelity boundary	application · protocol	Members its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:model.open-question-keysMember designs naming it: none
`component:protocol.model` the authored contracts and stable ids	domain · protocol	Members its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:model.core-model, spec:model.open-question-keys, spec:model.relations, spec:model.spec-sectionsMember designs naming it: none
`component:protocol.projections` read-only output, layout and owned publication	edge · protocol	Members its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:consumers.projections-modelMember designs naming it: none
`component:protocol.reader` the typed graph contract and body evaluator	application · protocol	Members its code satisfies: noneMembers its code references: Recipe answers fit an agent's context and explain their missesWhat the slice rests on, realized here: spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sink, spec:consumers.pack-design, spec:extraction.contract-declarations, spec:extraction.entry-locationsMember designs naming it: none
`component:protocol.studio-elements` optional browser behavior and proposal handoff	edge · protocol	Members its code satisfies: A change proposal is addressed, based and checked before it landsMembers 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: A rule or flow entry may carry a key that addresses itMembers its code references: noneWhat the slice rests on, realized here: spec:model.open-question-keys, spec:model.spec-sectionsMember designs naming it: none

Member component designs

None.

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

component:protocol.codegen · contracts and registrar output · anchored · a touched component uses it; it uses a touched component
component:protocol.notation · the leaf step codec · anchored · a touched component uses it
component:protocol.runner · provider-neutral example execution · anchored · a touched component uses it
component:protocol.testing · the generated registrar runtime · anchored · it uses a touched component

Units bound to a member and to no component

impl:protocol.answer-shape-recipes implements Recipe answers fit an agent's context and explain their misses
impl:protocol.authoring-grammar-recipes references Recipe answers fit an agent's context and explain their misses
impl:protocol.authoring-grammar-recipes implements A rule or flow entry may carry a key that addresses it
impl:protocol.authoring-grammar-recipes implements An open question may name who decides it, its links, a provisional reading and a re-entry trigger
impl:protocol.authoring-grammar-recipes implements An authored relation may carry its reason
impl:protocol.design-diff-recipe implements Designs are compared between a base commit and the working tree at entry grain
impl:protocol.context-bundle-recipe implements A context bundle is composed per invocation within a stated budget
impl:protocol.perspective-filter-recipe implements A Pack is read from a named perspective
impl:protocol.proposal-schema-and-recipe implements A change proposal is addressed, based and checked before it lands
impl:protocol.slimming-recipe implements Enrichment keeps one Spec while its detail changes
impl:protocol.curation-recipe implements File-level imports show where curation is missing

Decisions in scope

Decision	Rung	In the slice	Shapes	Questions
Delivery nouns remain familiar without workflow gates `spec:decisions.adopt-the-nouns`	ready floor ready	outside	An open question may name who decides it, its links, a provisional reading and a re-entry trigger	0 open, 0 blocking
The agent front door is one evaluation sink over the exported reader `spec:decisions.agent-front-door`	ready floor ready	outside	A context bundle is composed per invocation within a stated budget	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	File-level imports show where curation is missing	0 open, 0 blocking
A Spec id written in prose is a checked mention `spec:decisions.checked-mentions`	ready floor ready	outside	A rule or flow entry may carry a key that addresses it	0 open, 0 blocking
Planning truths live in ruled graph homes `spec:decisions.planning-truths-placement`	ready floor ready	outside	An open question may name who decides it, its links, a provisional reading and a re-entry trigger	0 open, 0 blocking
Prose belongs to typed graph owners `spec:decisions.prose-ownership`	ready floor ready	outside	An authored relation may carry its reason	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	outside	Designs are compared between a base commit and the working tree at entry grain	0 open, 0 blocking
The shipped projections stay frozen `spec:decisions.shipped-projections-frozen`	ready floor ready	outside	A rule or flow entry may carry a key that addresses it	0 open, 0 blocking

Open questions in scope

None.

Where the slice meets the rest

Rests on (26)

Spec	Rung	Implementation binding	Joined members	Holds
Agents script a visible typed graph `spec:consumers.agent-surface`	ready floor ready	present	refines: Recipe answers fit an agent's context and explain their misses, A context bundle is composed per invocation within a stated budget	none
Address resolution and dependency cycles stay executable graph recipes `spec:consumers.agent-surface.address-and-cycle-recipes`	ready floor ready	present	dependsOn: A change proposal is addressed, based and checked before it lands	none
Design work reads its answers from catalog recipes `spec:consumers.agent-surface.design-recipes`	ready floor ready	present	dependsOn: Recipe answers fit an agent's context and explain their misses, A context bundle is composed per invocation within a stated budget	none
The evaluation sink runs one body and prints its return `spec:consumers.agent-surface.evaluation-sink`	ready floor ready	present	dependsOn: Recipe answers fit an agent's context and explain their misses	none
Recipes take parameters as data and ship as runnable files `spec:consumers.agent-surface.recipe-parameters`	ready floor ready	present	dependsOn: Designs are compared between a base commit and the working tree at entry grain	none
Views compose scoped intent instead of patching canonical source `spec:consumers.edit-model`	ready floor ready	none	dependsOn: A change proposal is addressed, based and checked before it lands	none
Composed intent hands off on one proposal shape `spec:consumers.intent-composition`	ready floor ready	none	refines: A change proposal is addressed, based and checked before it lands	none
The Pack context carries the Pack's design `spec:consumers.pack-design`	ready floor ready	present	dependsOn: A Pack is read from a named perspective	none
Projections fan out from one graph without becoming truth stores `spec:consumers.projections-model`	ready floor ready	present	refines: Designs are compared between a base commit and the working tree at entry grain, A Pack is read from a named perspective, Mechanical code structure stays inferred and apart from curated intent	none
Delivery nouns remain familiar without workflow gates `spec:decisions.adopt-the-nouns`	ready floor ready	none	decidedBy: An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none
The agent front door is one evaluation sink over the exported reader `spec:decisions.agent-front-door`	ready floor ready	none	decidedBy: A context bundle is composed per invocation within a stated budget	none
Architectural significance is annotated where it is realized `spec:decisions.architectural-annotation`	ready floor ready	none	decidedBy: File-level imports show where curation is missing	none
A Spec id written in prose is a checked mention `spec:decisions.checked-mentions`	ready floor ready	none	decidedBy: A rule or flow entry may carry a key that addresses it	none
Planning truths live in ruled graph homes `spec:decisions.planning-truths-placement`	ready floor ready	none	decidedBy: An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none
Prose belongs to typed graph owners `spec:decisions.prose-ownership`	ready floor ready	none	decidedBy: An authored relation may carry its reason	none
A roadmap states advisory priority in the graph `spec:decisions.roadmap-priority`	ready floor ready	none	decidedBy: Designs are compared between a base commit and the working tree at entry grain	none
The shipped projections stay frozen `spec:decisions.shipped-projections-frozen`	ready floor ready	none	decidedBy: A rule or flow entry may carry a key that addresses it	none
Pinned declarations give an adopter a derived module to typecheck `spec:extraction.contract-declarations`	ready floor ready	present	dependsOn: Enrichment keeps one Spec while its detail changes	none
Carrier reification derives the one graph `spec:extraction.derive-graph`	ready floor ready	present	dependsOn: Mechanical code structure stays inferred and apart from curated intent	none
Committed source derives byte-identical output `spec:extraction.determinism`	ready floor ready	present	constrainedBy: Designs are compared between a base commit and the working tree at entry grain	none
The graph records where each addressable entry is written `spec:extraction.entry-locations`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it, An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none
The Protocol models delivery with one enrichable Spec `spec:model.core-model`	ready floor ready	present	refines: Enrichment keeps one Spec while its detail changes	none
An open question may carry a key that addresses it `spec:model.open-question-keys`	ready floor ready	present	refines: An open question may name who decides it, its links, a provisional reading and a re-entry triggerdependsOn: A rule or flow entry may carry a key that addresses it	none
Components are designed ahead of their code `spec:model.planned-architecture`	ready floor ready	present	dependsOn: File-level imports show where curation is missing	none
Specs declare typed directed relations `spec:model.relations`	ready floor ready	present	refines: An authored relation may carry its reason	none
Spec sections carry typed detail and direct verifier semantics `spec:model.spec-sections`	ready floor ready	present	refines: A rule or flow entry may carry a key that addresses it	none

Rested on by (33)

Spec	Rung	Implementation binding	Joined members	Holds
The Markdown envelope is explicit and bounded `spec:carrier.envelope-contract`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it, An authored relation may carry its reason	none
Gherkin authoring enters the one graph `spec:carrier.gherkin-authoring`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it	none
The Markdown body accepts one closed form per section `spec:carrier.markdown-body-grammar`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it, An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none
Every prose value has one typed owner `spec:carrier.prose-ownership-rule`	ready floor ready	present	dependsOn: An open question may name who decides it, its links, a provisional reading and a re-entry trigger, An authored relation may carry its reason	none
Address resolution and dependency cycles stay executable graph recipes `spec:consumers.agent-surface.address-and-cycle-recipes`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it	none
Register questions stay executable graph recipes `spec:consumers.agent-surface.register-recipes`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it, An open question may name who decides it, its links, a provisional reading and a re-entry trigger, An authored relation may carry its reason	none
Authors move one Spec from intent to reviewed evidence `spec:consumers.authoring-on-ramp`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it, An open question may name who decides it, its links, a provisional reading and a re-entry trigger, An authored relation may carry its reason	none
A member larger than the budget is named, and no part is returned `spec:consumers.context-bundle.oversized-member-named`	ready floor ready	none	refines: A context bundle is composed per invocation within a stated budget	none
A Pack too large for one bundle reads whole in parts `spec:consumers.context-bundle.parts-cover-the-pack`	ready floor ready	none	refines: A context bundle is composed per invocation within a stated budget	none
Delivery sessions route work from current graph state `spec:consumers.delivery-session-on-ramp`	ready floor ready	present	dependsOn: Designs are compared between a base commit and the working tree at entry grain, A context bundle is composed per invocation within a stated budget, A Pack is read from a named perspective, A change proposal is addressed, based and checked before it lands, Enrichment keeps one Spec while its detail changes	none
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	present	dependsOn: A rule or flow entry may carry a key that addresses it, An open question may name who decides it, its links, a provisional reading and a re-entry trigger, A context bundle is composed per invocation within a stated budget, A Pack is read from a named perspective	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	dependsOn: An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none
Exhaustive symbol reach waits for a language-neutral identity `spec:consumers.impact-graph.symbol-reach`	idea floor scoped	none	refines: Mechanical code structure stays inferred and apart from curated intent	none
Recipe 49 renders a change proposal as the Markdown memo a person reviews `spec:consumers.intent-composition.proposal.memo`	ready floor ready	present	refines: A change proposal is addressed, based and checked before it lands	none
A design pass is followed and answered from the vault `spec:consumers.obsidian-vault.iteration`	ready floor ready	present	dependsOn: A change proposal is addressed, based and checked before it lands	none
The Pack context carries the Pack's design `spec:consumers.pack-design`	ready floor ready	present	dependsOn: An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none
The readiness planner orders the statements a person can make `spec:consumers.readiness-planner`	ready floor ready	present	dependsOn: An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none
A roadmap orders the next bodies of work, and the graph says what each still needs `spec:consumers.roadmap`	ready floor ready	present	dependsOn: An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none
The Studio reads two named inputs beside the graph, a base graph and run records `spec:consumers.spec-studio.data.inputs`	ready floor ready	present	dependsOn: Designs are compared between a base commit and the working tree at entry grain	none
The diff page shows what changed in the design since a base graph `spec:consumers.spec-studio.diff-page`	ready floor ready	present	dependsOn: Designs are compared between a base commit and the working tree at entry grain	none
A composing panel on every page gathers scoped intent for an agent `spec:consumers.spec-studio.intent-panel`	ready floor ready	present	dependsOn: A change proposal is addressed, based and checked before it lands	none
The tests lens shows how far each Spec's verification reaches `spec:consumers.spec-studio.lenses.tests`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it	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: An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none
A slice page shows a Pack's design as one whole `spec:consumers.spec-studio.slice-page`	ready floor ready	present	dependsOn: An open question may name who decides it, its links, a provisional reading and a re-entry trigger	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 rule or flow entry may carry a key that addresses it, An open question may name who decides it, its links, a provisional reading and a re-entry trigger, An authored relation may carry its reason	none
A Spec page's core shows the whole Spec, with an anchor for every entry `spec:consumers.spec-studio.spec-page.core`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it, An open question may name who decides it, its links, a provisional reading and a re-entry trigger, An authored relation may carry its reason	none
The panels for examples, targets, verifiers and evidence `spec:consumers.spec-studio.verification-panels`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it	none
Capability adoption counts where each capability is used and where it could apply `spec:consumers.upgrade-kit.capability-adoption`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it, An open question may name who decides it, its links, a provisional reading and a re-entry trigger, An authored relation may carry its reason, A Pack is read from a named perspective	none
The rule-key proposal keys every unkeyed rule as a change proposal `spec:consumers.upgrade-kit.rule-key-proposal`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it, A change proposal is addressed, based and checked before it lands	none
A TypeScript question list that cannot be read drops whole with a warning `spec:model.open-question-fields.dropped-list-warns`	ready floor ready	none	refines: An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none
A Model term may carry a key that addresses it `spec:model.term-addresses`	ready floor ready	present	dependsOn: A rule or flow entry may carry a key that addresses it	none
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	present	dependsOn: A change proposal is addressed, based and checked before it lands	none
Every Spec id written in prose resolves `spec:validation.prose-mentions`	ready floor ready	present	dependsOn: An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none

Verified by (3)

Spec	Rung	Implementation binding	Joined members	Holds
A member larger than the budget is named, and no part is returned `spec:consumers.context-bundle.oversized-member-named`	ready floor ready	none	verifies: A context bundle is composed per invocation within a stated budget	none
A Pack too large for one bundle reads whole in parts `spec:consumers.context-bundle.parts-cover-the-pack`	ready floor ready	none	verifies: A context bundle is composed per invocation within a stated budget	none
A TypeScript question list that cannot be read drops whole with a warning `spec:model.open-question-fields.dropped-list-warns`	ready floor ready	none	verifies: An open question may name who decides it, its links, a provisional reading and a re-entry trigger	none

Superseded by (0)

None.

Composing (0)

Composing needs the script.