Design slice: Design management
pack:design-management-v1Read the Pack member by member
The design as a whole
- 24 members; 0 example members counted in their parents.
- 22 relations among members; deepest depth 5; 0 cycles.
- 2 members held below their stated next rung; 0 waiting only for their author.
- 42 outside Specs the slice rests on; 0 hold a member; 69 outside Specs rest on it.
- 11 components touched: 6 through members' code, 10 through what the slice rests on, 0 named by member designs; 2 outside components shown for context.
- 0 member component designs; 0 realized; 0 of those match.
- 10 decisions in scope; 0 state below ready.
- 5 open questions; 2 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
Depths are structural, never phases, dates or priority. Dashed relations order nothing. The text keeps every member and original relation.
Shown as text: this drawing exceeds the height budget of 2000 pixels after folding.
The diagram as text
- spec:decisions.pack-design-page: The Design Review's Pack page presents the Pack's design, depth 4, stated ready, floor ready
- spec:consumers.pack-design: The Pack context carries the Pack's design, depth 3, stated ready, floor ready
- spec:consumers.design-review.pack-design-page: A Pack page shows where the Pack's design stands, depth 5, stated ready, floor ready
- spec:extraction.entry-locations: The graph records where each addressable entry is written, depth 1, stated ready, floor ready
- spec:consumers.agent-surface.recipe-parameters: Recipes take parameters as data and ship as runnable files, depth 1, stated ready, floor ready
- spec:consumers.agent-surface.design-recipes: Design work reads its answers from catalog recipes, depth 4, stated ready, floor ready
- spec:consumers.agent-surface.example-space-coverage: Example spaces report which values their examples cover, depth 5, stated ready, floor ready
- spec:consumers.engine-provenance: The CLI names the engine that produced a result, depth 1, stated ready, floor ready
- spec:consumers.validate-watch: Validation re-runs while an author edits carriers, depth 1, stated ready, floor ready
- spec:model.design-maturity: What a Spec's design carries is derived, beside its readiness, depth 4, stated ready, floor ready
- spec:model.planned-architecture: Components are designed ahead of their code, 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 2, stated ready, floor ready
- spec:model.rule-keys: A rule or flow entry may carry a key that addresses it, depth 2, stated ready, floor ready
- spec:model.relation-reasons: An authored relation may carry its reason, depth 1, stated ready, floor ready
- spec:consumers.review-perspectives: A Pack is read from a named perspective, depth 4, stated ready, floor ready
- spec:consumers.context-bundle: A context bundle is composed per invocation within a stated budget, depth 5, stated ready, floor ready
- spec:consumers.design-diff: Designs are compared between a base commit and the working tree at entry grain, depth 2, stated ready, floor ready
- spec:consumers.intent-composition.proposal: A change proposal is addressed, based and checked before it lands, depth 3, stated ready, floor ready
- spec:consumers.reference-projection: A reference projection serves a reader outside the repository, depth 1, stated idea, floor idea
- spec:consumers.structural-mermaid: Mermaid diagrams can be rooted at code units, depth 1, stated scoped, floor scoped
- spec:validation.superseded-decision-signal: A Spec shaped by a superseded decision warns, depth 2, stated ready, floor ready
- spec:validation.architecture-constraints: Declared architecture rules are checked against anchored structure, depth 3, stated ready, floor ready
- spec:validation.corpus-rules: Corpus-authored rules run on the one validation path, depth 2, stated ready, floor ready
- spec:observation.run-evidence: CI run records are joined to verifiers in a view, depth 2, stated ready, floor ready
- Outside this scope: spec:carrier.slot-notation: Slot notation declares, binds, and refuses to guess, stated ready, floor ready
- Outside this scope: spec:consumers.adopter-on-ramp: An adopter learns graph homes, carrier grammar and shipped paths from the on-ramps, 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.evaluation-sink: The evaluation sink runs one body and prints its return, stated ready, floor ready
- Outside this scope: spec:consumers.agent-surface.register-recipes: Register questions stay executable graph recipes, stated ready, floor ready
- Outside this scope: spec:consumers.authoring-on-ramp: Authors move one Spec from intent to reviewed evidence, stated ready, floor ready
- Outside this scope: spec:consumers.binding-language-views: Views speak binding language, never the internal fact name, stated ready, floor ready
- Outside this scope: spec:consumers.command-line: Every verb answers --help, and one verb writes every projection root, stated ready, floor ready
- Outside this scope: spec:consumers.derived-readiness-banner: Derived readiness renders beside the stated rung and warns in one direction, stated ready, floor ready
- Outside this scope: spec:consumers.design-review: Design Review renders graph context without becoming a gate, 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.projections-model: Projections fan out from one graph without becoming truth stores, stated ready, floor ready
- Outside this scope: spec:consumers.reader: The reader bridges agent entry points to composable graph context, stated ready, floor ready
- Outside this scope: spec:consumers.spec-studio.lenses.architecture: The architecture lens draws components by context and layer, the planned beside the built, stated ready, floor ready
- Outside this scope: spec: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.binding-not-liveness: Bindings state existence, not liveness, 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.one-validation-path: Validation follows one graph, 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.delivery-facts: Resolving bindings confer direct delivery facts, stated ready, floor ready
- Outside this scope: spec:extraction.derive-graph: Carrier reification derives the one graph, stated ready, floor ready
- Outside this scope: spec:extraction.determinism: Committed source derives byte-identical output, stated ready, floor ready
- Outside this scope: spec:extraction.excludes: Extraction exclusions are strict consumer input, stated ready, floor ready
- Outside this scope: spec:extraction.executable-contracts: The build derives step and space contracts from graph examples, stated ready, floor ready
- Outside this scope: spec:extraction.pack-member-order: A Pack node keeps its members in authored order, 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:model.open-question-keys: An open question may carry a key that addresses it, 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
- 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.next-rung-floor: The floor names what blocks the floor's next rung, stated ready, floor ready
- Outside this scope: spec:validation.two-check-families: Validation separates well-formedness from non-pretending, stated ready, floor ready
- Outside this scope: spec:validation.warn-level-signals: Missing connective evidence warns without failing, stated ready, floor ready
- spec:consumers.agent-surface.design-recipes dependsOn spec:consumers.agent-surface.recipe-parameters · declared
- spec:consumers.agent-surface.design-recipes dependsOn spec:consumers.pack-design · declared
- spec:consumers.agent-surface.example-space-coverage refines spec:consumers.agent-surface.design-recipes · declared
- spec:consumers.context-bundle dependsOn spec:consumers.agent-surface.design-recipes · declared
- 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.design-review.pack-design-page decidedBy spec:decisions.pack-design-page · declared
- spec:consumers.design-review.pack-design-page dependsOn spec:consumers.pack-design · declared
- spec:consumers.intent-composition.proposal dependsOn spec:consumers.design-diff · declared
- spec:consumers.pack-design dependsOn spec:extraction.entry-locations · declared
- spec:consumers.pack-design dependsOn spec:model.open-question-fields · declared — each listed open question carries its fields
- spec:consumers.review-perspectives dependsOn spec:consumers.pack-design · declared
- spec:decisions.pack-design-page dependsOn spec:consumers.pack-design · declared
- spec:decisions.pack-design-page refines spec:consumers.design-review.pack-design-page · declared, orders nothing
- spec:model.design-maturity dependsOn spec:consumers.pack-design · declared
- spec:model.open-question-fields dependsOn spec:extraction.entry-locations · declared — adds rows to the location table
- spec:model.rule-keys dependsOn spec:extraction.entry-locations · declared — adds rows to the location table
- spec:observation.run-evidence dependsOn spec:consumers.agent-surface.recipe-parameters · declared — the caller passes run records to the recipe as data
- 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.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.superseded-decision-signal dependsOn spec:extraction.entry-locations · declared — the warning takes its line from the location row of the decidedBy target it names
- spec:consumers.agent-surface.example-space-coverage dependsOn spec:carrier.slot-notation · declared
- spec:consumers.engine-provenance dependsOn spec:consumers.adopter-on-ramp · declared — an adopter pinned to a build asks the CLI the adopter on-ramp points it to which build it runs
- spec:consumers.agent-surface.recipe-parameters refines spec:consumers.agent-surface · declared
- spec:consumers.context-bundle refines spec:consumers.agent-surface · 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:consumers.intent-composition.proposal dependsOn spec:consumers.agent-surface.address-and-cycle-recipes · declared — the check resolves entry-address scopes through address resolution
- 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:consumers.agent-surface.design-recipes refines spec:consumers.agent-surface.register-recipes · declared
- spec:consumers.validate-watch refines spec:consumers.authoring-on-ramp · declared
- spec:consumers.design-review.pack-design-page dependsOn spec:consumers.binding-language-views · declared
- spec:consumers.engine-provenance refines spec:consumers.command-line · declared — the version flag is one more answer the command line gives an adopter
- spec:consumers.design-review.pack-design-page dependsOn spec:consumers.derived-readiness-banner · declared — the member table renders the stated rung and floor reached as this rule specifies
- spec:consumers.design-review.pack-design-page refines spec:consumers.design-review · declared
- 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 refines spec:consumers.projections-model · declared
- spec:consumers.design-diff refines spec:consumers.projections-model · declared
- spec:consumers.reference-projection refines spec:consumers.projections-model · declared
- spec:consumers.structural-mermaid refines spec:consumers.projections-model · declared
- spec:observation.run-evidence refines spec:consumers.projections-model · declared — run records inform a view without becoming graph facts
- spec:consumers.pack-design refines spec:consumers.reader · declared
- spec:consumers.structural-mermaid dependsOn spec:consumers.spec-studio.lenses.architecture · declared — the lens draws the component diagram rooted at code units this Spec asked for
- 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.agent-surface.recipe-parameters decidedBy spec:decisions.agent-front-door · declared
- spec:consumers.context-bundle decidedBy spec:decisions.agent-front-door · declared
- spec:consumers.pack-design decidedBy spec:decisions.architectural-annotation · declared — a code unit binding carries the role, layer and context its anchors state
- spec:model.planned-architecture decidedBy spec:decisions.architectural-annotation · declared
- spec:validation.architecture-constraints decidedBy spec:decisions.architectural-annotation · declared
- spec:validation.corpus-rules decidedBy spec:decisions.architectural-annotation · declared — architecture checks remain the corpus's own rules
- spec:observation.run-evidence decidedBy spec:decisions.binding-not-liveness · declared
- spec:model.rule-keys decidedBy spec:decisions.checked-mentions · declared — rule addresses join the address law it rules
- spec:consumers.validate-watch dependsOn spec:decisions.one-validation-path · declared
- 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:validation.superseded-decision-signal decidedBy spec:decisions.planning-truths-placement · declared — supersedes replaces a decision whole and refines narrows it
- 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:decisions.pack-design-page refines spec:decisions.shipped-projections-frozen · declared — carves out the Pack page, which renders the Pack design
- spec:model.rule-keys decidedBy spec:decisions.shipped-projections-frozen · declared — keys stay off the frozen projections, which read the rule text unchanged
- spec:consumers.structural-mermaid decidedBy spec:decisions.shipped-projections-frozen · declared
- spec:consumers.pack-design dependsOn spec:extraction.contract-declarations · declared
- spec:observation.run-evidence dependsOn spec:extraction.delivery-facts · declared — the view reads verifier bindings while leaving their delivery facts unchanged
- spec:extraction.entry-locations refines spec:extraction.derive-graph · declared
- spec:extraction.entry-locations constrainedBy spec:extraction.determinism · declared
- spec:consumers.engine-provenance constrainedBy spec:extraction.determinism · declared
- spec:consumers.design-diff constrainedBy spec:extraction.determinism · declared — equal sources derive equal graphs, so a difference records a source change
- spec:consumers.validate-watch dependsOn spec:extraction.excludes · declared
- spec:consumers.agent-surface.example-space-coverage dependsOn spec:extraction.executable-contracts · declared — its decoded slots and bound points reuse the space-contract interpretation
- spec:consumers.pack-design dependsOn spec:extraction.pack-member-order · declared
- spec:model.planned-architecture dependsOn spec:model.anchors · declared — a planned component is realized by a component anchor that satisfies its design
- spec:validation.architecture-constraints dependsOn spec:model.anchors · declared
- spec:model.design-maturity refines spec:model.core-model · declared
- spec:model.planned-architecture refines spec:model.core-model · declared — planned components enrich Specs before code binds them
- spec:model.open-question-fields refines spec:model.open-question-keys · declared
- spec:extraction.entry-locations dependsOn spec:model.open-question-keys · declared
- spec:model.rule-keys dependsOn spec:model.open-question-keys · declared
- spec:model.relation-reasons refines spec:model.relations · declared
- spec:validation.superseded-decision-signal dependsOn spec:model.relations · declared — its supersedes term keeps a replaced record only while a reader still needs its text, so the edges the signal reads are records a corpus chose to keep
- spec:model.rule-keys refines spec:model.spec-sections · declared
- spec:validation.corpus-rules dependsOn spec:validation.diagnostic-rendering · declared — corpus findings use the shared diagnostic currency
- spec:consumers.pack-design dependsOn spec:validation.next-rung-floor · declared
- spec:validation.corpus-rules constrainedBy spec:validation.two-check-families · declared
- spec:validation.superseded-decision-signal refines spec:validation.warn-level-signals · declared
What each member needs next
| Member | Depth | Rung | Next rung | Design carried | Code |
|---|---|---|---|---|---|
The graph records where each addressable entry is writtenspec:extraction.entry-locationsbehavior | 1 | ready floor ready | 7 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound | 3 implementing1 referencing | |
Recipes take parameters as data and ship as runnable filesspec:consumers.agent-surface.recipe-parametersbehavior | 1 | ready floor ready | 8 rules, 3 keyed2 entries2 declarations0 questions1 decisions0 of 0 verifying examples bound | 4 implementing0 referencing | |
The CLI names the engine that produced a resultspec:consumers.engine-provenancebehavior | 1 | ready floor ready | 4 rules1 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound | 2 implementing0 referencing | |
Validation re-runs while an author edits carriersspec:consumers.validate-watchbehavior | 1 | ready floor ready | 5 rules, 1 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound | 1 implementing0 referencing | |
Components are designed ahead of their codespec:model.planned-architecturemodel | 1 | ready floor ready | 0 rules6 entries1 declarations0 questions1 decisions3 of 3 verifying examples bound | 1 implementing1 referencing | |
An authored relation may carry its reasonspec:model.relation-reasonsrule | 1 | ready floor ready | 7 rules5 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound | 2 implementing0 referencing | |
A reference projection serves a reader outside the repositoryspec:consumers.reference-projectionbehavior | 1 | idea floor idea | next scoped:
| 0 rules0 entries0 declarations2 questions, 1 blocking0 decisions0 of 0 verifying examples bound | 0 implementing0 referencing |
Mermaid diagrams can be rooted at code unitsspec:consumers.structural-mermaidbehavior | 1 | scoped floor scoped | next defined:
| 1 rules, 1 keyed0 entries0 declarations1 questions, 1 blocking1 decisions0 of 0 verifying examples bound | 0 implementing0 referencing |
An open question may name who decides it, its links, a provisional reading and a re-entry triggerspec:model.open-question-fieldsrule | 2 | ready floor ready | 12 rules, 2 keyed7 entries1 declarations0 questions2 decisions1 of 1 verifying examples bound | 2 implementing0 referencing | |
A rule or flow entry may carry a key that addresses itspec:model.rule-keysrule | 2 | ready floor ready | 7 rules10 entries6 declarations0 questions2 decisions0 of 0 verifying examples bound | 3 implementing0 referencing | |
Designs are compared between a base commit and the working tree at entry grainspec:consumers.design-diffbehavior | 2 | ready floor ready | 11 rules8 entries4 declarations0 questions1 decisions0 of 0 verifying examples bound | 1 implementing0 referencing | |
A Spec shaped by a superseded decision warnsspec:validation.superseded-decision-signalrule | 2 | ready floor ready | 10 rules, 10 keyed10 entries7 declarations0 questions1 decisions9 of 9 verifying examples bound | 1 implementing0 referencing | |
Corpus-authored rules run on the one validation pathspec:validation.corpus-rulesbehavior | 2 | ready floor ready | 16 rules, 10 keyed11 entries7 declarations0 questions1 decisions9 of 9 verifying examples bound | 3 implementing0 referencing | |
CI run records are joined to verifiers in a viewspec:observation.run-evidencebehavior | 2 | ready floor ready | 9 rules, 7 keyed7 entries5 declarations1 questions1 decisions2 of 2 verifying examples bound | 2 implementing0 referencing | |
The Pack context carries the Pack's designspec:consumers.pack-designbehavior | 3 | ready floor ready | 8 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound | 1 implementing0 referencing | |
A change proposal is addressed, based and checked before it landsspec:consumers.intent-composition.proposalcontract | 3 | ready floor ready | 9 rules7 entries2 declarations0 questions0 decisions0 of 0 verifying examples bound | 2 implementing0 referencing | |
Declared architecture rules are checked against anchored structurespec:validation.architecture-constraintsrule | 3 | ready floor ready | 8 rules, 4 keyed6 entries3 declarations0 questions1 decisions3 of 3 verifying examples bound | 1 implementing0 referencing | |
The Design Review's Pack page presents the Pack's designspec:decisions.pack-design-pagedecision | 4 | ready floor ready | 0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound | 0 implementing1 referencing | |
Design work reads its answers from catalog recipesspec:consumers.agent-surface.design-recipesbehavior | 4 | ready floor ready | 6 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound | 1 implementing0 referencing | |
What a Spec's design carries is derived, beside its readinessspec:model.design-maturitymodel | 4 | ready floor ready | 0 rules0 entries0 declarations1 questions0 decisions0 of 0 verifying examples bound | 1 implementing0 referencing | |
A Pack is read from a named perspectivespec:consumers.review-perspectivesbehavior | 4 | ready floor ready | 8 rules, 1 keyed4 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound | 1 implementing0 referencing | |
A Pack page shows where the Pack's design standsspec:consumers.design-review.pack-design-pagebehavior | 5 | ready floor ready | 7 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound | 1 implementing1 referencing | |
Example spaces report which values their examples coverspec:consumers.agent-surface.example-space-coveragebehavior | 5 | ready floor ready | 7 rules, 7 keyed7 entries5 declarations0 questions0 decisions2 of 2 verifying examples bound | 2 implementing0 referencing | |
A context bundle is composed per invocation within a stated budgetspec:consumers.context-bundlebehavior | 5 | ready floor ready | 19 rules, 9 keyed17 entries7 declarations0 questions1 decisions2 of 2 verifying examples bound | 1 implementing0 referencing |
The architecture it touches
Arrows: uses (anchored).
The diagram as text
- component:protocol.cli: entry points, shared build and publication, anchored, layer edge, context protocol; satisfies members spec:consumers.agent-surface.recipe-parameters, spec:consumers.engine-provenance, spec:consumers.validate-watch, spec:validation.corpus-rules; references members none; code for rests on spec:consumers.adopter-on-ramp, spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sink, spec:consumers.authoring-on-ramp, spec:consumers.command-line, spec:extraction.determinism, spec:validation.diagnostic-rendering; member designs none
- component:protocol.codegen: contracts and registrar output, anchored, layer application, context protocol; satisfies members none; references members none; code for rests on spec:extraction.executable-contracts; member designs none
- component:protocol.extract: the carrier and source pipeline, anchored, layer application, context protocol; satisfies members spec:extraction.entry-locations, spec:model.open-question-fields, spec:model.rule-keys, spec:model.relation-reasons; references members none; code for rests on spec:extraction.derive-graph, spec:extraction.determinism, spec:extraction.excludes, spec:extraction.pack-member-order, spec:model.anchors, 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.delivery-facts, spec:extraction.derive-graph, spec:extraction.executable-contracts; 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.anchors, spec:model.core-model, spec:model.open-question-keys, spec:model.relations, spec:model.spec-sections; member designs none
- component:protocol.notation: the leaf step codec, anchored, layer domain, context protocol; satisfies members none; references members none; code for rests on spec:carrier.slot-notation; member designs none
- component:protocol.projections: read-only output, layout and owned publication, anchored, layer edge, context protocol; satisfies members spec:consumers.design-review.pack-design-page, spec:observation.run-evidence; references members spec:decisions.pack-design-page, spec:consumers.design-review.pack-design-page; code for rests on spec:consumers.binding-language-views, spec:consumers.derived-readiness-banner, spec:consumers.design-review, spec:consumers.projections-model, spec:consumers.spec-studio.lenses.architecture, spec:extraction.pack-member-order, spec:validation.diagnostic-rendering; member designs none
- component:protocol.reader: the typed graph contract and body evaluator, anchored, layer application, context protocol; satisfies members spec:consumers.pack-design, spec:extraction.entry-locations, spec:consumers.agent-surface.example-space-coverage, spec:model.design-maturity; references members spec:extraction.entry-locations; code for rests on spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sink, spec:consumers.reader, spec:extraction.contract-declarations, spec:extraction.pack-member-order, spec:validation.next-rung-floor; 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, spec:validation.superseded-decision-signal; references members none; code for rests on spec:extraction.pack-member-order, spec:model.anchors, spec:model.open-question-keys, spec:model.spec-sections, spec:validation.diagnostic-rendering, spec:validation.next-rung-floor, spec:validation.two-check-families, spec:validation.warn-level-signals; member designs none
- component:protocol.adapters: external runtime and source adapters, outside scope, anchored, layer adapter, context protocol
- component:protocol.runner: provider-neutral example execution, outside scope, anchored, layer application, 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.graph · anchored
- component:protocol.codegen uses component:protocol.notation · anchored
- component:protocol.codegen uses component:protocol.reader · anchored
- component:protocol.codegen uses component:protocol.validate · anchored
- component:protocol.extract uses component:protocol.graph · anchored
- impl:protocol.derive-graph uses impl:protocol.delivery-facts · anchored
- component:protocol.extract uses component:protocol.model · anchored
- component:protocol.extract uses component:protocol.notation · anchored
- component:protocol.extract uses component:protocol.validate · anchored
- component:protocol.graph uses component:protocol.model · anchored
- component:protocol.graph uses component:protocol.notation · anchored
- component:protocol.import uses component:protocol.extract · anchored
- component:protocol.import uses component:protocol.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.runner uses component:protocol.notation · anchored
- component:protocol.studio-elements uses component:protocol.projections · anchored
- component:protocol.studio-elements uses component:protocol.reader · anchored
- component:protocol.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.entry-location-recipes implements spec:extraction.entry-locations; no component
- impl:protocol.recipe-parameters-catalog implements spec:consumers.agent-surface.recipe-parameters; no component
- impl:protocol.design-recipes implements spec:consumers.agent-surface.design-recipes; no component
- impl:protocol.example-space-coverage-recipe implements spec:consumers.agent-surface.example-space-coverage; 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
- impl:protocol.authoring-grammar-recipes implements spec:model.open-question-fields; no component
- impl:protocol.authoring-grammar-recipes implements spec:model.rule-keys; no component
- impl:protocol.authoring-grammar-recipes implements spec:model.relation-reasons; no component
- impl:protocol.perspective-filter-recipe implements spec:consumers.review-perspectives; no component
- impl:protocol.context-bundle-recipe implements spec:consumers.context-bundle; no component
- impl:protocol.design-diff-recipe implements spec:consumers.design-diff; no component
- impl:protocol.proposal-schema-and-recipe implements spec:consumers.intent-composition.proposal; no component
- impl:protocol.architecture-walk-recipe implements spec:validation.architecture-constraints; no component
- impl:protocol.run-evidence-recipe implements spec:observation.run-evidence; no component
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred syntax: block; flowchart fallback because block cannot carry edge claims and counts.
Components the slice touches
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 itcomponent:protocol.runner· provider-neutral example execution · anchored · it uses a touched component
Units bound to a member and to no component
impl:protocol.entry-location-recipesimplements The graph records where each addressable entry is writtenimpl:protocol.recipe-parameters-catalogimplements Recipes take parameters as data and ship as runnable filesimpl:protocol.design-recipesimplements Design work reads its answers from catalog recipesimpl:protocol.example-space-coverage-recipeimplements Example spaces report which values their examples coverimpl:protocol.planned-components-recipeimplements Components are designed ahead of their codeimpl:protocol.curation-recipereferences Components are designed ahead of their codeimpl:protocol.authoring-grammar-recipesimplements An open question may name who decides it, its links, a provisional reading and a re-entry triggerimpl:protocol.authoring-grammar-recipesimplements A rule or flow entry may carry a key that addresses itimpl:protocol.authoring-grammar-recipesimplements An authored relation may carry its reasonimpl:protocol.perspective-filter-recipeimplements A Pack is read from a named perspectiveimpl:protocol.context-bundle-recipeimplements A context bundle is composed per invocation within a stated budgetimpl:protocol.design-diff-recipeimplements Designs are compared between a base commit and the working tree at entry grainimpl:protocol.proposal-schema-and-recipeimplements A change proposal is addressed, based and checked before it landsimpl:protocol.architecture-walk-recipeimplements Declared architecture rules are checked against anchored structureimpl:protocol.run-evidence-recipeimplements CI run records are joined to verifiers in a view
Decisions in scope
Open questions in scope
- blocking · question.namedStructuralReader
· spec:consumers.structural-mermaid · Does a reader need diagrams rooted at code units, which census tables and Spec-rooted one-hop Mermaid do not serve?Decider: ownerTrigger: a named reader with that need, plus a decision that refines spec:decisions.shipped-projections-frozenfor the affected Mermaid rendering or supersedes that ruling wholeHolds: Mermaid diagrams can be rooted at code units - blocking · question.namedOutsideReader
· spec:consumers.reference-projection · Does a human reader outside the repository need a reference projection the four shipped roots do not serve? The taxonomy row is not that reader.Decider: ownerTrigger: a named consumer outside the repository, with a way to measure that demand inside the arc that builds the projection - non-blocking · question.referenceSource
· spec:consumers.reference-projection · Would the reference read pinned declarations, contract-kind Specs or api:code anchors, and does any of them hold enough to document an interface? - non-blocking · question.designColumnsSufficiency
· spec:model.design-maturity · If the first adopter's design passes show that the design columns cannot distinguish settled design from intent alone, should this representation be revisited?Decider: ownerProvisional: derive what design a Spec carries beside readiness without a new rung, floor clause or delivery fact - non-blocking · question.freshness
· spec:observation.run-evidence · How does a view say a run is stale: by its commit against the commit being read, or by whether the bound files changed between the two?Decider: ownerProvisional: Display the run and source commit identifiers when they differ, as the differing-commit rule requires; whether freshness also follows changes to bound files remains open.
Where the slice meets the rest
Rests on (42)
Rested on by (69)
Verified by (31)
Superseded by (0)
None.
Composing (0)
Composing needs the script.