Design slice: Corpus checks

pack:corpus-checks-v1

The design as a whole

16 members; 13 example members counted in their parents.
15 relations among members; deepest depth 3; 0 cycles.
0 members held below their stated next rung; 0 waiting only for their author.
9 outside Specs the slice rests on; 0 hold a member; 6 outside Specs rest on it.
6 components touched: 1 through members' code, 6 through what the slice rests on, 0 named by member designs; 6 outside components shown for context.
0 member component designs; 0 realized; 0 of those match.
1 decision 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:validation.corpus-rules: Corpus-authored rules run on the one validation path, depth 1, stated ready, floor ready
spec:validation.corpus-rules.error-finding-fails: An error from a corpus rule fails validation and leaves the Protocol's line alone, depth 2, stated ready, floor ready; example folded into spec:validation.corpus-rules
spec:validation.corpus-rules.warning-finding-informs: A warning from a corpus rule informs and passes, depth 2, stated ready, floor ready; example folded into spec:validation.corpus-rules
spec:validation.corpus-rules.malformed-finding-fails: A finding with no subject fails its rules file, depth 2, stated ready, floor ready; example folded into spec:validation.corpus-rules
spec:validation.corpus-rules.copies-contain-changes: A rules file that empties its graph leaves the next file's graph whole, depth 2, stated ready, floor ready; example folded into spec:validation.corpus-rules
spec:validation.corpus-rules.rules-edit-starts-a-cycle: Rewriting a rules file under node_modules starts a cycle that runs the new body, depth 2, stated ready, floor ready; example folded into spec:validation.corpus-rules
spec:validation.corpus-rules.params-edit-starts-a-cycle: Editing a parameter file starts a cycle that reads the new parameters, depth 2, stated ready, floor ready; example folded into spec:validation.corpus-rules
spec:validation.corpus-rules.unreadable-params-fail-one-file: A parameter file that stops being JSON fails only its own rules file, and the watcher runs on, depth 2, stated ready, floor ready; example folded into spec:validation.corpus-rules
spec:validation.architecture-constraints: Declared architecture rules are checked against anchored structure, depth 2, stated ready, floor ready
spec:validation.architecture-constraints.forbidden-layer-pair: A domain member that uses an infrastructure member breaks a forbidden pair, depth 3, stated ready, floor ready; example folded into spec:validation.architecture-constraints
spec:validation.architecture-constraints.isolated-context-as-rule: The walk named as a rules file fails validation on an isolation breach, depth 3, stated ready, floor ready; example folded into spec:validation.architecture-constraints
spec:validation.architecture-constraints.unstated-layer-unclassified: A component with no layer leaves its edge unclassified, depth 3, stated ready, floor ready; example folded into spec:validation.architecture-constraints
spec:model.planned-architecture: Components are designed ahead of their code, depth 1, stated ready, floor ready
spec:model.planned-architecture.unrealized-design: A component design no anchor satisfies is listed as unrealized, depth 2, stated ready, floor ready; example folded into spec:model.planned-architecture
spec:model.planned-architecture.differing-layer-and-uses: A realized component that differs from its design gives one row per field, depth 2, stated ready, floor ready; example folded into spec:model.planned-architecture
spec:model.planned-architecture.matching-design: A realized component that matches its design gives no row, depth 2, stated ready, floor ready; example folded into spec:model.planned-architecture
Outside this scope: spec:consumers.agent-surface: Agents script a visible typed graph, 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.validate-watch: Validation re-runs while an author edits carriers, 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:model.anchors: Source anchors bind code without carrying intent, 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:validation.diagnostic-rendering: One diagnostic currency, its location composed from structured fields, stated ready, floor ready
Outside this scope: spec:validation.two-check-families: Validation separates well-formedness from non-pretending, stated ready, floor ready
spec:model.planned-architecture.differing-layer-and-uses refines spec:model.planned-architecture · declared
spec:model.planned-architecture.matching-design refines spec:model.planned-architecture · declared
spec:model.planned-architecture.unrealized-design refines spec:model.planned-architecture · declared
spec:validation.architecture-constraints dependsOn spec:validation.corpus-rules · declared
spec:validation.architecture-constraints refines spec:validation.corpus-rules · declared — the architecture walk is a corpus-selected rule over anchored structure
spec:validation.architecture-constraints.forbidden-layer-pair refines spec:validation.architecture-constraints · declared
spec:validation.architecture-constraints.isolated-context-as-rule refines spec:validation.architecture-constraints · declared
spec:validation.architecture-constraints.unstated-layer-unclassified refines spec:validation.architecture-constraints · declared
spec:validation.corpus-rules.copies-contain-changes refines spec:validation.corpus-rules · declared
spec:validation.corpus-rules.error-finding-fails refines spec:validation.corpus-rules · declared
spec:validation.corpus-rules.malformed-finding-fails refines spec:validation.corpus-rules · declared
spec:validation.corpus-rules.params-edit-starts-a-cycle refines spec:validation.corpus-rules · declared
spec:validation.corpus-rules.rules-edit-starts-a-cycle refines spec:validation.corpus-rules · declared
spec:validation.corpus-rules.unreadable-params-fail-one-file refines spec:validation.corpus-rules · declared
spec:validation.corpus-rules.warning-finding-informs refines spec:validation.corpus-rules · declared
spec:validation.corpus-rules refines spec:consumers.agent-surface · declared — a corpus scripts the graph through the evaluation sink to report its own findings
spec:validation.corpus-rules dependsOn spec:consumers.agent-surface · declared
spec:validation.corpus-rules dependsOn spec:consumers.agent-surface.evaluation-sink · declared — a rules file holds the body the sink evaluates, with the sink's bindings and trust
spec:validation.corpus-rules dependsOn spec:consumers.agent-surface.recipe-parameters · declared — validate takes `--params` in the sink's grammar
spec:validation.corpus-rules dependsOn spec:consumers.validate-watch · declared — the watch loop reruns the named rules in each cycle
spec:validation.corpus-rules decidedBy spec:decisions.architectural-annotation · declared — architecture checks remain the corpus's own rules
spec:validation.architecture-constraints decidedBy spec:decisions.architectural-annotation · declared
spec:model.planned-architecture decidedBy spec:decisions.architectural-annotation · declared
spec:validation.architecture-constraints dependsOn spec:model.anchors · declared
spec:model.planned-architecture dependsOn spec:model.anchors · declared — a planned component is realized by a component anchor that satisfies its design
spec:model.planned-architecture refines spec:model.core-model · declared — planned components enrich Specs before code binds them
spec:validation.corpus-rules dependsOn spec:validation.diagnostic-rendering · declared — corpus findings use the shared diagnostic currency
spec:validation.corpus-rules constrainedBy spec:validation.two-check-families · 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["Declared architecture rules are checked against anchored structure, stated ready, floor ready, 3 example members folded in · spec:validation.architecture-constraints"]
  end
  subgraph depth1["Depth 1"]
    n1["Corpus-authored rules run on the one validation path, stated ready, floor ready, 7 example members folded in · spec:validation.corpus-rules"]
    n2["Components are designed ahead of their code, stated ready, floor ready, 3 example members folded in · spec:model.planned-architecture"]
  end
  subgraph depth2["Outside this scope"]
    n3["2 outside Specs, refines, folded"]
    n4["6 outside Specs, dependsOn, folded"]
    n5["1 outside Specs, decidedBy, folded"]
    n6["1 outside Specs, constrainedBy, folded"]
  end
  %% folded diagram.pack:corpus-checks-v1.dependencies.outside.refines: spec:consumers.agent-surface, spec:model.core-model
  %% folded diagram.pack:corpus-checks-v1.dependencies.outside.dependsOn: spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sink, spec:consumers.agent-surface.recipe-parameters, spec:consumers.validate-watch, spec:model.anchors, spec:validation.diagnostic-rendering
  %% folded diagram.pack:corpus-checks-v1.dependencies.outside.decidedBy: spec:decisions.architectural-annotation
  %% folded diagram.pack:corpus-checks-v1.dependencies.outside.constrainedBy: spec:validation.two-check-families
  n2 -->|"decidedBy · declared"| n5
  %% count: 1; spec:model.planned-architecture to diagram.pack:corpus-checks-v1.dependencies.outside.decidedBy
  n2 -->|"dependsOn · declared — a planned component is realized by a component anchor that satisfies its design"| n4
  %% count: 1; spec:model.planned-architecture to diagram.pack:corpus-checks-v1.dependencies.outside.dependsOn
  n2 -->|"refines · declared — planned components enrich Specs before code binds them"| n3
  %% count: 1; spec:model.planned-architecture to diagram.pack:corpus-checks-v1.dependencies.outside.refines
  n0 -->|"decidedBy · declared"| n5
  %% count: 1; spec:validation.architecture-constraints to diagram.pack:corpus-checks-v1.dependencies.outside.decidedBy
  n0 -->|"dependsOn · declared"| n4
  %% count: 1; spec:validation.architecture-constraints to diagram.pack:corpus-checks-v1.dependencies.outside.dependsOn
  n0 -->|"dependsOn, refines · declared"| n1
  %% count: 1; spec:validation.architecture-constraints to spec:validation.corpus-rules
  n1 -->|"constrainedBy · declared"| n6
  %% count: 1; spec:validation.corpus-rules to diagram.pack:corpus-checks-v1.dependencies.outside.constrainedBy
  n1 -->|"decidedBy · declared — architecture checks remain the corpus's own rules"| n5
  %% count: 1; spec:validation.corpus-rules to diagram.pack:corpus-checks-v1.dependencies.outside.decidedBy
  n1 -->|"dependsOn · declared (5 relations)"| n4
  %% count: 5; spec:validation.corpus-rules to diagram.pack:corpus-checks-v1.dependencies.outside.dependsOn
  n1 -->|"refines · declared — a corpus scripts the graph through the evaluation sink to report its own findings"| n3
  %% count: 1; spec:validation.corpus-rules to diagram.pack:corpus-checks-v1.dependencies.outside.refines

What each member needs next

Member	Depth	Rung	Design carried	Code
Corpus-authored rules run on the one validation path `spec:validation.corpus-rules` behavior	1	ready floor ready	16 rules, 10 keyed11 entries7 declarations0 questions1 decisions9 of 9 verifying examples bound	3 implementing0 referencing
7 example members folded in An error from a corpus rule fails validation and leaves the Protocol's line alone `spec:validation.corpus-rules.error-finding-fails` example · ready floor ready A warning from a corpus rule informs and passes `spec:validation.corpus-rules.warning-finding-informs` example · ready floor ready A finding with no subject fails its rules file `spec:validation.corpus-rules.malformed-finding-fails` example · ready floor ready A rules file that empties its graph leaves the next file's graph whole `spec:validation.corpus-rules.copies-contain-changes` example · ready floor ready Rewriting a rules file under node_modules starts a cycle that runs the new body `spec:validation.corpus-rules.rules-edit-starts-a-cycle` example · ready floor ready Editing a parameter file starts a cycle that reads the new parameters `spec:validation.corpus-rules.params-edit-starts-a-cycle` example · ready floor ready A parameter file that stops being JSON fails only its own rules file, and the watcher runs on `spec:validation.corpus-rules.unreadable-params-fail-one-file` example · ready floor ready
Components are designed ahead of their code `spec:model.planned-architecture` model	1	ready floor ready	0 rules6 entries1 declarations0 questions1 decisions3 of 3 verifying examples bound	1 implementing1 referencing
3 example members folded in A component design no anchor satisfies is listed as unrealized `spec:model.planned-architecture.unrealized-design` example · ready floor ready A realized component that differs from its design gives one row per field `spec:model.planned-architecture.differing-layer-and-uses` example · ready floor ready A realized component that matches its design gives no row `spec:model.planned-architecture.matching-design` example · ready floor ready
Declared architecture rules are checked against anchored structure `spec:validation.architecture-constraints` rule	2	ready floor ready	8 rules, 4 keyed6 entries3 declarations0 questions1 decisions3 of 3 verifying examples bound	1 implementing0 referencing
3 example members folded in A domain member that uses an infrastructure member breaks a forbidden pair `spec:validation.architecture-constraints.forbidden-layer-pair` example · ready floor ready The walk named as a rules file fails validation on an isolation breach `spec:validation.architecture-constraints.isolated-context-as-rule` example · ready floor ready A component with no layer leaves its edge unclassified `spec:validation.architecture-constraints.unstated-layer-unclassified` example · ready floor ready

The architecture it touches

Anchored components and member designs

Arrows: uses (anchored).

The diagram as text

component:protocol.cli: entry points, shared build and publication, anchored, layer edge, context protocol; satisfies members spec:validation.corpus-rules; references members none; code for rests on spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sink, spec:consumers.agent-surface.recipe-parameters, spec:consumers.validate-watch, spec:validation.diagnostic-rendering; member designs none
component:protocol.extract: the carrier and source pipeline, anchored, layer application, context protocol; satisfies members none; references members none; code for rests on spec:model.anchors; 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.anchors, spec:model.core-model; 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:validation.diagnostic-rendering; member designs none
component:protocol.reader: the typed graph contract and body evaluator, anchored, layer application, context protocol; satisfies members none; references members none; code for rests on spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sink; member designs none
component:protocol.validate: one finding currency and ordered checks, anchored, layer domain, context protocol; satisfies members none; references members none; code for rests on spec:model.anchors, spec:validation.diagnostic-rendering, spec:validation.two-check-families; member designs none
component:protocol.adapters: external runtime and source adapters, outside scope, anchored, layer adapter, context protocol
component:protocol.codegen: contracts and registrar output, outside scope, anchored, layer application, context protocol
component:protocol.graph: the one graph and its semantic decisions, outside scope, anchored, layer domain, context protocol
component:protocol.import: canonical conversion with a fidelity boundary, outside scope, anchored, layer application, context protocol
component:protocol.notation: the leaf step codec, outside scope, anchored, layer domain, context protocol
component:protocol.studio-elements: optional browser behavior and proposal handoff, outside scope, anchored, layer edge, context protocol
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.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.import uses component:protocol.extract · anchored
component:protocol.import uses component:protocol.validate · anchored
component:protocol.projections uses component:protocol.extract · anchored
impl:protocol.gherkin-view uses impl:protocol.gherkin-kind-policy · anchored
component:protocol.projections uses component:protocol.graph · anchored
component:protocol.projections uses component:protocol.model · anchored
component:protocol.projections uses component:protocol.notation · anchored
component:protocol.projections uses component:protocol.reader · anchored
impl:protocol.studio-recipes uses api:protocol.evaluate-body · anchored
impl:protocol.studio-recipes uses impl:protocol.reader · anchored
impl:protocol.vault-notes uses impl:protocol.reader · anchored
component:protocol.projections uses component:protocol.validate · anchored
component:protocol.reader uses component:protocol.graph · anchored
impl:protocol.reader uses impl:protocol.delivery-facts · anchored
component:protocol.reader uses component:protocol.model · anchored
component:protocol.reader uses component:protocol.notation · anchored
component:protocol.reader uses component:protocol.validate · anchored
impl:protocol.reader uses impl:protocol.next-rung-floor · anchored
component:protocol.studio-elements uses component:protocol.projections · anchored
component:protocol.studio-elements uses component:protocol.reader · 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.architecture-walk-recipe implements spec:validation.architecture-constraints; no component
impl:protocol.planned-components-recipe implements spec:model.planned-architecture; no component
impl:protocol.curation-recipe references spec:model.planned-architecture; 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["outside scope, 1 components, edge, folded"]
  %% folded outside.protocol.edge: component:protocol.studio-elements
  n3["the carrier and source pipeline, anchored, layer application, context protocol · component:protocol.extract"]
  n4["the typed graph contract and body evaluator, anchored, layer application, context protocol · component:protocol.reader"]
  n5["outside scope, 2 components, application, folded"]
  %% folded outside.protocol.application: component:protocol.codegen, component:protocol.import
  n6["the authored contracts and stable ids, anchored, layer domain, context protocol · component:protocol.model"]
  n7["one finding currency and ordered checks, anchored, layer domain, context protocol · component:protocol.validate"]
  n8["outside scope, 2 components, domain, folded"]
  %% folded outside.protocol.domain: component:protocol.graph, component:protocol.notation
  n9["outside scope, 1 components, adapter, folded"]
  %% folded outside.protocol.adapter: component:protocol.adapters
  n0 -->|"uses · anchored"| n3
  %% count: 1; component:protocol.cli to component:protocol.extract
  n0 -->|"uses · anchored"| n6
  %% 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"| n4
  %% count: 1; component:protocol.cli to component:protocol.reader
  n0 -->|"uses · anchored"| n7
  %% count: 1; component:protocol.cli to component:protocol.validate
  n0 -->|"uses · anchored"| n9
  %% count: 1; component:protocol.cli to outside.protocol.adapter
  n0 -->|"uses · anchored (2 unit edges)"| n5
  %% count: 2; component:protocol.cli to outside.protocol.application
  n0 -->|"uses · anchored (2 unit edges)"| n8
  %% count: 2; component:protocol.cli to outside.protocol.domain
  n3 -->|"uses · anchored"| n6
  %% count: 1; component:protocol.extract to component:protocol.model
  n3 -->|"uses · anchored"| n7
  %% count: 1; component:protocol.extract to component:protocol.validate
  n3 -->|"uses · anchored (3 unit edges)"| n8
  %% count: 3; component:protocol.extract to outside.protocol.domain
  n1 -->|"uses · anchored (2 unit edges)"| n3
  %% count: 2; component:protocol.projections to component:protocol.extract
  n1 -->|"uses · anchored"| n6
  %% count: 1; component:protocol.projections to component:protocol.model
  n1 -->|"uses · anchored (4 unit edges)"| n4
  %% count: 4; component:protocol.projections to component:protocol.reader
  n1 -->|"uses · anchored"| n7
  %% count: 1; component:protocol.projections to component:protocol.validate
  n1 -->|"uses · anchored (2 unit edges)"| n8
  %% count: 2; component:protocol.projections to outside.protocol.domain
  n4 -->|"uses · anchored"| n6
  %% count: 1; component:protocol.reader to component:protocol.model
  n4 -->|"uses · anchored (2 unit edges)"| n7
  %% count: 2; component:protocol.reader to component:protocol.validate
  n4 -->|"uses · anchored (3 unit edges)"| n8
  %% count: 3; component:protocol.reader to outside.protocol.domain
  n7 -->|"uses · anchored"| n6
  %% count: 1; component:protocol.validate to component:protocol.model
  n7 -->|"uses · anchored (3 unit edges)"| n8
  %% count: 3; component:protocol.validate to outside.protocol.domain
  n5 -->|"uses · anchored"| n3
  %% count: 1; outside.protocol.application to component:protocol.extract
  n5 -->|"uses · anchored"| n4
  %% count: 1; outside.protocol.application to component:protocol.reader
  n5 -->|"uses · anchored (2 unit edges)"| n7
  %% count: 2; outside.protocol.application to component:protocol.validate
  n8 -->|"uses · anchored"| n6
  %% count: 1; outside.protocol.domain to component:protocol.model
  n2 -->|"uses · anchored"| n1
  %% count: 1; outside.protocol.edge to component:protocol.projections
  n2 -->|"uses · anchored"| n4
  %% count: 1; outside.protocol.edge to component:protocol.reader

Components the slice touches

Component	Layer and context	Reached through
`component:protocol.cli` entry points, shared build and publication	edge · protocol	Members its code satisfies: Corpus-authored rules run on the one validation pathMembers 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:consumers.validate-watch, spec:validation.diagnostic-renderingMember designs naming it: none
`component:protocol.extract` the carrier and source pipeline	application · protocol	Members its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:model.anchorsMember 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.anchors, spec:model.core-modelMember 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:validation.diagnostic-renderingMember designs naming it: none
`component:protocol.reader` the typed graph contract and body evaluator	application · protocol	Members its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sinkMember designs naming it: none
`component:protocol.validate` one finding currency and ordered checks	domain · protocol	Members its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:model.anchors, spec:validation.diagnostic-rendering, spec:validation.two-check-familiesMember designs naming it: none

Member component designs

None.

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

component:protocol.adapters · external runtime and source adapters · anchored · a touched component uses it
component:protocol.codegen · contracts and registrar output · anchored · a touched component uses it; it uses a touched component
component:protocol.graph · the one graph and its semantic decisions · anchored · a touched component uses it; it uses a touched component
component:protocol.import · canonical conversion with a fidelity boundary · anchored · a touched component uses it; it uses a touched component
component:protocol.notation · the leaf step codec · anchored · a touched component uses it
component:protocol.studio-elements · optional browser behavior and proposal handoff · anchored · it uses a touched component

Units bound to a member and to no component

impl:protocol.architecture-walk-recipe implements Declared architecture rules are checked against anchored structure
impl:protocol.planned-components-recipe implements Components are designed ahead of their code
impl:protocol.curation-recipe references Components are designed ahead of their code

Decisions in scope

Decision	Rung	In the slice	Shapes	Questions
Architectural significance is annotated where it is realized `spec:decisions.architectural-annotation` refines spec:decisions.shipped-projections-frozen	ready floor ready	outside	Corpus-authored rules run on the one validation path, Declared architecture rules are checked against anchored structure, Components are designed ahead of their code	0 open, 0 blocking

Open questions in scope

None.

Where the slice meets the rest

Rests on (9)

Spec	Rung	Implementation binding	Joined members	Holds
Agents script a visible typed graph `spec:consumers.agent-surface`	ready floor ready	present	refines: Corpus-authored rules run on the one validation pathdependsOn: Corpus-authored rules run on the one validation path	none
The evaluation sink runs one body and prints its return `spec:consumers.agent-surface.evaluation-sink`	ready floor ready	present	dependsOn: Corpus-authored rules run on the one validation path	none
Recipes take parameters as data and ship as runnable files `spec:consumers.agent-surface.recipe-parameters`	ready floor ready	present	dependsOn: Corpus-authored rules run on the one validation path	none
Validation re-runs while an author edits carriers `spec:consumers.validate-watch`	ready floor ready	present	dependsOn: Corpus-authored rules run on the one validation path	none
Architectural significance is annotated where it is realized `spec:decisions.architectural-annotation`	ready floor ready	none	decidedBy: Corpus-authored rules run on the one validation path, Declared architecture rules are checked against anchored structure, Components are designed ahead of their code	none
Source anchors bind code without carrying intent `spec:model.anchors`	ready floor ready	present	dependsOn: Declared architecture rules are checked against anchored structure, Components are designed ahead of their code	none
The Protocol models delivery with one enrichable Spec `spec:model.core-model`	ready floor ready	present	refines: Components are designed ahead of their code	none
One diagnostic currency, its location composed from structured fields `spec:validation.diagnostic-rendering`	ready floor ready	present	dependsOn: Corpus-authored rules run on the one validation path	none
Validation separates well-formedness from non-pretending `spec:validation.two-check-families`	ready floor ready	present	constrainedBy: Corpus-authored rules run on the one validation path	none

Rested on by (6)

Spec	Rung	Implementation binding	Joined members	Holds
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: Components are designed ahead of their code	none
File-level imports show where curation is missing `spec:consumers.impact-graph.curation-assist`	ready floor ready	present	dependsOn: Components are designed ahead of their code	none
A Spec set draws the architecture it touches `spec:consumers.spec-studio.diagram-kinds.scoped-architecture`	ready floor ready	present	dependsOn: Components are designed ahead of their code	none
The architecture lens draws components by context and layer, the planned beside the built `spec:consumers.spec-studio.lenses.architecture`	ready floor ready	present	dependsOn: Components are designed ahead of their code	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: Components are designed ahead of their code	none
A corpus checks the register tokens its prose cites `spec:validation.external-registers`	ready floor ready	present	refines: Corpus-authored rules run on the one validation pathdependsOn: Corpus-authored rules run on the one validation path	none

Verified by (2)

Spec	Rung	Implementation binding	Joined members	Holds
The shipped dependency-cycles file fails a rules run on a cycle `spec:consumers.agent-surface.address-and-cycle-recipes.cycle-fails-a-rules-run`	ready floor ready	none	verifies: Corpus-authored rules run on the one validation path	none
The shipped address-resolution file fails a rules run on an address that names no entry `spec:consumers.agent-surface.address-and-cycle-recipes.unresolved-address-fails-a-rules-run`	ready floor ready	none	verifies: Corpus-authored rules run on the one validation path	none

Superseded by (0)

None.

Composing (0)

Composing needs the script.