Markdown authoring enters the one graph
spec:carrier.markdown-authoring
65 distinct descendants · 46 examples · 9 decisions.
Capabilities
Epics and their declared refinement, from the capability map.
Each rollup counts distinct descendants of that epic. Scopes may overlap; epic rows are not added together.
Agents script a visible typed graph
spec:consumers.agent-surface
Inside Projections fan out from one graph without becoming truth stores.
62 distinct descendants · 41 examples · 2 decisions.
Authors move one Spec from intent to reviewed evidence
spec:consumers.authoring-on-ramp
28 distinct descendants · 16 examples · No decisions.
Projections fan out from one graph without becoming truth stores
spec:consumers.projections-model
Contains epic Agents script a visible typed graph.
199 distinct descendants · 90 examples · 15 decisions.
Carrier reification derives the one graph
spec:extraction.derive-graph
27 distinct descendants · 12 examples · 1 decision.
Bound examples execute their authored steps
spec:extraction.executable-examples
10 distinct descendants · 5 examples · 1 decision.
The Protocol models delivery with one enrichable Spec
spec:model.core-model
49 distinct descendants · 19 examples · 15 decisions.
The Protocol authors and validates itself
spec:protocol.self-hosting
11 distinct descendants · No examples · 5 decisions.
Validation separates well-formedness from non-pretending
spec:validation.two-check-families
68 distinct descendants · 47 examples · 4 decisions.
Markdown authoring enters the one graph
Epic's own evidence
Markdown authoring enters the one graph ·
spec:carrier.markdown-authoring · behavior · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsDistinct descendants, excluding this epic: 65 Specs · 46 examples · 9 decisions.
- Stated rungs
- idea 1 · scoped 0 · defined 0 · ready 64
- Floors reached
- none 0 · idea 1 · scoped 0 · defined 0 · ready 64
- Kinds
- behavior 5 · workflow 0 · example 46 · rule 4 · constraint 0 · model 0 · decision 9 · contract 1
- Altitudes
- epic 0 · feature 14 · story 51
- Binding evidence
- 9 Specs with implementation binding present · 55 Specs with verifier binding present
- Questions
- 1 open question · 1 blocking question
Arrows: refines (declared). Later visits repeat a Spec and link to its first occurrence.
Complete refinement text
Agents script a visible typed graph
Epic's own evidence
Agents script a visible typed graph ·
spec:consumers.agent-surface · behavior · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsDistinct descendants, excluding this epic: 62 Specs · 41 examples · 2 decisions.
- Stated rungs
- idea 0 · scoped 0 · defined 0 · ready 62
- Floors reached
- none 0 · idea 0 · scoped 0 · defined 0 · ready 62
- Kinds
- behavior 18 · workflow 0 · example 41 · rule 1 · constraint 0 · model 0 · decision 2 · contract 0
- Altitudes
- epic 0 · feature 8 · story 54
- Binding evidence
- 19 Specs with implementation binding present · 60 Specs with verifier binding present
- Questions
- 1 open question · No blocking questions
Arrows: refines (declared). Later visits repeat a Spec and link to its first occurrence.
The diagram as text
63 unique Specs; 11 rendered boxes.
spec:consumers.agent-surface: Agents script a visible typed graph · epicspec:consumers.agent-surface.answer-shapes: Recipe answers fit an agent's context and explain their misses · storyspec:consumers.agent-surface.authoring-recipes: Authoring questions stay executable graph recipes · storyspec:consumers.agent-surface.demand-map-entries: One body reaches every entry point the demand map names, and no symbol entry · storyspec:consumers.agent-surface.evaluation-sink: The evaluation sink runs one body and prints its return · storyspec:consumers.agent-surface.evaluation-sink.exported-evaluator: A script holding a graph runs a shipped recipe through the exported evaluator · storyspec:consumers.agent-surface.evaluation-sink.recipe-call: A body calls a shipped recipe and returns its answer unchanged · storyspec:consumers.agent-surface.evaluation-sink.unknown-recipe: A call to a recipe the catalog does not hold fails the body · storyspec:consumers.agent-surface.recipe-parameters: Recipes take parameters as data and ship as runnable files · storyspec:consumers.agent-surface.register-recipes: Register questions stay executable graph recipes · storyspec:consumers.agent-surface.address-and-cycle-recipes: Address resolution and dependency cycles stay executable graph recipes · storyspec:consumers.agent-surface.address-and-cycle-recipes.chain-reports-nothing: A dependency chain with no cycle yields no finding · storyspec:consumers.agent-surface.address-and-cycle-recipes.cycle-fails-a-rules-run: The shipped dependency-cycles file fails a rules run on a cycle · storyspec:consumers.agent-surface.address-and-cycle-recipes.unresolved-address-fails-a-rules-run: The shipped address-resolution file fails a rules run on an address that names no entry · storyspec:consumers.agent-surface.design-recipes: Design work reads its answers from catalog recipes · storyspec:consumers.agent-surface.example-space-coverage: Example spaces report which values their examples cover · storyspec:consumers.agent-surface.example-space-coverage.number-not-enumerable: A number slot is not enumerable and reports no uncovered value · storyspec:consumers.agent-surface.example-space-coverage.uncovered-literal: A literal no example binds is reported uncovered, and an unbound child is named · storyspec:consumers.agent-surface.scripted-context-body: A scripted body returns claim-decoded context, pre-shaped by the body · storyspec:consumers.context-bundle: A context bundle is composed per invocation within a stated budget · featurespec:consumers.context-bundle.oversized-member-named: A member larger than the budget is named, and no part is returned · storyspec:consumers.context-bundle.parts-cover-the-pack: A Pack too large for one bundle reads whole in parts · storyspec:consumers.reader: The reader bridges agent entry points to composable graph context · featurespec:consumers.pack-design: The Pack context carries the Pack's design · featurespec:consumers.design-slice: A slice reads a Pack as one design, with the architecture it touches and what each member needs next · featurespec:consumers.design-slice.chain: Members rest on a chain · storyspec:consumers.design-slice.component-absent: An unanchored component design stays visible · storyspec:consumers.design-slice.component-differing: A realized component keeps its differing layer and uses apart · storyspec:consumers.design-slice.component-matching: A realized component matches its declared values · storyspec:consumers.design-slice.component-unreadable: An unreadable declared layer stays visible · storyspec:consumers.design-slice.component-unrelated: An anchor alone does not realize a component design · storyspec:consumers.design-slice.decision-backlink: A shaping decision comes before its member · storyspec:consumers.design-slice.dependency-cycle: A cycle shares a depth · storyspec:consumers.design-slice.folded-example: An example folds without lending its readiness · storyspec:consumers.design-slice.independent-example: An example with its own dependency stays unfolded · storyspec:consumers.design-slice.outside-components: Outside components stop at the touched components' neighbors · storyspec:consumers.design-slice.outside-holding: An outside prerequisite names the member it holds · storyspec:consumers.design-slice.outside-satisfied: A prerequisite reaches its satisfying component · storyspec:consumers.design-slice.outside-unbound: An unbound prerequisite invents no component · storyspec:consumers.spec-studio.slice-page: A slice page shows a Pack's design as one whole · storyspec:consumers.reader.changeset-entry: A changeset names what it reaches, why, and what it cannot see · storyspec:consumers.reader.concept-entry: A concept recorded only inside a Spec's sections is still reached, and the field is named · storyspec:consumers.reader.file-entry: A source file reaches the Spec its binding names, and a carrier reaches its own Spec · storyspec:consumers.reading-on-ramp: The reading skill teaches agents to query the graph · storyspec:consumers.studio-on-ramp: The Studio skill teaches agents to publish, share and read the Spec Studio · storyspec:consumers.vault-on-ramp: The vault skill teaches agents to keep an Obsidian vault of the graph · storyspec:decisions.agent-front-door: The agent front door is one evaluation sink over the exported reader · featurespec:decisions.agent-surface-scripts-graph: Agents script the visible graph · featurespec:validation.corpus-rules: Corpus-authored rules run on the one validation path · featurespec:validation.architecture-constraints: Declared architecture rules are checked against anchored structure · featurespec:validation.architecture-constraints.forbidden-layer-pair: A domain member that uses an infrastructure member breaks a forbidden pair · storyspec:validation.architecture-constraints.isolated-context-as-rule: The walk named as a rules file fails validation on an isolation breach · storyspec:validation.architecture-constraints.unstated-layer-unclassified: A component with no layer leaves its edge unclassified · storyspec:validation.corpus-rules.copies-contain-changes: A rules file that empties its graph leaves the next file's graph whole · storyspec:validation.corpus-rules.error-finding-fails: An error from a corpus rule fails validation and leaves the Protocol's line alone · storyspec:validation.corpus-rules.malformed-finding-fails: A finding with no subject fails its rules file · storyspec:validation.corpus-rules.params-edit-starts-a-cycle: Editing a parameter file starts a cycle that reads the new parameters · storyspec:validation.corpus-rules.rules-edit-starts-a-cycle: Rewriting a rules file under node_modules starts a cycle that runs the new body · storyspec: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 · storyspec:validation.corpus-rules.warning-finding-informs: A warning from a corpus rule informs and passes · storyspec:validation.external-registers: A corpus checks the register tokens its prose cites · storyspec:validation.external-registers.uncited-on-request: A held token no Spec cites fails a rules run only when the caller asks · storyspec:validation.external-registers.unknown-and-retired: A cited token the register lacks or retires fails a rules run · storyspec:consumers.agent-surface.address-and-cycle-recipesrefinesspec:consumers.agent-surface.register-recipes· declaredspec:consumers.agent-surface.address-and-cycle-recipes.chain-reports-nothingrefinesspec:consumers.agent-surface.address-and-cycle-recipes· declaredspec:consumers.agent-surface.address-and-cycle-recipes.cycle-fails-a-rules-runrefinesspec:consumers.agent-surface.address-and-cycle-recipes· declaredspec:consumers.agent-surface.address-and-cycle-recipes.unresolved-address-fails-a-rules-runrefinesspec:consumers.agent-surface.address-and-cycle-recipes· declaredspec:consumers.agent-surface.answer-shapesrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.authoring-recipesrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.demand-map-entriesrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.design-recipesrefinesspec:consumers.agent-surface.register-recipes· declaredspec:consumers.agent-surface.evaluation-sinkrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.evaluation-sink.exported-evaluatorrefinesspec:consumers.agent-surface.evaluation-sink· declaredspec:consumers.agent-surface.evaluation-sink.recipe-callrefinesspec:consumers.agent-surface.evaluation-sink· declaredspec:consumers.agent-surface.evaluation-sink.unknown-reciperefinesspec:consumers.agent-surface.evaluation-sink· declaredspec:consumers.agent-surface.example-space-coveragerefinesspec:consumers.agent-surface.design-recipes· declaredspec:consumers.agent-surface.example-space-coverage.number-not-enumerablerefinesspec:consumers.agent-surface.example-space-coverage· declaredspec:consumers.agent-surface.example-space-coverage.uncovered-literalrefinesspec:consumers.agent-surface.example-space-coverage· declaredspec:consumers.agent-surface.recipe-parametersrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.register-recipesrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.scripted-context-bodyrefinesspec:consumers.agent-surface· declaredspec:consumers.context-bundlerefinesspec:consumers.agent-surface· declaredspec:consumers.context-bundle.oversized-member-namedrefinesspec:consumers.context-bundle· declaredspec:consumers.context-bundle.parts-cover-the-packrefinesspec:consumers.context-bundle· declaredspec:consumers.design-slicerefinesspec:consumers.pack-design· declared — a slice reads a Pack's design as one whole, with its architecture and open decisions beside itspec:consumers.design-slice.chainrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.component-absentrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.component-differingrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.component-matchingrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.component-unreadablerefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.component-unrelatedrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.decision-backlinkrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.dependency-cyclerefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.folded-examplerefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.independent-examplerefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.outside-componentsrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.outside-holdingrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.outside-satisfiedrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.outside-unboundrefinesspec:consumers.design-slice· declaredspec:consumers.pack-designrefinesspec:consumers.reader· declaredspec:consumers.readerrefinesspec:consumers.agent-surface· declaredspec:consumers.reader.changeset-entryrefinesspec:consumers.reader· declaredspec:consumers.reader.concept-entryrefinesspec:consumers.reader· declaredspec:consumers.reader.file-entryrefinesspec:consumers.reader· declaredspec:consumers.reading-on-ramprefinesspec:consumers.agent-surface· declaredspec:consumers.spec-studio.slice-pagerefinesspec:consumers.design-slice· declared — the page is the design slice's reading for a personspec:consumers.studio-on-ramprefinesspec:consumers.reading-on-ramp· declared — a Studio page is a person's reading of the one graph, and the skill sends an agent from a page to the graph behind itspec:consumers.vault-on-ramprefinesspec:consumers.reading-on-ramp· declared — a vault note is a person's reading of the one graph, and the skill turns what the person writes beside it into checked editsspec:decisions.agent-front-doorrefinesspec:consumers.agent-surface· declaredspec:decisions.agent-surface-scripts-graphrefinesspec:consumers.agent-surface· declaredspec:validation.architecture-constraintsrefinesspec:validation.corpus-rules· declared — the architecture walk is a corpus-selected rule over anchored structurespec:validation.architecture-constraints.forbidden-layer-pairrefinesspec:validation.architecture-constraints· declaredspec:validation.architecture-constraints.isolated-context-as-rulerefinesspec:validation.architecture-constraints· declaredspec:validation.architecture-constraints.unstated-layer-unclassifiedrefinesspec:validation.architecture-constraints· declaredspec:validation.corpus-rulesrefinesspec:consumers.agent-surface· declared — a corpus scripts the graph through the evaluation sink to report its own findingsspec:validation.corpus-rules.copies-contain-changesrefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.error-finding-failsrefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.malformed-finding-failsrefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.params-edit-starts-a-cyclerefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.rules-edit-starts-a-cyclerefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.unreadable-params-fail-one-filerefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.warning-finding-informsrefinesspec:validation.corpus-rules· declaredspec:validation.external-registersrefinesspec:validation.corpus-rules· declared — external-register checks run as corpus-selected rulesspec:validation.external-registers.uncited-on-requestrefinesspec:validation.external-registers· declaredspec:validation.external-registers.unknown-and-retiredrefinesspec:validation.external-registers· declared
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred syntax: mindmap. Chosen syntax: flowchart BT because the drawing has a fold.
Complete refinement text
Root
Agents script a visible typed graph ·spec:consumers.agent-surface· behavior · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Recipe answers fit an agent's context and explain their misses ·spec:consumers.agent-surface.answer-shapes· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Example · One body reaches every entry point the demand map names, and no symbol entry
One body reaches every entry point the demand map names, and no symbol entry ·spec:consumers.agent-surface.demand-map-entries· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
The evaluation sink runs one body and prints its return ·spec:consumers.agent-surface.evaluation-sink· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.evaluation-sink
Example · A script holding a graph runs a shipped recipe through the exported evaluator
A script holding a graph runs a shipped recipe through the exported evaluator ·spec:consumers.agent-surface.evaluation-sink.exported-evaluator· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.evaluation-sink
Example · A body calls a shipped recipe and returns its answer unchanged
A body calls a shipped recipe and returns its answer unchanged ·spec:consumers.agent-surface.evaluation-sink.recipe-call· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.evaluation-sink
Example · A call to a recipe the catalog does not hold fails the body
A call to a recipe the catalog does not hold fails the body ·spec:consumers.agent-surface.evaluation-sink.unknown-recipe· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Recipes take parameters as data and ship as runnable files ·spec:consumers.agent-surface.recipe-parameters· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Register questions stay executable graph recipes ·spec:consumers.agent-surface.register-recipes· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.register-recipes
Address resolution and dependency cycles stay executable graph recipes ·spec:consumers.agent-surface.address-and-cycle-recipes· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.address-and-cycle-recipes
Example · A dependency chain with no cycle yields no finding
A dependency chain with no cycle yields no finding ·spec:consumers.agent-surface.address-and-cycle-recipes.chain-reports-nothing· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.address-and-cycle-recipes
Example · The shipped dependency-cycles file fails a rules run on a cycle
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· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.address-and-cycle-recipes
Example · The shipped address-resolution file fails a rules run on an address that names no entry
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· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.register-recipes
Design work reads its answers from catalog recipes ·spec:consumers.agent-surface.design-recipes· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.design-recipes
Example spaces report which values their examples cover ·spec:consumers.agent-surface.example-space-coverage· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.example-space-coverage
Example · A number slot is not enumerable and reports no uncovered value
A number slot is not enumerable and reports no uncovered value ·spec:consumers.agent-surface.example-space-coverage.number-not-enumerable· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.example-space-coverage
Example · A literal no example binds is reported uncovered, and an unbound child is named
A literal no example binds is reported uncovered, and an unbound child is named ·spec:consumers.agent-surface.example-space-coverage.uncovered-literal· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Example · A scripted body returns claim-decoded context, pre-shaped by the body
A scripted body returns claim-decoded context, pre-shaped by the body ·spec:consumers.agent-surface.scripted-context-body· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
A context bundle is composed per invocation within a stated budget ·spec:consumers.context-bundle· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.context-bundle
Example · A member larger than the budget is named, and no part is returned
A member larger than the budget is named, and no part is returned ·spec:consumers.context-bundle.oversized-member-named· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.context-bundle
Example · A Pack too large for one bundle reads whole in parts
A Pack too large for one bundle reads whole in parts ·spec:consumers.context-bundle.parts-cover-the-pack· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
The reader bridges agent entry points to composable graph context ·spec:consumers.reader· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.reader
The Pack context carries the Pack's design ·spec:consumers.pack-design· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.pack-design
A slice reads a Pack as one design, with the architecture it touches and what each member needs next ·spec:consumers.design-slice· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · Members rest on a chain
Members rest on a chain ·spec:consumers.design-slice.chain· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An unanchored component design stays visible
An unanchored component design stays visible ·spec:consumers.design-slice.component-absent· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · A realized component keeps its differing layer and uses apart
A realized component keeps its differing layer and uses apart ·spec:consumers.design-slice.component-differing· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · A realized component matches its declared values
A realized component matches its declared values ·spec:consumers.design-slice.component-matching· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An unreadable declared layer stays visible
An unreadable declared layer stays visible ·spec:consumers.design-slice.component-unreadable· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · A shaping decision comes before its member
A shaping decision comes before its member ·spec:consumers.design-slice.decision-backlink· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · A cycle shares a depth
A cycle shares a depth ·spec:consumers.design-slice.dependency-cycle· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An example folds without lending its readiness
An example folds without lending its readiness ·spec:consumers.design-slice.folded-example· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An example with its own dependency stays unfolded
An example with its own dependency stays unfolded ·spec:consumers.design-slice.independent-example· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · Outside components stop at the touched components' neighbors
Outside components stop at the touched components' neighbors ·spec:consumers.design-slice.outside-components· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An outside prerequisite names the member it holds
An outside prerequisite names the member it holds ·spec:consumers.design-slice.outside-holding· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · A prerequisite reaches its satisfying component
A prerequisite reaches its satisfying component ·spec:consumers.design-slice.outside-satisfied· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An unbound prerequisite invents no component
An unbound prerequisite invents no component ·spec:consumers.design-slice.outside-unbound· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
A slice page shows a Pack's design as one whole ·spec:consumers.spec-studio.slice-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · 1 open question · No blocking questions- non-blocking: Does a Pack export also carry the Pack's slice page?
Parent: spec:consumers.reader
Example · A changeset names what it reaches, why, and what it cannot see
A changeset names what it reaches, why, and what it cannot see ·spec:consumers.reader.changeset-entry· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.reader
Example · A concept recorded only inside a Spec's sections is still reached, and the field is named
A concept recorded only inside a Spec's sections is still reached, and the field is named ·spec:consumers.reader.concept-entry· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.reader
Example · A source file reaches the Spec its binding names, and a carrier reaches its own Spec
A source file reaches the Spec its binding names, and a carrier reaches its own Spec ·spec:consumers.reader.file-entry· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
The reading skill teaches agents to query the graph ·spec:consumers.reading-on-ramp· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.reading-on-ramp
The Studio skill teaches agents to publish, share and read the Spec Studio ·spec:consumers.studio-on-ramp· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.reading-on-ramp
The vault skill teaches agents to keep an Obsidian vault of the graph ·spec:consumers.vault-on-ramp· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Decision · The agent front door is one evaluation sink over the exported reader
The agent front door is one evaluation sink over the exported reader ·spec:decisions.agent-front-door· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Decision · Agents script the visible graph
Agents script the visible graph ·spec:decisions.agent-surface-scripts-graph· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Corpus-authored rules run on the one validation path ·spec:validation.corpus-rules· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Declared architecture rules are checked against anchored structure ·spec:validation.architecture-constraints· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.architecture-constraints
Example · A domain member that uses an infrastructure member breaks a forbidden pair
A domain member that uses an infrastructure member breaks a forbidden pair ·spec:validation.architecture-constraints.forbidden-layer-pair· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.architecture-constraints
Example · The walk named as a rules file fails validation on an isolation breach
The walk named as a rules file fails validation on an isolation breach ·spec:validation.architecture-constraints.isolated-context-as-rule· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.architecture-constraints
Example · A component with no layer leaves its edge unclassified
A component with no layer leaves its edge unclassified ·spec:validation.architecture-constraints.unstated-layer-unclassified· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · A rules file that empties its graph leaves the next file's graph whole
A rules file that empties its graph leaves the next file's graph whole ·spec:validation.corpus-rules.copies-contain-changes· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · An error from a corpus rule fails validation and leaves the Protocol's line alone
An error from a corpus rule fails validation and leaves the Protocol's line alone ·spec:validation.corpus-rules.error-finding-fails· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · A finding with no subject fails its rules file
A finding with no subject fails its rules file ·spec:validation.corpus-rules.malformed-finding-fails· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · Editing a parameter file starts a cycle that reads the new parameters
Editing a parameter file starts a cycle that reads the new parameters ·spec:validation.corpus-rules.params-edit-starts-a-cycle· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · Rewriting a rules file under node_modules starts a cycle that runs the new body
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 · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · A parameter file that stops being JSON fails only its own rules file, and the watcher runs on
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 · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · A warning from a corpus rule informs and passes
A warning from a corpus rule informs and passes ·spec:validation.corpus-rules.warning-finding-informs· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
A corpus checks the register tokens its prose cites ·spec:validation.external-registers· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.external-registers
Example · A held token no Spec cites fails a rules run only when the caller asks
A held token no Spec cites fails a rules run only when the caller asks ·spec:validation.external-registers.uncited-on-request· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.external-registers
Example · A cited token the register lacks or retires fails a rules run
A cited token the register lacks or retires fails a rules run ·spec:validation.external-registers.unknown-and-retired· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questions
Authors move one Spec from intent to reviewed evidence
Epic's own evidence
Authors move one Spec from intent to reviewed evidence ·
spec:consumers.authoring-on-ramp · behavior · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsDistinct descendants, excluding this epic: 28 Specs · 16 examples · No decisions.
- Stated rungs
- idea 0 · scoped 0 · defined 0 · ready 28
- Floors reached
- none 0 · idea 0 · scoped 0 · defined 0 · ready 28
- Kinds
- behavior 12 · workflow 0 · example 16 · rule 0 · constraint 0 · model 0 · decision 0 · contract 0
- Altitudes
- epic 0 · feature 4 · story 24
- Binding evidence
- 12 Specs with implementation binding present · 28 Specs with verifier binding present
- Questions
- No open questions · No blocking questions
Arrows: refines (declared). Later visits repeat a Spec and link to its first occurrence.
Complete refinement text
Projections fan out from one graph without becoming truth stores
Epic's own evidence
Projections fan out from one graph without becoming truth stores ·
spec:consumers.projections-model · model · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsDistinct descendants, excluding this epic: 199 Specs · 90 examples · 15 decisions.
- Stated rungs
- idea 2 · scoped 4 · defined 0 · ready 193
- Floors reached
- none 0 · idea 1 · scoped 5 · defined 0 · ready 193
- Kinds
- behavior 79 · workflow 0 · example 90 · rule 4 · constraint 0 · model 1 · decision 15 · contract 10
- Altitudes
- epic 1 · feature 39 · story 159
- Binding evidence
- 86 Specs with implementation binding present · 178 Specs with verifier binding present
- Questions
- 12 open questions · 7 blocking questions
Arrows: refines (declared). Later visits repeat a Spec and link to its first occurrence.
Scroll horizontally to read the whole drawing.
The diagram as text
200 unique Specs; 10 rendered boxes.
spec:consumers.projections-model: Projections fan out from one graph without becoming truth stores · epicspec:consumers.agent-surface: Agents script a visible typed graph · epicspec:consumers.agent-surface.answer-shapes: Recipe answers fit an agent's context and explain their misses · storyspec:consumers.agent-surface.authoring-recipes: Authoring questions stay executable graph recipes · storyspec:consumers.agent-surface.demand-map-entries: One body reaches every entry point the demand map names, and no symbol entry · storyspec:consumers.agent-surface.evaluation-sink: The evaluation sink runs one body and prints its return · storyspec:consumers.agent-surface.evaluation-sink.exported-evaluator: A script holding a graph runs a shipped recipe through the exported evaluator · storyspec:consumers.agent-surface.evaluation-sink.recipe-call: A body calls a shipped recipe and returns its answer unchanged · storyspec:consumers.agent-surface.evaluation-sink.unknown-recipe: A call to a recipe the catalog does not hold fails the body · storyspec:consumers.agent-surface.recipe-parameters: Recipes take parameters as data and ship as runnable files · storyspec:consumers.agent-surface.register-recipes: Register questions stay executable graph recipes · storyspec:consumers.agent-surface.address-and-cycle-recipes: Address resolution and dependency cycles stay executable graph recipes · storyspec:consumers.agent-surface.address-and-cycle-recipes.chain-reports-nothing: A dependency chain with no cycle yields no finding · storyspec:consumers.agent-surface.address-and-cycle-recipes.cycle-fails-a-rules-run: The shipped dependency-cycles file fails a rules run on a cycle · storyspec:consumers.agent-surface.address-and-cycle-recipes.unresolved-address-fails-a-rules-run: The shipped address-resolution file fails a rules run on an address that names no entry · storyspec:consumers.agent-surface.design-recipes: Design work reads its answers from catalog recipes · storyspec:consumers.agent-surface.example-space-coverage: Example spaces report which values their examples cover · storyspec:consumers.agent-surface.example-space-coverage.number-not-enumerable: A number slot is not enumerable and reports no uncovered value · storyspec:consumers.agent-surface.example-space-coverage.uncovered-literal: A literal no example binds is reported uncovered, and an unbound child is named · storyspec:consumers.agent-surface.scripted-context-body: A scripted body returns claim-decoded context, pre-shaped by the body · storyspec:consumers.context-bundle: A context bundle is composed per invocation within a stated budget · featurespec:consumers.context-bundle.oversized-member-named: A member larger than the budget is named, and no part is returned · storyspec:consumers.context-bundle.parts-cover-the-pack: A Pack too large for one bundle reads whole in parts · storyspec:consumers.reader: The reader bridges agent entry points to composable graph context · featurespec:consumers.pack-design: The Pack context carries the Pack's design · featurespec:consumers.design-slice: A slice reads a Pack as one design, with the architecture it touches and what each member needs next · featurespec:consumers.design-slice.chain: Members rest on a chain · storyspec:consumers.design-slice.component-absent: An unanchored component design stays visible · storyspec:consumers.design-slice.component-differing: A realized component keeps its differing layer and uses apart · storyspec:consumers.design-slice.component-matching: A realized component matches its declared values · storyspec:consumers.design-slice.component-unreadable: An unreadable declared layer stays visible · storyspec:consumers.design-slice.component-unrelated: An anchor alone does not realize a component design · storyspec:consumers.design-slice.decision-backlink: A shaping decision comes before its member · storyspec:consumers.design-slice.dependency-cycle: A cycle shares a depth · storyspec:consumers.design-slice.folded-example: An example folds without lending its readiness · storyspec:consumers.design-slice.independent-example: An example with its own dependency stays unfolded · storyspec:consumers.design-slice.outside-components: Outside components stop at the touched components' neighbors · storyspec:consumers.design-slice.outside-holding: An outside prerequisite names the member it holds · storyspec:consumers.design-slice.outside-satisfied: A prerequisite reaches its satisfying component · storyspec:consumers.design-slice.outside-unbound: An unbound prerequisite invents no component · storyspec:consumers.spec-studio.slice-page: A slice page shows a Pack's design as one whole · storyspec:consumers.reader.changeset-entry: A changeset names what it reaches, why, and what it cannot see · storyspec:consumers.reader.concept-entry: A concept recorded only inside a Spec's sections is still reached, and the field is named · storyspec:consumers.reader.file-entry: A source file reaches the Spec its binding names, and a carrier reaches its own Spec · storyspec:consumers.reading-on-ramp: The reading skill teaches agents to query the graph · storyspec:consumers.studio-on-ramp: The Studio skill teaches agents to publish, share and read the Spec Studio · storyspec:consumers.vault-on-ramp: The vault skill teaches agents to keep an Obsidian vault of the graph · storyspec:decisions.agent-front-door: The agent front door is one evaluation sink over the exported reader · featurespec:decisions.agent-surface-scripts-graph: Agents script the visible graph · featurespec:validation.corpus-rules: Corpus-authored rules run on the one validation path · featurespec:validation.architecture-constraints: Declared architecture rules are checked against anchored structure · featurespec:validation.architecture-constraints.forbidden-layer-pair: A domain member that uses an infrastructure member breaks a forbidden pair · storyspec:validation.architecture-constraints.isolated-context-as-rule: The walk named as a rules file fails validation on an isolation breach · storyspec:validation.architecture-constraints.unstated-layer-unclassified: A component with no layer leaves its edge unclassified · storyspec:validation.corpus-rules.copies-contain-changes: A rules file that empties its graph leaves the next file's graph whole · storyspec:validation.corpus-rules.error-finding-fails: An error from a corpus rule fails validation and leaves the Protocol's line alone · storyspec:validation.corpus-rules.malformed-finding-fails: A finding with no subject fails its rules file · storyspec:validation.corpus-rules.params-edit-starts-a-cycle: Editing a parameter file starts a cycle that reads the new parameters · storyspec:validation.corpus-rules.rules-edit-starts-a-cycle: Rewriting a rules file under node_modules starts a cycle that runs the new body · storyspec: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 · storyspec:validation.corpus-rules.warning-finding-informs: A warning from a corpus rule informs and passes · storyspec:validation.external-registers: A corpus checks the register tokens its prose cites · storyspec:validation.external-registers.uncited-on-request: A held token no Spec cites fails a rules run only when the caller asks · storyspec:validation.external-registers.unknown-and-retired: A cited token the register lacks or retires fails a rules run · storyspec:consumers.capability-map: The capability map reads every epic and its refinement descendants · featurespec:consumers.spec-studio.capability-map-page: The capability map page makes refinement readable by epic · storyspec:decisions.epics-of-any-kind: Capability epics keep kind independent of altitude · featurespec:consumers.census-page: Census renders the runtime taxonomy without becoming a registry · featurespec:consumers.command-line: Every verb answers --help, and one verb writes every projection root · storyspec:consumers.command-line.generate-check-failure: A root that fails its check is removed while sdp generate writes the others · storyspec:consumers.command-line.generate-writes-every-root: One run of sdp generate leaves all five roots current · storyspec:consumers.command-line.verb-help-touches-nothing: A publisher's --help prints its help and touches no root · storyspec:consumers.engine-provenance: The CLI names the engine that produced a result · storyspec:consumers.design-diff: Designs are compared between a base commit and the working tree at entry grain · featurespec:consumers.design-review: Design Review renders graph context without becoming a gate · featurespec:consumers.binding-language-views: Views speak binding language, never the internal fact name · featurespec:consumers.binding-language-views.bound-spec-page: A fully bound Spec renders binding language on the page and in the index · storyspec:consumers.binding-language-views.pack-member-table: The Pack member table speaks the page's binding language, not a shorthand · storyspec:consumers.derived-readiness-banner: Derived readiness renders beside the stated rung and warns in one direction · featurespec:consumers.derived-readiness-banner.dishonest-divergence: An overstated rung raises the banner and names the clause that refused · storyspec:consumers.derived-readiness-banner.honest-headroom: A rung the structure overshoots renders as information, not as a banner · storyspec:consumers.design-review.pack-design-page: A Pack page shows where the Pack's design stands · storyspec:decisions.pack-design-page: The Design Review's Pack page presents the Pack's design · featurespec:consumers.design-review.pure-projection: The view is the graph read twice, and the corpus is untouched by reading it · storyspec:consumers.wholesale-view-rewrite: Every view run rewrites the view wholesale · featurespec:consumers.wholesale-view-rewrite.build-invalidates-view: A build that never renders still takes the old view down · storyspec:consumers.wholesale-view-rewrite.failed-run-view-removed: A run that cannot produce a current view leaves no view at all · storyspec:consumers.wholesale-view-rewrite.late-stale-page: A page the build's invalidation never saw still does not survive the swap · storyspec:consumers.wholesale-view-rewrite.stale-page-removed: A page from an earlier run does not survive the next one · storyspec:decisions.authored-entry-order: The Design Review renders open-section entries as a list · featurespec:decisions.question-key-rendering: The Design Review shows an open question's key · featurespec:consumers.edit-model: Views compose scoped intent instead of patching canonical source · featurespec:consumers.intent-composition: Composed intent hands off on one proposal shape · storyspec:consumers.intent-composition.proposal: A change proposal is addressed, based and checked before it lands · storyspec:consumers.intent-composition.proposal.memo: Recipe 49 renders a change proposal as the Markdown memo a person reviews · storyspec:consumers.intent-composition.proposal.memo.shared: Recipe 49 and the composing panel write one memo for one proposal · storyspec:consumers.spec-studio.intent-panel: A composing panel on every page gathers scoped intent for an agent · storyspec:consumers.spec-studio.intent-panel.refresh-keeps-intents: Refreshing a tab keeps every gathered intent · storyspec:consumers.gherkin-view: Gherkin view renders any Spec as a disposable read shape · featurespec:consumers.impact-graph: Mechanical code structure stays inferred and apart from curated intent · featurespec:consumers.impact-graph.curation-assist: File-level imports show where curation is missing · featurespec:consumers.impact-graph.symbol-reach: Exhaustive symbol reach waits for a language-neutral identity · featurespec:consumers.mermaid-view: Mermaid renders bounded one-hop and Pack diagrams without becoming a graph browser · featurespec:consumers.obsidian-vault: An Obsidian vault lets a person iterate on designs from the one graph · featurespec:consumers.obsidian-vault.bases: A Pack's members and the standing queries are tables over the reader's values · storyspec:consumers.obsidian-vault.bases.views-match-sources: Each standing view selects what its source selects · storyspec:consumers.obsidian-vault.changed-note-refused: A generated note a person changed refuses the regeneration and keeps the edit · storyspec:consumers.obsidian-vault.failed-extraction-keeps-notes: A failed extraction keeps the notes and says so on the index · storyspec:consumers.obsidian-vault.failed-extraction-recovered: The run after a failed extraction passes the guard and restores the index · storyspec:consumers.obsidian-vault.fresh-vault: A fresh vault is written the same way twice and every link resolves · storyspec:consumers.obsidian-vault.hidden-file-refused: A person's file under a temporary's name refuses the regeneration · storyspec:consumers.obsidian-vault.interrupted-run-recovered: A run after a stopped synchronization finishes it · storyspec:consumers.obsidian-vault.iteration: A design pass is followed and answered from the vault · storyspec:consumers.obsidian-vault.iteration.watch-rewrites-changed-notes: A carrier edit under watch rewrites only the notes it changes · storyspec:consumers.obsidian-vault.iteration.watch-source-anchor: An anchor added in a source file under watch rewrites the Spec's note · storyspec:consumers.obsidian-vault.notes: Every Spec, Pack, code unit and keyed term is a note, and every relation is a link · storyspec:consumers.obsidian-vault.notes.case-collision-refused: Two Specs whose notes differ only in case refuse the run · storyspec:consumers.obsidian-vault.notes.entry-address-link: An entry address in prose opens the entry's block in its Spec's note · storyspec:consumers.obsidian-vault.notes.term-address-link: A keyed Model term gets a note, and its address in prose opens the term's block · storyspec:consumers.obsidian-vault.notes.unresolved-mention-stays: A mention of an entry that does not exist stays as written · storyspec:consumers.obsidian-vault.person-notes-survive: A regeneration removes a note that left the graph and keeps a person's notes · storyspec:consumers.obsidian-vault.unknown-note-refused: A note a person wrote inside the generated folder refuses the regeneration · storyspec:consumers.obsidian-vault.vault-in-build-path-refused: A vault directory the build removes refuses the run and keeps a person's notes · storyspec:decisions.vault-owned-folder: The vault's generator owns one folder and synchronizes it · featurespec:consumers.projections-model.roadmap-views: Roadmap views read releases, baselines and phases from git and the graph · storyspec:consumers.reference-projection: A reference projection serves a reader outside the repository · featurespec:consumers.review-perspectives: A Pack is read from a named perspective · featurespec:consumers.spec-studio: The Spec Studio is a static HTML workbench over the one graph · featurespec:consumers.spec-studio.cited-line-text: A pinned declaration shows the words of each test line that cites it · storyspec:consumers.spec-studio.components: The Studio's custom elements each hold one view the build renders · storyspec:consumers.spec-studio.diagrams: A diagram is laid out from graph values into SVG with a text equivalent · storyspec:consumers.spec-studio.diagram-kinds: The Studio chooses diagram kinds from graph values · featurespec:consumers.spec-studio.diagram-kinds.capability-tree: A refinement drawing follows the capability map · storyspec:consumers.spec-studio.diagram-kinds.dependency: A dependency drawing shows the declared footing of a Spec set · storyspec:consumers.spec-studio.diagram-kinds.edge-routing: Edges route around boxes with deterministic orthogonal paths · storyspec:consumers.spec-studio.diagram-kinds.legibility: A diagram preserves readable labels before zoom · storyspec:consumers.spec-studio.diagram-kinds.maturity-picture: The maturity map is drawn as a grid of counts · storyspec:consumers.spec-studio.diagram-kinds.mermaid-source: A diagram offers Mermaid source as copyable text · storyspec:consumers.spec-studio.diagram-kinds.requirement-trace: A requirement drawing separates intent from realization and verification · storyspec:consumers.spec-studio.diagram-kinds.scoped-architecture: A Spec set draws the architecture it touches · storyspec:consumers.spec-studio.diagram-kinds.edge-routing: Edges route around boxes with deterministic orthogonal paths · story · repeatspec:consumers.spec-studio.diagram-kinds.legibility: A diagram preserves readable labels before zoom · story · repeatspec:consumers.spec-studio.diagrams.folds-by-context: An architecture over the bound folds by context · storyspec:consumers.spec-studio.diagrams.folds-by-layer: One context over the bound folds by layer · storyspec:consumers.spec-studio.diagrams.within-bound: An architecture within the bound draws in one diagram, the same bytes twice · storyspec:consumers.spec-studio.page-elements: A few custom elements filter, search, open and copy on a rendered page · storyspec:consumers.spec-studio.data: The Studio renders from the reader's values and embeds only what its script reads · storyspec:consumers.spec-studio.data.inputs: The Studio reads two named inputs beside the graph, a base graph and run records · storyspec:consumers.spec-studio.data.inputs.both-given: Both inputs add their pages, named, and the same inputs write the same bytes · storyspec:consumers.spec-studio.data.inputs.graph-only: Without inputs the page set is the graph's alone · storyspec:consumers.spec-studio.data.recipe-answers: A page takes each recipe answer from the recipe's shipped body · storyspec:consumers.spec-studio.diff-page: The diff page shows what changed in the design since a base graph · storyspec:consumers.spec-studio.diff-page.changed-entry: The diff page shows a changed entry's base and built values · storyspec:consumers.spec-studio.export: A Pack exports as one file, and every page prints as a document · storyspec:consumers.spec-studio.export.self-contained: A Pack's export opens alone and keeps its links inside it · storyspec:consumers.spec-studio.glossary-page: The glossary page lists every term the corpus's Specs define · storyspec:consumers.spec-studio.glossary-page.same-word-twice: A word two Specs define appears once per Spec on the glossary page · storyspec:consumers.spec-studio.lenses: Five lenses read the graph as Packs, capabilities, architecture, tests and evidence · storyspec:consumers.spec-studio.capability-map-page: The capability map page makes refinement readable by epic · story · repeatspec:consumers.spec-studio.lenses.architecture: The architecture lens draws components by context and layer, the planned beside the built · storyspec:consumers.spec-studio.lenses.architecture.planned-apart: A component design no anchor realizes draws planned beside the built one · storyspec:consumers.spec-studio.lenses.architecture.unit-register: The architecture page lists each component's significant units by role · storyspec:consumers.spec-studio.lenses.evidence: The evidence lens names each source of runtime evidence and reads it as not tracked · storyspec:consumers.spec-studio.lenses.packs: The Packs lens groups every Spec by the Packs that hold it · storyspec:consumers.spec-studio.index-page: The index says where the corpus stands and narrows every Spec · storyspec:consumers.spec-studio.lenses.tests: The tests lens shows how far each Spec's verification reaches · storyspec:consumers.spec-studio.lenses.tests.coverage-row: A Spec's row on the tests lens counts its exercised keyed rules · storyspec:consumers.spec-studio.navigation: Every page of the page set is reached from the top navigation and the index · storyspec:consumers.spec-studio.owner-queue: The owner queue page orders the statements and questions only a person can settle · storyspec:consumers.spec-studio.owner-queue.dependency-first: The owner queue lists a waiting statement after the one it rests on · storyspec:consumers.spec-studio.pack-page: A Pack page shows the Pack's design as one card per member · storyspec:consumers.spec-studio.pack-page.maturity-map: A Pack page's maturity map places every member by its stated rung and its floor · storyspec:consumers.spec-studio.publisher: `sdp studio` publishes the Studio as one page set · storyspec:consumers.spec-studio.publisher.watch: `sdp studio --watch` rebuilds the page set on each carrier change · storyspec:consumers.spec-studio.publisher.watch.matches-plain-run: Each watch cycle writes the page set a plain run writes · storyspec:consumers.spec-studio.register-input: An outside register is a named Studio input, so a cited token links to its entry · storyspec:consumers.spec-studio.registers: The corpus's registers are pages a reviewer opens from a link · storyspec:consumers.spec-studio.registers.blocking-first: The questions page lists the Specs with a blocking question first · storyspec:consumers.spec-studio.responsive: The Studio reads on a phone as on a desktop · storyspec:consumers.spec-studio.roadmap-page: The roadmap page shows the upcoming work in priority order, split by what it needs · storyspec:consumers.spec-studio.runs-page: The runs page shows the run records the build was given, joined to test files · storyspec:consumers.spec-studio.runs-page.external-evidence: The runs page shows a run as external evidence from a test file · storyspec:consumers.spec-studio.sharing: A Studio build is stamped and shared from a static host · storyspec:consumers.spec-studio.sharing.stamp-written-apart: The stamp is written beside the page set, and a later build removes it · storyspec:consumers.spec-studio.shell: The Studio's shell frames every page with navigation, a rail and a canvas · storyspec:consumers.spec-studio.search: Search finds a Spec, a Pack, an entry or a bound file by a word · storyspec:consumers.spec-studio.slice-page: A slice page shows a Pack's design as one whole · story · repeatspec:consumers.spec-studio.spec-page: A Spec page shows one Spec in collapsible panels, in a fixed order · storyspec:consumers.spec-studio.spec-page.cited-declaration: A pinned declaration shows the test line that cites it · storyspec:consumers.spec-studio.spec-page.core: A Spec page's core shows the whole Spec, with an anchor for every entry · storyspec:consumers.spec-studio.verification-panels: The panels for examples, targets, verifiers and evidence · storyspec:consumers.spec-studio.verification-panels.rule-coverage: Each keyed rule shows the examples that exercise it, or that none does · storyspec:decisions.studio-html-surface: The Studio renders HTML, and the HTML stays derived · featurespec:decisions.studio-web-components: The Studio is built from custom elements, not a framework · featurespec:decisions.studio-build-renders: The build renders every Studio view, and an element only enhances it · storyspec:decisions.studio-diagram-renderer: The engine lays out every Studio diagram as static SVG when the page set is built · storyspec:consumers.structural-mermaid: Mermaid diagrams can be rooted at code units · featurespec:decisions.mcp-deferred: MCP integration remains deferred · featurespec:decisions.shipped-projections-frozen: The shipped projections stay frozen · featurespec:decisions.anchor-binding-grain: Bindings are optional, plural, and may reference a design · featurespec:decisions.architectural-annotation: Architectural significance is annotated where it is realized · featurespec:decisions.authored-entry-order: The Design Review renders open-section entries as a list · feature · repeatspec:decisions.pack-design-page: The Design Review's Pack page presents the Pack's design · feature · repeatspec:decisions.question-key-rendering: The Design Review shows an open question's key · feature · repeatspec:observation.run-evidence: CI run records are joined to verifiers in a view · featurespec:observation.run-evidence.absolute-path-joins: A test whose reporter wrote an absolute path joins its anchored file · storyspec:observation.run-evidence.unanchored-file-unjoined: A test in a file with no test anchor is reported as unjoined · storyspec:consumers.agent-surfacerefinesspec:consumers.projections-model· declaredspec:consumers.agent-surface.address-and-cycle-recipesrefinesspec:consumers.agent-surface.register-recipes· declaredspec:consumers.agent-surface.address-and-cycle-recipes.chain-reports-nothingrefinesspec:consumers.agent-surface.address-and-cycle-recipes· declaredspec:consumers.agent-surface.address-and-cycle-recipes.cycle-fails-a-rules-runrefinesspec:consumers.agent-surface.address-and-cycle-recipes· declaredspec:consumers.agent-surface.address-and-cycle-recipes.unresolved-address-fails-a-rules-runrefinesspec:consumers.agent-surface.address-and-cycle-recipes· declaredspec:consumers.agent-surface.answer-shapesrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.authoring-recipesrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.demand-map-entriesrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.design-recipesrefinesspec:consumers.agent-surface.register-recipes· declaredspec:consumers.agent-surface.evaluation-sinkrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.evaluation-sink.exported-evaluatorrefinesspec:consumers.agent-surface.evaluation-sink· declaredspec:consumers.agent-surface.evaluation-sink.recipe-callrefinesspec:consumers.agent-surface.evaluation-sink· declaredspec:consumers.agent-surface.evaluation-sink.unknown-reciperefinesspec:consumers.agent-surface.evaluation-sink· declaredspec:consumers.agent-surface.example-space-coveragerefinesspec:consumers.agent-surface.design-recipes· declaredspec:consumers.agent-surface.example-space-coverage.number-not-enumerablerefinesspec:consumers.agent-surface.example-space-coverage· declaredspec:consumers.agent-surface.example-space-coverage.uncovered-literalrefinesspec:consumers.agent-surface.example-space-coverage· declaredspec:consumers.agent-surface.recipe-parametersrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.register-recipesrefinesspec:consumers.agent-surface· declaredspec:consumers.agent-surface.scripted-context-bodyrefinesspec:consumers.agent-surface· declaredspec:consumers.binding-language-viewsrefinesspec:consumers.design-review· declaredspec:consumers.binding-language-views.bound-spec-pagerefinesspec:consumers.binding-language-views· declaredspec:consumers.binding-language-views.pack-member-tablerefinesspec:consumers.binding-language-views· declaredspec:consumers.capability-maprefinesspec:consumers.projections-model· declared — the capability map projects authored refinement without introducing a groupingspec:consumers.census-pagerefinesspec:consumers.projections-model· declaredspec:consumers.command-linerefinesspec:consumers.projections-model· declared — one verb publishes every projection root from one graphspec:consumers.command-line.generate-check-failurerefinesspec:consumers.command-line· declaredspec:consumers.command-line.generate-writes-every-rootrefinesspec:consumers.command-line· declaredspec:consumers.command-line.verb-help-touches-nothingrefinesspec:consumers.command-line· declaredspec:consumers.context-bundlerefinesspec:consumers.agent-surface· declaredspec:consumers.context-bundle.oversized-member-namedrefinesspec:consumers.context-bundle· declaredspec:consumers.context-bundle.parts-cover-the-packrefinesspec:consumers.context-bundle· declaredspec:consumers.derived-readiness-bannerrefinesspec:consumers.design-review· declaredspec:consumers.derived-readiness-banner.dishonest-divergencerefinesspec:consumers.derived-readiness-banner· declaredspec:consumers.derived-readiness-banner.honest-headroomrefinesspec:consumers.derived-readiness-banner· declaredspec:consumers.design-diffrefinesspec:consumers.projections-model· declaredspec:consumers.design-reviewrefinesspec:consumers.projections-model· declaredspec:consumers.design-review.pack-design-pagerefinesspec:consumers.design-review· declaredspec:consumers.design-review.pure-projectionrefinesspec:consumers.design-review· declaredspec:consumers.design-slicerefinesspec:consumers.pack-design· declared — a slice reads a Pack's design as one whole, with its architecture and open decisions beside itspec:consumers.design-slice.chainrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.component-absentrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.component-differingrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.component-matchingrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.component-unreadablerefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.component-unrelatedrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.decision-backlinkrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.dependency-cyclerefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.folded-examplerefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.independent-examplerefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.outside-componentsrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.outside-holdingrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.outside-satisfiedrefinesspec:consumers.design-slice· declaredspec:consumers.design-slice.outside-unboundrefinesspec:consumers.design-slice· declaredspec:consumers.edit-modelrefinesspec:consumers.projections-model· declaredspec:consumers.engine-provenancerefinesspec:consumers.command-line· declared — the version flag is one more answer the command line gives an adopterspec:consumers.gherkin-viewrefinesspec:consumers.projections-model· declaredspec:consumers.impact-graphrefinesspec:consumers.projections-model· declaredspec:consumers.impact-graph.curation-assistrefinesspec:consumers.impact-graph· declaredspec:consumers.impact-graph.symbol-reachrefinesspec:consumers.impact-graph· declaredspec:consumers.intent-compositionrefinesspec:consumers.edit-model· declaredspec:consumers.intent-composition.proposalrefinesspec:consumers.intent-composition· declaredspec:consumers.intent-composition.proposal.memorefinesspec:consumers.intent-composition.proposal· declaredspec:consumers.intent-composition.proposal.memo.sharedrefinesspec:consumers.intent-composition.proposal.memo· declaredspec:consumers.mermaid-viewrefinesspec:consumers.projections-model· declaredspec:consumers.obsidian-vaultrefinesspec:consumers.projections-model· declared — a projection for a person who iterates on designs in a notes appspec:consumers.obsidian-vault.basesrefinesspec:consumers.obsidian-vault· declaredspec:consumers.obsidian-vault.bases.views-match-sourcesrefinesspec:consumers.obsidian-vault.bases· declaredspec:consumers.obsidian-vault.changed-note-refusedrefinesspec:consumers.obsidian-vault· declaredspec:consumers.obsidian-vault.failed-extraction-keeps-notesrefinesspec:consumers.obsidian-vault· declaredspec:consumers.obsidian-vault.failed-extraction-recoveredrefinesspec:consumers.obsidian-vault· declaredspec:consumers.obsidian-vault.fresh-vaultrefinesspec:consumers.obsidian-vault· declaredspec:consumers.obsidian-vault.hidden-file-refusedrefinesspec:consumers.obsidian-vault· declaredspec:consumers.obsidian-vault.interrupted-run-recoveredrefinesspec:consumers.obsidian-vault· declaredspec:consumers.obsidian-vault.iterationrefinesspec:consumers.obsidian-vault· declaredspec:consumers.obsidian-vault.iteration.watch-rewrites-changed-notesrefinesspec:consumers.obsidian-vault.iteration· declaredspec:consumers.obsidian-vault.iteration.watch-source-anchorrefinesspec:consumers.obsidian-vault.iteration· declaredspec:consumers.obsidian-vault.notesrefinesspec:consumers.obsidian-vault· declaredspec:consumers.obsidian-vault.notes.case-collision-refusedrefinesspec:consumers.obsidian-vault.notes· declaredspec:consumers.obsidian-vault.notes.entry-address-linkrefinesspec:consumers.obsidian-vault.notes· declaredspec:consumers.obsidian-vault.notes.term-address-linkrefinesspec:consumers.obsidian-vault.notes· declaredspec:consumers.obsidian-vault.notes.unresolved-mention-staysrefinesspec:consumers.obsidian-vault.notes· declaredspec:consumers.obsidian-vault.person-notes-surviverefinesspec:consumers.obsidian-vault· declaredspec:consumers.obsidian-vault.unknown-note-refusedrefinesspec:consumers.obsidian-vault· declaredspec:consumers.obsidian-vault.vault-in-build-path-refusedrefinesspec:consumers.obsidian-vault· declaredspec:consumers.pack-designrefinesspec:consumers.reader· declaredspec:consumers.projections-model.roadmap-viewsrefinesspec:consumers.projections-model· declaredspec:consumers.readerrefinesspec:consumers.agent-surface· declaredspec:consumers.reader.changeset-entryrefinesspec:consumers.reader· declaredspec:consumers.reader.concept-entryrefinesspec:consumers.reader· declaredspec:consumers.reader.file-entryrefinesspec:consumers.reader· declaredspec:consumers.reading-on-ramprefinesspec:consumers.agent-surface· declaredspec:consumers.reference-projectionrefinesspec:consumers.projections-model· declaredspec:consumers.review-perspectivesrefinesspec:consumers.projections-model· declaredspec:consumers.spec-studiorefinesspec:consumers.projections-model· declaredspec:consumers.spec-studio.capability-map-pagerefinesspec:consumers.capability-map· declared — the page is the capability map's reading for a personspec:consumers.spec-studio.capability-map-pagerefinesspec:consumers.spec-studio.lenses· declared — the Capabilities page is a lens that reads refinementspec:consumers.spec-studio.cited-line-textrefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.componentsrefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.datarefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.data.inputsrefinesspec:consumers.spec-studio.data· declaredspec:consumers.spec-studio.data.inputs.both-givenrefinesspec:consumers.spec-studio.data.inputs· declaredspec:consumers.spec-studio.data.inputs.graph-onlyrefinesspec:consumers.spec-studio.data.inputs· declaredspec:consumers.spec-studio.data.recipe-answersrefinesspec:consumers.spec-studio.data· declaredspec:consumers.spec-studio.diagram-kindsrefinesspec:consumers.spec-studio.diagrams· declaredspec:consumers.spec-studio.diagram-kinds.capability-treerefinesspec:consumers.spec-studio.diagram-kinds· declaredspec:consumers.spec-studio.diagram-kinds.dependencyrefinesspec:consumers.spec-studio.diagram-kinds· declaredspec:consumers.spec-studio.diagram-kinds.edge-routingrefinesspec:consumers.spec-studio.diagram-kinds· declared — arrows that cover no label serve the readable drawings the diagram kinds statespec:consumers.spec-studio.diagram-kinds.edge-routingrefinesspec:consumers.spec-studio.diagrams· declaredspec:consumers.spec-studio.diagram-kinds.legibilityrefinesspec:consumers.spec-studio.diagram-kinds· declared — readable labels are part of the outcome the diagram kinds statespec:consumers.spec-studio.diagram-kinds.legibilityrefinesspec:consumers.spec-studio.diagrams· declaredspec:consumers.spec-studio.diagram-kinds.maturity-picturerefinesspec:consumers.spec-studio.diagram-kinds· declaredspec:consumers.spec-studio.diagram-kinds.mermaid-sourcerefinesspec:consumers.spec-studio.diagram-kinds· declaredspec:consumers.spec-studio.diagram-kinds.requirement-tracerefinesspec:consumers.spec-studio.diagram-kinds· declaredspec:consumers.spec-studio.diagram-kinds.scoped-architecturerefinesspec:consumers.spec-studio.diagram-kinds· declaredspec:consumers.spec-studio.diagramsrefinesspec:consumers.spec-studio.components· declaredspec:consumers.spec-studio.diagrams.folds-by-contextrefinesspec:consumers.spec-studio.diagrams· declaredspec:consumers.spec-studio.diagrams.folds-by-layerrefinesspec:consumers.spec-studio.diagrams· declaredspec:consumers.spec-studio.diagrams.within-boundrefinesspec:consumers.spec-studio.diagrams· declaredspec:consumers.spec-studio.diff-pagerefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.diff-page.changed-entryrefinesspec:consumers.spec-studio.diff-page· declaredspec:consumers.spec-studio.exportrefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.export.self-containedrefinesspec:consumers.spec-studio.export· declaredspec:consumers.spec-studio.glossary-pagerefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.glossary-page.same-word-twicerefinesspec:consumers.spec-studio.glossary-page· declaredspec:consumers.spec-studio.index-pagerefinesspec:consumers.spec-studio.lenses.packs· declared — the index is the Packs lens and where a person landsspec:consumers.spec-studio.intent-panelrefinesspec:consumers.intent-composition· declaredspec:consumers.spec-studio.intent-panel.refresh-keeps-intentsrefinesspec:consumers.spec-studio.intent-panel· declaredspec:consumers.spec-studio.lensesrefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.lenses.architecturerefinesspec:consumers.spec-studio.lenses· declaredspec:consumers.spec-studio.lenses.architecture.planned-apartrefinesspec:consumers.spec-studio.lenses.architecture· declaredspec:consumers.spec-studio.lenses.architecture.unit-registerrefinesspec:consumers.spec-studio.lenses.architecture· declaredspec:consumers.spec-studio.lenses.evidencerefinesspec:consumers.spec-studio.lenses· declaredspec:consumers.spec-studio.lenses.packsrefinesspec:consumers.spec-studio.lenses· declaredspec:consumers.spec-studio.lenses.testsrefinesspec:consumers.spec-studio.lenses· declaredspec:consumers.spec-studio.lenses.tests.coverage-rowrefinesspec:consumers.spec-studio.lenses.tests· declaredspec:consumers.spec-studio.navigationrefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.owner-queuerefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.owner-queue.dependency-firstrefinesspec:consumers.spec-studio.owner-queue· declaredspec:consumers.spec-studio.pack-pagerefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.pack-page.maturity-maprefinesspec:consumers.spec-studio.pack-page· declaredspec:consumers.spec-studio.page-elementsrefinesspec:consumers.spec-studio.components· declaredspec:consumers.spec-studio.publisherrefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.publisher.watchrefinesspec:consumers.spec-studio.publisher· declaredspec:consumers.spec-studio.publisher.watch.matches-plain-runrefinesspec:consumers.spec-studio.publisher.watch· declaredspec:consumers.spec-studio.register-inputrefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.registersrefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.registers.blocking-firstrefinesspec:consumers.spec-studio.registers· declaredspec:consumers.spec-studio.responsiverefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.roadmap-pagerefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.runs-pagerefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.runs-page.external-evidencerefinesspec:consumers.spec-studio.runs-page· declaredspec:consumers.spec-studio.searchrefinesspec:consumers.spec-studio.shell· declaredspec:consumers.spec-studio.sharingrefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.sharing.stamp-written-apartrefinesspec:consumers.spec-studio.sharing· declaredspec:consumers.spec-studio.shellrefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.slice-pagerefinesspec:consumers.design-slice· declared — the page is the design slice's reading for a personspec:consumers.spec-studio.slice-pagerefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.spec-pagerefinesspec:consumers.spec-studio· declaredspec:consumers.spec-studio.spec-page.cited-declarationrefinesspec:consumers.spec-studio.spec-page· declaredspec:consumers.spec-studio.spec-page.corerefinesspec:consumers.spec-studio.spec-page· declaredspec:consumers.spec-studio.verification-panelsrefinesspec:consumers.spec-studio.spec-page· declaredspec:consumers.spec-studio.verification-panels.rule-coveragerefinesspec:consumers.spec-studio.verification-panels· declaredspec:consumers.structural-mermaidrefinesspec:consumers.projections-model· declaredspec:consumers.studio-on-ramprefinesspec:consumers.reading-on-ramp· declared — a Studio page is a person's reading of the one graph, and the skill sends an agent from a page to the graph behind itspec:consumers.vault-on-ramprefinesspec:consumers.reading-on-ramp· declared — a vault note is a person's reading of the one graph, and the skill turns what the person writes beside it into checked editsspec:consumers.wholesale-view-rewriterefinesspec:consumers.design-review· declaredspec:consumers.wholesale-view-rewrite.build-invalidates-viewrefinesspec:consumers.wholesale-view-rewrite· declaredspec:consumers.wholesale-view-rewrite.failed-run-view-removedrefinesspec:consumers.wholesale-view-rewrite· declaredspec:consumers.wholesale-view-rewrite.late-stale-pagerefinesspec:consumers.wholesale-view-rewrite· declaredspec:consumers.wholesale-view-rewrite.stale-page-removedrefinesspec:consumers.wholesale-view-rewrite· declaredspec:decisions.agent-front-doorrefinesspec:consumers.agent-surface· declaredspec:decisions.agent-surface-scripts-graphrefinesspec:consumers.agent-surface· declaredspec:decisions.anchor-binding-grainrefinesspec:decisions.shipped-projections-frozen· declared — carves out the Design Review's Referenced by list and the census References tablespec:decisions.architectural-annotationrefinesspec:decisions.shipped-projections-frozen· declared — carves out the census Roles, Layers and Contexts tables and the role, layer and context on the Design Review's code unit rowsspec:decisions.authored-entry-orderrefinesspec:consumers.design-review· declaredspec:decisions.authored-entry-orderrefinesspec:decisions.shipped-projections-frozen· declared — carves out how the Design Review renders open-section entries, as a list in authored orderspec:decisions.epics-of-any-kindrefinesspec:consumers.capability-map· declared — settles which Specs the capability map reads as epicsspec:decisions.mcp-deferredrefinesspec:consumers.projections-model· declaredspec:decisions.pack-design-pagerefinesspec:consumers.design-review.pack-design-page· declaredspec:decisions.pack-design-pagerefinesspec:decisions.shipped-projections-frozen· declared — carves out the Pack page, which renders the Pack designspec:decisions.question-key-renderingrefinesspec:consumers.design-review· declaredspec:decisions.question-key-renderingrefinesspec:decisions.shipped-projections-frozen· declared — carves out one change, an open question's key shown before its textspec:decisions.shipped-projections-frozenrefinesspec:consumers.projections-model· declaredspec:decisions.studio-build-rendersrefinesspec:decisions.studio-web-components· declared — narrows where a view's values come from; the build writes them into the markup, so a host carries that markup and supplies no graph dataspec:decisions.studio-diagram-rendererrefinesspec:decisions.studio-web-components· declared — narrows how an element that shows a diagram renders it; the element only enhances an SVG the build drewspec:decisions.studio-html-surfacerefinesspec:consumers.spec-studio· declaredspec:decisions.studio-web-componentsrefinesspec:consumers.spec-studio· declaredspec:decisions.vault-owned-folderrefinesspec:consumers.obsidian-vault· declared — settles which files the vault's generator owns and how it regenerates themspec:observation.run-evidencerefinesspec:consumers.projections-model· declared — run records inform a view without becoming graph factsspec:observation.run-evidence.absolute-path-joinsrefinesspec:observation.run-evidence· declaredspec:observation.run-evidence.unanchored-file-unjoinedrefinesspec:observation.run-evidence· declaredspec:validation.architecture-constraintsrefinesspec:validation.corpus-rules· declared — the architecture walk is a corpus-selected rule over anchored structurespec:validation.architecture-constraints.forbidden-layer-pairrefinesspec:validation.architecture-constraints· declaredspec:validation.architecture-constraints.isolated-context-as-rulerefinesspec:validation.architecture-constraints· declaredspec:validation.architecture-constraints.unstated-layer-unclassifiedrefinesspec:validation.architecture-constraints· declaredspec:validation.corpus-rulesrefinesspec:consumers.agent-surface· declared — a corpus scripts the graph through the evaluation sink to report its own findingsspec:validation.corpus-rules.copies-contain-changesrefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.error-finding-failsrefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.malformed-finding-failsrefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.params-edit-starts-a-cyclerefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.rules-edit-starts-a-cyclerefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.unreadable-params-fail-one-filerefinesspec:validation.corpus-rules· declaredspec:validation.corpus-rules.warning-finding-informsrefinesspec:validation.corpus-rules· declaredspec:validation.external-registersrefinesspec:validation.corpus-rules· declared — external-register checks run as corpus-selected rulesspec:validation.external-registers.uncited-on-requestrefinesspec:validation.external-registers· declaredspec:validation.external-registers.unknown-and-retiredrefinesspec:validation.external-registers· declared
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred syntax: mindmap. Chosen syntax: flowchart BT because the drawing has repeated parentage, a fold.
Complete refinement text
Root
Projections fan out from one graph without becoming truth stores ·spec:consumers.projections-model· model · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.projections-model
Agents script a visible typed graph ·spec:consumers.agent-surface· behavior · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Recipe answers fit an agent's context and explain their misses ·spec:consumers.agent-surface.answer-shapes· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Example · One body reaches every entry point the demand map names, and no symbol entry
One body reaches every entry point the demand map names, and no symbol entry ·spec:consumers.agent-surface.demand-map-entries· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
The evaluation sink runs one body and prints its return ·spec:consumers.agent-surface.evaluation-sink· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.evaluation-sink
Example · A script holding a graph runs a shipped recipe through the exported evaluator
A script holding a graph runs a shipped recipe through the exported evaluator ·spec:consumers.agent-surface.evaluation-sink.exported-evaluator· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.evaluation-sink
Example · A body calls a shipped recipe and returns its answer unchanged
A body calls a shipped recipe and returns its answer unchanged ·spec:consumers.agent-surface.evaluation-sink.recipe-call· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.evaluation-sink
Example · A call to a recipe the catalog does not hold fails the body
A call to a recipe the catalog does not hold fails the body ·spec:consumers.agent-surface.evaluation-sink.unknown-recipe· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Recipes take parameters as data and ship as runnable files ·spec:consumers.agent-surface.recipe-parameters· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Register questions stay executable graph recipes ·spec:consumers.agent-surface.register-recipes· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.register-recipes
Address resolution and dependency cycles stay executable graph recipes ·spec:consumers.agent-surface.address-and-cycle-recipes· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.address-and-cycle-recipes
Example · A dependency chain with no cycle yields no finding
A dependency chain with no cycle yields no finding ·spec:consumers.agent-surface.address-and-cycle-recipes.chain-reports-nothing· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.address-and-cycle-recipes
Example · The shipped dependency-cycles file fails a rules run on a cycle
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· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.address-and-cycle-recipes
Example · The shipped address-resolution file fails a rules run on an address that names no entry
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· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.register-recipes
Design work reads its answers from catalog recipes ·spec:consumers.agent-surface.design-recipes· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.design-recipes
Example spaces report which values their examples cover ·spec:consumers.agent-surface.example-space-coverage· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.example-space-coverage
Example · A number slot is not enumerable and reports no uncovered value
A number slot is not enumerable and reports no uncovered value ·spec:consumers.agent-surface.example-space-coverage.number-not-enumerable· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface.example-space-coverage
Example · A literal no example binds is reported uncovered, and an unbound child is named
A literal no example binds is reported uncovered, and an unbound child is named ·spec:consumers.agent-surface.example-space-coverage.uncovered-literal· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Example · A scripted body returns claim-decoded context, pre-shaped by the body
A scripted body returns claim-decoded context, pre-shaped by the body ·spec:consumers.agent-surface.scripted-context-body· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
A context bundle is composed per invocation within a stated budget ·spec:consumers.context-bundle· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.context-bundle
Example · A member larger than the budget is named, and no part is returned
A member larger than the budget is named, and no part is returned ·spec:consumers.context-bundle.oversized-member-named· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.context-bundle
Example · A Pack too large for one bundle reads whole in parts
A Pack too large for one bundle reads whole in parts ·spec:consumers.context-bundle.parts-cover-the-pack· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
The reader bridges agent entry points to composable graph context ·spec:consumers.reader· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.reader
The Pack context carries the Pack's design ·spec:consumers.pack-design· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.pack-design
A slice reads a Pack as one design, with the architecture it touches and what each member needs next ·spec:consumers.design-slice· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · Members rest on a chain
Members rest on a chain ·spec:consumers.design-slice.chain· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An unanchored component design stays visible
An unanchored component design stays visible ·spec:consumers.design-slice.component-absent· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · A realized component keeps its differing layer and uses apart
A realized component keeps its differing layer and uses apart ·spec:consumers.design-slice.component-differing· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · A realized component matches its declared values
A realized component matches its declared values ·spec:consumers.design-slice.component-matching· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An unreadable declared layer stays visible
An unreadable declared layer stays visible ·spec:consumers.design-slice.component-unreadable· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · A shaping decision comes before its member
A shaping decision comes before its member ·spec:consumers.design-slice.decision-backlink· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · A cycle shares a depth
A cycle shares a depth ·spec:consumers.design-slice.dependency-cycle· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An example folds without lending its readiness
An example folds without lending its readiness ·spec:consumers.design-slice.folded-example· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An example with its own dependency stays unfolded
An example with its own dependency stays unfolded ·spec:consumers.design-slice.independent-example· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · Outside components stop at the touched components' neighbors
Outside components stop at the touched components' neighbors ·spec:consumers.design-slice.outside-components· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An outside prerequisite names the member it holds
An outside prerequisite names the member it holds ·spec:consumers.design-slice.outside-holding· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · A prerequisite reaches its satisfying component
A prerequisite reaches its satisfying component ·spec:consumers.design-slice.outside-satisfied· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
Example · An unbound prerequisite invents no component
An unbound prerequisite invents no component ·spec:consumers.design-slice.outside-unbound· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-slice
A slice page shows a Pack's design as one whole ·spec:consumers.spec-studio.slice-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · 1 open question · No blocking questions- non-blocking: Does a Pack export also carry the Pack's slice page?
Parent: spec:consumers.reader
Example · A changeset names what it reaches, why, and what it cannot see
A changeset names what it reaches, why, and what it cannot see ·spec:consumers.reader.changeset-entry· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.reader
Example · A concept recorded only inside a Spec's sections is still reached, and the field is named
A concept recorded only inside a Spec's sections is still reached, and the field is named ·spec:consumers.reader.concept-entry· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.reader
Example · A source file reaches the Spec its binding names, and a carrier reaches its own Spec
A source file reaches the Spec its binding names, and a carrier reaches its own Spec ·spec:consumers.reader.file-entry· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
The reading skill teaches agents to query the graph ·spec:consumers.reading-on-ramp· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.reading-on-ramp
The Studio skill teaches agents to publish, share and read the Spec Studio ·spec:consumers.studio-on-ramp· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.reading-on-ramp
The vault skill teaches agents to keep an Obsidian vault of the graph ·spec:consumers.vault-on-ramp· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Decision · The agent front door is one evaluation sink over the exported reader
The agent front door is one evaluation sink over the exported reader ·spec:decisions.agent-front-door· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Decision · Agents script the visible graph
Agents script the visible graph ·spec:decisions.agent-surface-scripts-graph· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:consumers.agent-surface
Corpus-authored rules run on the one validation path ·spec:validation.corpus-rules· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Declared architecture rules are checked against anchored structure ·spec:validation.architecture-constraints· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.architecture-constraints
Example · A domain member that uses an infrastructure member breaks a forbidden pair
A domain member that uses an infrastructure member breaks a forbidden pair ·spec:validation.architecture-constraints.forbidden-layer-pair· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.architecture-constraints
Example · The walk named as a rules file fails validation on an isolation breach
The walk named as a rules file fails validation on an isolation breach ·spec:validation.architecture-constraints.isolated-context-as-rule· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.architecture-constraints
Example · A component with no layer leaves its edge unclassified
A component with no layer leaves its edge unclassified ·spec:validation.architecture-constraints.unstated-layer-unclassified· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · A rules file that empties its graph leaves the next file's graph whole
A rules file that empties its graph leaves the next file's graph whole ·spec:validation.corpus-rules.copies-contain-changes· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · An error from a corpus rule fails validation and leaves the Protocol's line alone
An error from a corpus rule fails validation and leaves the Protocol's line alone ·spec:validation.corpus-rules.error-finding-fails· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · A finding with no subject fails its rules file
A finding with no subject fails its rules file ·spec:validation.corpus-rules.malformed-finding-fails· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · Editing a parameter file starts a cycle that reads the new parameters
Editing a parameter file starts a cycle that reads the new parameters ·spec:validation.corpus-rules.params-edit-starts-a-cycle· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · Rewriting a rules file under node_modules starts a cycle that runs the new body
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 · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · A parameter file that stops being JSON fails only its own rules file, and the watcher runs on
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 · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
Example · A warning from a corpus rule informs and passes
A warning from a corpus rule informs and passes ·spec:validation.corpus-rules.warning-finding-informs· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.corpus-rules
A corpus checks the register tokens its prose cites ·spec:validation.external-registers· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.external-registers
Example · A held token no Spec cites fails a rules run only when the caller asks
A held token no Spec cites fails a rules run only when the caller asks ·spec:validation.external-registers.uncited-on-request· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.external-registers
Example · A cited token the register lacks or retires fails a rules run
A cited token the register lacks or retires fails a rules run ·spec:validation.external-registers.unknown-and-retired· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.projections-model
The capability map reads every epic and its refinement descendants ·spec:consumers.capability-map· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.capability-map
The capability map page makes refinement readable by epic ·spec:consumers.spec-studio.capability-map-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.capability-map
Decision · Capability epics keep kind independent of altitude
Capability epics keep kind independent of altitude ·spec:decisions.epics-of-any-kind· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:consumers.projections-model
Census renders the runtime taxonomy without becoming a registry ·spec:consumers.census-page· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.projections-model
Every verb answers --help, and one verb writes every projection root ·spec:consumers.command-line· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.command-line
Example · A root that fails its check is removed while sdp generate writes the others
A root that fails its check is removed while sdp generate writes the others ·spec:consumers.command-line.generate-check-failure· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.command-line
Example · One run of sdp generate leaves all five roots current
One run of sdp generate leaves all five roots current ·spec:consumers.command-line.generate-writes-every-root· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.command-line
Example · A publisher's --help prints its help and touches no root
A publisher's --help prints its help and touches no root ·spec:consumers.command-line.verb-help-touches-nothing· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.command-line
The CLI names the engine that produced a result ·spec:consumers.engine-provenance· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.projections-model
Designs are compared between a base commit and the working tree at entry grain ·spec:consumers.design-diff· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.projections-model
Design Review renders graph context without becoming a gate ·spec:consumers.design-review· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-review
Views speak binding language, never the internal fact name ·spec:consumers.binding-language-views· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.binding-language-views
Example · A fully bound Spec renders binding language on the page and in the index
A fully bound Spec renders binding language on the page and in the index ·spec:consumers.binding-language-views.bound-spec-page· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.binding-language-views
Example · The Pack member table speaks the page's binding language, not a shorthand
The Pack member table speaks the page's binding language, not a shorthand ·spec:consumers.binding-language-views.pack-member-table· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-review
A Pack page shows where the Pack's design stands ·spec:consumers.design-review.pack-design-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-review.pack-design-page
Decision · The Design Review's Pack page presents the Pack's design
The Design Review's Pack page presents the Pack's design ·spec:decisions.pack-design-page· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:consumers.design-review
Example · The view is the graph read twice, and the corpus is untouched by reading it
The view is the graph read twice, and the corpus is untouched by reading it ·spec:consumers.design-review.pure-projection· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-review
Every view run rewrites the view wholesale ·spec:consumers.wholesale-view-rewrite· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.wholesale-view-rewrite
Example · A build that never renders still takes the old view down
A build that never renders still takes the old view down ·spec:consumers.wholesale-view-rewrite.build-invalidates-view· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.wholesale-view-rewrite
Example · A run that cannot produce a current view leaves no view at all
A run that cannot produce a current view leaves no view at all ·spec:consumers.wholesale-view-rewrite.failed-run-view-removed· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.wholesale-view-rewrite
Example · A page the build's invalidation never saw still does not survive the swap
A page the build's invalidation never saw still does not survive the swap ·spec:consumers.wholesale-view-rewrite.late-stale-page· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.wholesale-view-rewrite
Example · A page from an earlier run does not survive the next one
A page from an earlier run does not survive the next one ·spec:consumers.wholesale-view-rewrite.stale-page-removed· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.design-review
Decision · The Design Review shows an open question's key
The Design Review shows an open question's key ·spec:decisions.question-key-rendering· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:consumers.projections-model
Views compose scoped intent instead of patching canonical source ·spec:consumers.edit-model· behavior · feature · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.edit-model
Composed intent hands off on one proposal shape ·spec:consumers.intent-composition· behavior · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.intent-composition
A change proposal is addressed, based and checked before it lands ·spec:consumers.intent-composition.proposal· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.intent-composition.proposal
Recipe 49 renders a change proposal as the Markdown memo a person reviews ·spec:consumers.intent-composition.proposal.memo· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.intent-composition
A composing panel on every page gathers scoped intent for an agent ·spec:consumers.spec-studio.intent-panel· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.intent-panel
Example · Refreshing a tab keeps every gathered intent
Refreshing a tab keeps every gathered intent ·spec:consumers.spec-studio.intent-panel.refresh-keeps-intents· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.projections-model
Gherkin view renders any Spec as a disposable read shape ·spec:consumers.gherkin-view· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.projections-model
Mechanical code structure stays inferred and apart from curated intent ·spec:consumers.impact-graph· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.impact-graph
File-level imports show where curation is missing ·spec:consumers.impact-graph.curation-assist· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.impact-graph
Exhaustive symbol reach waits for a language-neutral identity ·spec:consumers.impact-graph.symbol-reach· behavior · feature · stated idea · floor scoped · implementation binding none · verifier binding none · 1 open question · 1 blocking question- blocking: Which language-neutral identity and extraction boundary can support exhaustive symbol reach without freezing a single compiler's representation into the Protocol?
Parent: spec:consumers.projections-model
Mermaid renders bounded one-hop and Pack diagrams without becoming a graph browser ·spec:consumers.mermaid-view· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.projections-model
An Obsidian vault lets a person iterate on designs from the one graph ·spec:consumers.obsidian-vault· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
A Pack's members and the standing queries are tables over the reader's values ·spec:consumers.obsidian-vault.bases· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault.bases
Example · Each standing view selects what its source selects
Each standing view selects what its source selects ·spec:consumers.obsidian-vault.bases.views-match-sources· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
Example · A generated note a person changed refuses the regeneration and keeps the edit
A generated note a person changed refuses the regeneration and keeps the edit ·spec:consumers.obsidian-vault.changed-note-refused· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
Example · A failed extraction keeps the notes and says so on the index
A failed extraction keeps the notes and says so on the index ·spec:consumers.obsidian-vault.failed-extraction-keeps-notes· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
Example · The run after a failed extraction passes the guard and restores the index
The run after a failed extraction passes the guard and restores the index ·spec:consumers.obsidian-vault.failed-extraction-recovered· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
Example · A fresh vault is written the same way twice and every link resolves
A fresh vault is written the same way twice and every link resolves ·spec:consumers.obsidian-vault.fresh-vault· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
Example · A run after a stopped synchronization finishes it
A run after a stopped synchronization finishes it ·spec:consumers.obsidian-vault.interrupted-run-recovered· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
A design pass is followed and answered from the vault ·spec:consumers.obsidian-vault.iteration· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault.iteration
Example · A carrier edit under watch rewrites only the notes it changes
A carrier edit under watch rewrites only the notes it changes ·spec:consumers.obsidian-vault.iteration.watch-rewrites-changed-notes· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault.iteration
Example · An anchor added in a source file under watch rewrites the Spec's note
An anchor added in a source file under watch rewrites the Spec's note ·spec:consumers.obsidian-vault.iteration.watch-source-anchor· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
Every Spec, Pack, code unit and keyed term is a note, and every relation is a link ·spec:consumers.obsidian-vault.notes· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault.notes
Example · Two Specs whose notes differ only in case refuse the run
Two Specs whose notes differ only in case refuse the run ·spec:consumers.obsidian-vault.notes.case-collision-refused· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault.notes
Example · An entry address in prose opens the entry's block in its Spec's note
An entry address in prose opens the entry's block in its Spec's note ·spec:consumers.obsidian-vault.notes.entry-address-link· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault.notes
Example · A keyed Model term gets a note, and its address in prose opens the term's block
A keyed Model term gets a note, and its address in prose opens the term's block ·spec:consumers.obsidian-vault.notes.term-address-link· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault.notes
Example · A mention of an entry that does not exist stays as written
A mention of an entry that does not exist stays as written ·spec:consumers.obsidian-vault.notes.unresolved-mention-stays· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
Example · A regeneration removes a note that left the graph and keeps a person's notes
A regeneration removes a note that left the graph and keeps a person's notes ·spec:consumers.obsidian-vault.person-notes-survive· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
Example · A note a person wrote inside the generated folder refuses the regeneration
A note a person wrote inside the generated folder refuses the regeneration ·spec:consumers.obsidian-vault.unknown-note-refused· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
Example · A vault directory the build removes refuses the run and keeps a person's notes
A vault directory the build removes refuses the run and keeps a person's notes ·spec:consumers.obsidian-vault.vault-in-build-path-refused· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.obsidian-vault
Decision · The vault's generator owns one folder and synchronizes it
The vault's generator owns one folder and synchronizes it ·spec:decisions.vault-owned-folder· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:consumers.projections-model
Roadmap views read releases, baselines and phases from git and the graph ·spec:consumers.projections-model.roadmap-views· model · story · stated scoped · floor scoped · implementation binding none · verifier binding none · 1 open question · 1 blocking question- blocking: Does a reader need release or baseline views that the roadmap, the recipes and git tags do not serve?
Parent: spec:consumers.projections-model
A reference projection serves a reader outside the repository ·spec:consumers.reference-projection· behavior · feature · stated idea · floor idea · implementation binding none · verifier binding none · 2 open questions · 1 blocking question- blocking: 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.
- non-blocking: Would the reference read pinned declarations, contract-kind Specs or
api:code anchors, and does any of them hold enough to document an interface?
Parent: spec:consumers.projections-model
A Pack is read from a named perspective ·spec:consumers.review-perspectives· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.projections-model
The Spec Studio is a static HTML workbench over the one graph ·spec:consumers.spec-studio· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
A pinned declaration shows the words of each test line that cites it ·spec:consumers.spec-studio.cited-line-text· behavior · story · stated scoped · floor scoped · implementation binding none · verifier binding none · 2 open questions · 1 blocking question- blocking: May the Studio show source text the graph does not hold, and if so is it recorded in the graph beside the citation or read as a named input?
- non-blocking: How long may a recorded line be, and how does a page show a line that was cut?
Parent: spec:consumers.spec-studio
The Studio's custom elements each hold one view the build renders ·spec:consumers.spec-studio.components· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.components
A diagram is laid out from graph values into SVG with a text equivalent ·spec:consumers.spec-studio.diagrams· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagrams
The Studio chooses diagram kinds from graph values ·spec:consumers.spec-studio.diagram-kinds· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagram-kinds
A refinement drawing follows the capability map ·spec:consumers.spec-studio.diagram-kinds.capability-tree· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagram-kinds
A dependency drawing shows the declared footing of a Spec set ·spec:consumers.spec-studio.diagram-kinds.dependency· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagram-kinds
Edges route around boxes with deterministic orthogonal paths ·spec:consumers.spec-studio.diagram-kinds.edge-routing· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagram-kinds
A diagram preserves readable labels before zoom ·spec:consumers.spec-studio.diagram-kinds.legibility· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagram-kinds
The maturity map is drawn as a grid of counts ·spec:consumers.spec-studio.diagram-kinds.maturity-picture· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagram-kinds
A diagram offers Mermaid source as copyable text ·spec:consumers.spec-studio.diagram-kinds.mermaid-source· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagram-kinds
A requirement drawing separates intent from realization and verification ·spec:consumers.spec-studio.diagram-kinds.requirement-trace· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagram-kinds
A Spec set draws the architecture it touches ·spec:consumers.spec-studio.diagram-kinds.scoped-architecture· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagrams
Edges route around boxes with deterministic orthogonal paths ·spec:consumers.spec-studio.diagram-kinds.edge-routing· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questions · Repeat of first occurrenceParent: spec:consumers.spec-studio.diagrams
A diagram preserves readable labels before zoom ·spec:consumers.spec-studio.diagram-kinds.legibility· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questions · Repeat of first occurrenceParent: spec:consumers.spec-studio.diagrams
Example · An architecture over the bound folds by context
An architecture over the bound folds by context ·spec:consumers.spec-studio.diagrams.folds-by-context· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagrams
Example · One context over the bound folds by layer
One context over the bound folds by layer ·spec:consumers.spec-studio.diagrams.folds-by-layer· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diagrams
Example · An architecture within the bound draws in one diagram, the same bytes twice
An architecture within the bound draws in one diagram, the same bytes twice ·spec:consumers.spec-studio.diagrams.within-bound· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.components
A few custom elements filter, search, open and copy on a rendered page ·spec:consumers.spec-studio.page-elements· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
The Studio renders from the reader's values and embeds only what its script reads ·spec:consumers.spec-studio.data· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.data
The Studio reads two named inputs beside the graph, a base graph and run records ·spec:consumers.spec-studio.data.inputs· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.data.inputs
Example · Both inputs add their pages, named, and the same inputs write the same bytes
Both inputs add their pages, named, and the same inputs write the same bytes ·spec:consumers.spec-studio.data.inputs.both-given· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.data.inputs
Example · Without inputs the page set is the graph's alone
Without inputs the page set is the graph's alone ·spec:consumers.spec-studio.data.inputs.graph-only· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.data
A page takes each recipe answer from the recipe's shipped body ·spec:consumers.spec-studio.data.recipe-answers· contract · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
The diff page shows what changed in the design since a base graph ·spec:consumers.spec-studio.diff-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.diff-page
Example · The diff page shows a changed entry's base and built values
The diff page shows a changed entry's base and built values ·spec:consumers.spec-studio.diff-page.changed-entry· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
A Pack exports as one file, and every page prints as a document ·spec:consumers.spec-studio.export· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.export
Example · A Pack's export opens alone and keeps its links inside it
A Pack's export opens alone and keeps its links inside it ·spec:consumers.spec-studio.export.self-contained· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
The glossary page lists every term the corpus's Specs define ·spec:consumers.spec-studio.glossary-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.glossary-page
Example · A word two Specs define appears once per Spec on the glossary page
A word two Specs define appears once per Spec on the glossary page ·spec:consumers.spec-studio.glossary-page.same-word-twice· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
Five lenses read the graph as Packs, capabilities, architecture, tests and evidence ·spec:consumers.spec-studio.lenses· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.lenses
The capability map page makes refinement readable by epic ·spec:consumers.spec-studio.capability-map-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questions · Repeat of first occurrenceParent: spec:consumers.spec-studio.lenses
The architecture lens draws components by context and layer, the planned beside the built ·spec:consumers.spec-studio.lenses.architecture· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.lenses.architecture
Example · A component design no anchor realizes draws planned beside the built one
A component design no anchor realizes draws planned beside the built one ·spec:consumers.spec-studio.lenses.architecture.planned-apart· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.lenses.architecture
The architecture page lists each component's significant units by role ·spec:consumers.spec-studio.lenses.architecture.unit-register· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.lenses
The evidence lens names each source of runtime evidence and reads it as not tracked ·spec:consumers.spec-studio.lenses.evidence· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.lenses
The Packs lens groups every Spec by the Packs that hold it ·spec:consumers.spec-studio.lenses.packs· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.lenses.packs
The index says where the corpus stands and narrows every Spec ·spec:consumers.spec-studio.index-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.lenses
The tests lens shows how far each Spec's verification reaches ·spec:consumers.spec-studio.lenses.tests· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.lenses.tests
Example · A Spec's row on the tests lens counts its exercised keyed rules
A Spec's row on the tests lens counts its exercised keyed rules ·spec:consumers.spec-studio.lenses.tests.coverage-row· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
The owner queue page orders the statements and questions only a person can settle ·spec:consumers.spec-studio.owner-queue· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.owner-queue
Example · The owner queue lists a waiting statement after the one it rests on
The owner queue lists a waiting statement after the one it rests on ·spec:consumers.spec-studio.owner-queue.dependency-first· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
A Pack page shows the Pack's design as one card per member ·spec:consumers.spec-studio.pack-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.pack-page
A Pack page's maturity map places every member by its stated rung and its floor ·spec:consumers.spec-studio.pack-page.maturity-map· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
sdp studiopublishes the Studio as one page set ·spec:consumers.spec-studio.publisher· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.publisher
sdp studio --watchrebuilds the page set on each carrier change ·spec:consumers.spec-studio.publisher.watch· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.publisher.watch
Example · Each watch cycle writes the page set a plain run writes
Each watch cycle writes the page set a plain run writes ·spec:consumers.spec-studio.publisher.watch.matches-plain-run· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
An outside register is a named Studio input, so a cited token links to its entry ·spec:consumers.spec-studio.register-input· behavior · story · stated scoped · floor scoped · implementation binding none · verifier binding none · 3 open questions · 2 blocking questions- blocking: What does a register file give the Studio beyond what the external-registers recipe reads, so a token's entry can be shown?
- blocking: How does the studio verb name a register, its pattern and the words that name it on a page?
- non-blocking: Does a cited token become a link inside the rendered text of a Spec, or only in a list beside it?
Parent: spec:consumers.spec-studio
The corpus's registers are pages a reviewer opens from a link ·spec:consumers.spec-studio.registers· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.registers
Example · The questions page lists the Specs with a blocking question first
The questions page lists the Specs with a blocking question first ·spec:consumers.spec-studio.registers.blocking-first· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
The Studio reads on a phone as on a desktop ·spec:consumers.spec-studio.responsive· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
The roadmap page shows the upcoming work in priority order, split by what it needs ·spec:consumers.spec-studio.roadmap-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
The runs page shows the run records the build was given, joined to test files ·spec:consumers.spec-studio.runs-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.runs-page
Example · The runs page shows a run as external evidence from a test file
The runs page shows a run as external evidence from a test file ·spec:consumers.spec-studio.runs-page.external-evidence· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
A Studio build is stamped and shared from a static host ·spec:consumers.spec-studio.sharing· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.sharing
Example · The stamp is written beside the page set, and a later build removes it
The stamp is written beside the page set, and a later build removes it ·spec:consumers.spec-studio.sharing.stamp-written-apart· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
The Studio's shell frames every page with navigation, a rail and a canvas ·spec:consumers.spec-studio.shell· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.shell
Search finds a Spec, a Pack, an entry or a bound file by a word ·spec:consumers.spec-studio.search· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
A slice page shows a Pack's design as one whole ·spec:consumers.spec-studio.slice-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · 1 open question · No blocking questions- non-blocking: Does a Pack export also carry the Pack's slice page?
Parent: spec:consumers.spec-studio
A Spec page shows one Spec in collapsible panels, in a fixed order ·spec:consumers.spec-studio.spec-page· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.spec-page
Example · A pinned declaration shows the test line that cites it
A pinned declaration shows the test line that cites it ·spec:consumers.spec-studio.spec-page.cited-declaration· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.spec-page
A Spec page's core shows the whole Spec, with an anchor for every entry ·spec:consumers.spec-studio.spec-page.core· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.spec-page
The panels for examples, targets, verifiers and evidence ·spec:consumers.spec-studio.verification-panels· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio.verification-panels
Example · Each keyed rule shows the examples that exercise it, or that none does
Each keyed rule shows the examples that exercise it, or that none does ·spec:consumers.spec-studio.verification-panels.rule-coverage· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:consumers.spec-studio
Decision · The Studio renders HTML, and the HTML stays derived
The Studio renders HTML, and the HTML stays derived ·spec:decisions.studio-html-surface· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:consumers.spec-studio
Decision · The Studio is built from custom elements, not a framework
The Studio is built from custom elements, not a framework ·spec:decisions.studio-web-components· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:decisions.studio-web-components
Decision · The build renders every Studio view, and an element only enhances it
The build renders every Studio view, and an element only enhances it ·spec:decisions.studio-build-renders· decision · story · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:decisions.studio-web-components
Decision · The engine lays out every Studio diagram as static SVG when the page set is built
The engine lays out every Studio diagram as static SVG when the page set is built ·spec:decisions.studio-diagram-renderer· decision · story · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:consumers.projections-model
Mermaid diagrams can be rooted at code units ·spec:consumers.structural-mermaid· behavior · feature · stated scoped · floor scoped · implementation binding none · verifier binding none · 1 open question · 1 blocking question- blocking: Does a reader need diagrams rooted at code units, which census tables and Spec-rooted one-hop Mermaid do not serve?
Parent: spec:consumers.projections-model
Decision · MCP integration remains deferred
MCP integration remains deferred ·spec:decisions.mcp-deferred· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:consumers.projections-model
Decision · The shipped projections stay frozen
The shipped projections stay frozen ·spec:decisions.shipped-projections-frozen· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:decisions.shipped-projections-frozen
Decision · Bindings are optional, plural, and may reference a design
Bindings are optional, plural, and may reference a design ·spec:decisions.anchor-binding-grain· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:decisions.shipped-projections-frozen
Decision · Architectural significance is annotated where it is realized
Architectural significance is annotated where it is realized ·spec:decisions.architectural-annotation· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:decisions.shipped-projections-frozen
Decision · The Design Review renders open-section entries as a list
The Design Review renders open-section entries as a list ·spec:decisions.authored-entry-order· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions · Repeat of first occurrenceParent: spec:decisions.shipped-projections-frozen
Decision · The Design Review's Pack page presents the Pack's design
The Design Review's Pack page presents the Pack's design ·spec:decisions.pack-design-page· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions · Repeat of first occurrenceParent: spec:decisions.shipped-projections-frozen
Decision · The Design Review shows an open question's key
The Design Review shows an open question's key ·spec:decisions.question-key-rendering· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions · Repeat of first occurrenceParent: spec:consumers.projections-model
CI run records are joined to verifiers in a view ·spec:observation.run-evidence· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · 1 open question · No blocking questions- non-blocking: 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?
Parent: spec:observation.run-evidence
Example · A test whose reporter wrote an absolute path joins its anchored file
A test whose reporter wrote an absolute path joins its anchored file ·spec:observation.run-evidence.absolute-path-joins· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:observation.run-evidence
Example · A test in a file with no test anchor is reported as unjoined
A test in a file with no test anchor is reported as unjoined ·spec:observation.run-evidence.unanchored-file-unjoined· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questions
Carrier reification derives the one graph
Epic's own evidence
Carrier reification derives the one graph ·
spec:extraction.derive-graph · behavior · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsDistinct descendants, excluding this epic: 27 Specs · 12 examples · 1 decision.
- Stated rungs
- idea 1 · scoped 0 · defined 0 · ready 26
- Floors reached
- none 0 · idea 1 · scoped 0 · defined 0 · ready 26
- Kinds
- behavior 6 · workflow 1 · example 12 · rule 5 · constraint 1 · model 1 · decision 1 · contract 0
- Altitudes
- epic 0 · feature 9 · story 18
- Binding evidence
- 13 Specs with implementation binding present · 25 Specs with verifier binding present
- Questions
- 1 open question · 1 blocking question
Arrows: refines (declared). Later visits repeat a Spec and link to its first occurrence.
The diagram as text
28 unique Specs; 11 rendered boxes.
spec:extraction.derive-graph: Carrier reification derives the one graph · epicspec:extraction.build-pipeline: The build pipeline has one ordered flow · featurespec:extraction.build-pipeline.same-invocation: One query invocation shares its extracted graph and validation result · storyspec:extraction.executable-contracts: The build derives step and space contracts from graph examples · featurespec:extraction.contract-declarations: Pinned declarations give an adopter a derived module to typecheck · featurespec:extraction.executable-contracts.case-colliding-path: A case-only path collision withholds the whole contracts tree · storyspec:extraction.executable-contracts.concreteness-refusal: An unbound slot in a used step earns no step contract · storyspec:extraction.executable-contracts.multi-entry-example: A second structured entry is named, never left silently inert · storyspec:extraction.claim-taxonomy: Graph claims retain their epistemic source · featurespec:extraction.delivery-facts: Resolving bindings confer direct delivery facts · storyspec:extraction.determinism: Committed source derives byte-identical output · featurespec:extraction.regenerability: Generated artifacts are disposable projections · featurespec:extraction.entry-citations: The graph records where anchored source cites an entry address · storyspec:extraction.entry-citations.code-comment-cites-declaration: A code file's comment cites a declaration without reading as a test line · storyspec:extraction.entry-citations.test-title-cites-declaration: A test title in an anchored file cites a pinned declaration · storyspec:extraction.entry-citations.unanchored-file-unread: A file that carries no anchor is not read for citations · storyspec:extraction.entry-citations.unresolved-citation: A citation of an entry its Spec lacks reports through the recipe, never as a Protocol finding · storyspec:extraction.entry-locations: The graph records where each addressable entry is written · storyspec:extraction.excludes: Extraction exclusions are strict consumer input · featurespec:decisions.exclusion-contract: Consumer exclusions stay exact · featurespec:extraction.excludes.refused-path: A Windows-drive absolute path is refused rather than normalized · storyspec:extraction.excludes.segment-boundary: A prefix excludes its own tree and leaves a similar sibling standing · storyspec:extraction.open-section-order: Serialization preserves authored entry order · storyspec:extraction.pack-member-order: A Pack node keeps its members in authored order · storyspec:extraction.pack-member-order.manifest-order-kept: A manifest's member order survives into the graph and the reader · storyspec:extraction.schema-versioning: The graph declares its schema version · storyspec:extraction.schema-versioning.declared-version: A derived payload carries a schema version its consumer can read · storyspec:observation.runtime-overlay: Runtime observations can close the liveness loop · featurespec:decisions.exclusion-contractrefinesspec:extraction.excludes· declaredspec:extraction.build-pipelinerefinesspec:extraction.derive-graph· declared — the build orchestrates derivation and publication of the one graphspec:extraction.build-pipeline.same-invocationrefinesspec:extraction.build-pipeline· declaredspec:extraction.claim-taxonomyrefinesspec:extraction.derive-graph· declaredspec:extraction.contract-declarationsrefinesspec:extraction.executable-contracts· declaredspec:extraction.delivery-factsrefinesspec:extraction.derive-graph· declaredspec:extraction.determinismrefinesspec:extraction.derive-graph· declared — deterministic output constrains the derivation capabilityspec:extraction.entry-citationsrefinesspec:extraction.derive-graph· declaredspec:extraction.entry-citations.code-comment-cites-declarationrefinesspec:extraction.entry-citations· declaredspec:extraction.entry-citations.test-title-cites-declarationrefinesspec:extraction.entry-citations· declaredspec:extraction.entry-citations.unanchored-file-unreadrefinesspec:extraction.entry-citations· declaredspec:extraction.entry-citations.unresolved-citationrefinesspec:extraction.entry-citations· declaredspec:extraction.entry-locationsrefinesspec:extraction.derive-graph· declaredspec:extraction.excludesrefinesspec:extraction.derive-graph· declaredspec:extraction.excludes.refused-pathrefinesspec:extraction.excludes· declaredspec:extraction.excludes.segment-boundaryrefinesspec:extraction.excludes· declaredspec:extraction.executable-contractsrefinesspec:extraction.build-pipeline· declaredspec:extraction.executable-contracts.case-colliding-pathrefinesspec:extraction.executable-contracts· declaredspec:extraction.executable-contracts.concreteness-refusalrefinesspec:extraction.executable-contracts· declaredspec:extraction.executable-contracts.multi-entry-examplerefinesspec:extraction.executable-contracts· declaredspec:extraction.open-section-orderrefinesspec:extraction.derive-graph· declaredspec:extraction.pack-member-orderrefinesspec:extraction.derive-graph· declaredspec:extraction.pack-member-order.manifest-order-keptrefinesspec:extraction.pack-member-order· declaredspec:extraction.regenerabilityrefinesspec:extraction.determinism· declaredspec:extraction.schema-versioningrefinesspec:extraction.derive-graph· declaredspec:extraction.schema-versioning.declared-versionrefinesspec:extraction.schema-versioning· declaredspec:observation.runtime-overlayrefinesspec:extraction.derive-graph· declared — an observed fact would be derived beside implemented and has-verifier
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred syntax: mindmap. Chosen syntax: flowchart BT because the drawing has a fold.
Complete refinement text
Root
Carrier reification derives the one graph ·spec:extraction.derive-graph· behavior · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.derive-graph
The build pipeline has one ordered flow ·spec:extraction.build-pipeline· workflow · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.build-pipeline
Example · One query invocation shares its extracted graph and validation result
One query invocation shares its extracted graph and validation result ·spec:extraction.build-pipeline.same-invocation· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.build-pipeline
The build derives step and space contracts from graph examples ·spec:extraction.executable-contracts· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.executable-contracts
Pinned declarations give an adopter a derived module to typecheck ·spec:extraction.contract-declarations· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.executable-contracts
Example · A case-only path collision withholds the whole contracts tree
A case-only path collision withholds the whole contracts tree ·spec:extraction.executable-contracts.case-colliding-path· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.executable-contracts
Example · An unbound slot in a used step earns no step contract
An unbound slot in a used step earns no step contract ·spec:extraction.executable-contracts.concreteness-refusal· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.executable-contracts
Example · A second structured entry is named, never left silently inert
A second structured entry is named, never left silently inert ·spec:extraction.executable-contracts.multi-entry-example· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.derive-graph
Graph claims retain their epistemic source ·spec:extraction.claim-taxonomy· model · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.derive-graph
Resolving bindings confer direct delivery facts ·spec:extraction.delivery-facts· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.derive-graph
Committed source derives byte-identical output ·spec:extraction.determinism· constraint · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.determinism
Generated artifacts are disposable projections ·spec:extraction.regenerability· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.derive-graph
The graph records where anchored source cites an entry address ·spec:extraction.entry-citations· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.entry-citations
Example · A code file's comment cites a declaration without reading as a test line
A code file's comment cites a declaration without reading as a test line ·spec:extraction.entry-citations.code-comment-cites-declaration· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.entry-citations
Example · A test title in an anchored file cites a pinned declaration
A test title in an anchored file cites a pinned declaration ·spec:extraction.entry-citations.test-title-cites-declaration· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.entry-citations
Example · A file that carries no anchor is not read for citations
A file that carries no anchor is not read for citations ·spec:extraction.entry-citations.unanchored-file-unread· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.entry-citations
Example · A citation of an entry its Spec lacks reports through the recipe, never as a Protocol finding
A citation of an entry its Spec lacks reports through the recipe, never as a Protocol finding ·spec:extraction.entry-citations.unresolved-citation· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.derive-graph
The graph records where each addressable entry is written ·spec:extraction.entry-locations· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.derive-graph
Extraction exclusions are strict consumer input ·spec:extraction.excludes· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.excludes
Decision · Consumer exclusions stay exact
Consumer exclusions stay exact ·spec:decisions.exclusion-contract· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:extraction.excludes
Example · A Windows-drive absolute path is refused rather than normalized
A Windows-drive absolute path is refused rather than normalized ·spec:extraction.excludes.refused-path· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.excludes
Example · A prefix excludes its own tree and leaves a similar sibling standing
A prefix excludes its own tree and leaves a similar sibling standing ·spec:extraction.excludes.segment-boundary· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.derive-graph
Serialization preserves authored entry order ·spec:extraction.open-section-order· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.derive-graph
A Pack node keeps its members in authored order ·spec:extraction.pack-member-order· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.pack-member-order
Example · A manifest's member order survives into the graph and the reader
A manifest's member order survives into the graph and the reader ·spec:extraction.pack-member-order.manifest-order-kept· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.derive-graph
The graph declares its schema version ·spec:extraction.schema-versioning· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.schema-versioning
Example · A derived payload carries a schema version its consumer can read
A derived payload carries a schema version its consumer can read ·spec:extraction.schema-versioning.declared-version· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.derive-graph
Runtime observations can close the liveness loop ·spec:observation.runtime-overlay· behavior · feature · stated idea · floor idea · implementation binding none · verifier binding none · 1 open question · 1 blocking question- blocking: Which external observation identity and freshness boundary is small enough for the graph while still supporting an honest
observeddelivery fact?
- blocking: Which external observation identity and freshness boundary is small enough for the graph while still supporting an honest
Bound examples execute their authored steps
Epic's own evidence
Bound examples execute their authored steps ·
spec:extraction.executable-examples · behavior · epic · stated ready · floor ready · implementation binding present · verifier binding none · No open questions · No blocking questionsDistinct descendants, excluding this epic: 10 Specs · 5 examples · 1 decision.
- Stated rungs
- idea 0 · scoped 0 · defined 0 · ready 10
- Floors reached
- none 0 · idea 0 · scoped 0 · defined 0 · ready 10
- Kinds
- behavior 4 · workflow 0 · example 5 · rule 0 · constraint 0 · model 0 · decision 1 · contract 0
- Altitudes
- epic 0 · feature 5 · story 5
- Binding evidence
- 4 Specs with implementation binding present · 9 Specs with verifier binding present
- Questions
- No open questions · No blocking questions
Arrows: refines (declared). Later visits repeat a Spec and link to its first occurrence.
The diagram as text
11 unique Specs; 11 rendered boxes.
spec:extraction.executable-examples: Bound examples execute their authored steps · epicspec:extraction.example-runner: A bound example runs its contract steps against a fresh world · featurespec:extraction.example-runner.red-step-naming: A red step names itself before the assertion detail · storyspec:extraction.example-runner.step-order: A repeated step runs its one handler at each occurrence, in contract order · storyspec:extraction.runnable-modules: Derived runnable modules freeze the registrar interface · featurespec:decisions.adopted-registrars-committed: Adopted runnable registrars are committed · featurespec:extraction.executable-contracts: The build derives step and space contracts from graph examples · featurespec:extraction.contract-declarations: Pinned declarations give an adopter a derived module to typecheck · featurespec:extraction.executable-contracts.case-colliding-path: A case-only path collision withholds the whole contracts tree · storyspec:extraction.executable-contracts.concreteness-refusal: An unbound slot in a used step earns no step contract · storyspec:extraction.executable-contracts.multi-entry-example: A second structured entry is named, never left silently inert · storyspec:decisions.adopted-registrars-committedrefinesspec:extraction.runnable-modules· declaredspec:extraction.contract-declarationsrefinesspec:extraction.executable-contracts· declaredspec:extraction.example-runnerrefinesspec:extraction.executable-examples· declared — step dispatch and failure rendering execute a bound examplespec:extraction.example-runner.red-step-namingrefinesspec:extraction.example-runner· declaredspec:extraction.example-runner.step-orderrefinesspec:extraction.example-runner· declaredspec:extraction.executable-contractsrefinesspec:extraction.executable-examples· declared — typed contracts carry the authored steps and example space into executionspec:extraction.executable-contracts.case-colliding-pathrefinesspec:extraction.executable-contracts· declaredspec:extraction.executable-contracts.concreteness-refusalrefinesspec:extraction.executable-contracts· declaredspec:extraction.executable-contracts.multi-entry-examplerefinesspec:extraction.executable-contracts· declaredspec:extraction.runnable-modulesrefinesspec:extraction.example-runner· declared
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred syntax: mindmap. Chosen syntax: mindmap.
Complete refinement text
Root
Bound examples execute their authored steps ·spec:extraction.executable-examples· behavior · epic · stated ready · floor ready · implementation binding present · verifier binding none · No open questions · No blocking questionsParent: spec:extraction.executable-examples
A bound example runs its contract steps against a fresh world ·spec:extraction.example-runner· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.example-runner
Example · A red step names itself before the assertion detail
A red step names itself before the assertion detail ·spec:extraction.example-runner.red-step-naming· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.example-runner
Example · A repeated step runs its one handler at each occurrence, in contract order
A repeated step runs its one handler at each occurrence, in contract order ·spec:extraction.example-runner.step-order· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.example-runner
Derived runnable modules freeze the registrar interface ·spec:extraction.runnable-modules· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.runnable-modules
Decision · Adopted runnable registrars are committed
Adopted runnable registrars are committed ·spec:decisions.adopted-registrars-committed· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:extraction.executable-examples
The build derives step and space contracts from graph examples ·spec:extraction.executable-contracts· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.executable-contracts
Pinned declarations give an adopter a derived module to typecheck ·spec:extraction.contract-declarations· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.executable-contracts
Example · A case-only path collision withholds the whole contracts tree
A case-only path collision withholds the whole contracts tree ·spec:extraction.executable-contracts.case-colliding-path· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.executable-contracts
Example · An unbound slot in a used step earns no step contract
An unbound slot in a used step earns no step contract ·spec:extraction.executable-contracts.concreteness-refusal· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:extraction.executable-contracts
Example · A second structured entry is named, never left silently inert
A second structured entry is named, never left silently inert ·spec:extraction.executable-contracts.multi-entry-example· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questions
The Protocol models delivery with one enrichable Spec
Epic's own evidence
The Protocol models delivery with one enrichable Spec ·
spec:model.core-model · model · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsDistinct descendants, excluding this epic: 49 Specs · 19 examples · 15 decisions.
- Stated rungs
- idea 0 · scoped 0 · defined 0 · ready 49
- Floors reached
- none 0 · idea 0 · scoped 0 · defined 0 · ready 49
- Kinds
- behavior 1 · workflow 0 · example 19 · rule 6 · constraint 0 · model 8 · decision 15 · contract 0
- Altitudes
- epic 0 · feature 23 · story 26
- Binding evidence
- 15 Specs with implementation binding present · 33 Specs with verifier binding present
- Questions
- 1 open question · No blocking questions
Arrows: refines (declared). Later visits repeat a Spec and link to its first occurrence.
The diagram as text
50 unique Specs; 12 rendered boxes.
spec:model.core-model: The Protocol models delivery with one enrichable Spec · epicspec:decisions.example-realization-posture: Example realization stays evidence, not backlog work · featurespec:decisions.one-primitive: One Spec carries named delivery coordinates · featurespec:model.anchors: Source anchors bind code without carrying intent · featurespec:decisions.anchor-binding-grain: Bindings are optional, plural, and may reference a design · featurespec:decisions.anchor-comment-form: The comment form is a second anchor representation · featurespec:decisions.architectural-annotation: Architectural significance is annotated where it is realized · featurespec:decisions.binding-not-liveness: Bindings state existence, not liveness · featurespec:model.anchors.lookalike-refusal: A consumer-local lookalike builder mints no anchor and no finding · storyspec:model.anchors.physical-identity: A deep relative import that resolves to the Protocol builders is trusted · storyspec:model.structural-patterns: Architecturally significant units are annotated where they are realized · featurespec:model.design-maturity: What a Spec's design carries is derived, beside its readiness · featurespec:model.enrichment-lifecycle: Enrichment keeps one Spec while its detail changes · featurespec:model.pack-aggregate: A Pack is a truth-free review aggregate · storyspec:carrier.markdown-pack-authoring: A Pack has a Markdown manifest carrier · featurespec:carrier.markdown-pack-authoring.markdown-ts-parity: A Markdown Pack twin matches its TypeScript manifest · storyspec:carrier.markdown-pack-authoring.spec-envelope-refused: A Spec key on a Pack envelope is refused · storyspec:decisions.pack-reified: Packs group review context without becoming truth · featurespec:model.planned-architecture: Components are designed ahead of their code · featurespec:model.planned-architecture.differing-layer-and-uses: A realized component that differs from its design gives one row per field · storyspec:model.planned-architecture.matching-design: A realized component that matches its design gives no row · storyspec:model.planned-architecture.unrealized-design: A component design no anchor satisfies is listed as unrealized · storyspec:model.relations: Specs declare typed directed relations · featurespec:decisions.planning-truths-placement: Planning truths live in ruled graph homes · featurespec:decisions.roadmap-over-plans: Plan and review files stop carrying the delivery record once the roadmap and the pull request do · featurespec:decisions.roadmap-priority: A roadmap states advisory priority in the graph · featurespec:model.relation-reasons: An authored relation may carry its reason · storyspec:model.spec-sections: Spec sections carry typed detail and direct verifier semantics · featurespec:decisions.content-only-sections: Sections carry content while relations carry links · featurespec:decisions.point-per-example: Each example binds one point · featurespec:decisions.typing-law: Floor-read sections are closed typed shapes · featurespec:decisions.verification-posture-not-realization: Verification mode states posture, not realization · featurespec:model.open-question-keys: An open question may carry a key that addresses it · storyspec:model.open-question-fields: An open question may name who decides it, its links, a provisional reading and a re-entry trigger · storyspec:model.open-question-fields.dropped-list-warns: A TypeScript question list that cannot be read drops whole with a warning · storyspec:model.open-question-keys.keyed-question-resolves: A keyed question is reified and its address resolves · storyspec:model.open-question-keys.renamed-key-breaks: A renamed question key fails the mention that addresses it · storyspec:model.open-question-keys.repeated-key-refused: A repeated question key refuses its carrier · storyspec:model.rule-keys: A rule or flow entry may carry a key that addresses it · storyspec:model.term-addresses: A Model term may carry a key that addresses it · storyspec:model.term-addresses.keyed-term-resolves: A keyed term is reified and its address resolves · storyspec:model.term-addresses.malformed-term-marker-refused: A term marker whose key is off the grammar refuses its carrier · storyspec:model.term-addresses.repeated-term-key-refused: A term key repeated in one Spec refuses its carrier · storyspec:model.term-addresses.typescript-term-imports-keyed: A keyed TypeScript term keeps its address through import to Markdown · storyspec:model.term-addresses.unknown-term-key-refused: An address that names a term key no term carries is an error · storyspec:model.stable-ids: Stable IDs are the Protocol's durable join key · storyspec:decisions.checked-mentions: A Spec id written in prose is a checked mention · featurespec:model.stable-ids.malformed-refusal: An uppercase namespace is refused with its reason named · storyspec:model.stable-ids.namespaced-round-trip: A namespaced dotted path with a sub-part survives parsing unchanged · storyspec:model.stable-ids.unsectioned-address-refused: A `#` sub-part without its section is refused with its reason named · storyspec:carrier.markdown-pack-authoringrefinesspec:model.pack-aggregate· declaredspec:carrier.markdown-pack-authoring.markdown-ts-parityrefinesspec:carrier.markdown-pack-authoring· declaredspec:carrier.markdown-pack-authoring.spec-envelope-refusedrefinesspec:carrier.markdown-pack-authoring· declaredspec:decisions.anchor-binding-grainrefinesspec:model.anchors· declaredspec:decisions.anchor-comment-formrefinesspec:model.anchors· declaredspec:decisions.architectural-annotationrefinesspec:model.anchors· declaredspec:decisions.binding-not-livenessrefinesspec:model.anchors· declaredspec:decisions.checked-mentionsrefinesspec:model.stable-ids· declaredspec:decisions.content-only-sectionsrefinesspec:model.spec-sections· declaredspec:decisions.example-realization-posturerefinesspec:model.core-model· declaredspec:decisions.one-primitiverefinesspec:model.core-model· declaredspec:decisions.pack-reifiedrefinesspec:model.pack-aggregate· declaredspec:decisions.planning-truths-placementrefinesspec:model.relations· declaredspec:decisions.point-per-examplerefinesspec:model.spec-sections· declaredspec:decisions.roadmap-over-plansrefinesspec:decisions.planning-truths-placement· declared — narrows what a plan file may still carry once a roadmap holds priorityspec:decisions.roadmap-priorityrefinesspec:decisions.planning-truths-placement· declared — narrows the refusal of recorded work order for one case, the advisory priority of a roadmapspec:decisions.typing-lawrefinesspec:model.spec-sections· declaredspec:decisions.verification-posture-not-realizationrefinesspec:model.spec-sections· declaredspec:model.anchorsrefinesspec:model.core-model· declaredspec:model.anchors.lookalike-refusalrefinesspec:model.anchors· declaredspec:model.anchors.physical-identityrefinesspec:model.anchors· declaredspec:model.design-maturityrefinesspec:model.core-model· declaredspec:model.enrichment-lifecyclerefinesspec:model.core-model· declaredspec:model.open-question-fieldsrefinesspec:model.open-question-keys· declaredspec:model.open-question-fields.dropped-list-warnsrefinesspec:model.open-question-fields· declaredspec:model.open-question-keysrefinesspec:model.spec-sections· declaredspec:model.open-question-keys.keyed-question-resolvesrefinesspec:model.open-question-keys· declaredspec:model.open-question-keys.renamed-key-breaksrefinesspec:model.open-question-keys· declaredspec:model.open-question-keys.repeated-key-refusedrefinesspec:model.open-question-keys· declaredspec:model.pack-aggregaterefinesspec:model.core-model· declaredspec:model.planned-architecturerefinesspec:model.core-model· declared — planned components enrich Specs before code binds themspec:model.planned-architecture.differing-layer-and-usesrefinesspec:model.planned-architecture· declaredspec:model.planned-architecture.matching-designrefinesspec:model.planned-architecture· declaredspec:model.planned-architecture.unrealized-designrefinesspec:model.planned-architecture· declaredspec:model.relation-reasonsrefinesspec:model.relations· declaredspec:model.relationsrefinesspec:model.core-model· declaredspec:model.rule-keysrefinesspec:model.spec-sections· declaredspec:model.spec-sectionsrefinesspec:model.core-model· declaredspec:model.stable-idsrefinesspec:model.core-model· declaredspec:model.stable-ids.malformed-refusalrefinesspec:model.stable-ids· declaredspec:model.stable-ids.namespaced-round-triprefinesspec:model.stable-ids· declaredspec:model.stable-ids.unsectioned-address-refusedrefinesspec:model.stable-ids· declaredspec:model.structural-patternsrefinesspec:model.anchors· declaredspec:model.term-addressesrefinesspec:model.spec-sections· declared — extends entry addresses to the terms a Model section definesspec:model.term-addresses.keyed-term-resolvesrefinesspec:model.term-addresses· declaredspec:model.term-addresses.malformed-term-marker-refusedrefinesspec:model.term-addresses· declaredspec:model.term-addresses.repeated-term-key-refusedrefinesspec:model.term-addresses· declaredspec:model.term-addresses.typescript-term-imports-keyedrefinesspec:model.term-addresses· declaredspec:model.term-addresses.unknown-term-key-refusedrefinesspec:model.term-addresses· declared
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred syntax: mindmap. Chosen syntax: flowchart BT because the drawing has a fold.
Complete refinement text
Root
The Protocol models delivery with one enrichable Spec ·spec:model.core-model· model · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.core-model
Decision · Example realization stays evidence, not backlog work
Example realization stays evidence, not backlog work ·spec:decisions.example-realization-posture· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.core-model
Decision · One Spec carries named delivery coordinates
One Spec carries named delivery coordinates ·spec:decisions.one-primitive· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.core-model
Source anchors bind code without carrying intent ·spec:model.anchors· model · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.anchors
Decision · Bindings are optional, plural, and may reference a design
Bindings are optional, plural, and may reference a design ·spec:decisions.anchor-binding-grain· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.anchors
Decision · The comment form is a second anchor representation
The comment form is a second anchor representation ·spec:decisions.anchor-comment-form· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.anchors
Decision · Architectural significance is annotated where it is realized
Architectural significance is annotated where it is realized ·spec:decisions.architectural-annotation· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.anchors
Decision · Bindings state existence, not liveness
Bindings state existence, not liveness ·spec:decisions.binding-not-liveness· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.anchors
Example · A consumer-local lookalike builder mints no anchor and no finding
A consumer-local lookalike builder mints no anchor and no finding ·spec:model.anchors.lookalike-refusal· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.anchors
Example · A deep relative import that resolves to the Protocol builders is trusted
A deep relative import that resolves to the Protocol builders is trusted ·spec:model.anchors.physical-identity· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.anchors
Architecturally significant units are annotated where they are realized ·spec:model.structural-patterns· model · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.core-model
What a Spec's design carries is derived, beside its readiness ·spec:model.design-maturity· model · feature · stated ready · floor ready · implementation binding present · verifier binding present · 1 open question · No blocking questions- non-blocking: If the first adopter's design passes show that the design columns cannot distinguish settled design from intent alone, should this representation be revisited?
Parent: spec:model.core-model
Enrichment keeps one Spec while its detail changes ·spec:model.enrichment-lifecycle· model · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.core-model
A Pack is a truth-free review aggregate ·spec:model.pack-aggregate· model · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.pack-aggregate
Decision · Packs group review context without becoming truth
Packs group review context without becoming truth ·spec:decisions.pack-reified· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.core-model
Components are designed ahead of their code ·spec:model.planned-architecture· model · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.planned-architecture
Example · A realized component that differs from its design gives one row per field
A realized component that differs from its design gives one row per field ·spec:model.planned-architecture.differing-layer-and-uses· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.planned-architecture
Example · A realized component that matches its design gives no row
A realized component that matches its design gives no row ·spec:model.planned-architecture.matching-design· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.planned-architecture
Example · A component design no anchor satisfies is listed as unrealized
A component design no anchor satisfies is listed as unrealized ·spec:model.planned-architecture.unrealized-design· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.core-model
Specs declare typed directed relations ·spec:model.relations· model · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.relations
Decision · Planning truths live in ruled graph homes
Planning truths live in ruled graph homes ·spec:decisions.planning-truths-placement· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:decisions.planning-truths-placement
Decision · Plan and review files stop carrying the delivery record once the roadmap and the pull request do
Plan and review files stop carrying the delivery record once the roadmap and the pull request do ·spec:decisions.roadmap-over-plans· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:decisions.planning-truths-placement
Decision · A roadmap states advisory priority in the graph
A roadmap states advisory priority in the graph ·spec:decisions.roadmap-priority· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.relations
An authored relation may carry its reason ·spec:model.relation-reasons· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.core-model
Spec sections carry typed detail and direct verifier semantics ·spec:model.spec-sections· model · feature · stated ready · floor ready · implementation binding present · verifier binding none · No open questions · No blocking questionsParent: spec:model.spec-sections
Decision · Sections carry content while relations carry links
Sections carry content while relations carry links ·spec:decisions.content-only-sections· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.spec-sections
Decision · Each example binds one point
Each example binds one point ·spec:decisions.point-per-example· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.spec-sections
Decision · Floor-read sections are closed typed shapes
Floor-read sections are closed typed shapes ·spec:decisions.typing-law· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.spec-sections
Decision · Verification mode states posture, not realization
Verification mode states posture, not realization ·spec:decisions.verification-posture-not-realization· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.spec-sections
An open question may carry a key that addresses it ·spec:model.open-question-keys· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.open-question-keys
An open question may name who decides it, its links, a provisional reading and a re-entry trigger ·spec:model.open-question-fields· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.open-question-fields
Example · A TypeScript question list that cannot be read drops whole with a warning
A TypeScript question list that cannot be read drops whole with a warning ·spec:model.open-question-fields.dropped-list-warns· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.open-question-keys
Example · A keyed question is reified and its address resolves
A keyed question is reified and its address resolves ·spec:model.open-question-keys.keyed-question-resolves· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.open-question-keys
Example · A renamed question key fails the mention that addresses it
A renamed question key fails the mention that addresses it ·spec:model.open-question-keys.renamed-key-breaks· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.open-question-keys
Example · A repeated question key refuses its carrier
A repeated question key refuses its carrier ·spec:model.open-question-keys.repeated-key-refused· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.spec-sections
A rule or flow entry may carry a key that addresses it ·spec:model.rule-keys· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.spec-sections
A Model term may carry a key that addresses it ·spec:model.term-addresses· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.term-addresses
Example · A keyed term is reified and its address resolves
A keyed term is reified and its address resolves ·spec:model.term-addresses.keyed-term-resolves· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.term-addresses
Example · A term marker whose key is off the grammar refuses its carrier
A term marker whose key is off the grammar refuses its carrier ·spec:model.term-addresses.malformed-term-marker-refused· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.term-addresses
Example · A term key repeated in one Spec refuses its carrier
A term key repeated in one Spec refuses its carrier ·spec:model.term-addresses.repeated-term-key-refused· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.term-addresses
Example · A keyed TypeScript term keeps its address through import to Markdown
A keyed TypeScript term keeps its address through import to Markdown ·spec:model.term-addresses.typescript-term-imports-keyed· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.term-addresses
Example · An address that names a term key no term carries is an error
An address that names a term key no term carries is an error ·spec:model.term-addresses.unknown-term-key-refused· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.core-model
Stable IDs are the Protocol's durable join key ·spec:model.stable-ids· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:model.stable-ids
Decision · A Spec id written in prose is a checked mention
A Spec id written in prose is a checked mention ·spec:decisions.checked-mentions· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:model.stable-ids
Example · An uppercase namespace is refused with its reason named
An uppercase namespace is refused with its reason named ·spec:model.stable-ids.malformed-refusal· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.stable-ids
Example · A namespaced dotted path with a sub-part survives parsing unchanged
A namespaced dotted path with a sub-part survives parsing unchanged ·spec:model.stable-ids.namespaced-round-trip· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:model.stable-ids
Example · A `#` sub-part without its section is refused with its reason named
A#sub-part without its section is refused with its reason named ·spec:model.stable-ids.unsectioned-address-refused· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questions
The Protocol authors and validates itself
Epic's own evidence
The Protocol authors and validates itself ·
spec:protocol.self-hosting · behavior · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsDistinct descendants, excluding this epic: 11 Specs · No examples · 5 decisions.
- Stated rungs
- idea 1 · scoped 0 · defined 0 · ready 10
- Floors reached
- none 0 · idea 1 · scoped 0 · defined 0 · ready 10
- Kinds
- behavior 5 · workflow 0 · example 0 · rule 0 · constraint 0 · model 1 · decision 5 · contract 0
- Altitudes
- epic 0 · feature 10 · story 1
- Binding evidence
- 5 Specs with implementation binding present · 4 Specs with verifier binding present
- Questions
- 1 open question · 1 blocking question
Arrows: refines (declared). Later visits repeat a Spec and link to its first occurrence.
The diagram as text
12 unique Specs; 12 rendered boxes.
spec:protocol.self-hosting: The Protocol authors and validates itself · epicspec:decisions.adopt-the-nouns: Delivery nouns remain familiar without workflow gates · featurespec:decisions.concept-docs-dissolve: Concept documents may dissolve after executable truth lands · featurespec:decisions.executable-meta-model: The Protocol is an executable meta-model · featurespec:decisions.plain-language-references: Durable references lead with meaning · featurespec:decisions.protocol-naming: The meta-model is a software delivery protocol · featurespec:protocol.capability-epics: The Protocol organizes its own features in capability epics · featurespec:protocol.roadmap-replaces-plans: The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests · featurespec:protocol.delivery-record-cleanup: The Protocol removes its frozen plans, review reports and superseded concept material · featurespec:protocol.structural-self-binding: The engine's structural self-binding covers its architecturally significant units · storyspec:protocol.role-vocabulary: The engine's architectural roles each name one pattern · featurespec:protocol.significant-units-review: The engine's accepted set covers its significant abstractions and only those · featurespec:decisions.adopt-the-nounsrefinesspec:protocol.self-hosting· declaredspec:decisions.concept-docs-dissolverefinesspec:protocol.self-hosting· declaredspec:decisions.executable-meta-modelrefinesspec:protocol.self-hosting· declaredspec:decisions.plain-language-referencesrefinesspec:protocol.self-hosting· declaredspec:decisions.protocol-namingrefinesspec:protocol.self-hosting· declaredspec:protocol.capability-epicsrefinesspec:protocol.self-hosting· declaredspec:protocol.delivery-record-cleanuprefinesspec:protocol.roadmap-replaces-plans· declared — carries out the removal the roadmap and the pull request record made possible for frozen historyspec:protocol.roadmap-replaces-plansrefinesspec:protocol.self-hosting· declaredspec:protocol.role-vocabularyrefinesspec:protocol.structural-self-binding· declared — names what each role value the engine's significant units carry meansspec:protocol.significant-units-reviewrefinesspec:protocol.structural-self-binding· declared — states what the independently reviewed accepted set must contain and excludespec:protocol.structural-self-bindingrefinesspec:protocol.self-hosting· declared
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred syntax: mindmap. Chosen syntax: mindmap.
Complete refinement text
Root
The Protocol authors and validates itself ·spec:protocol.self-hosting· behavior · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:protocol.self-hosting
Decision · Delivery nouns remain familiar without workflow gates
Delivery nouns remain familiar without workflow gates ·spec:decisions.adopt-the-nouns· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:protocol.self-hosting
Decision · Concept documents may dissolve after executable truth lands
Concept documents may dissolve after executable truth lands ·spec:decisions.concept-docs-dissolve· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:protocol.self-hosting
Decision · The Protocol is an executable meta-model
The Protocol is an executable meta-model ·spec:decisions.executable-meta-model· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:protocol.self-hosting
Decision · Durable references lead with meaning
Durable references lead with meaning ·spec:decisions.plain-language-references· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:protocol.self-hosting
Decision · The meta-model is a software delivery protocol
The meta-model is a software delivery protocol ·spec:decisions.protocol-naming· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:protocol.self-hosting
The Protocol organizes its own features in capability epics ·spec:protocol.capability-epics· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:protocol.self-hosting
The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests ·spec:protocol.roadmap-replaces-plans· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:protocol.roadmap-replaces-plans
The Protocol removes its frozen plans, review reports and superseded concept material ·spec:protocol.delivery-record-cleanup· behavior · feature · stated idea · floor idea · implementation binding none · verifier binding none · 1 open question · 1 blocking question- blocking: Which content in
plans/,reviews/and the concept documents does no Spec, test, decision or recipe carry yet, and where does each piece belong?
- blocking: Which content in
Parent: spec:protocol.self-hosting
The engine's structural self-binding covers its architecturally significant units ·spec:protocol.structural-self-binding· behavior · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:protocol.structural-self-binding
The engine's architectural roles each name one pattern ·spec:protocol.role-vocabulary· model · feature · stated ready · floor ready · implementation binding present · verifier binding none · No open questions · No blocking questionsParent: spec:protocol.structural-self-binding
The engine's accepted set covers its significant abstractions and only those ·spec:protocol.significant-units-review· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questions
Validation separates well-formedness from non-pretending
Epic's own evidence
Validation separates well-formedness from non-pretending ·
spec:validation.two-check-families · rule · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsDistinct descendants, excluding this epic: 68 Specs · 47 examples · 4 decisions.
- Stated rungs
- idea 0 · scoped 0 · defined 0 · ready 68
- Floors reached
- none 0 · idea 0 · scoped 0 · defined 0 · ready 68
- Kinds
- behavior 1 · workflow 0 · example 47 · rule 16 · constraint 0 · model 0 · decision 4 · contract 0
- Altitudes
- epic 0 · feature 12 · story 56
- Binding evidence
- 17 Specs with implementation binding present · 64 Specs with verifier binding present
- Questions
- No open questions · No blocking questions
Arrows: refines (declared). Later visits repeat a Spec and link to its first occurrence.
The diagram as text
69 unique Specs; 9 rendered boxes.
spec:validation.two-check-families: Validation separates well-formedness from non-pretending · epicspec:decisions.one-validation-path: Validation follows one graph · featurespec:validation.authored-honesty: Machine truth is never authored · featurespec:validation.authored-honesty.section-authored-fact: A delivery fact smuggled into a section is refused · storyspec:validation.authored-honesty.unearned-stated-fact: A stated delivery fact no binding earns is refused · storyspec:validation.claim-separation: Graph claims and contracts stay distinct · storyspec:validation.claim-separation.collapsed-edge-claim: A binding edge cannot borrow the declared claim · storyspec:validation.claim-separation.unratified-descriptor: An unratified kind fails closed instead of reaching the floor · storyspec:validation.diagnostic-rendering: One diagnostic currency, its location composed from structured fields · featurespec:validation.diagnostic-rendering.composed-location: One finding, three location shapes, one composition rule · storyspec:validation.diagnostic-rendering.table-cell-location: The same three location shapes, rendered as table cells · storyspec:validation.duplicate-ids: Duplicate carrier IDs are excluded loudly · featurespec:validation.duplicate-ids.dual-carrier: TypeScript and Markdown duplicates are both refused · storyspec:validation.pack-coherence: Packs are coherent aggregates · storyspec:validation.pack-coherence.incoherent-aggregate: A repeated member and a non-model modelRef are both named · storyspec:validation.readiness-floor: Stated readiness must clear its floor · featurespec:decisions.carried-evidence: Promoted evidence must carry its own evidence · featurespec:decisions.kind-conditional-floor: Readiness evidence follows the Spec kind · featurespec:validation.kind-evidence: Each kind carries its own evidence · featurespec:validation.kind-evidence.constraints-alone: Constraints alone stop short of complete behavior evidence · storyspec:validation.kind-evidence.empty-promoted-child: An empty promoted child confers no evidence · storyspec:validation.kind-evidence.second-entry-untargeted: A constraint whose second entry has no target is not complete · storyspec:validation.kind-evidence.untargeted-constraint: A constraint without a machine-readable target is not complete · storyspec:validation.next-rung-floor: The floor names what blocks the floor's next rung · storyspec:validation.next-rung-floor.blocking-question: A scoped Spec held by a blocking question is told the clause · storyspec:validation.next-rung-floor.typed-dependency-targets: A defined Spec resting on a scoped dependency is told which one · storyspec:validation.readiness-floor.blocking-open-question: A blocking open question holds a Spec below defined · storyspec:validation.readiness-floor.unrelated-scoped-spec: A scoped Spec with no relation names the relation clause · storyspec:validation.typed-dependency-floor: A ready Spec rests only on settled dependencies · storyspec:validation.typed-dependency-floor.missing-targets: Missing targets fail relation resolution once · storyspec:validation.typed-dependency-floor.relation-rungs: Every relation reads the four stated target rungs · storyspec:validation.typed-dependency-floor.stated-readiness: Target floor failures do not propagate across dependencies · storyspec:validation.typed-dependency-floor.unsettled-fact: An unsettled constraint bounds ready but permits defined · storyspec:validation.referential-integrity: Every graph reference resolves · storyspec:validation.prose-mentions: Every Spec id written in prose resolves · storyspec:validation.referential-integrity.dangling-target: An unrelated missing target is a bare conformance error · storyspec:validation.referential-integrity.did-you-mean: A unique near miss earns a did-you-mean suggestion · storyspec:validation.two-check-families.split-report: One report carries both families and claims neither as its own · storyspec:validation.validator-self-testing: Every validator ships evidence in both directions · featurespec:validation.validator-self-testing.duplicate-pair-named: A check paired twice is named · storyspec:validation.validator-self-testing.overeager-check-named: A check that reports its near miss is named overeager · storyspec:validation.validator-self-testing.shipped-checks-paired: Every shipped check reports its refusing probe and leaves its near miss alone · storyspec:validation.validator-self-testing.silent-check-named: A check that stops reporting is named silent · storyspec:validation.validator-self-testing.unpaired-check-named: A registered check without a probe pair is named unpaired · storyspec:validation.validator-self-testing.unregistered-id-named: A finding id the source writes outside every registry is named · storyspec:validation.verification-linkage: Example verification and oracle bindings resolve honestly · featurespec:validation.oracle-target-eligibility: Oracle eligibility follows example-space ownership · storyspec:validation.oracle-target-eligibility.missing-space-refused: A target without an example space refuses an oracle · storyspec:validation.oracle-target-eligibility.rule-space-accepted: A rule owning an example space accepts an oracle · storyspec:validation.unbound-example-posture: An unbound example below ready is data, not a warning · storyspec:validation.unbound-example-posture.lower-rungs: Below-ready examples keep declared verifier data · storyspec:validation.unbound-example-posture.parent-traces: Parent gaps follow enabled bindings and preserve the decision exemption · storyspec:validation.unbound-example-posture.warning-cases: Ready examples and non-example verifiers keep warnings · storyspec:validation.verification-linkage.unbound-example: A declared verifier no test binds confers nothing · storyspec:validation.verification-linkage.unresolved-oracle: An oracle targeting a Spec with no example space is refused · storyspec:validation.warn-level-signals: Missing connective evidence warns without failing · featurespec:decisions.decision-readiness-posture: Decision records state readiness from ratification evidence · featurespec:validation.superseded-decision-signal: A Spec shaped by a superseded decision warns · storyspec:validation.superseded-decision-signal.branch-names-every-end: A replacement chain that branches names every end · storyspec:validation.superseded-decision-signal.chain-end-named: The warning names the decision at the end of a chain of replacements · storyspec:validation.superseded-decision-signal.closed-chain-named: A chain of replacements that closes on itself is named and fails nothing · storyspec:validation.superseded-decision-signal.dependency-unread: A dependency on a replaced decision raises no warning · storyspec:validation.superseded-decision-signal.end-and-loop-named: A chain of replacements that reaches an end and a loop names both · storyspec:validation.superseded-decision-signal.live-replacement-warns: A decision still decided by the record it replaces warns · storyspec:validation.superseded-decision-signal.replaced-ruling-warns: A Spec shaped by a replaced decision warns once and fails nothing · storyspec:validation.superseded-decision-signal.replacement-below-ready-named: A replacement still below ready is named as it stands · storyspec:validation.superseded-decision-signal.superseded-subject-silent: A superseded decision is not warned for the decision it names · storyspec:validation.warn-level-signals.orphan-signal: A disconnected Spec warns and fails nothing · storyspec:validation.warn-level-signals.ready-gap-signal: A ready Spec without a verifier warns and fails nothing · storyspec:decisions.carried-evidencerefinesspec:validation.readiness-floor· declaredspec:decisions.decision-readiness-posturerefinesspec:validation.warn-level-signals· declaredspec:decisions.kind-conditional-floorrefinesspec:validation.readiness-floor· declaredspec:decisions.one-validation-pathrefinesspec:validation.two-check-families· declaredspec:validation.authored-honestyrefinesspec:validation.two-check-families· declaredspec:validation.authored-honesty.section-authored-factrefinesspec:validation.authored-honesty· declaredspec:validation.authored-honesty.unearned-stated-factrefinesspec:validation.authored-honesty· declaredspec:validation.claim-separationrefinesspec:validation.two-check-families· declaredspec:validation.claim-separation.collapsed-edge-claimrefinesspec:validation.claim-separation· declaredspec:validation.claim-separation.unratified-descriptorrefinesspec:validation.claim-separation· declaredspec:validation.diagnostic-renderingrefinesspec:validation.two-check-families· declaredspec:validation.diagnostic-rendering.composed-locationrefinesspec:validation.diagnostic-rendering· declaredspec:validation.diagnostic-rendering.table-cell-locationrefinesspec:validation.diagnostic-rendering· declaredspec:validation.duplicate-idsrefinesspec:validation.two-check-families· declared — duplicate identity is a conformance refusalspec:validation.duplicate-ids.dual-carrierrefinesspec:validation.duplicate-ids· declaredspec:validation.kind-evidencerefinesspec:validation.readiness-floor· declaredspec:validation.kind-evidence.constraints-alonerefinesspec:validation.kind-evidence· declaredspec:validation.kind-evidence.empty-promoted-childrefinesspec:validation.kind-evidence· declaredspec:validation.kind-evidence.second-entry-untargetedrefinesspec:validation.kind-evidence· declaredspec:validation.kind-evidence.untargeted-constraintrefinesspec:validation.kind-evidence· declaredspec:validation.next-rung-floorrefinesspec:validation.readiness-floor· declaredspec:validation.next-rung-floor.blocking-questionrefinesspec:validation.next-rung-floor· declaredspec:validation.next-rung-floor.typed-dependency-targetsrefinesspec:validation.next-rung-floor· declaredspec:validation.oracle-target-eligibilityrefinesspec:validation.verification-linkage· declaredspec:validation.oracle-target-eligibility.missing-space-refusedrefinesspec:validation.oracle-target-eligibility· declaredspec:validation.oracle-target-eligibility.rule-space-acceptedrefinesspec:validation.oracle-target-eligibility· declaredspec:validation.pack-coherencerefinesspec:validation.two-check-families· declaredspec:validation.pack-coherence.incoherent-aggregaterefinesspec:validation.pack-coherence· declaredspec:validation.prose-mentionsrefinesspec:validation.referential-integrity· declaredspec:validation.readiness-floorrefinesspec:validation.two-check-families· declared — the readiness floor checks honesty of the stated rungspec:validation.readiness-floor.blocking-open-questionrefinesspec:validation.readiness-floor· declaredspec:validation.readiness-floor.unrelated-scoped-specrefinesspec:validation.readiness-floor· declaredspec:validation.referential-integrityrefinesspec:validation.two-check-families· declaredspec:validation.referential-integrity.dangling-targetrefinesspec:validation.referential-integrity· declaredspec:validation.referential-integrity.did-you-meanrefinesspec:validation.referential-integrity· declaredspec:validation.superseded-decision-signalrefinesspec:validation.warn-level-signals· declaredspec:validation.superseded-decision-signal.branch-names-every-endrefinesspec:validation.superseded-decision-signal· declaredspec:validation.superseded-decision-signal.chain-end-namedrefinesspec:validation.superseded-decision-signal· declaredspec:validation.superseded-decision-signal.closed-chain-namedrefinesspec:validation.superseded-decision-signal· declaredspec:validation.superseded-decision-signal.dependency-unreadrefinesspec:validation.superseded-decision-signal· declaredspec:validation.superseded-decision-signal.end-and-loop-namedrefinesspec:validation.superseded-decision-signal· declaredspec:validation.superseded-decision-signal.live-replacement-warnsrefinesspec:validation.superseded-decision-signal· declaredspec:validation.superseded-decision-signal.replaced-ruling-warnsrefinesspec:validation.superseded-decision-signal· declaredspec:validation.superseded-decision-signal.replacement-below-ready-namedrefinesspec:validation.superseded-decision-signal· declaredspec:validation.superseded-decision-signal.superseded-subject-silentrefinesspec:validation.superseded-decision-signal· declaredspec:validation.two-check-families.split-reportrefinesspec:validation.two-check-families· declaredspec:validation.typed-dependency-floorrefinesspec:validation.readiness-floor· declaredspec:validation.typed-dependency-floor.missing-targetsrefinesspec:validation.typed-dependency-floor· declaredspec:validation.typed-dependency-floor.relation-rungsrefinesspec:validation.typed-dependency-floor· declaredspec:validation.typed-dependency-floor.stated-readinessrefinesspec:validation.typed-dependency-floor· declaredspec:validation.typed-dependency-floor.unsettled-factrefinesspec:validation.typed-dependency-floor· declaredspec:validation.unbound-example-posturerefinesspec:validation.verification-linkage· declaredspec:validation.unbound-example-posture.lower-rungsrefinesspec:validation.unbound-example-posture· declaredspec:validation.unbound-example-posture.parent-tracesrefinesspec:validation.unbound-example-posture· declaredspec:validation.unbound-example-posture.warning-casesrefinesspec:validation.unbound-example-posture· declaredspec:validation.validator-self-testingrefinesspec:validation.two-check-families· declaredspec:validation.validator-self-testing.duplicate-pair-namedrefinesspec:validation.validator-self-testing· declaredspec:validation.validator-self-testing.overeager-check-namedrefinesspec:validation.validator-self-testing· declaredspec:validation.validator-self-testing.shipped-checks-pairedrefinesspec:validation.validator-self-testing· declaredspec:validation.validator-self-testing.silent-check-namedrefinesspec:validation.validator-self-testing· declaredspec:validation.validator-self-testing.unpaired-check-namedrefinesspec:validation.validator-self-testing· declaredspec:validation.validator-self-testing.unregistered-id-namedrefinesspec:validation.validator-self-testing· declaredspec:validation.verification-linkagerefinesspec:validation.two-check-families· declaredspec:validation.verification-linkage.unbound-examplerefinesspec:validation.verification-linkage· declaredspec:validation.verification-linkage.unresolved-oraclerefinesspec:validation.verification-linkage· declaredspec:validation.warn-level-signalsrefinesspec:validation.two-check-families· declaredspec:validation.warn-level-signals.orphan-signalrefinesspec:validation.warn-level-signals· declaredspec:validation.warn-level-signals.ready-gap-signalrefinesspec:validation.warn-level-signals· declared
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred syntax: mindmap. Chosen syntax: flowchart BT because the drawing has a fold.
Complete refinement text
Root
Validation separates well-formedness from non-pretending ·spec:validation.two-check-families· rule · epic · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.two-check-families
Decision · Validation follows one graph
Validation follows one graph ·spec:decisions.one-validation-path· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:validation.two-check-families
Graph claims and contracts stay distinct ·spec:validation.claim-separation· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.claim-separation
Example · A binding edge cannot borrow the declared claim
A binding edge cannot borrow the declared claim ·spec:validation.claim-separation.collapsed-edge-claim· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.claim-separation
Example · An unratified kind fails closed instead of reaching the floor
An unratified kind fails closed instead of reaching the floor ·spec:validation.claim-separation.unratified-descriptor· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.two-check-families
One diagnostic currency, its location composed from structured fields ·spec:validation.diagnostic-rendering· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.diagnostic-rendering
Example · One finding, three location shapes, one composition rule
One finding, three location shapes, one composition rule ·spec:validation.diagnostic-rendering.composed-location· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.diagnostic-rendering
Example · The same three location shapes, rendered as table cells
The same three location shapes, rendered as table cells ·spec:validation.diagnostic-rendering.table-cell-location· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.two-check-families
Duplicate carrier IDs are excluded loudly ·spec:validation.duplicate-ids· behavior · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.duplicate-ids
Example · TypeScript and Markdown duplicates are both refused
TypeScript and Markdown duplicates are both refused ·spec:validation.duplicate-ids.dual-carrier· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.two-check-families
Packs are coherent aggregates ·spec:validation.pack-coherence· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.pack-coherence
Example · A repeated member and a non-model modelRef are both named
A repeated member and a non-model modelRef are both named ·spec:validation.pack-coherence.incoherent-aggregate· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.two-check-families
Stated readiness must clear its floor ·spec:validation.readiness-floor· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.readiness-floor
Decision · Promoted evidence must carry its own evidence
Promoted evidence must carry its own evidence ·spec:decisions.carried-evidence· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:validation.readiness-floor
Decision · Readiness evidence follows the Spec kind
Readiness evidence follows the Spec kind ·spec:decisions.kind-conditional-floor· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:validation.readiness-floor
Each kind carries its own evidence ·spec:validation.kind-evidence· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.kind-evidence
Example · Constraints alone stop short of complete behavior evidence
Constraints alone stop short of complete behavior evidence ·spec:validation.kind-evidence.constraints-alone· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.kind-evidence
Example · An empty promoted child confers no evidence
An empty promoted child confers no evidence ·spec:validation.kind-evidence.empty-promoted-child· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.kind-evidence
Example · A constraint whose second entry has no target is not complete
A constraint whose second entry has no target is not complete ·spec:validation.kind-evidence.second-entry-untargeted· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.kind-evidence
Example · A constraint without a machine-readable target is not complete
A constraint without a machine-readable target is not complete ·spec:validation.kind-evidence.untargeted-constraint· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.readiness-floor
The floor names what blocks the floor's next rung ·spec:validation.next-rung-floor· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.next-rung-floor
Example · A scoped Spec held by a blocking question is told the clause
A scoped Spec held by a blocking question is told the clause ·spec:validation.next-rung-floor.blocking-question· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.next-rung-floor
Example · A defined Spec resting on a scoped dependency is told which one
A defined Spec resting on a scoped dependency is told which one ·spec:validation.next-rung-floor.typed-dependency-targets· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.readiness-floor
Example · A blocking open question holds a Spec below defined
A blocking open question holds a Spec below defined ·spec:validation.readiness-floor.blocking-open-question· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.readiness-floor
A ready Spec rests only on settled dependencies ·spec:validation.typed-dependency-floor· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.typed-dependency-floor
Example · Missing targets fail relation resolution once
Missing targets fail relation resolution once ·spec:validation.typed-dependency-floor.missing-targets· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.typed-dependency-floor
Example · Every relation reads the four stated target rungs
Every relation reads the four stated target rungs ·spec:validation.typed-dependency-floor.relation-rungs· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.typed-dependency-floor
Example · Target floor failures do not propagate across dependencies
Target floor failures do not propagate across dependencies ·spec:validation.typed-dependency-floor.stated-readiness· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.typed-dependency-floor
Example · An unsettled constraint bounds ready but permits defined
An unsettled constraint bounds ready but permits defined ·spec:validation.typed-dependency-floor.unsettled-fact· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.two-check-families
Every graph reference resolves ·spec:validation.referential-integrity· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.referential-integrity
Every Spec id written in prose resolves ·spec:validation.prose-mentions· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.referential-integrity
Example · An unrelated missing target is a bare conformance error
An unrelated missing target is a bare conformance error ·spec:validation.referential-integrity.dangling-target· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.referential-integrity
Example · A unique near miss earns a did-you-mean suggestion
A unique near miss earns a did-you-mean suggestion ·spec:validation.referential-integrity.did-you-mean· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.two-check-families
Example · One report carries both families and claims neither as its own
One report carries both families and claims neither as its own ·spec:validation.two-check-families.split-report· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.two-check-families
Every validator ships evidence in both directions ·spec:validation.validator-self-testing· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.validator-self-testing
Example · A check paired twice is named
A check paired twice is named ·spec:validation.validator-self-testing.duplicate-pair-named· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.validator-self-testing
Example · A check that reports its near miss is named overeager
A check that reports its near miss is named overeager ·spec:validation.validator-self-testing.overeager-check-named· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.validator-self-testing
Example · Every shipped check reports its refusing probe and leaves its near miss alone
Every shipped check reports its refusing probe and leaves its near miss alone ·spec:validation.validator-self-testing.shipped-checks-paired· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.validator-self-testing
Example · A check that stops reporting is named silent
A check that stops reporting is named silent ·spec:validation.validator-self-testing.silent-check-named· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.validator-self-testing
Example · A registered check without a probe pair is named unpaired
A registered check without a probe pair is named unpaired ·spec:validation.validator-self-testing.unpaired-check-named· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.validator-self-testing
Example · A finding id the source writes outside every registry is named
A finding id the source writes outside every registry is named ·spec:validation.validator-self-testing.unregistered-id-named· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.two-check-families
Example verification and oracle bindings resolve honestly ·spec:validation.verification-linkage· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.verification-linkage
Oracle eligibility follows example-space ownership ·spec:validation.oracle-target-eligibility· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.oracle-target-eligibility
Example · A target without an example space refuses an oracle
A target without an example space refuses an oracle ·spec:validation.oracle-target-eligibility.missing-space-refused· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.oracle-target-eligibility
Example · A rule owning an example space accepts an oracle
A rule owning an example space accepts an oracle ·spec:validation.oracle-target-eligibility.rule-space-accepted· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.verification-linkage
An unbound example below ready is data, not a warning ·spec:validation.unbound-example-posture· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.unbound-example-posture
Example · Below-ready examples keep declared verifier data
Below-ready examples keep declared verifier data ·spec:validation.unbound-example-posture.lower-rungs· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.unbound-example-posture
Example · Parent gaps follow enabled bindings and preserve the decision exemption
Parent gaps follow enabled bindings and preserve the decision exemption ·spec:validation.unbound-example-posture.parent-traces· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.unbound-example-posture
Example · Ready examples and non-example verifiers keep warnings
Ready examples and non-example verifiers keep warnings ·spec:validation.unbound-example-posture.warning-cases· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.verification-linkage
Example · A declared verifier no test binds confers nothing
A declared verifier no test binds confers nothing ·spec:validation.verification-linkage.unbound-example· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.verification-linkage
Example · An oracle targeting a Spec with no example space is refused
An oracle targeting a Spec with no example space is refused ·spec:validation.verification-linkage.unresolved-oracle· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.two-check-families
Missing connective evidence warns without failing ·spec:validation.warn-level-signals· rule · feature · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.warn-level-signals
Decision · Decision records state readiness from ratification evidence
Decision records state readiness from ratification evidence ·spec:decisions.decision-readiness-posture· decision · feature · stated ready · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questionsParent: spec:validation.warn-level-signals
A Spec shaped by a superseded decision warns ·spec:validation.superseded-decision-signal· rule · story · stated ready · floor ready · implementation binding present · verifier binding present · No open questions · No blocking questionsParent: spec:validation.superseded-decision-signal
Example · A replacement chain that branches names every end
A replacement chain that branches names every end ·spec:validation.superseded-decision-signal.branch-names-every-end· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.superseded-decision-signal
Example · The warning names the decision at the end of a chain of replacements
The warning names the decision at the end of a chain of replacements ·spec:validation.superseded-decision-signal.chain-end-named· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.superseded-decision-signal
Example · A chain of replacements that closes on itself is named and fails nothing
A chain of replacements that closes on itself is named and fails nothing ·spec:validation.superseded-decision-signal.closed-chain-named· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.superseded-decision-signal
Example · A dependency on a replaced decision raises no warning
A dependency on a replaced decision raises no warning ·spec:validation.superseded-decision-signal.dependency-unread· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.superseded-decision-signal
Example · A chain of replacements that reaches an end and a loop names both
A chain of replacements that reaches an end and a loop names both ·spec:validation.superseded-decision-signal.end-and-loop-named· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.superseded-decision-signal
Example · A decision still decided by the record it replaces warns
A decision still decided by the record it replaces warns ·spec:validation.superseded-decision-signal.live-replacement-warns· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.superseded-decision-signal
Example · A Spec shaped by a replaced decision warns once and fails nothing
A Spec shaped by a replaced decision warns once and fails nothing ·spec:validation.superseded-decision-signal.replaced-ruling-warns· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.superseded-decision-signal
Example · A replacement still below ready is named as it stands
A replacement still below ready is named as it stands ·spec:validation.superseded-decision-signal.replacement-below-ready-named· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.superseded-decision-signal
Example · A superseded decision is not warned for the decision it names
A superseded decision is not warned for the decision it names ·spec:validation.superseded-decision-signal.superseded-subject-silent· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.warn-level-signals
Example · A disconnected Spec warns and fails nothing
A disconnected Spec warns and fails nothing ·spec:validation.warn-level-signals.orphan-signal· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questionsParent: spec:validation.warn-level-signals
Example · A ready Spec without a verifier warns and fails nothing
A ready Spec without a verifier warns and fails nothing ·spec:validation.warn-level-signals.ready-gap-signal· example · story · stated ready · floor ready · implementation binding none · verifier binding present · No open questions · No blocking questions
No epic reaches these Specs
No unreached Specs.
Composing (0)
Composing needs the script.