Spec Studio

Design slice: Self-hosting

pack:self-hosting-v1

Read the Pack member by member

The design as a whole

  • 456 members; 232 example members counted in their parents.
  • 983 relations among members; deepest depth 18; 1 cycle.
  • 8 members held below their stated next rung; 1 waiting only for their author.
  • 0 outside Specs the slice rests on; 0 hold a member; 0 outside Specs rest on it.
  • 14 components touched: 14 through members' code, 0 through what the slice rests on, 0 named by member designs; 0 outside components shown for context.
  • 0 member component designs; 0 realized; 0 of those match.
  • 47 decisions in scope; 0 state below ready.
  • 16 open questions; 10 blocking.

Members read with the ones others rest on first. The columns count the design each member carries beside its rung; they never judge whether it is enough. This page records no review and approves nothing.

How the members rest on each other

Declared relations by depth

Depths are structural, never phases, dates or priority. Dashed relations order nothing. The text keeps every member and original relation.

Shown as text: this drawing exceeds the bound of 40 boxes and 100 edges.

The diagram as text
  • spec:carrier.markdown-authoring: Markdown authoring enters the one graph, depth 6, stated ready, floor ready
  • spec:carrier.envelope-contract: The Markdown envelope is explicit and bounded, depth 6, stated ready, floor ready
  • spec:carrier.markdown-parser: The Markdown parser reifies the ruled subset, depth 6, stated ready, floor ready
  • spec:carrier.markdown-parser.bounded-parity: One finding class is shared while the carriers' outcomes stay their own, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-parser
  • spec:carrier.sdp-import: A TypeScript-carried Spec can be converted to Markdown, depth 7, stated ready, floor ready
  • spec:carrier.sdp-import.round-trip: A TypeScript carrier survives import as an equal Markdown graph, depth 8, stated ready, floor ready; example folded into spec:carrier.sdp-import
  • spec:carrier.sdp-import.feature-adapter: A bare .feature corpus can be imported, depth 8, stated idea, floor idea
  • spec:carrier.prose-ownership-rule: Every prose value has one typed owner, depth 7, stated ready, floor ready
  • spec:carrier.markdown-pack-authoring: A Pack has a Markdown manifest carrier, depth 7, stated ready, floor ready
  • spec:carrier.markdown-pack-authoring.markdown-ts-parity: A Markdown Pack twin matches its TypeScript manifest, depth 8, stated ready, floor ready; example folded into spec:carrier.markdown-pack-authoring
  • spec:carrier.markdown-pack-authoring.spec-envelope-refused: A Spec key on a Pack envelope is refused, depth 8, stated ready, floor ready; example folded into spec:carrier.markdown-pack-authoring
  • spec:carrier.markdown-body-grammar: The Markdown body accepts one closed form per section, depth 6, stated ready, floor ready
  • spec:carrier.markdown-body-grammar.table-refused: A table under a section is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.continuation-line-refused: A bullet wrapped onto a second line is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.ordered-list-refused: An ordered list is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.foreign-fence-refused: A fence other than gwt or gwt-vocabulary is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.h3-refused: An H3 under Design is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.plain-bullet-refused: A plain bullet under an open section is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.keyed-bullet-refused: A keyed bullet under a plain-bullet owner is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.trailing-prose-refused: Prose after structured content is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.repeated-field-refused: A repeated single-valued field is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.unrecognized-heading-refused: An unrecognized heading is refused with a suggestion, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.second-primary-owner-refused: A second primary owner is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.raw-html-refused: Raw HTML outside a code span is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.shared-description-refused: A second description across Behavior and Example space is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.markdown-body-grammar.integer-term-refused: An integer-like Model term is refused, depth 7, stated ready, floor ready; example folded into spec:carrier.markdown-body-grammar
  • spec:carrier.inline-code-spans: Inline code is content, never markup, depth 6, stated ready, floor ready
  • spec:carrier.inline-code-spans.narrative: Code spans in a Spec narrative are literal, depth 7, stated ready, floor ready; example folded into spec:carrier.inline-code-spans
  • spec:carrier.inline-code-spans.description: Code spans in section descriptions are literal, depth 7, stated ready, floor ready; example folded into spec:carrier.inline-code-spans
  • spec:carrier.inline-code-spans.list: Code spans in list entries are literal, depth 7, stated ready, floor ready; example folded into spec:carrier.inline-code-spans
  • spec:carrier.inline-code-spans.pack: Code spans in Pack framing are literal, depth 7, stated ready, floor ready; example folded into spec:carrier.inline-code-spans
  • spec:carrier.gherkin-authoring: Gherkin authoring enters the one graph, depth 7, stated ready, floor ready
  • spec:carrier.gherkin-authoring.parent-child-extraction: A Feature and Scenario enter the graph as parent and child, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.example-space-extraction: The pseudo-scenario supplies example space without a node, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.contract-parity: Markdown and Gherkin twins derive equal graphs and contracts, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.missing-id-refused: A Feature without identity is refused, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.unsupported-construct-refused: A Scenario Outline is refused, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.unknown-tag-refused: A graph-aware tag near miss is refused, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.authored-fact-refused: An authored delivery fact lookalike is refused, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.malformed-relation-refused: A malformed relation target is refused, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.unbound-ready-refused: A Gherkin example with an unbound used slot fails its stated readiness floor, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.duplicate-surface-refused: Duplicate Markdown and Gherkin surfaces are both excluded, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.description-location-refused: A bad description key reports its physical source line, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.step-less-scenario-refused: A step-less Scenario is refused at its Scenario line, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.gherkin-authoring.multi-finding-bounded: Multiple findings exclude one carrier and keep a healthy sibling, depth 8, stated ready, floor ready; example folded into spec:carrier.gherkin-authoring
  • spec:carrier.slot-notation: Slot notation declares, binds, and refuses to guess, depth 6, stated ready, floor ready
  • spec:carrier.slot-notation.typed-declaration: A typed declaration normalizes to the skeleton its binding shares, depth 7, stated ready, floor ready; example folded into spec:carrier.slot-notation
  • spec:carrier.slot-notation.refused-guess: A stray brace stays prose while an unusable group stays a named slot, depth 7, stated ready, floor ready; example folded into spec:carrier.slot-notation
  • spec:carrier.slot-notation.one-literal-binding: A one-literal group in a vocabulary is a binding that declares nothing, depth 7, stated ready, floor ready; example folded into spec:carrier.slot-notation
  • spec:carrier.step-keys: An example step may carry a key that survives rewording, depth 6, stated ready, floor ready
  • spec:carrier.step-keys.reworded-keyed-step-stays-bound: A keyed step reworded in its vocabulary and its example keeps its binding, depth 7, stated ready, floor ready; example folded into spec:carrier.step-keys
  • spec:carrier.step-keys.reworded-unkeyed-step-breaks: The same rewording without a key breaks the binding, depth 7, stated ready, floor ready; example folded into spec:carrier.step-keys
  • spec:carrier.step-keys.gherkin-keyed-step-stays-bound: A keyed Gherkin step keeps its binding across a rewording, depth 7, stated ready, floor ready; example folded into spec:carrier.step-keys
  • spec:carrier.step-keys.renamed-key-breaks: Renaming a step key breaks the binding, depth 7, stated ready, floor ready; example folded into spec:carrier.step-keys
  • spec:carrier.step-keys.repeated-key-refused: One key on two vocabulary steps refuses the carrier, depth 7, stated ready, floor ready; example folded into spec:carrier.step-keys
  • spec:carrier.step-keys.two-keys-on-one-step-refused: Two keys on one step refuse the carrier, depth 7, stated ready, floor ready; example folded into spec:carrier.step-keys
  • spec:carrier.step-keys.malformed-marker-refused: A step marker whose key is off the grammar refuses the carrier, depth 7, stated ready, floor ready; example folded into spec:carrier.step-keys
  • spec:carrier.step-keys.conflicting-example-key-withheld: An example marker that disagrees with its vocabulary withholds the contract, depth 7, stated ready, floor ready; example folded into spec:carrier.step-keys
  • spec:carrier.step-keys.key-equal-to-a-skeleton-withheld: A step key equal to another step's skeleton withholds the contract, depth 7, stated ready, floor ready; example folded into spec:carrier.step-keys
  • spec:carrier.step-keys.typescript-keyed-step-imports-keyed: A keyed TypeScript step keeps its key through import to Markdown, depth 7, stated ready, floor ready; example folded into spec:carrier.step-keys
  • spec:model.core-model: The Protocol models delivery with one enrichable Spec, depth 3, stated ready, floor ready
  • spec:model.enrichment-lifecycle: Enrichment keeps one Spec while its detail changes, depth 9, stated ready, floor ready
  • spec:model.spec-sections: Spec sections carry typed detail and direct verifier semantics, depth 4, stated ready, floor ready
  • spec:model.relations: Specs declare typed directed relations, depth 4, stated ready, floor ready
  • spec:model.stable-ids: Stable IDs are the Protocol's durable join key, depth 4, stated ready, floor ready
  • spec:model.stable-ids.namespaced-round-trip: A namespaced dotted path with a sub-part survives parsing unchanged, depth 5, stated ready, floor ready; example folded into spec:model.stable-ids
  • spec:model.stable-ids.malformed-refusal: An uppercase namespace is refused with its reason named, depth 5, stated ready, floor ready; example folded into spec:model.stable-ids
  • spec:model.stable-ids.unsectioned-address-refused: A # sub-part without its section is refused with its reason named, depth 5, stated ready, floor ready; example folded into spec:model.stable-ids
  • spec:model.pack-aggregate: A Pack is a truth-free review aggregate, depth 4, stated ready, floor ready
  • spec:model.anchors: Source anchors bind code without carrying intent, depth 4, stated ready, floor ready
  • spec:model.anchors.lookalike-refusal: A consumer-local lookalike builder mints no anchor and no finding, depth 5, stated ready, floor ready; example folded into spec:model.anchors
  • spec:model.anchors.physical-identity: A deep relative import that resolves to the Protocol builders is trusted, depth 5, stated ready, floor ready; example folded into spec:model.anchors
  • spec:model.structural-patterns: Architecturally significant units are annotated where they are realized, depth 5, stated ready, floor ready
  • spec:model.open-question-keys: An open question may carry a key that addresses it, depth 6, stated ready, floor ready
  • spec:model.open-question-keys.keyed-question-resolves: A keyed question is reified and its address resolves, depth 7, stated ready, floor ready; example folded into spec:model.open-question-keys
  • spec:model.open-question-keys.renamed-key-breaks: A renamed question key fails the mention that addresses it, depth 7, stated ready, floor ready; example folded into spec:model.open-question-keys
  • spec:model.open-question-keys.repeated-key-refused: A repeated question key refuses its carrier, depth 7, stated ready, floor ready; example folded into spec:model.open-question-keys
  • spec:model.design-maturity: What a Spec's design carries is derived, beside its readiness, depth 10, stated ready, floor ready
  • spec:model.planned-architecture: Components are designed ahead of their code, depth 5, stated ready, floor ready
  • spec:model.planned-architecture.unrealized-design: A component design no anchor satisfies is listed as unrealized, depth 6, stated ready, floor ready; example folded into spec:model.planned-architecture
  • spec:model.planned-architecture.differing-layer-and-uses: A realized component that differs from its design gives one row per field, depth 6, stated ready, floor ready; example folded into spec:model.planned-architecture
  • spec:model.planned-architecture.matching-design: A realized component that matches its design gives no row, depth 6, stated ready, floor ready; example folded into spec:model.planned-architecture
  • spec:model.open-question-fields: An open question may name who decides it, its links, a provisional reading and a re-entry trigger, depth 6, stated ready, floor ready
  • spec:model.open-question-fields.dropped-list-warns: A TypeScript question list that cannot be read drops whole with a warning, depth 7, stated ready, floor ready; example folded into spec:model.open-question-fields
  • spec:model.rule-keys: A rule or flow entry may carry a key that addresses it, depth 6, stated ready, floor ready
  • spec:model.relation-reasons: An authored relation may carry its reason, depth 5, stated ready, floor ready
  • spec:model.term-addresses: A Model term may carry a key that addresses it, depth 6, stated ready, floor ready
  • spec:model.term-addresses.keyed-term-resolves: A keyed term is reified and its address resolves, depth 7, stated ready, floor ready; example folded into spec:model.term-addresses
  • spec:model.term-addresses.unknown-term-key-refused: An address that names a term key no term carries is an error, depth 7, stated ready, floor ready; example folded into spec:model.term-addresses
  • spec:model.term-addresses.repeated-term-key-refused: A term key repeated in one Spec refuses its carrier, depth 7, stated ready, floor ready; example folded into spec:model.term-addresses
  • spec:model.term-addresses.malformed-term-marker-refused: A term marker whose key is off the grammar refuses its carrier, depth 7, stated ready, floor ready; example folded into spec:model.term-addresses
  • spec:model.term-addresses.typescript-term-imports-keyed: A keyed TypeScript term keeps its address through import to Markdown, depth 7, stated ready, floor ready; example folded into spec:model.term-addresses
  • spec:extraction.derive-graph: Carrier reification derives the one graph, depth 5, stated ready, floor ready
  • spec:extraction.delivery-facts: Resolving bindings confer direct delivery facts, depth 2, stated ready, floor ready
  • spec:extraction.determinism: Committed source derives byte-identical output, depth 1, stated ready, floor ready
  • spec:extraction.build-pipeline: The build pipeline has one ordered flow, depth 6, stated ready, floor ready
  • spec:extraction.build-pipeline.same-invocation: One query invocation shares its extracted graph and validation result, depth 7, stated ready, floor ready; example folded into spec:extraction.build-pipeline
  • spec:extraction.excludes: Extraction exclusions are strict consumer input, depth 6, stated ready, floor ready
  • spec:extraction.excludes.segment-boundary: A prefix excludes its own tree and leaves a similar sibling standing, depth 7, stated ready, floor ready; example folded into spec:extraction.excludes
  • spec:extraction.excludes.refused-path: A Windows-drive absolute path is refused rather than normalized, depth 7, stated ready, floor ready; example folded into spec:extraction.excludes
  • spec:extraction.claim-taxonomy: Graph claims retain their epistemic source, depth 6, stated ready, floor ready
  • spec:extraction.regenerability: Generated artifacts are disposable projections, depth 2, stated ready, floor ready
  • spec:extraction.schema-versioning: The graph declares its schema version, depth 6, stated ready, floor ready
  • spec:extraction.schema-versioning.declared-version: A derived payload carries a schema version its consumer can read, depth 7, stated ready, floor ready; example folded into spec:extraction.schema-versioning
  • spec:extraction.executable-examples: Bound examples execute their authored steps, depth 6, stated ready, floor ready
  • spec:extraction.executable-contracts: The build derives step and space contracts from graph examples, depth 7, stated ready, floor ready
  • spec:extraction.executable-contracts.concreteness-refusal: An unbound slot in a used step earns no step contract, depth 8, stated ready, floor ready; example folded into spec:extraction.executable-contracts
  • spec:extraction.executable-contracts.multi-entry-example: A second structured entry is named, never left silently inert, depth 8, stated ready, floor ready; example folded into spec:extraction.executable-contracts
  • spec:extraction.executable-contracts.case-colliding-path: A case-only path collision withholds the whole contracts tree, depth 8, stated ready, floor ready; example folded into spec:extraction.executable-contracts
  • spec:extraction.contract-declarations: Pinned declarations give an adopter a derived module to typecheck, depth 8, stated ready, floor ready
  • spec:extraction.open-section-order: Serialization preserves authored entry order, depth 6, stated ready, floor ready
  • spec:extraction.runnable-modules: Derived runnable modules freeze the registrar interface, depth 9, stated ready, floor ready
  • spec:extraction.example-runner: A bound example runs its contract steps against a fresh world, depth 8, stated ready, floor ready
  • spec:extraction.example-runner.step-order: A repeated step runs its one handler at each occurrence, in contract order, depth 9, stated ready, floor ready; example folded into spec:extraction.example-runner
  • spec:extraction.example-runner.red-step-naming: A red step names itself before the assertion detail, depth 9, stated ready, floor ready; example folded into spec:extraction.example-runner
  • spec:extraction.pack-member-order: A Pack node keeps its members in authored order, depth 8, stated ready, floor ready
  • spec:extraction.pack-member-order.manifest-order-kept: A manifest's member order survives into the graph and the reader, depth 9, stated ready, floor ready; example folded into spec:extraction.pack-member-order
  • spec:extraction.entry-locations: The graph records where each addressable entry is written, depth 6, stated ready, floor ready
  • spec:extraction.entry-citations: The graph records where anchored source cites an entry address, depth 8, stated ready, floor ready
  • spec:extraction.entry-citations.code-comment-cites-declaration: A code file's comment cites a declaration without reading as a test line, depth 9, stated ready, floor ready; example folded into spec:extraction.entry-citations
  • spec:extraction.entry-citations.test-title-cites-declaration: A test title in an anchored file cites a pinned declaration, depth 9, stated ready, floor ready; example folded into spec:extraction.entry-citations
  • spec:extraction.entry-citations.unanchored-file-unread: A file that carries no anchor is not read for citations, depth 9, stated ready, floor ready; example folded into spec:extraction.entry-citations
  • spec:extraction.entry-citations.unresolved-citation: A citation of an entry its Spec lacks reports through the recipe, never as a Protocol finding, depth 9, stated ready, floor ready; example folded into spec:extraction.entry-citations
  • spec:validation.readiness-floor: Stated readiness must clear its floor, depth 4, stated ready, floor ready
  • spec:validation.readiness-floor.unrelated-scoped-spec: A scoped Spec with no relation names the relation clause, depth 5, stated ready, floor ready; example folded into spec:validation.readiness-floor
  • spec:validation.readiness-floor.blocking-open-question: A blocking open question holds a Spec below defined, depth 5, stated ready, floor ready; example folded into spec:validation.readiness-floor
  • spec:validation.typed-dependency-floor: A ready Spec rests only on settled dependencies, depth 5, stated ready, floor ready
  • spec:validation.typed-dependency-floor.relation-rungs: Every relation reads the four stated target rungs, depth 6, stated ready, floor ready; example folded into spec:validation.typed-dependency-floor
  • spec:validation.typed-dependency-floor.missing-targets: Missing targets fail relation resolution once, depth 6, stated ready, floor ready; example folded into spec:validation.typed-dependency-floor
  • spec:validation.typed-dependency-floor.unsettled-fact: An unsettled constraint bounds ready but permits defined, depth 6, stated ready, floor ready; example folded into spec:validation.typed-dependency-floor
  • spec:validation.typed-dependency-floor.stated-readiness: Target floor failures do not propagate across dependencies, depth 6, stated ready, floor ready; example folded into spec:validation.typed-dependency-floor
  • spec:validation.duplicate-ids: Duplicate carrier IDs are excluded loudly, depth 7, stated ready, floor ready
  • spec:validation.duplicate-ids.dual-carrier: TypeScript and Markdown duplicates are both refused, depth 8, stated ready, floor ready; example folded into spec:validation.duplicate-ids
  • spec:validation.two-check-families: Validation separates well-formedness from non-pretending, depth 2, stated ready, floor ready
  • spec:validation.two-check-families.split-report: One report carries both families and claims neither as its own, depth 3, stated ready, floor ready; example folded into spec:validation.two-check-families
  • spec:validation.referential-integrity: Every graph reference resolves, depth 3, stated ready, floor ready
  • spec:validation.referential-integrity.dangling-target: An unrelated missing target is a bare conformance error, depth 4, stated ready, floor ready; example folded into spec:validation.referential-integrity
  • spec:validation.referential-integrity.did-you-mean: A unique near miss earns a did-you-mean suggestion, depth 4, stated ready, floor ready; example folded into spec:validation.referential-integrity
  • spec:validation.prose-mentions: Every Spec id written in prose resolves, depth 7, stated ready, floor ready
  • spec:validation.claim-separation: Graph claims and contracts stay distinct, depth 7, stated ready, floor ready
  • spec:validation.claim-separation.collapsed-edge-claim: A binding edge cannot borrow the declared claim, depth 8, stated ready, floor ready; example folded into spec:validation.claim-separation
  • spec:validation.claim-separation.unratified-descriptor: An unratified kind fails closed instead of reaching the floor, depth 8, stated ready, floor ready; example folded into spec:validation.claim-separation
  • spec:validation.verification-linkage: Example verification and oracle bindings resolve honestly, depth 3, stated ready, floor ready
  • spec:validation.verification-linkage.unbound-example: A declared verifier no test binds confers nothing, depth 4, stated ready, floor ready; example folded into spec:validation.verification-linkage
  • spec:validation.verification-linkage.unresolved-oracle: An oracle targeting a Spec with no example space is refused, depth 4, stated ready, floor ready; example folded into spec:validation.verification-linkage
  • spec:validation.unbound-example-posture: An unbound example below ready is data, not a warning, depth 4, stated ready, floor ready
  • spec:validation.unbound-example-posture.lower-rungs: Below-ready examples keep declared verifier data, depth 5, stated ready, floor ready; example folded into spec:validation.unbound-example-posture
  • spec:validation.unbound-example-posture.warning-cases: Ready examples and non-example verifiers keep warnings, depth 5, stated ready, floor ready; example folded into spec:validation.unbound-example-posture
  • spec:validation.unbound-example-posture.parent-traces: Parent gaps follow enabled bindings and preserve the decision exemption, depth 5, stated ready, floor ready; example folded into spec:validation.unbound-example-posture
  • spec:validation.oracle-target-eligibility: Oracle eligibility follows example-space ownership, depth 5, stated ready, floor ready
  • spec:validation.oracle-target-eligibility.rule-space-accepted: A rule owning an example space accepts an oracle, depth 6, stated ready, floor ready; example folded into spec:validation.oracle-target-eligibility
  • spec:validation.oracle-target-eligibility.missing-space-refused: A target without an example space refuses an oracle, depth 6, stated ready, floor ready; example folded into spec:validation.oracle-target-eligibility
  • spec:validation.pack-coherence: Packs are coherent aggregates, depth 5, stated ready, floor ready
  • spec:validation.pack-coherence.incoherent-aggregate: A repeated member and a non-model modelRef are both named, depth 6, stated ready, floor ready; example folded into spec:validation.pack-coherence
  • spec:validation.authored-honesty: Machine truth is never authored, depth 3, stated ready, floor ready
  • spec:validation.authored-honesty.section-authored-fact: A delivery fact smuggled into a section is refused, depth 4, stated ready, floor ready; example folded into spec:validation.authored-honesty
  • spec:validation.authored-honesty.unearned-stated-fact: A stated delivery fact no binding earns is refused, depth 4, stated ready, floor ready; example folded into spec:validation.authored-honesty
  • spec:validation.warn-level-signals: Missing connective evidence warns without failing, depth 3, stated ready, floor ready
  • spec:validation.warn-level-signals.orphan-signal: A disconnected Spec warns and fails nothing, depth 4, stated ready, floor ready; example folded into spec:validation.warn-level-signals
  • spec:validation.warn-level-signals.ready-gap-signal: A ready Spec without a verifier warns and fails nothing, depth 4, stated ready, floor ready; example folded into spec:validation.warn-level-signals
  • spec:validation.kind-evidence: Each kind carries its own evidence, depth 5, stated ready, floor ready
  • spec:validation.kind-evidence.constraints-alone: Constraints alone stop short of complete behavior evidence, depth 6, stated ready, floor ready; example folded into spec:validation.kind-evidence
  • spec:validation.kind-evidence.untargeted-constraint: A constraint without a machine-readable target is not complete, depth 6, stated ready, floor ready; example folded into spec:validation.kind-evidence
  • spec:validation.kind-evidence.empty-promoted-child: An empty promoted child confers no evidence, depth 6, stated ready, floor ready; example folded into spec:validation.kind-evidence
  • spec:validation.kind-evidence.second-entry-untargeted: A constraint whose second entry has no target is not complete, depth 6, stated ready, floor ready; example folded into spec:validation.kind-evidence
  • spec:validation.diagnostic-rendering: One diagnostic currency, its location composed from structured fields, depth 9, stated ready, floor ready
  • spec:validation.diagnostic-rendering.composed-location: One finding, three location shapes, one composition rule, depth 10, stated ready, floor ready; example folded into spec:validation.diagnostic-rendering
  • spec:validation.diagnostic-rendering.table-cell-location: The same three location shapes, rendered as table cells, depth 10, stated ready, floor ready; example folded into spec:validation.diagnostic-rendering
  • spec:validation.validator-self-testing: Every validator ships evidence in both directions, depth 3, stated ready, floor ready
  • spec:validation.validator-self-testing.shipped-checks-paired: Every shipped check reports its refusing probe and leaves its near miss alone, depth 4, stated ready, floor ready; example folded into spec:validation.validator-self-testing
  • spec:validation.validator-self-testing.silent-check-named: A check that stops reporting is named silent, depth 4, stated ready, floor ready; example folded into spec:validation.validator-self-testing
  • spec:validation.validator-self-testing.overeager-check-named: A check that reports its near miss is named overeager, depth 4, stated ready, floor ready; example folded into spec:validation.validator-self-testing
  • spec:validation.validator-self-testing.unpaired-check-named: A registered check without a probe pair is named unpaired, depth 4, stated ready, floor ready; example folded into spec:validation.validator-self-testing
  • spec:validation.validator-self-testing.duplicate-pair-named: A check paired twice is named, depth 4, stated ready, floor ready; example folded into spec:validation.validator-self-testing
  • spec:validation.validator-self-testing.unregistered-id-named: A finding id the source writes outside every registry is named, depth 4, stated ready, floor ready; example folded into spec:validation.validator-self-testing
  • spec:validation.next-rung-floor: The floor names what blocks the floor's next rung, depth 6, stated ready, floor ready
  • spec:validation.next-rung-floor.typed-dependency-targets: A defined Spec resting on a scoped dependency is told which one, depth 7, stated ready, floor ready; example folded into spec:validation.next-rung-floor
  • spec:validation.next-rung-floor.blocking-question: A scoped Spec held by a blocking question is told the clause, depth 7, stated ready, floor ready; example folded into spec:validation.next-rung-floor
  • spec:validation.superseded-decision-signal: A Spec shaped by a superseded decision warns, depth 7, stated ready, floor ready
  • spec:validation.superseded-decision-signal.replaced-ruling-warns: A Spec shaped by a replaced decision warns once and fails nothing, depth 8, stated ready, floor ready; example folded into spec:validation.superseded-decision-signal
  • spec:validation.superseded-decision-signal.chain-end-named: The warning names the decision at the end of a chain of replacements, depth 8, stated ready, floor ready; example folded into spec:validation.superseded-decision-signal
  • spec:validation.superseded-decision-signal.branch-names-every-end: A replacement chain that branches names every end, depth 8, stated ready, floor ready; example folded into spec:validation.superseded-decision-signal
  • spec:validation.superseded-decision-signal.closed-chain-named: A chain of replacements that closes on itself is named and fails nothing, depth 8, stated ready, floor ready; example folded into spec:validation.superseded-decision-signal
  • spec:validation.superseded-decision-signal.dependency-unread: A dependency on a replaced decision raises no warning, depth 8, stated ready, floor ready; example folded into spec:validation.superseded-decision-signal
  • spec:validation.superseded-decision-signal.superseded-subject-silent: A superseded decision is not warned for the decision it names, depth 8, stated ready, floor ready; example folded into spec:validation.superseded-decision-signal
  • spec:validation.superseded-decision-signal.replacement-below-ready-named: A replacement still below ready is named as it stands, depth 8, stated ready, floor ready; example folded into spec:validation.superseded-decision-signal
  • spec:validation.superseded-decision-signal.live-replacement-warns: A decision still decided by the record it replaces warns, depth 8, stated ready, floor ready; example folded into spec:validation.superseded-decision-signal
  • spec:validation.superseded-decision-signal.end-and-loop-named: A chain of replacements that reaches an end and a loop names both, depth 8, stated ready, floor ready; example folded into spec:validation.superseded-decision-signal
  • spec:validation.architecture-constraints: Declared architecture rules are checked against anchored structure, depth 11, stated ready, floor ready
  • spec:validation.architecture-constraints.forbidden-layer-pair: A domain member that uses an infrastructure member breaks a forbidden pair, depth 12, stated ready, floor ready; example folded into spec:validation.architecture-constraints
  • spec:validation.architecture-constraints.isolated-context-as-rule: The walk named as a rules file fails validation on an isolation breach, depth 12, stated ready, floor ready; example folded into spec:validation.architecture-constraints
  • spec:validation.architecture-constraints.unstated-layer-unclassified: A component with no layer leaves its edge unclassified, depth 12, stated ready, floor ready; example folded into spec:validation.architecture-constraints
  • spec:validation.corpus-rules: Corpus-authored rules run on the one validation path, depth 10, stated ready, floor ready
  • spec:validation.corpus-rules.copies-contain-changes: A rules file that empties its graph leaves the next file's graph whole, depth 11, stated ready, floor ready; example folded into spec:validation.corpus-rules
  • spec:validation.corpus-rules.error-finding-fails: An error from a corpus rule fails validation and leaves the Protocol's line alone, depth 11, stated ready, floor ready; example folded into spec:validation.corpus-rules
  • spec:validation.corpus-rules.malformed-finding-fails: A finding with no subject fails its rules file, depth 11, stated ready, floor ready; example folded into spec:validation.corpus-rules
  • spec:validation.corpus-rules.params-edit-starts-a-cycle: Editing a parameter file starts a cycle that reads the new parameters, depth 11, stated ready, floor ready; example folded into spec:validation.corpus-rules
  • spec:validation.corpus-rules.rules-edit-starts-a-cycle: Rewriting a rules file under node_modules starts a cycle that runs the new body, depth 11, stated ready, floor ready; example folded into spec:validation.corpus-rules
  • spec:validation.corpus-rules.unreadable-params-fail-one-file: A parameter file that stops being JSON fails only its own rules file, and the watcher runs on, depth 11, stated ready, floor ready; example folded into spec:validation.corpus-rules
  • spec:validation.corpus-rules.warning-finding-informs: A warning from a corpus rule informs and passes, depth 11, stated ready, floor ready; example folded into spec:validation.corpus-rules
  • spec:validation.external-registers: A corpus checks the register tokens its prose cites, depth 11, stated ready, floor ready
  • spec:validation.external-registers.unknown-and-retired: A cited token the register lacks or retires fails a rules run, depth 12, stated ready, floor ready; example folded into spec:validation.external-registers
  • spec:validation.external-registers.uncited-on-request: A held token no Spec cites fails a rules run only when the caller asks, depth 12, stated ready, floor ready; example folded into spec:validation.external-registers
  • spec:consumers.projections-model: Projections fan out from one graph without becoming truth stores, depth 2, stated ready, floor ready
  • spec:consumers.projections-model.roadmap-views: Roadmap views read releases, baselines and phases from git and the graph, depth 16, stated scoped, floor scoped
  • spec:consumers.impact-graph: Mechanical code structure stays inferred and apart from curated intent, depth 6, stated ready, floor ready
  • spec:consumers.impact-graph.curation-assist: File-level imports show where curation is missing, depth 7, stated ready, floor ready
  • spec:consumers.impact-graph.symbol-reach: Exhaustive symbol reach waits for a language-neutral identity, depth 7, stated idea, floor scoped
  • spec:consumers.agent-surface: Agents script a visible typed graph, depth 3, stated ready, floor ready
  • spec:consumers.agent-surface.scripted-context-body: A scripted body returns claim-decoded context, pre-shaped by the body, depth 4, stated ready, floor ready; example folded into spec:consumers.agent-surface
  • spec:consumers.agent-surface.demand-map-entries: One body reaches every entry point the demand map names, and no symbol entry, depth 4, stated ready, floor ready; example folded into spec:consumers.agent-surface
  • spec:consumers.agent-surface.answer-shapes: Recipe answers fit an agent's context and explain their misses, depth 11, stated ready, floor ready
  • spec:consumers.agent-surface.evaluation-sink: The evaluation sink runs one body and prints its return, depth 4, stated ready, floor ready
  • spec:consumers.agent-surface.evaluation-sink.recipe-call: A body calls a shipped recipe and returns its answer unchanged, depth 5, stated ready, floor ready; example folded into spec:consumers.agent-surface.evaluation-sink
  • spec:consumers.agent-surface.evaluation-sink.unknown-recipe: A call to a recipe the catalog does not hold fails the body, depth 5, stated ready, floor ready; example folded into spec:consumers.agent-surface.evaluation-sink
  • spec:consumers.agent-surface.evaluation-sink.exported-evaluator: A script holding a graph runs a shipped recipe through the exported evaluator, depth 5, stated ready, floor ready; example folded into spec:consumers.agent-surface.evaluation-sink
  • spec:consumers.design-review: Design Review renders graph context without becoming a gate, depth 8, stated ready, floor ready
  • spec:consumers.design-review.pure-projection: The view is the graph read twice, and the corpus is untouched by reading it, depth 9, stated ready, floor ready; example folded into spec:consumers.design-review
  • spec:consumers.census-page: Census renders the runtime taxonomy without becoming a registry, depth 10, stated ready, floor ready
  • spec:consumers.mermaid-view: Mermaid renders bounded one-hop and Pack diagrams without becoming a graph browser, depth 10, stated ready, floor ready
  • spec:consumers.gherkin-view: Gherkin view renders any Spec as a disposable read shape, depth 10, stated ready, floor ready
  • spec:consumers.reader: The reader bridges agent entry points to composable graph context, depth 4, stated ready, floor ready
  • spec:consumers.reader.concept-entry: A concept recorded only inside a Spec's sections is still reached, and the field is named, depth 5, stated ready, floor ready; example folded into spec:consumers.reader
  • spec:consumers.reader.file-entry: A source file reaches the Spec its binding names, and a carrier reaches its own Spec, depth 5, stated ready, floor ready; example folded into spec:consumers.reader
  • spec:consumers.reader.changeset-entry: A changeset names what it reaches, why, and what it cannot see, depth 5, stated ready, floor ready; example folded into spec:consumers.reader
  • spec:consumers.edit-model: Views compose scoped intent instead of patching canonical source, depth 3, stated ready, floor ready
  • spec:consumers.authoring-on-ramp: Authors move one Spec from intent to reviewed evidence, depth 8, stated ready, floor ready
  • spec:consumers.reading-on-ramp: The reading skill teaches agents to query the graph, depth 4, stated ready, floor ready
  • spec:consumers.delivery-session-on-ramp: Delivery sessions route work from current graph state, depth 12, stated ready, floor ready
  • spec:consumers.agent-surface.authoring-recipes: Authoring questions stay executable graph recipes, depth 4, stated ready, floor ready
  • spec:consumers.agent-surface.register-recipes: Register questions stay executable graph recipes, depth 7, stated ready, floor ready
  • spec:consumers.intent-composition: Composed intent hands off on one proposal shape, depth 4, stated ready, floor ready
  • spec:consumers.graph-first-planning: The next body of work is planned from the graph, not from a prose index, depth 13, stated ready, floor ready
  • spec:consumers.adopter-on-ramp: An adopter learns graph homes, carrier grammar and shipped paths from the on-ramps, depth 10, stated ready, floor ready
  • spec:consumers.shipped-protocol-corpus: The package ships the Specs and on-ramps its skills cite, depth 9, stated ready, floor ready
  • spec:consumers.derived-readiness-banner: Derived readiness renders beside the stated rung and warns in one direction, depth 9, stated ready, floor ready
  • spec:consumers.derived-readiness-banner.dishonest-divergence: An overstated rung raises the banner and names the clause that refused, depth 10, stated ready, floor ready; example folded into spec:consumers.derived-readiness-banner
  • spec:consumers.derived-readiness-banner.honest-headroom: A rung the structure overshoots renders as information, not as a banner, depth 10, stated ready, floor ready; example folded into spec:consumers.derived-readiness-banner
  • spec:consumers.binding-language-views: Views speak binding language, never the internal fact name, depth 9, stated ready, floor ready
  • spec:consumers.binding-language-views.bound-spec-page: A fully bound Spec renders binding language on the page and in the index, depth 10, stated ready, floor ready; example folded into spec:consumers.binding-language-views
  • spec:consumers.binding-language-views.pack-member-table: The Pack member table speaks the page's binding language, not a shorthand, depth 10, stated ready, floor ready; example folded into spec:consumers.binding-language-views
  • spec:consumers.wholesale-view-rewrite: Every view run rewrites the view wholesale, depth 9, stated ready, floor ready
  • spec:consumers.wholesale-view-rewrite.stale-page-removed: A page from an earlier run does not survive the next one, depth 10, stated ready, floor ready; example folded into spec:consumers.wholesale-view-rewrite
  • spec:consumers.wholesale-view-rewrite.late-stale-page: A page the build's invalidation never saw still does not survive the swap, depth 10, stated ready, floor ready; example folded into spec:consumers.wholesale-view-rewrite
  • spec:consumers.wholesale-view-rewrite.failed-run-view-removed: A run that cannot produce a current view leaves no view at all, depth 10, stated ready, floor ready; example folded into spec:consumers.wholesale-view-rewrite
  • spec:consumers.wholesale-view-rewrite.build-invalidates-view: A build that never renders still takes the old view down, depth 10, stated ready, floor ready; example folded into spec:consumers.wholesale-view-rewrite
  • spec:consumers.agent-surface.address-and-cycle-recipes: Address resolution and dependency cycles stay executable graph recipes, depth 8, stated ready, floor ready
  • spec:consumers.agent-surface.address-and-cycle-recipes.cycle-fails-a-rules-run: The shipped dependency-cycles file fails a rules run on a cycle, depth 9, stated ready, floor ready; example folded into spec:consumers.agent-surface.address-and-cycle-recipes
  • spec: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, depth 9, stated ready, floor ready; example folded into spec:consumers.agent-surface.address-and-cycle-recipes
  • spec:consumers.agent-surface.address-and-cycle-recipes.chain-reports-nothing: A dependency chain with no cycle yields no finding, depth 9, stated ready, floor ready; example folded into spec:consumers.agent-surface.address-and-cycle-recipes
  • spec:consumers.spec-studio: The Spec Studio is a static HTML workbench over the one graph, depth 5, stated ready, floor ready
  • spec:consumers.spec-studio.index-page: The index says where the corpus stands and narrows every Spec, depth 16, stated ready, floor ready
  • spec:consumers.spec-studio.pack-page: A Pack page shows the Pack's design as one card per member, depth 16, stated ready, floor ready
  • spec:consumers.spec-studio.publisher: sdp studio publishes the Studio as one page set, depth 11, stated ready, floor ready
  • spec:consumers.spec-studio.search: Search finds a Spec, a Pack, an entry or a bound file by a word, depth 16, stated ready, floor ready
  • spec:consumers.spec-studio.page-elements: A few custom elements filter, search, open and copy on a rendered page, depth 17, stated ready, floor ready
  • spec:consumers.spec-studio.data: The Studio renders from the reader's values and embeds only what its script reads, depth 10, stated ready, floor ready
  • spec:consumers.spec-studio.shell: The Studio's shell frames every page with navigation, a rail and a canvas, depth 15, stated ready, floor ready
  • spec:consumers.spec-studio.lenses: Five lenses read the graph as Packs, capabilities, architecture, tests and evidence, depth 11, stated ready, floor ready
  • spec:consumers.spec-studio.spec-page: A Spec page shows one Spec in collapsible panels, in a fixed order, depth 16, stated ready, floor ready
  • spec:consumers.spec-studio.spec-page.core: A Spec page's core shows the whole Spec, with an anchor for every entry, depth 17, stated ready, floor ready
  • spec:consumers.spec-studio.verification-panels: The panels for examples, targets, verifiers and evidence, depth 17, stated ready, floor ready
  • spec:consumers.spec-studio.intent-panel: A composing panel on every page gathers scoped intent for an agent, depth 11, stated ready, floor ready
  • spec:consumers.spec-studio.components: The Studio's custom elements each hold one view the build renders, depth 12, stated ready, floor ready
  • spec:consumers.spec-studio.responsive: The Studio reads on a phone as on a desktop, depth 7, stated ready, floor ready
  • spec:consumers.spec-studio.sharing: A Studio build is stamped and shared from a static host, depth 14, stated ready, floor ready
  • spec:consumers.spec-studio.sharing.stamp-written-apart: The stamp is written beside the page set, and a later build removes it, depth 15, stated ready, floor ready; example folded into spec:consumers.spec-studio.sharing
  • spec:consumers.spec-studio.data.recipe-answers: A page takes each recipe answer from the recipe's shipped body, depth 11, stated ready, floor ready
  • spec:consumers.spec-studio.data.inputs: The Studio reads two named inputs beside the graph, a base graph and run records, depth 12, stated ready, floor ready
  • spec:consumers.spec-studio.data.inputs.graph-only: Without inputs the page set is the graph's alone, depth 13, stated ready, floor ready; example folded into spec:consumers.spec-studio.data.inputs
  • spec:consumers.spec-studio.data.inputs.both-given: Both inputs add their pages, named, and the same inputs write the same bytes, depth 13, stated ready, floor ready; example folded into spec:consumers.spec-studio.data.inputs
  • spec:consumers.spec-studio.publisher.watch: sdp studio --watch rebuilds the page set on each carrier change, depth 12, stated ready, floor ready
  • spec:consumers.spec-studio.publisher.watch.matches-plain-run: Each watch cycle writes the page set a plain run writes, depth 13, stated ready, floor ready; example folded into spec:consumers.spec-studio.publisher.watch
  • spec:consumers.spec-studio.navigation: Every page of the page set is reached from the top navigation and the index, depth 17, stated ready, floor ready
  • spec:consumers.spec-studio.lenses.packs: The Packs lens groups every Spec by the Packs that hold it, depth 12, stated ready, floor ready
  • spec:consumers.spec-studio.lenses.architecture: The architecture lens draws components by context and layer, the planned beside the built, depth 14, stated ready, floor ready
  • spec:consumers.spec-studio.lenses.architecture.unit-register: The architecture page lists each component's significant units by role, depth 15, stated ready, floor ready
  • spec:consumers.spec-studio.lenses.architecture.planned-apart: A component design no anchor realizes draws planned beside the built one, depth 15, stated ready, floor ready; example folded into spec:consumers.spec-studio.lenses.architecture
  • spec:consumers.spec-studio.lenses.tests: The tests lens shows how far each Spec's verification reaches, depth 12, stated ready, floor ready
  • spec:consumers.spec-studio.lenses.tests.coverage-row: A Spec's row on the tests lens counts its exercised keyed rules, depth 13, stated ready, floor ready; example folded into spec:consumers.spec-studio.lenses.tests
  • spec:consumers.spec-studio.lenses.evidence: The evidence lens names each source of runtime evidence and reads it as not tracked, depth 12, stated ready, floor ready
  • spec:consumers.spec-studio.pack-page.maturity-map: A Pack page's maturity map places every member by its stated rung and its floor, depth 17, stated ready, floor ready
  • spec:consumers.spec-studio.spec-page.cited-declaration: A pinned declaration shows the test line that cites it, depth 17, stated ready, floor ready; example folded into spec:consumers.spec-studio.spec-page
  • spec:consumers.spec-studio.verification-panels.rule-coverage: Each keyed rule shows the examples that exercise it, or that none does, depth 18, stated ready, floor ready; example folded into spec:consumers.spec-studio.verification-panels
  • spec:consumers.spec-studio.registers: The corpus's registers are pages a reviewer opens from a link, depth 16, stated ready, floor ready
  • spec:consumers.spec-studio.registers.blocking-first: The questions page lists the Specs with a blocking question first, depth 17, stated ready, floor ready; example folded into spec:consumers.spec-studio.registers
  • spec:consumers.spec-studio.owner-queue: The owner queue page orders the statements and questions only a person can settle, depth 16, stated ready, floor ready
  • spec:consumers.spec-studio.owner-queue.dependency-first: The owner queue lists a waiting statement after the one it rests on, depth 17, stated ready, floor ready; example folded into spec:consumers.spec-studio.owner-queue
  • spec:consumers.spec-studio.diff-page: The diff page shows what changed in the design since a base graph, depth 13, stated ready, floor ready
  • spec:consumers.spec-studio.diff-page.changed-entry: The diff page shows a changed entry's base and built values, depth 14, stated ready, floor ready; example folded into spec:consumers.spec-studio.diff-page
  • spec:consumers.spec-studio.runs-page: The runs page shows the run records the build was given, joined to test files, depth 13, stated ready, floor ready
  • spec:consumers.spec-studio.runs-page.external-evidence: The runs page shows a run as external evidence from a test file, depth 14, stated ready, floor ready; example folded into spec:consumers.spec-studio.runs-page
  • spec:consumers.spec-studio.glossary-page: The glossary page lists every term the corpus's Specs define, depth 11, stated ready, floor ready
  • spec:consumers.spec-studio.glossary-page.same-word-twice: A word two Specs define appears once per Spec on the glossary page, depth 12, stated ready, floor ready; example folded into spec:consumers.spec-studio.glossary-page
  • spec:consumers.spec-studio.intent-panel.refresh-keeps-intents: Refreshing a tab keeps every gathered intent, depth 12, stated ready, floor ready; example folded into spec:consumers.spec-studio.intent-panel
  • spec:consumers.spec-studio.diagrams: A diagram is laid out from graph values into SVG with a text equivalent, depth 13, stated ready, floor ready
  • spec:consumers.spec-studio.diagrams.within-bound: An architecture within the bound draws in one diagram, the same bytes twice, depth 14, stated ready, floor ready; example folded into spec:consumers.spec-studio.diagrams
  • spec:consumers.spec-studio.diagrams.folds-by-context: An architecture over the bound folds by context, depth 14, stated ready, floor ready; example folded into spec:consumers.spec-studio.diagrams
  • spec:consumers.spec-studio.diagrams.folds-by-layer: One context over the bound folds by layer, depth 14, stated ready, floor ready; example folded into spec:consumers.spec-studio.diagrams
  • spec:consumers.spec-studio.export: A Pack exports as one file, and every page prints as a document, depth 17, stated ready, floor ready
  • spec:consumers.spec-studio.export.self-contained: A Pack's export opens alone and keeps its links inside it, depth 18, stated ready, floor ready; example folded into spec:consumers.spec-studio.export
  • spec:consumers.studio-on-ramp: The Studio skill teaches agents to publish, share and read the Spec Studio, depth 18, stated ready, floor ready
  • spec:consumers.pack-design: The Pack context carries the Pack's design, depth 9, stated ready, floor ready
  • spec:consumers.design-review.pack-design-page: A Pack page shows where the Pack's design stands, depth 11, stated ready, floor ready
  • spec:consumers.agent-surface.recipe-parameters: Recipes take parameters as data and ship as runnable files, depth 4, stated ready, floor ready
  • spec:consumers.agent-surface.design-recipes: Design work reads its answers from catalog recipes, depth 10, stated ready, floor ready
  • spec:consumers.engine-provenance: The CLI names the engine that produced a result, depth 13, stated ready, floor ready
  • spec:consumers.validate-watch: Validation re-runs while an author edits carriers, depth 9, stated ready, floor ready
  • spec:consumers.agent-surface.example-space-coverage: Example spaces report which values their examples cover, depth 11, stated ready, floor ready
  • spec:consumers.agent-surface.example-space-coverage.uncovered-literal: A literal no example binds is reported uncovered, and an unbound child is named, depth 12, stated ready, floor ready; example folded into spec:consumers.agent-surface.example-space-coverage
  • spec:consumers.agent-surface.example-space-coverage.number-not-enumerable: A number slot is not enumerable and reports no uncovered value, depth 12, stated ready, floor ready; example folded into spec:consumers.agent-surface.example-space-coverage
  • spec:consumers.review-perspectives: A Pack is read from a named perspective, depth 10, stated ready, floor ready
  • spec:consumers.context-bundle: A context bundle is composed per invocation within a stated budget, depth 11, stated ready, floor ready
  • spec:consumers.context-bundle.parts-cover-the-pack: A Pack too large for one bundle reads whole in parts, depth 12, stated ready, floor ready; example folded into spec:consumers.context-bundle
  • spec:consumers.context-bundle.oversized-member-named: A member larger than the budget is named, and no part is returned, depth 12, stated ready, floor ready; example folded into spec:consumers.context-bundle
  • spec:consumers.design-diff: Designs are compared between a base commit and the working tree at entry grain, depth 5, stated ready, floor ready
  • spec:consumers.intent-composition.proposal: A change proposal is addressed, based and checked before it lands, depth 9, stated ready, floor ready
  • spec:consumers.intent-composition.proposal.memo: Recipe 49 renders a change proposal as the Markdown memo a person reviews, depth 10, stated ready, floor ready
  • spec:consumers.intent-composition.proposal.memo.shared: Recipe 49 and the composing panel write one memo for one proposal, depth 11, stated ready, floor ready; example folded into spec:consumers.intent-composition.proposal.memo
  • spec:consumers.reference-projection: A reference projection serves a reader outside the repository, depth 3, stated idea, floor idea
  • spec:consumers.structural-mermaid: Mermaid diagrams can be rooted at code units, depth 15, stated scoped, floor scoped
  • spec:consumers.obsidian-vault: An Obsidian vault lets a person iterate on designs from the one graph, depth 10, stated ready, floor ready
  • spec:consumers.obsidian-vault.fresh-vault: A fresh vault is written the same way twice and every link resolves, depth 11, stated ready, floor ready; example folded into spec:consumers.obsidian-vault
  • spec:consumers.obsidian-vault.person-notes-survive: A regeneration removes a note that left the graph and keeps a person's notes, depth 11, stated ready, floor ready; example folded into spec:consumers.obsidian-vault
  • spec:consumers.obsidian-vault.unknown-note-refused: A note a person wrote inside the generated folder refuses the regeneration, depth 11, stated ready, floor ready; example folded into spec:consumers.obsidian-vault
  • spec:consumers.obsidian-vault.changed-note-refused: A generated note a person changed refuses the regeneration and keeps the edit, depth 11, stated ready, floor ready; example folded into spec:consumers.obsidian-vault
  • spec:consumers.obsidian-vault.hidden-file-refused: A person's file under a temporary's name refuses the regeneration, depth 11, stated ready, floor ready; example folded into spec:consumers.obsidian-vault
  • spec:consumers.obsidian-vault.vault-in-build-path-refused: A vault directory the build removes refuses the run and keeps a person's notes, depth 11, stated ready, floor ready; example folded into spec:consumers.obsidian-vault
  • spec:consumers.obsidian-vault.interrupted-run-recovered: A run after a stopped synchronization finishes it, depth 11, stated ready, floor ready; example folded into spec:consumers.obsidian-vault
  • spec:consumers.obsidian-vault.failed-extraction-keeps-notes: A failed extraction keeps the notes and says so on the index, depth 11, stated ready, floor ready; example folded into spec:consumers.obsidian-vault
  • spec:consumers.obsidian-vault.failed-extraction-recovered: The run after a failed extraction passes the guard and restores the index, depth 11, stated ready, floor ready; example folded into spec:consumers.obsidian-vault
  • spec:consumers.obsidian-vault.notes: Every Spec, Pack, code unit and keyed term is a note, and every relation is a link, depth 11, stated ready, floor ready
  • spec:consumers.obsidian-vault.notes.entry-address-link: An entry address in prose opens the entry's block in its Spec's note, depth 12, stated ready, floor ready; example folded into spec:consumers.obsidian-vault.notes
  • spec:consumers.obsidian-vault.notes.unresolved-mention-stays: A mention of an entry that does not exist stays as written, depth 12, stated ready, floor ready; example folded into spec:consumers.obsidian-vault.notes
  • spec:consumers.obsidian-vault.notes.term-address-link: A keyed Model term gets a note, and its address in prose opens the term's block, depth 12, stated ready, floor ready; example folded into spec:consumers.obsidian-vault.notes
  • spec:consumers.obsidian-vault.notes.case-collision-refused: Two Specs whose notes differ only in case refuse the run, depth 12, stated ready, floor ready; example folded into spec:consumers.obsidian-vault.notes
  • spec:consumers.obsidian-vault.bases: A Pack's members and the standing queries are tables over the reader's values, depth 11, stated ready, floor ready
  • spec:consumers.obsidian-vault.bases.views-match-sources: Each standing view selects what its source selects, depth 12, stated ready, floor ready; example folded into spec:consumers.obsidian-vault.bases
  • spec:consumers.obsidian-vault.iteration: A design pass is followed and answered from the vault, depth 11, stated ready, floor ready
  • spec:consumers.obsidian-vault.iteration.watch-rewrites-changed-notes: A carrier edit under watch rewrites only the notes it changes, depth 12, stated ready, floor ready; example folded into spec:consumers.obsidian-vault.iteration
  • spec:consumers.obsidian-vault.iteration.watch-source-anchor: An anchor added in a source file under watch rewrites the Spec's note, depth 12, stated ready, floor ready; example folded into spec:consumers.obsidian-vault.iteration
  • spec:consumers.vault-on-ramp: The vault skill teaches agents to keep an Obsidian vault of the graph, depth 12, stated ready, floor ready
  • spec:consumers.readiness-planner: The readiness planner orders the statements a person can make, depth 14, stated ready, floor ready
  • spec:consumers.readiness-planner.dependency-order: The Spec another rests on comes first in the queue, depth 15, stated ready, floor ready; example folded into spec:consumers.readiness-planner
  • spec:consumers.readiness-planner.decision-first: A waiting decision comes before the Spec it shapes, depth 15, stated ready, floor ready; example folded into spec:consumers.readiness-planner
  • spec:consumers.readiness-planner.cycle-shares-a-round: Waiting Specs that rest on each other share a round and report a cycle, depth 15, stated ready, floor ready; example folded into spec:consumers.readiness-planner
  • spec:consumers.readiness-planner.owner-question-holds: An owner's blocking question lists the Specs it holds, depth 15, stated ready, floor ready; example folded into spec:consumers.readiness-planner
  • spec:consumers.upgrade-kit: The upgrade kit shows a corpus what it could adopt, depth 16, stated ready, floor ready
  • spec:consumers.upgrade-kit.capability-adoption: Capability adoption counts where each capability is used and where it could apply, depth 17, stated ready, floor ready
  • spec:consumers.upgrade-kit.capability-adoption.counts-a-corpus: Capability adoption counts keyed rules and reasoned relations, depth 18, stated ready, floor ready; example folded into spec:consumers.upgrade-kit.capability-adoption
  • spec:consumers.upgrade-kit.rule-key-proposal: The rule-key proposal keys every unkeyed rule as a change proposal, depth 17, stated ready, floor ready
  • spec:consumers.upgrade-kit.rule-key-proposal.proposal-applies-clean: A rule-key proposal passes the proposal check and validates once applied, depth 18, stated ready, floor ready; example folded into spec:consumers.upgrade-kit.rule-key-proposal
  • spec:consumers.upgrade-kit.rule-key-proposal.collision-and-unkeyable: Two rules that coin one key stay apart, and a rule with no ASCII word stays unkeyed, depth 18, stated ready, floor ready; example folded into spec:consumers.upgrade-kit.rule-key-proposal
  • spec:consumers.command-line: Every verb answers --help, and one verb writes every projection root, depth 12, stated ready, floor ready
  • spec:consumers.command-line.generate-check-failure: A root that fails its check is removed while sdp generate writes the others, depth 13, stated ready, floor ready; example folded into spec:consumers.command-line
  • spec:consumers.command-line.generate-writes-every-root: One run of sdp generate leaves all five roots current, depth 13, stated ready, floor ready; example folded into spec:consumers.command-line
  • spec:consumers.command-line.verb-help-touches-nothing: A publisher's --help prints its help and touches no root, depth 13, stated ready, floor ready; example folded into spec:consumers.command-line
  • spec:consumers.capability-map: The capability map reads every epic and its refinement descendants, depth 5, stated ready, floor ready
  • spec:consumers.spec-studio.capability-map-page: The capability map page makes refinement readable by epic, depth 17, stated ready, floor ready
  • spec:consumers.spec-studio.diagram-kinds: The Studio chooses diagram kinds from graph values, depth 14, stated ready, floor ready
  • spec:consumers.spec-studio.diagram-kinds.legibility: A diagram preserves readable labels before zoom, depth 15, stated ready, floor ready
  • spec:consumers.spec-studio.diagram-kinds.edge-routing: Edges route around boxes with deterministic orthogonal paths, depth 15, stated ready, floor ready
  • spec:consumers.spec-studio.diagram-kinds.mermaid-source: A diagram offers Mermaid source as copyable text, depth 18, stated ready, floor ready
  • spec:consumers.spec-studio.diagram-kinds.dependency: A dependency drawing shows the declared footing of a Spec set, depth 16, stated ready, floor ready
  • spec:consumers.spec-studio.diagram-kinds.capability-tree: A refinement drawing follows the capability map, depth 15, stated ready, floor ready
  • spec:consumers.spec-studio.diagram-kinds.scoped-architecture: A Spec set draws the architecture it touches, depth 16, stated ready, floor ready
  • spec:consumers.spec-studio.diagram-kinds.maturity-picture: The maturity map is drawn as a grid of counts, depth 15, stated ready, floor ready
  • spec:consumers.spec-studio.diagram-kinds.requirement-trace: A requirement drawing separates intent from realization and verification, depth 15, stated ready, floor ready
  • spec:consumers.design-slice: A slice reads a Pack as one design, with the architecture it touches and what each member needs next, depth 15, stated ready, floor ready
  • spec:consumers.design-slice.outside-components: Outside components stop at the touched components' neighbors, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.chain: Members rest on a chain, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.decision-backlink: A shaping decision comes before its member, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.dependency-cycle: A cycle shares a depth, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.folded-example: An example folds without lending its readiness, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.independent-example: An example with its own dependency stays unfolded, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.component-absent: An unanchored component design stays visible, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.component-unrelated: An anchor alone does not realize a component design, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.component-matching: A realized component matches its declared values, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.component-differing: A realized component keeps its differing layer and uses apart, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.component-unreadable: An unreadable declared layer stays visible, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.outside-satisfied: A prerequisite reaches its satisfying component, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.outside-unbound: An unbound prerequisite invents no component, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.design-slice.outside-holding: An outside prerequisite names the member it holds, depth 16, stated ready, floor ready; example folded into spec:consumers.design-slice
  • spec:consumers.spec-studio.slice-page: A slice page shows a Pack's design as one whole, depth 17, stated ready, floor ready
  • spec:consumers.roadmap: A roadmap orders the next bodies of work, and the graph says what each still needs, depth 15, stated ready, floor ready
  • spec:consumers.roadmap.built-work: Built work stays on the roadmap, depth 16, stated ready, floor ready; example folded into spec:consumers.roadmap
  • spec:consumers.roadmap.buildable-part: A ready unbound part needs building, depth 16, stated ready, floor ready; example folded into spec:consumers.roadmap
  • spec:consumers.roadmap.statement-part: A complete part waits for a statement, depth 16, stated ready, floor ready; example folded into spec:consumers.roadmap
  • spec:consumers.roadmap.design-part: An unfinished part needs design, depth 16, stated ready, floor ready; example folded into spec:consumers.roadmap
  • spec:consumers.roadmap.drifting-part: A binding below ready remains drift, depth 16, stated ready, floor ready; example folded into spec:consumers.roadmap
  • spec:consumers.roadmap.missing-evidence: A descendant without evidence names its holding clause, depth 16, stated ready, floor ready; example folded into spec:consumers.roadmap
  • spec:consumers.roadmap.blocking-part: A descendant question holds the entry for design, depth 16, stated ready, floor ready; example folded into spec:consumers.roadmap
  • spec:consumers.roadmap.outside-parent: A descendant names its outside parent, depth 16, stated ready, floor ready; example folded into spec:consumers.roadmap
  • spec:consumers.roadmap.statement-order: Waiting statements keep dependency order against roadmap places, depth 16, stated ready, floor ready; example folded into spec:consumers.roadmap
  • spec:consumers.spec-studio.roadmap-page: The roadmap page shows the upcoming work in priority order, split by what it needs, depth 17, stated ready, floor ready
  • spec:consumers.roadmap.memo: A roadmap renders as the forward section of a pull request description, depth 16, stated ready, floor ready
  • spec:consumers.spec-studio.cited-line-text: A pinned declaration shows the words of each test line that cites it, depth 17, stated scoped, floor scoped
  • spec:consumers.spec-studio.register-input: An outside register is a named Studio input, so a cited token links to its entry, depth 13, stated scoped, floor scoped
  • spec:observation.runtime-overlay: Runtime observations can close the liveness loop, depth 6, stated idea, floor idea
  • spec:observation.run-evidence: CI run records are joined to verifiers in a view, depth 5, stated ready, floor ready
  • spec:observation.run-evidence.absolute-path-joins: A test whose reporter wrote an absolute path joins its anchored file, depth 6, stated ready, floor ready; example folded into spec:observation.run-evidence
  • spec:observation.run-evidence.unanchored-file-unjoined: A test in a file with no test anchor is reported as unjoined, depth 6, stated ready, floor ready; example folded into spec:observation.run-evidence
  • spec:protocol.self-hosting: The Protocol authors and validates itself, depth 7, stated ready, floor ready
  • spec:protocol.structural-self-binding: The engine's structural self-binding covers its architecturally significant units, depth 8, stated ready, floor ready
  • spec:protocol.significant-units-review: The engine's accepted set covers its significant abstractions and only those, depth 10, stated ready, floor ready
  • spec:protocol.role-vocabulary: The engine's architectural roles each name one pattern, depth 9, stated ready, floor ready
  • spec:protocol.capability-epics: The Protocol organizes its own features in capability epics, depth 8, stated ready, floor ready
  • spec:protocol.roadmap-replaces-plans: The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests, depth 17, stated ready, floor ready
  • spec:protocol.delivery-record-cleanup: The Protocol removes its frozen plans, review reports and superseded concept material, depth 18, stated idea, floor idea
  • spec:decisions.plain-language-references: Durable references lead with meaning, depth 1, stated ready, floor ready
  • spec:decisions.concept-docs-dissolve: Concept documents may dissolve after executable truth lands, depth 1, stated ready, floor ready
  • spec:decisions.one-validation-path: Validation follows one graph, depth 1, stated ready, floor ready
  • spec:decisions.sdp-ts-extension: Spec extensions identify the carrier without colliding with tests, depth 1, stated ready, floor ready
  • spec:decisions.point-per-example: Each example binds one point, depth 1, stated ready, floor ready
  • spec:decisions.carrier-ruling: Markdown is the default Spec carrier, depth 1, stated ready, floor ready
  • spec:decisions.prose-ownership: Prose belongs to typed graph owners, depth 1, stated ready, floor ready
  • spec:decisions.envelope-grammar-posture: The Protocol owns the envelope grammar, depth 1, stated ready, floor ready
  • spec:decisions.exclusion-contract: Consumer exclusions stay exact, depth 1, stated ready, floor ready
  • spec:decisions.executable-meta-model: The Protocol is an executable meta-model, depth 1, stated ready, floor ready
  • spec:decisions.adopt-the-nouns: Delivery nouns remain familiar without workflow gates, depth 1, stated ready, floor ready
  • spec:decisions.one-primitive: One Spec carries named delivery coordinates, depth 1, stated ready, floor ready
  • spec:decisions.protocol-naming: The meta-model is a software delivery protocol, depth 1, stated ready, floor ready
  • spec:decisions.binding-not-liveness: Bindings state existence, not liveness, depth 1, stated ready, floor ready
  • spec:decisions.content-only-sections: Sections carry content while relations carry links, depth 1, stated ready, floor ready
  • spec:decisions.typing-law: Floor-read sections are closed typed shapes, depth 1, stated ready, floor ready
  • spec:decisions.kind-conditional-floor: Readiness evidence follows the Spec kind, depth 1, stated ready, floor ready
  • spec:decisions.carried-evidence: Promoted evidence must carry its own evidence, depth 2, stated ready, floor ready
  • spec:decisions.pack-reified: Packs group review context without becoming truth, depth 1, stated ready, floor ready
  • spec:decisions.agent-surface-scripts-graph: Agents script the visible graph, depth 1, stated ready, floor ready
  • spec:decisions.mcp-deferred: MCP integration remains deferred, depth 1, stated ready, floor ready
  • spec:decisions.agent-front-door: The agent front door is one evaluation sink over the exported reader, depth 2, stated ready, floor ready
  • spec:decisions.verification-posture-not-realization: Verification mode states posture, not realization, depth 2, stated ready, floor ready
  • spec:decisions.example-realization-posture: Example realization stays evidence, not backlog work, depth 2, stated ready, floor ready
  • spec:decisions.pack-markdown-carrier: Packs have a Markdown manifest carrier, depth 2, stated ready, floor ready
  • spec:decisions.decision-readiness-posture: Decision records state readiness from ratification evidence, depth 2, stated ready, floor ready
  • spec:decisions.gherkin-carrier-option: Behavior and example Specs may use Gherkin canonically, depth 2, stated ready, floor ready
  • spec:decisions.sdp-gherkin-extension: Canonical Gherkin carriers use .sdp.gherkin, depth 3, stated ready, floor ready
  • spec:decisions.carrier-universality: Carrier universality is bounded by honest kind structure, depth 3, stated ready, floor ready
  • spec:decisions.adopted-registrars-committed: Adopted runnable registrars are committed, depth 1, stated ready, floor ready
  • spec:decisions.shipped-projections-frozen: The shipped projections stay frozen, depth 1, stated ready, floor ready
  • spec:decisions.planning-truths-placement: Planning truths live in ruled graph homes, depth 1, stated ready, floor ready
  • spec:decisions.checked-mentions: A Spec id written in prose is a checked mention, depth 2, stated ready, floor ready
  • spec:decisions.authored-entry-order: The Design Review renders open-section entries as a list, depth 7, stated ready, floor ready
  • spec:decisions.question-key-rendering: The Design Review shows an open question's key, depth 7, stated ready, floor ready
  • spec:decisions.studio-html-surface: The Studio renders HTML, and the HTML stays derived, depth 3, stated ready, floor ready
  • spec:decisions.studio-web-components: The Studio is built from custom elements, not a framework, depth 1, stated ready, floor ready
  • spec:decisions.studio-build-renders: The build renders every Studio view, and an element only enhances it, depth 2, stated ready, floor ready
  • spec:decisions.studio-diagram-renderer: The engine lays out every Studio diagram as static SVG when the page set is built, depth 2, stated ready, floor ready
  • spec:decisions.anchor-comment-form: The comment form is a second anchor representation, depth 2, stated ready, floor ready
  • spec:decisions.anchor-binding-grain: Bindings are optional, plural, and may reference a design, depth 2, stated ready, floor ready
  • spec:decisions.architectural-annotation: Architectural significance is annotated where it is realized, depth 3, stated ready, floor ready
  • spec:decisions.pack-design-page: The Design Review's Pack page presents the Pack's design, depth 10, stated ready, floor ready
  • spec:decisions.vault-owned-folder: The vault's generator owns one folder and synchronizes it, depth 1, stated ready, floor ready
  • spec:decisions.roadmap-priority: A roadmap states advisory priority in the graph, depth 3, stated ready, floor ready
  • spec:decisions.roadmap-over-plans: Plan and review files stop carrying the delivery record once the roadmap and the pull request do, depth 4, stated ready, floor ready
  • spec:decisions.epics-of-any-kind: Capability epics keep kind independent of altitude, depth 2, stated ready, floor ready
  • spec:carrier.envelope-contract constrainedBy spec:validation.authored-honesty · declared
  • spec:carrier.envelope-contract decidedBy spec:decisions.envelope-grammar-posture · declared
  • spec:carrier.envelope-contract dependsOn spec:model.relation-reasons · declared
  • spec:carrier.envelope-contract dependsOn spec:model.rule-keys · declared
  • spec:carrier.envelope-contract refines spec:carrier.markdown-authoring · declared
  • spec:carrier.gherkin-authoring decidedBy spec:decisions.carrier-universality · declared
  • spec:carrier.gherkin-authoring decidedBy spec:decisions.gherkin-carrier-option · declared
  • spec:carrier.gherkin-authoring decidedBy spec:decisions.pack-markdown-carrier · declared
  • spec:carrier.gherkin-authoring decidedBy spec:decisions.prose-ownership · declared
  • spec:carrier.gherkin-authoring decidedBy spec:decisions.sdp-gherkin-extension · declared
  • spec:carrier.gherkin-authoring dependsOn spec:carrier.slot-notation · declared
  • spec:carrier.gherkin-authoring dependsOn spec:carrier.step-keys · declared — a step may open with a step key marker
  • spec:carrier.gherkin-authoring dependsOn spec:model.rule-keys · declared
  • spec:carrier.gherkin-authoring refines spec:carrier.markdown-authoring · declared
  • spec:carrier.gherkin-authoring.authored-fact-refused refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.contract-parity refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.description-location-refused refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.duplicate-surface-refused refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.example-space-extraction refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.malformed-relation-refused refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.missing-id-refused refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.multi-finding-bounded refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.parent-child-extraction refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.step-less-scenario-refused refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.unbound-ready-refused refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.unknown-tag-refused refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.gherkin-authoring.unsupported-construct-refused refines spec:carrier.gherkin-authoring · declared
  • spec:carrier.inline-code-spans refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.inline-code-spans.description refines spec:carrier.inline-code-spans · declared
  • spec:carrier.inline-code-spans.list refines spec:carrier.inline-code-spans · declared
  • spec:carrier.inline-code-spans.narrative refines spec:carrier.inline-code-spans · declared
  • spec:carrier.inline-code-spans.pack refines spec:carrier.inline-code-spans · declared
  • spec:carrier.markdown-authoring decidedBy spec:decisions.carrier-ruling · declared
  • spec:carrier.markdown-authoring decidedBy spec:decisions.sdp-ts-extension · declared
  • spec:carrier.markdown-authoring dependsOn spec:carrier.markdown-parser · declared
  • spec:carrier.markdown-body-grammar constrainedBy spec:validation.authored-honesty · declared
  • spec:carrier.markdown-body-grammar decidedBy spec:decisions.carrier-ruling · declared
  • spec:carrier.markdown-body-grammar decidedBy spec:decisions.prose-ownership · declared
  • spec:carrier.markdown-body-grammar dependsOn spec:carrier.slot-notation · declared
  • spec:carrier.markdown-body-grammar dependsOn spec:carrier.step-keys · declared — a fence step may open with a step key marker
  • spec:carrier.markdown-body-grammar dependsOn spec:model.open-question-fields · declared
  • spec:carrier.markdown-body-grammar dependsOn spec:model.rule-keys · declared
  • spec:carrier.markdown-body-grammar dependsOn spec:model.spec-sections · declared
  • spec:carrier.markdown-body-grammar dependsOn spec:model.term-addresses · declared — a Model definition may open with a term key marker
  • spec:carrier.markdown-body-grammar dependsOn spec:validation.kind-evidence · declared — its evidence clauses read every constraint entry a Spec carries, whichever carrier wrote it
  • spec:carrier.markdown-body-grammar refines spec:carrier.markdown-authoring · declared
  • spec:carrier.markdown-body-grammar.continuation-line-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.foreign-fence-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.h3-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.integer-term-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.keyed-bullet-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.ordered-list-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.plain-bullet-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.raw-html-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.repeated-field-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.second-primary-owner-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.shared-description-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.table-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.trailing-prose-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-body-grammar.unrecognized-heading-refused refines spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-pack-authoring decidedBy spec:decisions.pack-markdown-carrier · declared
  • spec:carrier.markdown-pack-authoring decidedBy spec:decisions.roadmap-priority · declared
  • spec:carrier.markdown-pack-authoring dependsOn spec:carrier.markdown-parser · declared
  • spec:carrier.markdown-pack-authoring dependsOn spec:decisions.carrier-ruling · declared
  • spec:carrier.markdown-pack-authoring refines spec:model.pack-aggregate · declared
  • spec:carrier.markdown-pack-authoring.markdown-ts-parity refines spec:carrier.markdown-pack-authoring · declared
  • spec:carrier.markdown-pack-authoring.spec-envelope-refused refines spec:carrier.markdown-pack-authoring · declared
  • spec:carrier.markdown-parser constrainedBy spec:carrier.inline-code-spans · declared
  • spec:carrier.markdown-parser dependsOn spec:carrier.envelope-contract · declared
  • spec:carrier.markdown-parser dependsOn spec:carrier.markdown-body-grammar · declared
  • spec:carrier.markdown-parser refines spec:carrier.markdown-authoring · declared, orders nothing
  • spec:carrier.markdown-parser.bounded-parity refines spec:carrier.markdown-parser · declared
  • spec:carrier.prose-ownership-rule decidedBy spec:decisions.prose-ownership · declared
  • spec:carrier.prose-ownership-rule dependsOn spec:carrier.markdown-body-grammar · declared
  • spec:carrier.prose-ownership-rule dependsOn spec:model.open-question-fields · declared
  • spec:carrier.prose-ownership-rule dependsOn spec:model.relation-reasons · declared
  • spec:carrier.prose-ownership-rule refines spec:carrier.markdown-authoring · declared
  • spec:carrier.sdp-import decidedBy spec:decisions.carrier-ruling · declared
  • spec:carrier.sdp-import refines spec:carrier.markdown-authoring · declared
  • spec:carrier.sdp-import.feature-adapter refines spec:carrier.sdp-import · declared
  • spec:carrier.sdp-import.round-trip refines spec:carrier.sdp-import · declared
  • spec:carrier.slot-notation refines spec:carrier.markdown-authoring · declared
  • spec:carrier.slot-notation.one-literal-binding refines spec:carrier.slot-notation · declared
  • spec:carrier.slot-notation.refused-guess refines spec:carrier.slot-notation · declared
  • spec:carrier.slot-notation.typed-declaration refines spec:carrier.slot-notation · declared
  • spec:carrier.step-keys decidedBy spec:decisions.shipped-projections-frozen · declared — keys stay off the frozen projections, which read the step text unchanged
  • spec:carrier.step-keys refines spec:carrier.slot-notation · declared — a key joins the step text the notation reads, ahead of its slots
  • spec:carrier.step-keys.conflicting-example-key-withheld refines spec:carrier.step-keys · declared
  • spec:carrier.step-keys.gherkin-keyed-step-stays-bound refines spec:carrier.step-keys · declared
  • spec:carrier.step-keys.key-equal-to-a-skeleton-withheld refines spec:carrier.step-keys · declared
  • spec:carrier.step-keys.malformed-marker-refused refines spec:carrier.step-keys · declared
  • spec:carrier.step-keys.renamed-key-breaks refines spec:carrier.step-keys · declared
  • spec:carrier.step-keys.repeated-key-refused refines spec:carrier.step-keys · declared
  • spec:carrier.step-keys.reworded-keyed-step-stays-bound refines spec:carrier.step-keys · declared
  • spec:carrier.step-keys.reworded-unkeyed-step-breaks refines spec:carrier.step-keys · declared
  • spec:carrier.step-keys.two-keys-on-one-step-refused refines spec:carrier.step-keys · declared
  • spec:carrier.step-keys.typescript-keyed-step-imports-keyed refines spec:carrier.step-keys · declared
  • spec:consumers.adopter-on-ramp decidedBy spec:decisions.decision-readiness-posture · declared
  • spec:consumers.adopter-on-ramp decidedBy spec:decisions.planning-truths-placement · declared
  • spec:consumers.adopter-on-ramp dependsOn spec:carrier.markdown-body-grammar · declared
  • spec:consumers.adopter-on-ramp dependsOn spec:consumers.agent-surface.register-recipes · declared
  • spec:consumers.adopter-on-ramp dependsOn spec:consumers.shipped-protocol-corpus · declared — the help points the reader at the corpus the package ships
  • spec:consumers.adopter-on-ramp dependsOn spec:validation.typed-dependency-floor · declared
  • spec:consumers.adopter-on-ramp refines spec:consumers.authoring-on-ramp · declared
  • spec:consumers.agent-surface decidedBy spec:decisions.agent-front-door · declared
  • spec:consumers.agent-surface decidedBy spec:decisions.agent-surface-scripts-graph · declared
  • spec:consumers.agent-surface refines spec:consumers.projections-model · declared
  • spec:consumers.agent-surface.address-and-cycle-recipes dependsOn spec:consumers.agent-surface.recipe-parameters · declared — address resolution reads its addresses from params
  • spec:consumers.agent-surface.address-and-cycle-recipes dependsOn spec:decisions.checked-mentions · declared
  • spec:consumers.agent-surface.address-and-cycle-recipes dependsOn spec:model.rule-keys · declared — a rule address resolves through the Spec's rule keys
  • spec:consumers.agent-surface.address-and-cycle-recipes dependsOn spec:model.term-addresses · declared — a term address resolves through the Spec's term keys
  • spec:consumers.agent-surface.address-and-cycle-recipes refines spec:consumers.agent-surface.register-recipes · declared
  • spec:consumers.agent-surface.address-and-cycle-recipes.chain-reports-nothing refines spec:consumers.agent-surface.address-and-cycle-recipes · declared
  • spec:consumers.agent-surface.address-and-cycle-recipes.cycle-fails-a-rules-run refines spec:consumers.agent-surface.address-and-cycle-recipes · declared
  • spec:consumers.agent-surface.address-and-cycle-recipes.unresolved-address-fails-a-rules-run refines spec:consumers.agent-surface.address-and-cycle-recipes · declared
  • spec:consumers.agent-surface.answer-shapes dependsOn spec:consumers.agent-surface.design-recipes · declared
  • spec:consumers.agent-surface.answer-shapes dependsOn spec:consumers.agent-surface.evaluation-sink · declared — a caller runs a shipped body, and wraps it in its own body, through the evaluation sink
  • spec:consumers.agent-surface.answer-shapes refines spec:consumers.agent-surface · declared
  • spec:consumers.agent-surface.authoring-recipes refines spec:consumers.agent-surface · declared
  • spec:consumers.agent-surface.demand-map-entries refines spec:consumers.agent-surface · declared
  • spec:consumers.agent-surface.design-recipes dependsOn spec:consumers.agent-surface.recipe-parameters · declared
  • spec:consumers.agent-surface.design-recipes dependsOn spec:consumers.pack-design · declared
  • spec:consumers.agent-surface.design-recipes refines spec:consumers.agent-surface.register-recipes · declared
  • spec:consumers.agent-surface.evaluation-sink decidedBy spec:decisions.agent-front-door · declared
  • spec:consumers.agent-surface.evaluation-sink refines spec:consumers.agent-surface · declared
  • spec:consumers.agent-surface.evaluation-sink.exported-evaluator refines spec:consumers.agent-surface.evaluation-sink · declared
  • spec:consumers.agent-surface.evaluation-sink.recipe-call refines spec:consumers.agent-surface.evaluation-sink · declared
  • spec:consumers.agent-surface.evaluation-sink.unknown-recipe refines spec:consumers.agent-surface.evaluation-sink · declared
  • spec:consumers.agent-surface.example-space-coverage dependsOn spec:carrier.slot-notation · declared
  • spec:consumers.agent-surface.example-space-coverage dependsOn spec:extraction.executable-contracts · declared — its decoded slots and bound points reuse the space-contract interpretation
  • spec:consumers.agent-surface.example-space-coverage refines spec:consumers.agent-surface.design-recipes · declared
  • spec:consumers.agent-surface.example-space-coverage.number-not-enumerable refines spec:consumers.agent-surface.example-space-coverage · declared
  • spec:consumers.agent-surface.example-space-coverage.uncovered-literal refines spec:consumers.agent-surface.example-space-coverage · declared
  • spec:consumers.agent-surface.recipe-parameters decidedBy spec:decisions.agent-front-door · declared
  • spec:consumers.agent-surface.recipe-parameters refines spec:consumers.agent-surface · declared
  • spec:consumers.agent-surface.register-recipes dependsOn spec:extraction.entry-locations · declared — the key-family register gives each row the line the location table records
  • spec:consumers.agent-surface.register-recipes dependsOn spec:model.open-question-fields · declared — the open-question register lists each question's fields
  • spec:consumers.agent-surface.register-recipes dependsOn spec:model.relation-reasons · declared — the mention audit reads a caller's intended mentions with their reasons
  • spec:consumers.agent-surface.register-recipes dependsOn spec:model.rule-keys · declared — entry search and the mention audit read rule addresses
  • spec:consumers.agent-surface.register-recipes dependsOn spec:model.term-addresses · declared — entry search and the mention audit read term addresses
  • spec:consumers.agent-surface.register-recipes refines spec:consumers.agent-surface · declared
  • spec:consumers.agent-surface.scripted-context-body refines spec:consumers.agent-surface · declared
  • spec:consumers.authoring-on-ramp decidedBy spec:decisions.anchor-binding-grain · declared — the skill teaches optional and plural targets, references and the collective promise test under this ruling
  • spec:consumers.authoring-on-ramp decidedBy spec:decisions.anchor-comment-form · declared — the skill teaches both extracted anchor forms and their silent non-binding hazards under this ruling
  • spec:consumers.authoring-on-ramp decidedBy spec:decisions.architectural-annotation · declared
  • spec:consumers.authoring-on-ramp dependsOn spec:carrier.gherkin-authoring · declared
  • spec:consumers.authoring-on-ramp dependsOn spec:carrier.markdown-pack-authoring · declared
  • spec:consumers.authoring-on-ramp dependsOn spec:consumers.edit-model · declared — an author edits the canonical carrier as the edit model states, never through a derived view
  • spec:consumers.authoring-on-ramp dependsOn spec:model.open-question-fields · declared
  • spec:consumers.authoring-on-ramp dependsOn spec:model.open-question-keys · declared
  • spec:consumers.authoring-on-ramp dependsOn spec:model.relation-reasons · declared
  • spec:consumers.authoring-on-ramp dependsOn spec:model.rule-keys · declared
  • spec:consumers.binding-language-views decidedBy spec:decisions.binding-not-liveness · declared
  • spec:consumers.binding-language-views refines spec:consumers.design-review · declared
  • spec:consumers.binding-language-views.bound-spec-page refines spec:consumers.binding-language-views · declared
  • spec:consumers.binding-language-views.pack-member-table refines spec:consumers.binding-language-views · declared
  • spec:consumers.capability-map decidedBy spec:decisions.epics-of-any-kind · declared
  • spec:consumers.capability-map dependsOn spec:extraction.delivery-facts · declared — rollups count direct bindings without conferring facts on ancestors
  • spec:consumers.capability-map dependsOn spec:validation.readiness-floor · declared — each node reads the existing floor beside the author's statement
  • spec:consumers.capability-map refines spec:consumers.projections-model · declared — the capability map projects authored refinement without introducing a grouping
  • spec:consumers.census-page decidedBy spec:decisions.anchor-binding-grain · declared — the census renders the references edges ruled by this decision
  • spec:consumers.census-page decidedBy spec:decisions.architectural-annotation · declared — the census renders the structural edges and the role, layer and context attributes ruled by this decision
  • spec:consumers.census-page decidedBy spec:decisions.shipped-projections-frozen · declared
  • spec:consumers.census-page dependsOn spec:consumers.wholesale-view-rewrite · declared — the shared build invalidates the projection roots before this publisher renders
  • spec:consumers.census-page refines spec:consumers.projections-model · declared
  • spec:consumers.command-line decidedBy spec:decisions.shipped-projections-frozen · declared — the verb writes the frozen roots unchanged and adds no projection of its own
  • spec:consumers.command-line dependsOn spec:consumers.adopter-on-ramp · declared — a verb's help repeats the top-level help that names the shipped on-ramps
  • spec:consumers.command-line dependsOn spec:consumers.spec-studio.publisher · declared — the Studio's page set is one of the roots the verb writes
  • spec:consumers.command-line dependsOn spec:consumers.wholesale-view-rewrite · declared — each root the verb writes is written and invalidated as every view run's is
  • spec:consumers.command-line refines spec:consumers.projections-model · declared — one verb publishes every projection root from one graph
  • spec:consumers.command-line.generate-check-failure refines spec:consumers.command-line · declared
  • spec:consumers.command-line.generate-writes-every-root refines spec:consumers.command-line · declared
  • spec:consumers.command-line.verb-help-touches-nothing refines spec:consumers.command-line · declared
  • spec:consumers.context-bundle decidedBy spec:decisions.agent-front-door · declared
  • spec:consumers.context-bundle dependsOn spec:consumers.agent-surface.design-recipes · declared
  • spec:consumers.context-bundle refines spec:consumers.agent-surface · declared
  • spec:consumers.context-bundle.oversized-member-named refines spec:consumers.context-bundle · declared
  • spec:consumers.context-bundle.parts-cover-the-pack refines spec:consumers.context-bundle · declared
  • spec:consumers.delivery-session-on-ramp decidedBy spec:decisions.planning-truths-placement · declared
  • spec:consumers.delivery-session-on-ramp dependsOn spec:consumers.context-bundle · declared — the design loop composes each pass's reading material as a context bundle
  • spec:consumers.delivery-session-on-ramp dependsOn spec:consumers.design-diff · declared — the design loop starts from what changed since the last pass
  • spec:consumers.delivery-session-on-ramp dependsOn spec:consumers.intent-composition.proposal · declared — the design loop hands its findings back as a change proposal checked against its base
  • spec:consumers.delivery-session-on-ramp dependsOn spec:consumers.review-perspectives · declared — the design loop narrows a Pack to one perspective's members
  • spec:consumers.delivery-session-on-ramp dependsOn spec:model.enrichment-lifecycle · declared — the close guidance reads its distillation boundary for Design entries
  • spec:consumers.delivery-session-on-ramp refines spec:consumers.authoring-on-ramp · declared — a work shape routes an agent into one stretch of the authoring path, from capture to review
  • spec:consumers.derived-readiness-banner dependsOn spec:validation.readiness-floor · declared
  • spec:consumers.derived-readiness-banner refines spec:consumers.design-review · declared
  • spec:consumers.derived-readiness-banner.dishonest-divergence refines spec:consumers.derived-readiness-banner · declared
  • spec:consumers.derived-readiness-banner.honest-headroom refines spec:consumers.derived-readiness-banner · declared
  • spec:consumers.design-diff constrainedBy spec:extraction.determinism · declared — equal sources derive equal graphs, so a difference records a source change
  • spec:consumers.design-diff decidedBy spec:decisions.roadmap-priority · declared
  • spec:consumers.design-diff dependsOn spec:consumers.agent-surface.recipe-parameters · declared — the base graph is supplied as recipe-parameter data, including the KEY=@PATH file form
  • spec:consumers.design-diff refines spec:consumers.projections-model · declared
  • spec:consumers.design-review decidedBy spec:decisions.anchor-binding-grain · declared — a Spec page lists the units that reference it apart from the units that realize it
  • spec:consumers.design-review decidedBy spec:decisions.architectural-annotation · declared — binding rows show a unit's role and a component's layer and context
  • spec:consumers.design-review decidedBy spec:decisions.authored-entry-order · declared — open-section entries render as a list in authored order
  • spec:consumers.design-review decidedBy spec:decisions.question-key-rendering · declared — a keyed open question shows its key before its text
  • spec:consumers.design-review decidedBy spec:decisions.shipped-projections-frozen · declared
  • spec:consumers.design-review refines spec:consumers.projections-model · declared
  • spec:consumers.design-review.pack-design-page decidedBy spec:decisions.pack-design-page · declared
  • spec:consumers.design-review.pack-design-page dependsOn spec:consumers.binding-language-views · declared
  • spec:consumers.design-review.pack-design-page dependsOn spec:consumers.derived-readiness-banner · declared — the member table renders the stated rung and floor reached as this rule specifies
  • spec:consumers.design-review.pack-design-page dependsOn spec:consumers.pack-design · declared
  • spec:consumers.design-review.pack-design-page refines spec:consumers.design-review · declared
  • spec:consumers.design-review.pure-projection refines spec:consumers.design-review · declared
  • spec:consumers.design-slice decidedBy spec:decisions.anchor-binding-grain · declared — the code a design builds on is reached through the design's own relations, never through a reference from that code
  • spec:consumers.design-slice decidedBy spec:decisions.architectural-annotation · declared — a touched component carries the layer and context its anchor states
  • spec:consumers.design-slice dependsOn spec:consumers.agent-surface.design-recipes · declared — decisions in scope read the decision register's rows
  • spec:consumers.design-slice dependsOn spec:consumers.context-bundle · declared — a slice takes its scope as the bundle does, and builds a Spec list's boundary the same way
  • spec:consumers.design-slice dependsOn spec:consumers.readiness-planner · declared — members rest on each other as the statement queue reads the four typed relations, and a cycle reports in its shape
  • spec:consumers.design-slice dependsOn spec:consumers.review-perspectives · declared — a slice read for one concern takes the members a perspective selects
  • spec:consumers.design-slice dependsOn spec:model.open-question-fields · declared — each question in scope carries its fields
  • spec:consumers.design-slice dependsOn spec:model.planned-architecture · declared — planned components and differing designs come from the realization comparison
  • spec:consumers.design-slice dependsOn spec:model.rule-keys · declared — each member's rule count is the count rule coverage reports
  • spec:consumers.design-slice refines spec:consumers.pack-design · declared — a slice reads a Pack's design as one whole, with its architecture and open decisions beside it
  • spec:consumers.design-slice.chain refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.component-absent refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.component-differing refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.component-matching refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.component-unreadable refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.component-unrelated refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.decision-backlink refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.dependency-cycle refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.folded-example refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.independent-example refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.outside-components refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.outside-holding refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.outside-satisfied refines spec:consumers.design-slice · declared
  • spec:consumers.design-slice.outside-unbound refines spec:consumers.design-slice · declared
  • spec:consumers.edit-model refines spec:consumers.projections-model · declared
  • spec:consumers.engine-provenance constrainedBy spec:extraction.determinism · declared
  • spec:consumers.engine-provenance dependsOn spec:consumers.adopter-on-ramp · declared — an adopter pinned to a build asks the CLI the adopter on-ramp points it to which build it runs
  • spec:consumers.engine-provenance refines spec:consumers.command-line · declared — the version flag is one more answer the command line gives an adopter
  • spec:consumers.gherkin-view decidedBy spec:decisions.carrier-universality · declared
  • spec:consumers.gherkin-view decidedBy spec:decisions.prose-ownership · declared — description prose stays on its typed graph owner
  • spec:consumers.gherkin-view decidedBy spec:decisions.shipped-projections-frozen · declared
  • spec:consumers.gherkin-view dependsOn spec:consumers.wholesale-view-rewrite · declared — the shared build invalidates the projection roots before this publisher renders
  • spec:consumers.gherkin-view refines spec:consumers.projections-model · declared
  • spec:consumers.graph-first-planning decidedBy spec:decisions.planning-truths-placement · declared
  • spec:consumers.graph-first-planning dependsOn spec:consumers.delivery-session-on-ramp · declared — per-session routing remains owned by the delivery-session on-ramp
  • spec:consumers.graph-first-planning dependsOn spec:model.open-question-fields · declared — the placement rule uses the question's explicit re-entry trigger field
  • spec:consumers.graph-first-planning refines spec:consumers.authoring-on-ramp · declared — the planning rules specialize graph-first authoring for capturing and reading the next body of work
  • spec:consumers.impact-graph dependsOn spec:extraction.derive-graph · declared
  • spec:consumers.impact-graph refines spec:consumers.projections-model · declared
  • spec:consumers.impact-graph.curation-assist decidedBy spec:decisions.architectural-annotation · declared
  • spec:consumers.impact-graph.curation-assist dependsOn spec:model.planned-architecture · declared — the report uses the component-design convention to identify unrealized planned components
  • spec:consumers.impact-graph.curation-assist refines spec:consumers.impact-graph · declared
  • spec:consumers.impact-graph.symbol-reach decidedBy spec:decisions.planning-truths-placement · declared — that decision homes a deferral as a blocking open question on its own Spec, as symbol identity is here
  • spec:consumers.impact-graph.symbol-reach refines spec:consumers.impact-graph · declared
  • spec:consumers.intent-composition refines spec:consumers.edit-model · declared
  • spec:consumers.intent-composition.proposal dependsOn spec:consumers.agent-surface.address-and-cycle-recipes · declared — the check resolves entry-address scopes through address resolution
  • spec:consumers.intent-composition.proposal dependsOn spec:consumers.design-diff · declared
  • spec:consumers.intent-composition.proposal dependsOn spec:consumers.edit-model · declared
  • spec:consumers.intent-composition.proposal refines spec:consumers.intent-composition · declared
  • spec:consumers.intent-composition.proposal.memo refines spec:consumers.intent-composition.proposal · declared
  • spec:consumers.intent-composition.proposal.memo.shared refines spec:consumers.intent-composition.proposal.memo · declared
  • spec:consumers.mermaid-view decidedBy spec:decisions.shipped-projections-frozen · declared
  • spec:consumers.mermaid-view dependsOn spec:consumers.wholesale-view-rewrite · declared — the shared build invalidates the projection roots before this publisher renders
  • spec:consumers.mermaid-view refines spec:consumers.projections-model · declared
  • spec:consumers.obsidian-vault constrainedBy spec:extraction.determinism · declared
  • spec:consumers.obsidian-vault decidedBy spec:decisions.shipped-projections-frozen · declared — the vault is a new root, since the four shipped projections stay frozen
  • spec:consumers.obsidian-vault decidedBy spec:decisions.vault-owned-folder · declared — the generator owns one folder of the vault and synchronizes it instead of rewriting a root
  • spec:consumers.obsidian-vault dependsOn spec:consumers.reader · declared — the generator reads the graph through the reader's joined values
  • spec:consumers.obsidian-vault dependsOn spec:consumers.wholesale-view-rewrite · declared — the shared build's invalidation removes the five projection roots and never the vault
  • spec:consumers.obsidian-vault refines spec:consumers.projections-model · declared — a projection for a person who iterates on designs in a notes app
  • spec:consumers.obsidian-vault.bases dependsOn spec:consumers.pack-design · declared — a Pack's Base shows the members, rungs and design columns the Pack design assembles
  • spec:consumers.obsidian-vault.bases refines spec:consumers.obsidian-vault · declared
  • spec:consumers.obsidian-vault.bases.views-match-sources refines spec:consumers.obsidian-vault.bases · declared
  • spec:consumers.obsidian-vault.changed-note-refused refines spec:consumers.obsidian-vault · declared
  • spec:consumers.obsidian-vault.failed-extraction-keeps-notes refines spec:consumers.obsidian-vault · declared
  • spec:consumers.obsidian-vault.failed-extraction-recovered refines spec:consumers.obsidian-vault · declared
  • spec:consumers.obsidian-vault.fresh-vault refines spec:consumers.obsidian-vault · declared
  • spec:consumers.obsidian-vault.hidden-file-refused refines spec:consumers.obsidian-vault · declared
  • spec:consumers.obsidian-vault.interrupted-run-recovered refines spec:consumers.obsidian-vault · declared
  • spec:consumers.obsidian-vault.iteration dependsOn spec:consumers.edit-model · declared — the vault composes intent and never patches a carrier
  • spec:consumers.obsidian-vault.iteration dependsOn spec:consumers.intent-composition.proposal · declared — intent composed in the vault hands off on the one proposal contract
  • spec:consumers.obsidian-vault.iteration dependsOn spec:consumers.validate-watch · declared — the vault's watch runs the same loop over carriers and anchored source files
  • spec:consumers.obsidian-vault.iteration refines spec:consumers.obsidian-vault · declared
  • spec:consumers.obsidian-vault.iteration.watch-rewrites-changed-notes refines spec:consumers.obsidian-vault.iteration · declared
  • spec:consumers.obsidian-vault.iteration.watch-source-anchor refines spec:consumers.obsidian-vault.iteration · declared
  • spec:consumers.obsidian-vault.notes dependsOn spec:consumers.binding-language-views · declared — rendered binding labels must state existence rather than liveness
  • spec:consumers.obsidian-vault.notes dependsOn spec:model.term-addresses · declared — a term note exists for a Model term that carries a key and so an address
  • spec:consumers.obsidian-vault.notes dependsOn spec:validation.prose-mentions · declared — a mention can become a link because validation already refuses one that does not resolve
  • spec:consumers.obsidian-vault.notes refines spec:consumers.obsidian-vault · declared
  • spec:consumers.obsidian-vault.notes.case-collision-refused refines spec:consumers.obsidian-vault.notes · declared
  • spec:consumers.obsidian-vault.notes.entry-address-link refines spec:consumers.obsidian-vault.notes · declared
  • spec:consumers.obsidian-vault.notes.term-address-link refines spec:consumers.obsidian-vault.notes · declared
  • spec:consumers.obsidian-vault.notes.unresolved-mention-stays refines spec:consumers.obsidian-vault.notes · declared
  • spec:consumers.obsidian-vault.person-notes-survive refines spec:consumers.obsidian-vault · declared
  • spec:consumers.obsidian-vault.unknown-note-refused refines spec:consumers.obsidian-vault · declared
  • spec:consumers.obsidian-vault.vault-in-build-path-refused refines spec:consumers.obsidian-vault · declared
  • spec:consumers.pack-design decidedBy spec:decisions.architectural-annotation · declared — a code unit binding carries the role, layer and context its anchors state
  • spec:consumers.pack-design dependsOn spec:extraction.contract-declarations · declared
  • spec:consumers.pack-design dependsOn spec:extraction.entry-locations · declared
  • spec:consumers.pack-design dependsOn spec:extraction.pack-member-order · declared
  • spec:consumers.pack-design dependsOn spec:model.open-question-fields · declared — each listed open question carries its fields
  • spec:consumers.pack-design dependsOn spec:validation.next-rung-floor · declared
  • spec:consumers.pack-design refines spec:consumers.reader · declared
  • spec:consumers.projections-model decidedBy spec:decisions.mcp-deferred · declared — MCP integration waits for a concrete caller to establish its boundary and contract
  • spec:consumers.projections-model decidedBy spec:decisions.shipped-projections-frozen · declared
  • spec:consumers.projections-model.roadmap-views dependsOn spec:consumers.roadmap · declared — the roadmap view the owner asked for is the roadmap reading, its page and its memo
  • spec:consumers.projections-model.roadmap-views refines spec:consumers.projections-model · declared
  • spec:consumers.reader decidedBy spec:decisions.agent-front-door · declared
  • spec:consumers.reader decidedBy spec:decisions.agent-surface-scripts-graph · declared
  • spec:consumers.reader decidedBy spec:decisions.anchor-binding-grain · declared
  • spec:consumers.reader decidedBy spec:decisions.decision-readiness-posture · declared
  • spec:consumers.reader dependsOn spec:extraction.delivery-facts · declared
  • spec:consumers.reader refines spec:consumers.agent-surface · declared
  • spec:consumers.reader.changeset-entry refines spec:consumers.reader · declared
  • spec:consumers.reader.concept-entry refines spec:consumers.reader · declared
  • spec:consumers.reader.file-entry refines spec:consumers.reader · declared
  • spec:consumers.readiness-planner dependsOn spec:consumers.agent-surface.address-and-cycle-recipes · declared — a cycle among waiting Specs reports in the shape dependency cycles reports
  • spec:consumers.readiness-planner dependsOn spec:model.open-question-fields · declared — the owner's questions are selected by their decider field
  • spec:consumers.readiness-planner dependsOn spec:validation.next-rung-floor · declared — the rung each Spec's floor allows, and the targets that hold a rung, come from the one floor evaluator
  • spec:consumers.readiness-planner dependsOn spec:validation.typed-dependency-floor · declared — the order reads the four typed relations the ready floor reads
  • spec:consumers.readiness-planner refines spec:consumers.graph-first-planning · declared — the planner is an advisory planning recipe that orders nothing the Protocol enforces
  • spec:consumers.readiness-planner.cycle-shares-a-round refines spec:consumers.readiness-planner · declared
  • spec:consumers.readiness-planner.decision-first refines spec:consumers.readiness-planner · declared
  • spec:consumers.readiness-planner.dependency-order refines spec:consumers.readiness-planner · declared
  • spec:consumers.readiness-planner.owner-question-holds refines spec:consumers.readiness-planner · declared
  • spec:consumers.reading-on-ramp decidedBy spec:decisions.agent-front-door · declared
  • spec:consumers.reading-on-ramp refines spec:consumers.agent-surface · declared
  • spec:consumers.reference-projection refines spec:consumers.projections-model · declared
  • spec:consumers.review-perspectives dependsOn spec:consumers.pack-design · declared
  • spec:consumers.review-perspectives refines spec:consumers.projections-model · declared
  • spec:consumers.roadmap decidedBy spec:decisions.roadmap-priority · declared
  • spec:consumers.roadmap dependsOn spec:consumers.readiness-planner · declared — the statements waiting on a person follow the statement queue's order
  • spec:consumers.roadmap dependsOn spec:model.open-question-fields · declared — the questions waiting on a person are selected by their decider field
  • spec:consumers.roadmap dependsOn spec:validation.next-rung-floor · declared — an entry's stated next rung and the clauses that hold it come from the one floor evaluator
  • spec:consumers.roadmap dependsOn spec:validation.typed-dependency-floor · declared — what an entry rests on is read through the relations the ready floor reads
  • spec:consumers.roadmap refines spec:consumers.graph-first-planning · declared — a roadmap is advisory reading of the graph for choosing the next work
  • spec:consumers.roadmap.blocking-part refines spec:consumers.roadmap · declared
  • spec:consumers.roadmap.buildable-part refines spec:consumers.roadmap · declared
  • spec:consumers.roadmap.built-work refines spec:consumers.roadmap · declared
  • spec:consumers.roadmap.design-part refines spec:consumers.roadmap · declared
  • spec:consumers.roadmap.drifting-part refines spec:consumers.roadmap · declared
  • spec:consumers.roadmap.memo dependsOn spec:consumers.agent-surface.register-recipes · declared — the deferred items come from the open-question register
  • spec:consumers.roadmap.memo dependsOn spec:consumers.intent-composition.proposal.memo · declared — the memo writes its code spans by the proposal memo's markup rules
  • spec:consumers.roadmap.memo refines spec:consumers.roadmap · declared
  • spec:consumers.roadmap.missing-evidence refines spec:consumers.roadmap · declared
  • spec:consumers.roadmap.outside-parent refines spec:consumers.roadmap · declared
  • spec:consumers.roadmap.statement-order refines spec:consumers.roadmap · declared
  • spec:consumers.roadmap.statement-part refines spec:consumers.roadmap · declared
  • spec:consumers.shipped-protocol-corpus dependsOn spec:extraction.excludes · declared — the shipped corpus stays out of an adopter's graph under its canonical discovery rules
  • spec:consumers.shipped-protocol-corpus refines spec:consumers.authoring-on-ramp · declared
  • spec:consumers.spec-studio constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio decidedBy spec:decisions.shipped-projections-frozen · declared
  • spec:consumers.spec-studio decidedBy spec:decisions.studio-build-renders · declared
  • spec:consumers.spec-studio decidedBy spec:decisions.studio-html-surface · declared
  • spec:consumers.spec-studio decidedBy spec:decisions.studio-web-components · declared
  • spec:consumers.spec-studio dependsOn spec:consumers.edit-model · declared — wanted changes leave the view as intent for an ordinary source edit
  • spec:consumers.spec-studio dependsOn spec:consumers.reader · declared
  • spec:consumers.spec-studio refines spec:consumers.projections-model · declared
  • spec:consumers.spec-studio.capability-map-page dependsOn spec:consumers.binding-language-views · declared — aggregate rows use the same binding labels as Spec pages
  • spec:consumers.spec-studio.capability-map-page dependsOn spec:consumers.capability-map · declared — the page and index filter render the capability map's answer
  • spec:consumers.spec-studio.capability-map-page dependsOn spec:consumers.spec-studio.diagram-kinds · declared — the refinement drawing shares the Studio's diagram layout and accessible text contract
  • spec:consumers.spec-studio.capability-map-page dependsOn spec:consumers.spec-studio.index-page · declared — the Epic filter extends the index's Specs filters
  • spec:consumers.spec-studio.capability-map-page refines spec:consumers.capability-map · declared — the page is the capability map's reading for a person
  • spec:consumers.spec-studio.capability-map-page refines spec:consumers.spec-studio.lenses · declared — the Capabilities page is a lens that reads refinement
  • spec:consumers.spec-studio.cited-line-text dependsOn spec:consumers.spec-studio.registers · declared — the declarations page lists each citing line beside its declaration
  • spec:consumers.spec-studio.cited-line-text dependsOn spec:extraction.entry-citations · declared — the words belong to a citation the graph already records by file and line
  • spec:consumers.spec-studio.cited-line-text refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.components decidedBy spec:decisions.studio-build-renders · declared
  • spec:consumers.spec-studio.components decidedBy spec:decisions.studio-diagram-renderer · declared
  • spec:consumers.spec-studio.components decidedBy spec:decisions.studio-web-components · declared
  • spec:consumers.spec-studio.components dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.components dependsOn spec:consumers.spec-studio.intent-panel · declared — the panel element renders the gathered intents that Spec designs
  • spec:consumers.spec-studio.components refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.data constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.data dependsOn spec:consumers.pack-design · declared
  • spec:consumers.spec-studio.data dependsOn spec:consumers.reader · declared
  • spec:consumers.spec-studio.data dependsOn spec:extraction.entry-locations · declared
  • spec:consumers.spec-studio.data dependsOn spec:extraction.pack-member-order · declared
  • spec:consumers.spec-studio.data dependsOn spec:validation.next-rung-floor · declared
  • spec:consumers.spec-studio.data refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.data.inputs constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.data.inputs dependsOn spec:consumers.design-diff · declared — the base graph input is the design diff's base
  • spec:consumers.spec-studio.data.inputs dependsOn spec:consumers.spec-studio.publisher · declared — each input is named by a flag of the studio verb
  • spec:consumers.spec-studio.data.inputs dependsOn spec:observation.run-evidence · declared — the run records input is read only as run evidence
  • spec:consumers.spec-studio.data.inputs refines spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.data.inputs.both-given refines spec:consumers.spec-studio.data.inputs · declared
  • spec:consumers.spec-studio.data.inputs.graph-only refines spec:consumers.spec-studio.data.inputs · declared
  • spec:consumers.spec-studio.data.recipe-answers dependsOn spec:consumers.agent-surface.evaluation-sink · declared — the build composes recipe answers through the same body evaluation `sdp q` runs
  • spec:consumers.spec-studio.data.recipe-answers refines spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.diagram-kinds decidedBy spec:decisions.studio-diagram-renderer · declared — every new kind is laid out by the engine at build time as the renderer decision rules
  • spec:consumers.spec-studio.diagram-kinds refines spec:consumers.spec-studio.diagrams · declared
  • spec:consumers.spec-studio.diagram-kinds.capability-tree dependsOn spec:consumers.capability-map · declared
  • spec:consumers.spec-studio.diagram-kinds.capability-tree refines spec:consumers.spec-studio.diagram-kinds · declared
  • spec:consumers.spec-studio.diagram-kinds.dependency dependsOn spec:consumers.design-slice · declared
  • spec:consumers.spec-studio.diagram-kinds.dependency refines spec:consumers.spec-studio.diagram-kinds · declared
  • spec:consumers.spec-studio.diagram-kinds.edge-routing refines spec:consumers.spec-studio.diagram-kinds · declared — arrows that cover no label serve the readable drawings the diagram kinds state
  • spec:consumers.spec-studio.diagram-kinds.edge-routing refines spec:consumers.spec-studio.diagrams · declared
  • spec:consumers.spec-studio.diagram-kinds.legibility dependsOn spec:consumers.spec-studio.responsive · declared
  • spec:consumers.spec-studio.diagram-kinds.legibility refines spec:consumers.spec-studio.diagram-kinds · declared — readable labels are part of the outcome the diagram kinds state
  • spec:consumers.spec-studio.diagram-kinds.legibility refines spec:consumers.spec-studio.diagrams · declared
  • spec:consumers.spec-studio.diagram-kinds.maturity-picture refines spec:consumers.spec-studio.diagram-kinds · declared
  • spec:consumers.spec-studio.diagram-kinds.mermaid-source decidedBy spec:decisions.shipped-projections-frozen · declared
  • spec:consumers.spec-studio.diagram-kinds.mermaid-source decidedBy spec:decisions.studio-diagram-renderer · declared
  • spec:consumers.spec-studio.diagram-kinds.mermaid-source dependsOn spec:consumers.spec-studio.page-elements · declared
  • spec:consumers.spec-studio.diagram-kinds.mermaid-source refines spec:consumers.spec-studio.diagram-kinds · declared
  • spec:consumers.spec-studio.diagram-kinds.requirement-trace dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.diagram-kinds.requirement-trace refines spec:consumers.spec-studio.diagram-kinds · declared
  • spec:consumers.spec-studio.diagram-kinds.scoped-architecture dependsOn spec:consumers.design-slice · declared
  • spec:consumers.spec-studio.diagram-kinds.scoped-architecture dependsOn spec:consumers.spec-studio.lenses.architecture · declared
  • spec:consumers.spec-studio.diagram-kinds.scoped-architecture dependsOn spec:model.planned-architecture · declared
  • spec:consumers.spec-studio.diagram-kinds.scoped-architecture refines spec:consumers.spec-studio.diagram-kinds · declared
  • spec:consumers.spec-studio.diagrams constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.diagrams decidedBy spec:decisions.studio-diagram-renderer · declared
  • spec:consumers.spec-studio.diagrams dependsOn spec:consumers.spec-studio.data · declared — a diagram is laid out from the values and recipe answers its page renders
  • spec:consumers.spec-studio.diagrams dependsOn spec:decisions.architectural-annotation · declared — the architecture grid reads the layer and context a component anchor states
  • spec:consumers.spec-studio.diagrams refines spec:consumers.spec-studio.components · declared
  • spec:consumers.spec-studio.diagrams.folds-by-context refines spec:consumers.spec-studio.diagrams · declared
  • spec:consumers.spec-studio.diagrams.folds-by-layer refines spec:consumers.spec-studio.diagrams · declared
  • spec:consumers.spec-studio.diagrams.within-bound refines spec:consumers.spec-studio.diagrams · declared
  • spec:consumers.spec-studio.diff-page dependsOn spec:consumers.design-diff · declared — the page renders the design diff between the base graph and the graph built
  • spec:consumers.spec-studio.diff-page dependsOn spec:consumers.spec-studio.data.inputs · declared — the base graph reaches the page as the build's named base input
  • spec:consumers.spec-studio.diff-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.diff-page.changed-entry refines spec:consumers.spec-studio.diff-page · declared
  • spec:consumers.spec-studio.export constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.export dependsOn spec:consumers.spec-studio.pack-page · declared — an export opens with its Pack page's content
  • spec:consumers.spec-studio.export dependsOn spec:consumers.spec-studio.publisher · declared — the export files are part of the page set the publisher writes
  • spec:consumers.spec-studio.export dependsOn spec:consumers.spec-studio.spec-page · declared — an export holds each member's Spec page content
  • spec:consumers.spec-studio.export refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.export.self-contained refines spec:consumers.spec-studio.export · declared
  • spec:consumers.spec-studio.glossary-page dependsOn spec:carrier.markdown-body-grammar · declared — the page splits a Model entry into its term and definition as the body grammar reads it
  • spec:consumers.spec-studio.glossary-page dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.glossary-page dependsOn spec:model.term-addresses · declared — a keyed term's address links it to its definition
  • spec:consumers.spec-studio.glossary-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.glossary-page.same-word-twice refines spec:consumers.spec-studio.glossary-page · declared
  • spec:consumers.spec-studio.index-page dependsOn spec:consumers.binding-language-views · declared
  • spec:consumers.spec-studio.index-page dependsOn spec:consumers.derived-readiness-banner · declared
  • spec:consumers.spec-studio.index-page dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.index-page dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.index-page refines spec:consumers.spec-studio.lenses.packs · declared — the index is the Packs lens and where a person lands
  • spec:consumers.spec-studio.intent-panel dependsOn spec:consumers.edit-model · declared
  • spec:consumers.spec-studio.intent-panel dependsOn spec:consumers.intent-composition.proposal · declared — the panel hands off a change proposal
  • spec:consumers.spec-studio.intent-panel dependsOn spec:consumers.intent-composition.proposal.memo · declared — the panel writes the memo recipe 49 renders, byte for byte
  • spec:consumers.spec-studio.intent-panel dependsOn spec:model.open-question-keys · declared
  • spec:consumers.spec-studio.intent-panel refines spec:consumers.intent-composition · declared
  • spec:consumers.spec-studio.intent-panel.refresh-keeps-intents refines spec:consumers.spec-studio.intent-panel · declared
  • spec:consumers.spec-studio.lenses dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.lenses refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.lenses.architecture decidedBy spec:decisions.architectural-annotation · declared — the lens draws only what component anchors state, membership, uses, layer, context and role
  • spec:consumers.spec-studio.lenses.architecture dependsOn spec:consumers.spec-studio.diagrams · declared — the lens's drawings are the architecture grid and the member diagrams
  • spec:consumers.spec-studio.lenses.architecture dependsOn spec:model.planned-architecture · declared — planned components come from the component designs recipe 43 reads
  • spec:consumers.spec-studio.lenses.architecture refines spec:consumers.spec-studio.lenses · declared
  • spec:consumers.spec-studio.lenses.architecture.planned-apart refines spec:consumers.spec-studio.lenses.architecture · declared
  • spec:consumers.spec-studio.lenses.architecture.unit-register refines spec:consumers.spec-studio.lenses.architecture · declared
  • spec:consumers.spec-studio.lenses.evidence decidedBy spec:decisions.binding-not-liveness · declared
  • spec:consumers.spec-studio.lenses.evidence refines spec:consumers.spec-studio.lenses · declared
  • spec:consumers.spec-studio.lenses.packs dependsOn spec:extraction.pack-member-order · declared — the lens lists each Pack's members in the order its manifest gives
  • spec:consumers.spec-studio.lenses.packs refines spec:consumers.spec-studio.lenses · declared
  • spec:consumers.spec-studio.lenses.tests decidedBy spec:decisions.binding-not-liveness · declared
  • spec:consumers.spec-studio.lenses.tests decidedBy spec:decisions.verification-posture-not-realization · declared
  • spec:consumers.spec-studio.lenses.tests dependsOn spec:consumers.agent-surface.example-space-coverage · declared — a row reads its example space's uncovered values from recipe 44
  • spec:consumers.spec-studio.lenses.tests dependsOn spec:model.rule-keys · declared — rule coverage counts the keyed rules examples exercise
  • spec:consumers.spec-studio.lenses.tests dependsOn spec:observation.run-evidence · declared — with run records, a row adds the results recipe 45 joins from its verifiers' files
  • spec:consumers.spec-studio.lenses.tests refines spec:consumers.spec-studio.lenses · declared
  • spec:consumers.spec-studio.lenses.tests.coverage-row refines spec:consumers.spec-studio.lenses.tests · declared
  • spec:consumers.spec-studio.navigation dependsOn spec:consumers.spec-studio.index-page · declared — the routes extend the index's task list
  • spec:consumers.spec-studio.navigation dependsOn spec:consumers.spec-studio.lenses · declared — the lens entries keep the order the lenses take
  • spec:consumers.spec-studio.navigation dependsOn spec:consumers.spec-studio.shell · declared — the entries extend the shell's top navigation
  • spec:consumers.spec-studio.navigation refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.owner-queue dependsOn spec:consumers.readiness-planner · declared — the page renders the statement queue the planner orders
  • spec:consumers.spec-studio.owner-queue dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.owner-queue dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.owner-queue refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.owner-queue.dependency-first refines spec:consumers.spec-studio.owner-queue · declared
  • spec:consumers.spec-studio.pack-page dependsOn spec:consumers.binding-language-views · declared
  • spec:consumers.spec-studio.pack-page dependsOn spec:consumers.derived-readiness-banner · declared
  • spec:consumers.spec-studio.pack-page dependsOn spec:consumers.pack-design · declared — the page renders the Pack design the Pack context carries
  • spec:consumers.spec-studio.pack-page dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.pack-page dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.pack-page dependsOn spec:model.open-question-fields · declared
  • spec:consumers.spec-studio.pack-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.pack-page.maturity-map dependsOn spec:consumers.derived-readiness-banner · declared — the map sets each stated rung beside the floor reached, as the banner reads them
  • spec:consumers.spec-studio.pack-page.maturity-map dependsOn spec:consumers.spec-studio.diagram-kinds.maturity-picture · declared — the map is drawn as the picture defines
  • spec:consumers.spec-studio.pack-page.maturity-map refines spec:consumers.spec-studio.pack-page · declared
  • spec:consumers.spec-studio.page-elements decidedBy spec:decisions.studio-web-components · declared
  • spec:consumers.spec-studio.page-elements dependsOn spec:consumers.spec-studio.search · declared
  • spec:consumers.spec-studio.page-elements dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.page-elements refines spec:consumers.spec-studio.components · declared
  • spec:consumers.spec-studio.publisher constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.publisher decidedBy spec:decisions.shipped-projections-frozen · declared — the Studio publishes to a root of its own beside the four frozen ones
  • spec:consumers.spec-studio.publisher dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.publisher dependsOn spec:consumers.wholesale-view-rewrite · declared — the Studio's root is written, invalidated and certified the way the shipped roots are
  • spec:consumers.spec-studio.publisher refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.publisher.watch dependsOn spec:consumers.validate-watch · declared — the watch reruns on the carrier events validate's watch follows
  • spec:consumers.spec-studio.publisher.watch refines spec:consumers.spec-studio.publisher · declared
  • spec:consumers.spec-studio.publisher.watch.matches-plain-run refines spec:consumers.spec-studio.publisher.watch · declared
  • spec:consumers.spec-studio.register-input dependsOn spec:consumers.spec-studio.data.inputs · declared — the register joins the base graph and the run records as a named input
  • spec:consumers.spec-studio.register-input dependsOn spec:validation.external-registers · declared — the input is the register file and pattern the external-registers recipe already reads
  • spec:consumers.spec-studio.register-input refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.registers dependsOn spec:consumers.agent-surface.design-recipes · declared — the decisions page renders the decision register
  • spec:consumers.spec-studio.registers dependsOn spec:consumers.agent-surface.register-recipes · declared — the questions page renders the open-question register
  • spec:consumers.spec-studio.registers dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.registers dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.registers dependsOn spec:extraction.contract-declarations · declared — the declarations page lists the pinned declarations recipe 24 reads
  • spec:consumers.spec-studio.registers dependsOn spec:extraction.entry-citations · declared — each declaration shows the source lines that cite its address
  • spec:consumers.spec-studio.registers refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.registers.blocking-first refines spec:consumers.spec-studio.registers · declared
  • spec:consumers.spec-studio.responsive dependsOn spec:extraction.claim-taxonomy · declared
  • spec:consumers.spec-studio.responsive refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.roadmap-page dependsOn spec:consumers.roadmap · declared — the page renders the roadmap reading
  • spec:consumers.spec-studio.roadmap-page dependsOn spec:consumers.roadmap.memo · declared — the page carries the roadmap memo for a description's author to copy
  • spec:consumers.spec-studio.roadmap-page dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.roadmap-page dependsOn spec:consumers.spec-studio.publisher · declared — an entry's element id carries the name the page set gives its roadmap's Pack page
  • spec:consumers.spec-studio.roadmap-page dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.roadmap-page refines spec:consumers.roadmap · declared — the page is the roadmap's reading for a person
  • spec:consumers.spec-studio.roadmap-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.runs-page decidedBy spec:decisions.binding-not-liveness · declared
  • spec:consumers.spec-studio.runs-page dependsOn spec:consumers.spec-studio.data.inputs · declared — the run records reach the page as the build's named runs input
  • spec:consumers.spec-studio.runs-page dependsOn spec:observation.run-evidence · declared — the page renders the run evidence recipe 45 joins from the run records
  • spec:consumers.spec-studio.runs-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.runs-page.external-evidence refines spec:consumers.spec-studio.runs-page · declared
  • spec:consumers.spec-studio.search dependsOn spec:consumers.reader · declared — the page matches with the reader's concept matching
  • spec:consumers.spec-studio.search dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.search refines spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.sharing constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.sharing dependsOn spec:consumers.engine-provenance · declared
  • spec:consumers.spec-studio.sharing dependsOn spec:consumers.spec-studio.publisher · declared — the stamp and the preview take the page set the publisher wrote
  • spec:consumers.spec-studio.sharing dependsOn spec:extraction.schema-versioning · declared
  • spec:consumers.spec-studio.sharing refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.sharing.stamp-written-apart refines spec:consumers.spec-studio.sharing · declared
  • spec:consumers.spec-studio.shell dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.shell dependsOn spec:consumers.spec-studio.lenses · declared — the top navigation opens each lens
  • spec:consumers.spec-studio.shell dependsOn spec:consumers.spec-studio.responsive · declared — the rail moves below the canvas under the phone breakpoint
  • spec:consumers.spec-studio.shell dependsOn spec:consumers.spec-studio.sharing · declared — the shell shows the stamp a publishing step writes beside the page set
  • spec:consumers.spec-studio.shell dependsOn spec:validation.prose-mentions · declared — a mention links where the validator resolves it
  • spec:consumers.spec-studio.shell refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.slice-page dependsOn spec:consumers.binding-language-views · declared
  • spec:consumers.spec-studio.slice-page dependsOn spec:consumers.derived-readiness-banner · declared
  • spec:consumers.spec-studio.slice-page dependsOn spec:consumers.design-slice · declared — the page renders the slice's answer
  • spec:consumers.spec-studio.slice-page dependsOn spec:consumers.spec-studio.data.recipe-answers · declared — the build evaluates the slice recipe once for each Pack, and the page reads that answer
  • spec:consumers.spec-studio.slice-page dependsOn spec:consumers.spec-studio.diagram-kinds.dependency · declared — the dependency drawing given the slice's order is a drawing kind, which owns layout, folding and the text equivalent
  • spec:consumers.spec-studio.slice-page dependsOn spec:consumers.spec-studio.diagram-kinds.scoped-architecture · declared — the scoped architecture drawing is a drawing kind, which owns layout, folding and the text equivalent
  • spec:consumers.spec-studio.slice-page dependsOn spec:consumers.spec-studio.diagrams · declared — both drawings keep the diagram contract, bound and text equivalent included
  • spec:consumers.spec-studio.slice-page dependsOn spec:consumers.spec-studio.pack-page · declared — each member links to its card on the Pack page, whose element id is the member's id
  • spec:consumers.spec-studio.slice-page dependsOn spec:model.open-question-fields · declared
  • spec:consumers.spec-studio.slice-page refines spec:consumers.design-slice · declared — the page is the design slice's reading for a person
  • spec:consumers.spec-studio.slice-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.spec-page decidedBy spec:decisions.authored-entry-order · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.binding-language-views · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.derived-readiness-banner · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.pack-design · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.spec-studio.diagram-kinds.requirement-trace · declared — the Design view reads the selected set and claims the requirement drawing defines
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.spec-studio.diagrams · declared — the design view and impact panel draw requirement traceability and the one-hop trace graph
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.spec-studio.diff-page · declared — given a base graph, the header's change note links the Spec's row on the diff page
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.spec-studio.sharing · declared — a recorded file and line become a link only from a stamp's source template
  • spec:consumers.spec-studio.spec-page dependsOn spec:extraction.entry-citations · declared — the design section shows the source lines that cite each entry
  • spec:consumers.spec-studio.spec-page dependsOn spec:extraction.entry-locations · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:model.open-question-fields · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:model.open-question-keys · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:model.relation-reasons · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:model.rule-keys · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:model.term-addresses · declared — a keyed term's address names the element a glossary row links to
  • spec:consumers.spec-studio.spec-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.spec-page.cited-declaration refines spec:consumers.spec-studio.spec-page · declared
  • spec:consumers.spec-studio.spec-page.core decidedBy spec:decisions.authored-entry-order · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:consumers.binding-language-views · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:consumers.derived-readiness-banner · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:extraction.entry-locations · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:model.open-question-fields · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:model.relation-reasons · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:model.rule-keys · declared
  • spec:consumers.spec-studio.spec-page.core refines spec:consumers.spec-studio.spec-page · declared
  • spec:consumers.spec-studio.verification-panels decidedBy spec:decisions.binding-not-liveness · declared
  • spec:consumers.spec-studio.verification-panels decidedBy spec:decisions.verification-posture-not-realization · declared
  • spec:consumers.spec-studio.verification-panels dependsOn spec:consumers.agent-surface.example-space-coverage · declared — the grid renders recipe 44's per-slot coverage
  • spec:consumers.spec-studio.verification-panels dependsOn spec:consumers.spec-studio.intent-panel · declared — each panel action gathers intent in the composing panel
  • spec:consumers.spec-studio.verification-panels dependsOn spec:extraction.executable-contracts · declared
  • spec:consumers.spec-studio.verification-panels dependsOn spec:model.rule-keys · declared
  • spec:consumers.spec-studio.verification-panels dependsOn spec:observation.run-evidence · declared — with run records, a verifier's row adds the results recipe 45 joins from its test file
  • spec:consumers.spec-studio.verification-panels refines spec:consumers.spec-studio.spec-page · declared
  • spec:consumers.spec-studio.verification-panels.rule-coverage refines spec:consumers.spec-studio.verification-panels · declared
  • spec:consumers.structural-mermaid decidedBy spec:decisions.shipped-projections-frozen · declared
  • spec:consumers.structural-mermaid dependsOn spec:consumers.spec-studio.lenses.architecture · declared — the lens draws the component diagram rooted at code units this Spec asked for
  • spec:consumers.structural-mermaid refines spec:consumers.projections-model · declared
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.intent-composition · declared — a received proposal is checked and applied as the hand-off law states
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.spec-studio.data.inputs · declared — the skill teaches the base graph and run records and where they may lie
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.spec-studio.export · declared — the skill teaches the Pack export and what it leaves out
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.spec-studio.intent-panel · declared — the skill teaches what the composing panel hands off and what stays scoped-intent text
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.spec-studio.publisher · declared — the skill teaches the verb, its watch and what each shared build removes
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.spec-studio.sharing · declared — the skill teaches the stamp, its lifetime and the pull-request preview workflow
  • spec:consumers.studio-on-ramp refines spec: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 it
  • spec:consumers.upgrade-kit dependsOn spec:consumers.capability-map · declared — the guide teaches epic organization through the capability map
  • spec:consumers.upgrade-kit dependsOn spec:consumers.edit-model · declared — a carrier changes only through an agent's or a person's edit, recorded by git
  • spec:consumers.upgrade-kit dependsOn spec:consumers.intent-composition · declared — a proposed upgrade hands off on the one change-proposal shape and is applied after its check
  • spec:consumers.upgrade-kit dependsOn spec:consumers.roadmap · declared — the guide teaches advisory priority and the roadmap memo as planning records
  • spec:consumers.upgrade-kit refines spec:consumers.authoring-on-ramp · declared — the kit moves a whole corpus onto the capabilities the on-ramp teaches one Spec at a time
  • spec:consumers.upgrade-kit.capability-adoption dependsOn spec:carrier.step-keys · declared — step keys are counted where example steps are
  • spec:consumers.upgrade-kit.capability-adoption dependsOn spec:consumers.review-perspectives · declared — perspectives are counted from the objects the caller passes
  • spec:consumers.upgrade-kit.capability-adoption dependsOn spec:extraction.contract-declarations · declared — pinned declarations are counted where keyed Design entries are
  • spec:consumers.upgrade-kit.capability-adoption dependsOn spec:extraction.entry-citations · declared — a pinned declaration counts as cited when an anchored line cites it
  • spec:consumers.upgrade-kit.capability-adoption dependsOn spec:model.open-question-fields · declared — question keys and fields are counted where open questions are
  • spec:consumers.upgrade-kit.capability-adoption dependsOn spec:model.open-question-keys · declared — question keys are counted where open questions are
  • spec:consumers.upgrade-kit.capability-adoption dependsOn spec:model.planned-architecture · declared — component designs are selected by the convention that Spec states
  • spec:consumers.upgrade-kit.capability-adoption dependsOn spec:model.relation-reasons · declared — relation reasons are counted where authored relations are
  • spec:consumers.upgrade-kit.capability-adoption dependsOn spec:model.rule-keys · declared — rule keys and `exercises` are two of the capabilities it counts
  • spec:consumers.upgrade-kit.capability-adoption dependsOn spec:model.term-addresses · declared — term keys are counted where Model terms are
  • spec:consumers.upgrade-kit.capability-adoption refines spec:consumers.upgrade-kit · declared
  • spec:consumers.upgrade-kit.capability-adoption.counts-a-corpus refines spec:consumers.upgrade-kit.capability-adoption · declared
  • spec:consumers.upgrade-kit.rule-key-proposal dependsOn spec:consumers.intent-composition.proposal · declared — the recipe writes a change proposal in the shape the proposal check reads
  • spec:consumers.upgrade-kit.rule-key-proposal dependsOn spec:extraction.entry-locations · declared — each change names the file and line the location table records for its entry
  • spec:consumers.upgrade-kit.rule-key-proposal dependsOn spec:model.rule-keys · declared — a coined key follows the rule-key grammar and marker
  • spec:consumers.upgrade-kit.rule-key-proposal refines spec:consumers.upgrade-kit · declared
  • spec:consumers.upgrade-kit.rule-key-proposal.collision-and-unkeyable refines spec:consumers.upgrade-kit.rule-key-proposal · declared
  • spec:consumers.upgrade-kit.rule-key-proposal.proposal-applies-clean refines spec:consumers.upgrade-kit.rule-key-proposal · declared
  • spec:consumers.validate-watch dependsOn spec:decisions.one-validation-path · declared
  • spec:consumers.validate-watch dependsOn spec:extraction.excludes · declared
  • spec:consumers.validate-watch refines spec:consumers.authoring-on-ramp · declared
  • spec:consumers.vault-on-ramp decidedBy spec:decisions.vault-owned-folder · declared — the skill keeps a person's notes outside the one folder the command owns
  • spec:consumers.vault-on-ramp dependsOn spec:consumers.intent-composition · declared — intent written in the vault is applied through a checked change proposal
  • spec:consumers.vault-on-ramp dependsOn spec:consumers.obsidian-vault · declared — the skill teaches the verb, where the vault may lie and the guard's refusals
  • spec:consumers.vault-on-ramp dependsOn spec:consumers.obsidian-vault.iteration · declared — the skill teaches the watch and the intent notes a design pass is answered in
  • spec:consumers.vault-on-ramp dependsOn spec:consumers.obsidian-vault.notes · declared — the skill converts a note name or block id back to the id or entry address it names
  • spec:consumers.vault-on-ramp refines spec: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 edits
  • spec:consumers.wholesale-view-rewrite dependsOn spec:extraction.determinism · declared — check-clean refuses when two renders of one graph differ
  • spec:consumers.wholesale-view-rewrite refines spec:consumers.design-review · declared
  • spec:consumers.wholesale-view-rewrite.build-invalidates-view refines spec:consumers.wholesale-view-rewrite · declared
  • spec:consumers.wholesale-view-rewrite.failed-run-view-removed refines spec:consumers.wholesale-view-rewrite · declared
  • spec:consumers.wholesale-view-rewrite.late-stale-page refines spec:consumers.wholesale-view-rewrite · declared
  • spec:consumers.wholesale-view-rewrite.stale-page-removed refines spec:consumers.wholesale-view-rewrite · declared
  • spec:decisions.adopt-the-nouns refines spec:protocol.self-hosting · declared, orders nothing
  • spec:decisions.adopted-registrars-committed refines spec:extraction.runnable-modules · declared, orders nothing
  • spec:decisions.agent-front-door dependsOn spec:decisions.agent-surface-scripts-graph · declared
  • spec:decisions.agent-front-door refines spec:consumers.agent-surface · declared, orders nothing
  • spec:decisions.agent-surface-scripts-graph refines spec:consumers.agent-surface · declared, orders nothing
  • spec:decisions.anchor-binding-grain dependsOn spec:decisions.binding-not-liveness · declared
  • spec:decisions.anchor-binding-grain refines spec:decisions.shipped-projections-frozen · declared — carves out the Design Review's Referenced by list and the census References table
  • spec:decisions.anchor-binding-grain refines spec:model.anchors · declared, orders nothing
  • spec:decisions.anchor-comment-form dependsOn spec:decisions.one-validation-path · declared — both anchor forms feed the same extraction and graph-validation path
  • spec:decisions.anchor-comment-form refines spec:model.anchors · declared, orders nothing
  • spec:decisions.architectural-annotation dependsOn spec:decisions.anchor-binding-grain · declared
  • spec:decisions.architectural-annotation dependsOn spec:decisions.binding-not-liveness · declared
  • spec:decisions.architectural-annotation refines spec: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 rows
  • spec:decisions.architectural-annotation refines spec:model.anchors · declared, orders nothing
  • spec:decisions.authored-entry-order dependsOn spec:extraction.open-section-order · declared
  • spec:decisions.authored-entry-order refines spec:consumers.design-review · declared, orders nothing
  • spec:decisions.authored-entry-order refines spec:decisions.shipped-projections-frozen · declared — carves out how the Design Review renders open-section entries, as a list in authored order
  • spec:decisions.binding-not-liveness refines spec:model.anchors · declared, orders nothing
  • spec:decisions.carried-evidence dependsOn spec:decisions.content-only-sections · declared
  • spec:decisions.carried-evidence dependsOn spec:decisions.kind-conditional-floor · declared
  • spec:decisions.carried-evidence refines spec:validation.readiness-floor · declared, orders nothing
  • spec:decisions.carrier-ruling refines spec:carrier.markdown-authoring · declared, orders nothing
  • spec:decisions.carrier-universality dependsOn spec:decisions.pack-markdown-carrier · declared — leaves the Pack carrier to its separate syntax ruling
  • spec:decisions.carrier-universality dependsOn spec:decisions.prose-ownership · declared
  • spec:decisions.carrier-universality refines spec:decisions.gherkin-carrier-option · declared — settles the admitted description prose and the meaning of universality as a generated read projection, while reaffirming the behavior and example kind bound
  • spec:decisions.checked-mentions dependsOn spec:decisions.content-only-sections · declared
  • spec:decisions.checked-mentions refines spec:model.stable-ids · declared, orders nothing
  • spec:decisions.concept-docs-dissolve refines spec:protocol.self-hosting · declared, orders nothing
  • spec:decisions.content-only-sections refines spec:model.spec-sections · declared, orders nothing
  • spec:decisions.decision-readiness-posture dependsOn spec:decisions.kind-conditional-floor · declared — decision maturity uses decision content as natural evidence instead of implementation or verifier bindings
  • spec:decisions.decision-readiness-posture refines spec:validation.warn-level-signals · declared, orders nothing
  • spec:decisions.envelope-grammar-posture refines spec:carrier.envelope-contract · declared, orders nothing
  • spec:decisions.epics-of-any-kind dependsOn spec:decisions.one-primitive · declared — kind and altitude are independent named coordinates on the one primitive
  • spec:decisions.epics-of-any-kind refines spec:consumers.capability-map · declared, orders nothing — settles which Specs the capability map reads as epics
  • spec:decisions.example-realization-posture dependsOn spec:decisions.binding-not-liveness · declared
  • spec:decisions.example-realization-posture refines spec:model.core-model · declared, orders nothing
  • spec:decisions.exclusion-contract refines spec:extraction.excludes · declared, orders nothing
  • spec:decisions.executable-meta-model refines spec:protocol.self-hosting · declared, orders nothing
  • spec:decisions.gherkin-carrier-option refines spec:decisions.carrier-ruling · declared — admits Gherkin as a canonical per-ID carrier for behavior and example Specs beside the Markdown default
  • spec:decisions.kind-conditional-floor refines spec:validation.readiness-floor · declared, orders nothing
  • spec:decisions.mcp-deferred refines spec:consumers.projections-model · declared, orders nothing
  • spec:decisions.one-primitive refines spec:model.core-model · declared, orders nothing
  • spec:decisions.one-validation-path refines spec:validation.two-check-families · declared, orders nothing
  • spec:decisions.pack-design-page dependsOn spec:consumers.pack-design · declared
  • spec:decisions.pack-design-page refines spec:consumers.design-review.pack-design-page · declared, orders nothing
  • spec:decisions.pack-design-page refines spec:decisions.shipped-projections-frozen · declared — carves out the Pack page, which renders the Pack design
  • spec:decisions.pack-markdown-carrier refines spec:decisions.carrier-ruling · declared — extends the Markdown carrier to Packs and keeps the TypeScript builder as a per-ID option
  • spec:decisions.pack-reified refines spec:model.pack-aggregate · declared, orders nothing
  • spec:decisions.plain-language-references refines spec:protocol.self-hosting · declared, orders nothing
  • spec:decisions.planning-truths-placement refines spec:model.relations · declared, orders nothing
  • spec:decisions.point-per-example refines spec:model.spec-sections · declared, orders nothing
  • spec:decisions.prose-ownership refines spec:carrier.prose-ownership-rule · declared, orders nothing
  • spec:decisions.protocol-naming refines spec:protocol.self-hosting · declared, orders nothing
  • spec:decisions.question-key-rendering dependsOn spec:model.open-question-keys · declared
  • spec:decisions.question-key-rendering refines spec:consumers.design-review · declared, orders nothing
  • spec:decisions.question-key-rendering refines spec:decisions.shipped-projections-frozen · declared — carves out one change, an open question's key shown before its text
  • spec:decisions.roadmap-over-plans dependsOn spec:decisions.roadmap-priority · declared — plan files give up forward planning only once a roadmap holds priority in the graph
  • spec:decisions.roadmap-over-plans refines spec:decisions.planning-truths-placement · declared — narrows what a plan file may still carry once a roadmap holds priority
  • spec:decisions.roadmap-priority refines spec:decisions.pack-markdown-carrier · declared — opens the closed Pack manifest envelope to one optional field, `order`
  • spec:decisions.roadmap-priority refines spec:decisions.planning-truths-placement · declared — narrows the refusal of recorded work order for one case, the advisory priority of a roadmap
  • spec:decisions.sdp-gherkin-extension dependsOn spec:decisions.sdp-ts-extension · declared
  • spec:decisions.sdp-gherkin-extension refines spec:decisions.gherkin-carrier-option · declared — fixes the canonical Gherkin suffix as .sdp.gherkin and keeps bare .feature files out of discovery
  • spec:decisions.sdp-ts-extension refines spec:carrier.markdown-authoring · declared, orders nothing
  • spec:decisions.shipped-projections-frozen refines spec:consumers.projections-model · declared, orders nothing
  • spec:decisions.studio-build-renders refines spec: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 data
  • spec:decisions.studio-diagram-renderer dependsOn spec:extraction.determinism · declared — a diagram laid out from graph values alone keeps one graph to one set of bytes
  • spec:decisions.studio-diagram-renderer refines spec:decisions.studio-web-components · declared — narrows how an element that shows a diagram renders it; the element only enhances an SVG the build drew
  • spec:decisions.studio-html-surface dependsOn spec:extraction.regenerability · declared — disposable HTML can be regenerated from the graph instead of committed as authored source
  • spec:decisions.studio-html-surface refines spec:consumers.spec-studio · declared, orders nothing
  • spec:decisions.studio-web-components refines spec:consumers.spec-studio · declared, orders nothing
  • spec:decisions.typing-law refines spec:model.spec-sections · declared, orders nothing
  • spec:decisions.vault-owned-folder refines spec:consumers.obsidian-vault · declared, orders nothing — settles which files the vault's generator owns and how it regenerates them
  • spec:decisions.verification-posture-not-realization dependsOn spec:decisions.binding-not-liveness · declared
  • spec:decisions.verification-posture-not-realization refines spec:model.spec-sections · declared, orders nothing
  • spec:extraction.build-pipeline dependsOn spec:extraction.derive-graph · declared
  • spec:extraction.build-pipeline refines spec:extraction.derive-graph · declared — the build orchestrates derivation and publication of the one graph
  • spec:extraction.build-pipeline.same-invocation refines spec:extraction.build-pipeline · declared
  • spec:extraction.claim-taxonomy refines spec:extraction.derive-graph · declared
  • spec:extraction.contract-declarations decidedBy spec:decisions.typing-law · declared — the Design section stays open, so the Protocol fixes no declaration key vocabulary
  • spec:extraction.contract-declarations dependsOn spec:carrier.inline-code-spans · declared
  • spec:extraction.contract-declarations refines spec:extraction.executable-contracts · declared
  • spec:extraction.delivery-facts decidedBy spec:decisions.binding-not-liveness · declared
  • spec:extraction.delivery-facts refines spec:extraction.derive-graph · declared, orders nothing
  • spec:extraction.derive-graph constrainedBy spec:extraction.determinism · declared
  • spec:extraction.derive-graph decidedBy spec:decisions.anchor-binding-grain · declared
  • spec:extraction.derive-graph decidedBy spec:decisions.one-validation-path · declared
  • spec:extraction.derive-graph dependsOn spec:extraction.delivery-facts · declared — computes delivery facts by the shared conferral law
  • spec:extraction.derive-graph dependsOn spec:model.anchors · declared — the anchors Spec owns binding eligibility and structural endpoint restrictions
  • spec:extraction.derive-graph dependsOn spec:model.relations · declared — the relations Spec owns the kind restrictions on authored relations
  • spec:extraction.determinism refines spec:extraction.derive-graph · declared, orders nothing — deterministic output constrains the derivation capability
  • spec:extraction.entry-citations constrainedBy spec:extraction.determinism · declared
  • spec:extraction.entry-citations dependsOn spec:extraction.claim-taxonomy · declared — every citation carries the inferred claim
  • spec:extraction.entry-citations dependsOn spec:extraction.entry-locations · declared — the citation table is the location table's sibling, and a resolving citation names an entry it locates
  • spec:extraction.entry-citations dependsOn spec:model.anchors · declared — only a source file that carries an anchor is read for citations
  • spec:extraction.entry-citations dependsOn spec:validation.prose-mentions · declared — a citation is a token the prose-mention scan would read, and resolves by the same address rules
  • spec:extraction.entry-citations refines spec:extraction.derive-graph · declared
  • spec:extraction.entry-citations.code-comment-cites-declaration refines spec:extraction.entry-citations · declared
  • spec:extraction.entry-citations.test-title-cites-declaration refines spec:extraction.entry-citations · declared
  • spec:extraction.entry-citations.unanchored-file-unread refines spec:extraction.entry-citations · declared
  • spec:extraction.entry-citations.unresolved-citation refines spec:extraction.entry-citations · declared
  • spec:extraction.entry-locations constrainedBy spec:extraction.determinism · declared
  • spec:extraction.entry-locations dependsOn spec:model.open-question-keys · declared
  • spec:extraction.entry-locations refines spec:extraction.derive-graph · declared
  • spec:extraction.example-runner dependsOn spec:extraction.executable-contracts · declared — runs the step contracts the build emits
  • spec:extraction.example-runner refines spec:extraction.executable-examples · declared — step dispatch and failure rendering execute a bound example
  • spec:extraction.example-runner.red-step-naming refines spec:extraction.example-runner · declared
  • spec:extraction.example-runner.step-order refines spec:extraction.example-runner · declared
  • spec:extraction.excludes decidedBy spec:decisions.exclusion-contract · declared
  • spec:extraction.excludes refines spec:extraction.derive-graph · declared
  • spec:extraction.excludes.refused-path refines spec:extraction.excludes · declared
  • spec:extraction.excludes.segment-boundary refines spec:extraction.excludes · declared
  • spec:extraction.executable-contracts decidedBy spec:decisions.point-per-example · declared
  • spec:extraction.executable-contracts dependsOn spec:carrier.step-keys · declared — a keyed step's contract key is its step key
  • spec:extraction.executable-contracts refines spec:extraction.build-pipeline · declared
  • spec:extraction.executable-contracts refines spec:extraction.executable-examples · declared — typed contracts carry the authored steps and example space into execution
  • spec:extraction.executable-contracts.case-colliding-path refines spec:extraction.executable-contracts · declared
  • spec:extraction.executable-contracts.concreteness-refusal refines spec:extraction.executable-contracts · declared
  • spec:extraction.executable-contracts.multi-entry-example refines spec:extraction.executable-contracts · declared
  • spec:extraction.executable-examples dependsOn spec:extraction.derive-graph · declared — executable contracts read the one graph rather than another carrier path
  • spec:extraction.open-section-order refines spec:extraction.derive-graph · declared
  • spec:extraction.pack-member-order constrainedBy spec:extraction.determinism · declared
  • spec:extraction.pack-member-order decidedBy spec:decisions.roadmap-priority · declared
  • spec:extraction.pack-member-order dependsOn spec:carrier.markdown-pack-authoring · declared
  • spec:extraction.pack-member-order refines spec:extraction.derive-graph · declared
  • spec:extraction.pack-member-order.manifest-order-kept refines spec:extraction.pack-member-order · declared
  • spec:extraction.regenerability refines spec:extraction.determinism · declared
  • spec:extraction.runnable-modules decidedBy spec:decisions.adopted-registrars-committed · declared
  • spec:extraction.runnable-modules decidedBy spec:decisions.anchor-comment-form · declared
  • spec:extraction.runnable-modules decidedBy spec:decisions.binding-not-liveness · declared
  • spec:extraction.runnable-modules decidedBy spec:decisions.point-per-example · declared
  • spec:extraction.runnable-modules dependsOn spec:carrier.step-keys · declared — the registrar binds each step under its contract key
  • spec:extraction.runnable-modules dependsOn spec:extraction.build-pipeline · declared — the build publishes the registrars and their manifest under its staged-publication law
  • spec:extraction.runnable-modules dependsOn spec:extraction.executable-contracts · declared
  • spec:extraction.runnable-modules refines spec:extraction.example-runner · declared
  • spec:extraction.schema-versioning refines spec:extraction.derive-graph · declared
  • spec:extraction.schema-versioning.declared-version refines spec:extraction.schema-versioning · declared
  • spec:model.anchors decidedBy spec:decisions.anchor-binding-grain · declared
  • spec:model.anchors decidedBy spec:decisions.anchor-comment-form · declared
  • spec:model.anchors decidedBy spec:decisions.architectural-annotation · declared
  • spec:model.anchors decidedBy spec:decisions.binding-not-liveness · declared
  • spec:model.anchors refines spec:model.core-model · declared
  • spec:model.anchors.lookalike-refusal refines spec:model.anchors · declared
  • spec:model.anchors.physical-identity refines spec:model.anchors · declared
  • spec:model.core-model decidedBy spec:decisions.example-realization-posture · declared
  • spec:model.core-model decidedBy spec:decisions.one-primitive · declared
  • spec:model.design-maturity dependsOn spec:consumers.pack-design · declared
  • spec:model.design-maturity refines spec:model.core-model · declared
  • spec:model.enrichment-lifecycle dependsOn spec:extraction.contract-declarations · declared — a slimming candidate is a pinned declaration
  • spec:model.enrichment-lifecycle refines spec:model.core-model · declared
  • spec:model.open-question-fields decidedBy spec:decisions.adopt-the-nouns · declared — question fields describe the question without adding workflow state or gates
  • spec:model.open-question-fields decidedBy spec:decisions.planning-truths-placement · declared — a deferral's re-entry trigger rides its own blocking question, the home that decision rules
  • spec:model.open-question-fields dependsOn spec:extraction.entry-locations · declared — adds rows to the location table
  • spec:model.open-question-fields refines spec:model.open-question-keys · declared
  • spec:model.open-question-fields.dropped-list-warns refines spec:model.open-question-fields · declared
  • spec:model.open-question-keys decidedBy spec:decisions.checked-mentions · declared
  • spec:model.open-question-keys dependsOn spec:carrier.markdown-body-grammar · declared
  • spec:model.open-question-keys refines spec:model.spec-sections · declared
  • spec:model.open-question-keys.keyed-question-resolves refines spec:model.open-question-keys · declared
  • spec:model.open-question-keys.renamed-key-breaks refines spec:model.open-question-keys · declared
  • spec:model.open-question-keys.repeated-key-refused refines spec:model.open-question-keys · declared
  • spec:model.pack-aggregate decidedBy spec:decisions.pack-reified · declared
  • spec:model.pack-aggregate decidedBy spec:decisions.roadmap-priority · declared
  • spec:model.pack-aggregate refines spec:model.core-model · declared
  • spec:model.planned-architecture decidedBy spec:decisions.architectural-annotation · declared
  • spec:model.planned-architecture dependsOn spec:model.anchors · declared — a planned component is realized by a component anchor that satisfies its design
  • spec:model.planned-architecture refines spec:model.core-model · declared — planned components enrich Specs before code binds them
  • spec:model.planned-architecture.differing-layer-and-uses refines spec:model.planned-architecture · declared
  • spec:model.planned-architecture.matching-design refines spec:model.planned-architecture · declared
  • spec:model.planned-architecture.unrealized-design refines spec:model.planned-architecture · declared
  • spec:model.relation-reasons decidedBy spec:decisions.prose-ownership · declared — the relation owns its reason as typed prose
  • spec:model.relation-reasons refines spec:model.relations · declared
  • spec:model.relations decidedBy spec:decisions.planning-truths-placement · declared — planning truths ride these six relation types, and new relation types were refused
  • spec:model.relations refines spec:model.core-model · declared
  • spec:model.rule-keys decidedBy spec:decisions.checked-mentions · declared — rule addresses join the address law it rules
  • spec:model.rule-keys decidedBy spec:decisions.shipped-projections-frozen · declared — keys stay off the frozen projections, which read the rule text unchanged
  • spec:model.rule-keys dependsOn spec:extraction.entry-locations · declared — adds rows to the location table
  • spec:model.rule-keys dependsOn spec:model.open-question-keys · declared
  • spec:model.rule-keys refines spec:model.spec-sections · declared
  • spec:model.spec-sections decidedBy spec:decisions.anchor-comment-form · declared — it restates comment promotion for the comment form
  • spec:model.spec-sections decidedBy spec:decisions.content-only-sections · declared
  • spec:model.spec-sections decidedBy spec:decisions.point-per-example · declared
  • spec:model.spec-sections decidedBy spec:decisions.typing-law · declared
  • spec:model.spec-sections decidedBy spec:decisions.verification-posture-not-realization · declared
  • spec:model.spec-sections refines spec:model.core-model · declared
  • spec:model.stable-ids decidedBy spec:decisions.checked-mentions · declared
  • spec:model.stable-ids refines spec:model.core-model · declared
  • spec:model.stable-ids.malformed-refusal refines spec:model.stable-ids · declared
  • spec:model.stable-ids.namespaced-round-trip refines spec:model.stable-ids · declared
  • spec:model.stable-ids.unsectioned-address-refused refines spec:model.stable-ids · declared
  • spec:model.structural-patterns decidedBy spec:decisions.architectural-annotation · declared
  • spec:model.structural-patterns refines spec:model.anchors · declared
  • spec:model.term-addresses decidedBy spec:decisions.checked-mentions · declared — a term address joins the address law that decision rules
  • spec:model.term-addresses decidedBy spec:decisions.shipped-projections-frozen · declared — term keys stay off the frozen projections, which read the definition unchanged
  • spec:model.term-addresses dependsOn spec:extraction.entry-locations · declared — adds a row per Model term to the location table
  • spec:model.term-addresses dependsOn spec:model.rule-keys · declared — the term-key design follows the rule-entry address pattern
  • spec:model.term-addresses dependsOn spec:model.stable-ids · declared — a term address extends the Spec entry-address grammar
  • spec:model.term-addresses refines spec:model.spec-sections · declared — extends entry addresses to the terms a Model section defines
  • spec:model.term-addresses.keyed-term-resolves refines spec:model.term-addresses · declared
  • spec:model.term-addresses.malformed-term-marker-refused refines spec:model.term-addresses · declared
  • spec:model.term-addresses.repeated-term-key-refused refines spec:model.term-addresses · declared
  • spec:model.term-addresses.typescript-term-imports-keyed refines spec:model.term-addresses · declared
  • spec:model.term-addresses.unknown-term-key-refused refines spec:model.term-addresses · declared
  • spec:observation.run-evidence decidedBy spec:decisions.binding-not-liveness · declared
  • spec:observation.run-evidence dependsOn spec:consumers.agent-surface.recipe-parameters · declared — the caller passes run records to the recipe as data
  • spec:observation.run-evidence dependsOn spec:extraction.delivery-facts · declared — the view reads verifier bindings while leaving their delivery facts unchanged
  • spec:observation.run-evidence refines spec:consumers.projections-model · declared — run records inform a view without becoming graph facts
  • spec:observation.run-evidence.absolute-path-joins refines spec:observation.run-evidence · declared
  • spec:observation.run-evidence.unanchored-file-unjoined refines spec:observation.run-evidence · declared
  • spec:observation.runtime-overlay dependsOn spec:model.core-model · declared
  • spec:observation.runtime-overlay refines spec:extraction.derive-graph · declared — an observed fact would be derived beside implemented and has-verifier
  • spec:protocol.capability-epics decidedBy spec:decisions.epics-of-any-kind · declared
  • spec:protocol.capability-epics dependsOn spec:consumers.capability-map · declared — the capability map exposes the corpus's authored refinement
  • spec:protocol.capability-epics dependsOn spec:validation.readiness-floor · declared — reparenting preserves the floor of each existing ready child
  • spec:protocol.capability-epics refines spec:protocol.self-hosting · declared
  • spec:protocol.delivery-record-cleanup decidedBy spec:decisions.roadmap-over-plans · declared
  • spec:protocol.delivery-record-cleanup refines spec:protocol.roadmap-replaces-plans · declared — carries out the removal the roadmap and the pull request record made possible for frozen history
  • spec:protocol.roadmap-replaces-plans decidedBy spec:decisions.roadmap-over-plans · declared
  • spec:protocol.roadmap-replaces-plans dependsOn spec:consumers.intent-composition.proposal · declared — a review's findings against Specs travel as a checked change proposal
  • spec:protocol.roadmap-replaces-plans dependsOn spec:consumers.intent-composition.proposal.memo · declared — the pull request carries a review's proposal as its memo
  • spec:protocol.roadmap-replaces-plans dependsOn spec:consumers.roadmap · declared — the Protocol reads its own next work from its roadmap
  • spec:protocol.roadmap-replaces-plans dependsOn spec:consumers.roadmap.memo · declared — each description's forward section is the roadmap memo
  • spec:protocol.roadmap-replaces-plans dependsOn spec:observation.run-evidence · declared — an arc's acceptance reads run records as evidence from test files at their recorded commit
  • spec:protocol.roadmap-replaces-plans refines spec:protocol.self-hosting · declared
  • spec:protocol.role-vocabulary decidedBy spec:decisions.architectural-annotation · declared
  • spec:protocol.role-vocabulary refines spec:protocol.structural-self-binding · declared — names what each role value the engine's significant units carry means
  • spec:protocol.self-hosting decidedBy spec:decisions.adopt-the-nouns · declared
  • spec:protocol.self-hosting decidedBy spec:decisions.concept-docs-dissolve · declared
  • spec:protocol.self-hosting decidedBy spec:decisions.executable-meta-model · declared
  • spec:protocol.self-hosting decidedBy spec:decisions.one-validation-path · declared
  • spec:protocol.self-hosting decidedBy spec:decisions.plain-language-references · declared
  • spec:protocol.self-hosting decidedBy spec:decisions.protocol-naming · declared
  • spec:protocol.self-hosting dependsOn spec:carrier.markdown-authoring · declared — the self-hosted corpus uses the Markdown carrier
  • spec:protocol.self-hosting dependsOn spec:model.core-model · declared — the self-hosted corpus is authored as Specs on the Protocol's core model
  • spec:protocol.significant-units-review decidedBy spec:decisions.anchor-binding-grain · declared
  • spec:protocol.significant-units-review decidedBy spec:decisions.architectural-annotation · declared
  • spec:protocol.significant-units-review dependsOn spec:model.structural-patterns · declared
  • spec:protocol.significant-units-review dependsOn spec:protocol.role-vocabulary · declared
  • spec:protocol.significant-units-review refines spec:protocol.structural-self-binding · declared — states what the independently reviewed accepted set must contain and exclude
  • spec:protocol.structural-self-binding decidedBy spec:decisions.anchor-binding-grain · declared
  • spec:protocol.structural-self-binding decidedBy spec:decisions.architectural-annotation · declared
  • spec:protocol.structural-self-binding dependsOn spec:model.structural-patterns · declared — this model defines the significance criterion and the owner-reviewed accepted set
  • spec:protocol.structural-self-binding refines spec:protocol.self-hosting · declared
  • spec:validation.architecture-constraints decidedBy spec:decisions.architectural-annotation · declared
  • spec:validation.architecture-constraints dependsOn spec:model.anchors · declared
  • spec:validation.architecture-constraints dependsOn spec:validation.corpus-rules · declared
  • spec:validation.architecture-constraints refines spec:validation.corpus-rules · declared — the architecture walk is a corpus-selected rule over anchored structure
  • spec:validation.architecture-constraints.forbidden-layer-pair refines spec:validation.architecture-constraints · declared
  • spec:validation.architecture-constraints.isolated-context-as-rule refines spec:validation.architecture-constraints · declared
  • spec:validation.architecture-constraints.unstated-layer-unclassified refines spec:validation.architecture-constraints · declared
  • spec:validation.authored-honesty decidedBy spec:decisions.binding-not-liveness · declared
  • spec:validation.authored-honesty dependsOn spec:extraction.delivery-facts · declared
  • spec:validation.authored-honesty refines spec:validation.two-check-families · declared
  • spec:validation.authored-honesty.section-authored-fact refines spec:validation.authored-honesty · declared
  • spec:validation.authored-honesty.unearned-stated-fact refines spec:validation.authored-honesty · declared
  • spec:validation.claim-separation dependsOn spec:extraction.claim-taxonomy · declared
  • spec:validation.claim-separation dependsOn spec:extraction.derive-graph · declared
  • spec:validation.claim-separation refines spec:validation.two-check-families · declared
  • spec:validation.claim-separation.collapsed-edge-claim refines spec:validation.claim-separation · declared
  • spec:validation.claim-separation.unratified-descriptor refines spec:validation.claim-separation · declared
  • spec:validation.corpus-rules constrainedBy spec:validation.two-check-families · declared
  • spec:validation.corpus-rules decidedBy spec:decisions.architectural-annotation · declared — architecture checks remain the corpus's own rules
  • spec:validation.corpus-rules dependsOn spec:consumers.agent-surface · declared
  • spec:validation.corpus-rules dependsOn spec:consumers.agent-surface.evaluation-sink · declared — a rules file holds the body the sink evaluates, with the sink's bindings and trust
  • spec:validation.corpus-rules dependsOn spec:consumers.agent-surface.recipe-parameters · declared — validate takes `--params` in the sink's grammar
  • spec:validation.corpus-rules dependsOn spec:consumers.validate-watch · declared — the watch loop reruns the named rules in each cycle
  • spec:validation.corpus-rules dependsOn spec:validation.diagnostic-rendering · declared — corpus findings use the shared diagnostic currency
  • spec:validation.corpus-rules refines spec:consumers.agent-surface · declared — a corpus scripts the graph through the evaluation sink to report its own findings
  • spec:validation.corpus-rules.copies-contain-changes refines spec:validation.corpus-rules · declared
  • spec:validation.corpus-rules.error-finding-fails refines spec:validation.corpus-rules · declared
  • spec:validation.corpus-rules.malformed-finding-fails refines spec:validation.corpus-rules · declared
  • spec:validation.corpus-rules.params-edit-starts-a-cycle refines spec:validation.corpus-rules · declared
  • spec:validation.corpus-rules.rules-edit-starts-a-cycle refines spec:validation.corpus-rules · declared
  • spec:validation.corpus-rules.unreadable-params-fail-one-file refines spec:validation.corpus-rules · declared
  • spec:validation.corpus-rules.warning-finding-informs refines spec:validation.corpus-rules · declared
  • spec:validation.diagnostic-rendering dependsOn spec:consumers.design-review · declared
  • spec:validation.diagnostic-rendering refines spec:validation.two-check-families · declared
  • spec:validation.diagnostic-rendering.composed-location refines spec:validation.diagnostic-rendering · declared
  • spec:validation.diagnostic-rendering.table-cell-location refines spec:validation.diagnostic-rendering · declared
  • spec:validation.duplicate-ids dependsOn spec:carrier.markdown-parser · declared — duplicate exclusion includes the default Markdown carrier
  • spec:validation.duplicate-ids refines spec:validation.two-check-families · declared — duplicate identity is a conformance refusal
  • spec:validation.duplicate-ids.dual-carrier refines spec:validation.duplicate-ids · declared
  • spec:validation.external-registers dependsOn spec:consumers.agent-surface.recipe-parameters · declared — the register arrives as data through `--params register=@PATH`
  • spec:validation.external-registers dependsOn spec:consumers.agent-surface.register-recipes · declared — the recipe reads the strings entry search walks, with its entry paths and lines
  • spec:validation.external-registers dependsOn spec:validation.corpus-rules · declared — the recipe answers with findings and runs as a rules file
  • spec:validation.external-registers refines spec:validation.corpus-rules · declared — external-register checks run as corpus-selected rules
  • spec:validation.external-registers.uncited-on-request refines spec:validation.external-registers · declared
  • spec:validation.external-registers.unknown-and-retired refines spec:validation.external-registers · declared
  • spec:validation.kind-evidence decidedBy spec:decisions.carried-evidence · declared — promoted children and constrainedBy targets count only when they carry evidence
  • spec:validation.kind-evidence decidedBy spec:decisions.kind-conditional-floor · declared
  • spec:validation.kind-evidence refines spec:validation.readiness-floor · declared
  • spec:validation.kind-evidence.constraints-alone refines spec:validation.kind-evidence · declared
  • spec:validation.kind-evidence.empty-promoted-child refines spec:validation.kind-evidence · declared
  • spec:validation.kind-evidence.second-entry-untargeted refines spec:validation.kind-evidence · declared
  • spec:validation.kind-evidence.untargeted-constraint refines spec:validation.kind-evidence · declared
  • spec:validation.next-rung-floor dependsOn spec:validation.typed-dependency-floor · declared
  • spec:validation.next-rung-floor refines spec:validation.readiness-floor · declared
  • spec:validation.next-rung-floor.blocking-question refines spec:validation.next-rung-floor · declared
  • spec:validation.next-rung-floor.typed-dependency-targets refines spec:validation.next-rung-floor · declared
  • spec:validation.oracle-target-eligibility dependsOn spec:model.anchors · declared
  • spec:validation.oracle-target-eligibility refines spec:validation.verification-linkage · declared
  • spec:validation.oracle-target-eligibility.missing-space-refused refines spec:validation.oracle-target-eligibility · declared
  • spec:validation.oracle-target-eligibility.rule-space-accepted refines spec:validation.oracle-target-eligibility · declared
  • spec:validation.pack-coherence dependsOn spec:model.pack-aggregate · declared — membership and modelRefs use the Pack model
  • spec:validation.pack-coherence refines spec:validation.two-check-families · declared
  • spec:validation.pack-coherence.incoherent-aggregate refines spec:validation.pack-coherence · declared
  • spec:validation.prose-mentions decidedBy spec:decisions.checked-mentions · declared
  • spec:validation.prose-mentions dependsOn spec:model.open-question-fields · declared — the links field it checks whole is defined by the open-question field grammar
  • spec:validation.prose-mentions dependsOn spec:model.term-addresses · declared — a term address resolves through the Spec's term keys
  • spec:validation.prose-mentions refines spec:validation.referential-integrity · declared
  • spec:validation.readiness-floor decidedBy spec:decisions.carried-evidence · declared
  • spec:validation.readiness-floor decidedBy spec:decisions.kind-conditional-floor · declared
  • spec:validation.readiness-floor dependsOn spec:model.core-model · declared — the floor reads the Protocol descriptor model
  • spec:validation.readiness-floor refines spec:validation.two-check-families · declared — the readiness floor checks honesty of the stated rung
  • spec:validation.readiness-floor.blocking-open-question refines spec:validation.readiness-floor · declared
  • spec:validation.readiness-floor.unrelated-scoped-spec refines spec:validation.readiness-floor · declared
  • spec:validation.referential-integrity refines spec:validation.two-check-families · declared
  • spec:validation.referential-integrity.dangling-target refines spec:validation.referential-integrity · declared
  • spec:validation.referential-integrity.did-you-mean refines spec:validation.referential-integrity · declared
  • spec:validation.superseded-decision-signal decidedBy spec:decisions.planning-truths-placement · declared — supersedes replaces a decision whole and refines narrows it
  • spec:validation.superseded-decision-signal dependsOn spec:extraction.entry-locations · declared — the warning takes its line from the location row of the decidedBy target it names
  • spec:validation.superseded-decision-signal dependsOn spec:model.relations · declared — its supersedes term keeps a replaced record only while a reader still needs its text, so the edges the signal reads are records a corpus chose to keep
  • spec:validation.superseded-decision-signal refines spec:validation.warn-level-signals · declared
  • spec:validation.superseded-decision-signal.branch-names-every-end refines spec:validation.superseded-decision-signal · declared
  • spec:validation.superseded-decision-signal.chain-end-named refines spec:validation.superseded-decision-signal · declared
  • spec:validation.superseded-decision-signal.closed-chain-named refines spec:validation.superseded-decision-signal · declared
  • spec:validation.superseded-decision-signal.dependency-unread refines spec:validation.superseded-decision-signal · declared
  • spec:validation.superseded-decision-signal.end-and-loop-named refines spec:validation.superseded-decision-signal · declared
  • spec:validation.superseded-decision-signal.live-replacement-warns refines spec:validation.superseded-decision-signal · declared
  • spec:validation.superseded-decision-signal.replaced-ruling-warns refines spec:validation.superseded-decision-signal · declared
  • spec:validation.superseded-decision-signal.replacement-below-ready-named refines spec:validation.superseded-decision-signal · declared
  • spec:validation.superseded-decision-signal.superseded-subject-silent refines spec:validation.superseded-decision-signal · declared
  • spec:validation.two-check-families decidedBy spec:decisions.one-validation-path · declared
  • spec:validation.two-check-families.split-report refines spec:validation.two-check-families · declared
  • spec:validation.typed-dependency-floor dependsOn spec:model.relations · declared
  • spec:validation.typed-dependency-floor refines spec:validation.readiness-floor · declared
  • spec:validation.typed-dependency-floor.missing-targets refines spec:validation.typed-dependency-floor · declared
  • spec:validation.typed-dependency-floor.relation-rungs refines spec:validation.typed-dependency-floor · declared
  • spec:validation.typed-dependency-floor.stated-readiness refines spec:validation.typed-dependency-floor · declared
  • spec:validation.typed-dependency-floor.unsettled-fact refines spec:validation.typed-dependency-floor · declared
  • spec:validation.unbound-example-posture refines spec:validation.verification-linkage · declared
  • spec:validation.unbound-example-posture.lower-rungs refines spec:validation.unbound-example-posture · declared
  • spec:validation.unbound-example-posture.parent-traces refines spec:validation.unbound-example-posture · declared
  • spec:validation.unbound-example-posture.warning-cases refines spec:validation.unbound-example-posture · declared
  • spec:validation.validator-self-testing refines spec:validation.two-check-families · declared
  • spec:validation.validator-self-testing.duplicate-pair-named refines spec:validation.validator-self-testing · declared
  • spec:validation.validator-self-testing.overeager-check-named refines spec:validation.validator-self-testing · declared
  • spec:validation.validator-self-testing.shipped-checks-paired refines spec:validation.validator-self-testing · declared
  • spec:validation.validator-self-testing.silent-check-named refines spec:validation.validator-self-testing · declared
  • spec:validation.validator-self-testing.unpaired-check-named refines spec:validation.validator-self-testing · declared
  • spec:validation.validator-self-testing.unregistered-id-named refines spec:validation.validator-self-testing · declared
  • spec:validation.verification-linkage refines spec:validation.two-check-families · declared
  • spec:validation.verification-linkage.unbound-example refines spec:validation.verification-linkage · declared
  • spec:validation.verification-linkage.unresolved-oracle refines spec:validation.verification-linkage · declared
  • spec:validation.warn-level-signals decidedBy spec:decisions.decision-readiness-posture · declared
  • spec:validation.warn-level-signals refines spec:validation.two-check-families · declared
  • spec:validation.warn-level-signals.orphan-signal refines spec:validation.warn-level-signals · declared
  • spec:validation.warn-level-signals.ready-gap-signal refines spec:validation.warn-level-signals · declared
  • Cycle: spec:carrier.envelope-contract, spec:carrier.inline-code-spans, spec:carrier.markdown-authoring, spec:carrier.markdown-body-grammar, spec:carrier.markdown-parser, spec:carrier.slot-notation, spec:carrier.step-keys, spec:extraction.entry-locations, spec:model.open-question-fields, spec:model.open-question-keys, spec:model.rule-keys, spec:model.term-addresses; spec:carrier.envelope-contract → spec:carrier.markdown-authoring → spec:carrier.markdown-parser → spec:carrier.envelope-contract

What each member needs next

MemberDepthRungNext rungDesign carriedCode
Committed source derives byte-identical output
spec:extraction.determinism
constraint
1ready floor ready2 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound2 implementing0 referencing
Durable references lead with meaning
spec:decisions.plain-language-references
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Concept documents may dissolve after executable truth lands
spec:decisions.concept-docs-dissolve
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Validation follows one graph
spec:decisions.one-validation-path
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Spec extensions identify the carrier without colliding with tests
spec:decisions.sdp-ts-extension
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Each example binds one point
spec:decisions.point-per-example
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Markdown is the default Spec carrier
spec:decisions.carrier-ruling
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Prose belongs to typed graph owners
spec:decisions.prose-ownership
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
The Protocol owns the envelope grammar
spec:decisions.envelope-grammar-posture
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Consumer exclusions stay exact
spec:decisions.exclusion-contract
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
The Protocol is an executable meta-model
spec:decisions.executable-meta-model
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Delivery nouns remain familiar without workflow gates
spec:decisions.adopt-the-nouns
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
One Spec carries named delivery coordinates
spec:decisions.one-primitive
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
The meta-model is a software delivery protocol
spec:decisions.protocol-naming
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Bindings state existence, not liveness
spec:decisions.binding-not-liveness
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Sections carry content while relations carry links
spec:decisions.content-only-sections
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Floor-read sections are closed typed shapes
spec:decisions.typing-law
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Readiness evidence follows the Spec kind
spec:decisions.kind-conditional-floor
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Packs group review context without becoming truth
spec:decisions.pack-reified
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Agents script the visible graph
spec:decisions.agent-surface-scripts-graph
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
MCP integration remains deferred
spec:decisions.mcp-deferred
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Adopted runnable registrars are committed
spec:decisions.adopted-registrars-committed
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
The shipped projections stay frozen
spec:decisions.shipped-projections-frozen
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Planning truths live in ruled graph homes
spec:decisions.planning-truths-placement
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
The Studio is built from custom elements, not a framework
spec:decisions.studio-web-components
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
The vault's generator owns one folder and synchronizes it
spec:decisions.vault-owned-folder
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing2 referencing
Resolving bindings confer direct delivery facts
spec:extraction.delivery-facts
behavior
2ready floor ready10 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
Generated artifacts are disposable projections
spec:extraction.regenerability
rule
2ready floor ready3 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
Validation separates well-formedness from non-pretending
spec:validation.two-check-families
rule
2ready floor ready6 rules, 1 keyed0 entries0 declarations0 questions1 decisions1 of 1 verifying examples bound4 implementing0 referencing
1 example members folded in
Projections fan out from one graph without becoming truth stores
spec:consumers.projections-model
model
2ready floor ready0 rules0 entries0 declarations0 questions2 decisions0 of 0 verifying examples bound2 implementing0 referencing
Promoted evidence must carry its own evidence
spec:decisions.carried-evidence
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
The agent front door is one evaluation sink over the exported reader
spec:decisions.agent-front-door
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Verification mode states posture, not realization
spec:decisions.verification-posture-not-realization
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Example realization stays evidence, not backlog work
spec:decisions.example-realization-posture
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Packs have a Markdown manifest carrier
spec:decisions.pack-markdown-carrier
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Decision records state readiness from ratification evidence
spec:decisions.decision-readiness-posture
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Behavior and example Specs may use Gherkin canonically
spec:decisions.gherkin-carrier-option
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
A Spec id written in prose is a checked mention
spec:decisions.checked-mentions
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
The build renders every Studio view, and an element only enhances it
spec:decisions.studio-build-renders
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing6 referencing
The engine lays out every Studio diagram as static SVG when the page set is built
spec:decisions.studio-diagram-renderer
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing2 referencing
The comment form is a second anchor representation
spec:decisions.anchor-comment-form
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing2 referencing
Bindings are optional, plural, and may reference a design
spec:decisions.anchor-binding-grain
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing3 referencing
Capability epics keep kind independent of altitude
spec:decisions.epics-of-any-kind
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing1 referencing
The Protocol models delivery with one enrichable Spec
spec:model.core-model
model
3ready floor ready0 rules0 entries0 declarations0 questions2 decisions0 of 0 verifying examples bound3 implementing0 referencing
Every graph reference resolves
spec:validation.referential-integrity
rule
3ready floor ready2 rules0 entries0 declarations0 questions0 decisions2 of 2 verifying examples bound1 implementing0 referencing
2 example members folded in
Example verification and oracle bindings resolve honestly
spec:validation.verification-linkage
rule
3ready floor ready3 rules0 entries0 declarations0 questions0 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
Machine truth is never authored
spec:validation.authored-honesty
rule
3ready floor ready2 rules0 entries0 declarations0 questions1 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
Missing connective evidence warns without failing
spec:validation.warn-level-signals
rule
3ready floor ready4 rules0 entries0 declarations0 questions1 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
Every validator ships evidence in both directions
spec:validation.validator-self-testing
rule
3ready floor ready8 rules, 8 keyed5 entries5 declarations0 questions0 decisions6 of 6 verifying examples bound2 implementing0 referencing
6 example members folded in
Agents script a visible typed graph
spec:consumers.agent-surface
behavior
3ready floor ready7 rules, 4 keyed0 entries0 declarations0 questions2 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
Views compose scoped intent instead of patching canonical source
spec:consumers.edit-model
behavior
3ready floor ready3 rules, 2 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing2 referencing
A reference projection serves a reader outside the repository
spec:consumers.reference-projection
behavior
3idea floor ideanext scoped:
  • kind-evidence-present · The kind's natural evidence is present (per-kind evidence table).
0 rules0 entries0 declarations2 questions, 1 blocking0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Canonical Gherkin carriers use .sdp.gherkin
spec:decisions.sdp-gherkin-extension
decision
3ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Carrier universality is bounded by honest kind structure
spec:decisions.carrier-universality
decision
3ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing1 referencing
The Studio renders HTML, and the HTML stays derived
spec:decisions.studio-html-surface
decision
3ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Architectural significance is annotated where it is realized
spec:decisions.architectural-annotation
decision
3ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing3 referencing
A roadmap states advisory priority in the graph
spec:decisions.roadmap-priority
decision
3ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing2 referencing
Spec sections carry typed detail and direct verifier semantics
spec:model.spec-sections
model
4ready floor ready0 rules0 entries0 declarations0 questions5 decisions0 of 0 verifying examples bound2 implementing0 referencing
Specs declare typed directed relations
spec:model.relations
model
4ready floor ready0 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
Stable IDs are the Protocol's durable join key
spec:model.stable-ids
rule
4ready floor ready5 rules, 1 keyed0 entries0 declarations0 questions1 decisions3 of 3 verifying examples bound1 implementing0 referencing
3 example members folded in
A Pack is a truth-free review aggregate
spec:model.pack-aggregate
model
4ready floor ready0 rules0 entries0 declarations0 questions2 decisions0 of 0 verifying examples bound1 implementing0 referencing
Source anchors bind code without carrying intent
spec:model.anchors
model
4ready floor ready0 rules1 entries1 declarations0 questions4 decisions2 of 2 verifying examples bound5 implementing0 referencing
2 example members folded in
Stated readiness must clear its floor
spec:validation.readiness-floor
rule
4ready floor ready14 rules, 5 keyed0 entries0 declarations0 questions2 decisions2 of 2 verifying examples bound1 implementing0 referencing
2 example members folded in
An unbound example below ready is data, not a warning
spec:validation.unbound-example-posture
rule
4ready floor ready5 rules0 entries0 declarations0 questions0 decisions3 of 3 verifying examples bound1 implementing0 referencing
3 example members folded in
The evaluation sink runs one body and prints its return
spec:consumers.agent-surface.evaluation-sink
behavior
4ready floor ready10 rules, 5 keyed7 entries3 declarations0 questions1 decisions3 of 3 verifying examples bound2 implementing0 referencing
3 example members folded in
The reader bridges agent entry points to composable graph context
spec:consumers.reader
behavior
4ready floor ready11 rules, 4 keyed0 entries0 declarations0 questions4 decisions3 of 3 verifying examples bound2 implementing0 referencing
3 example members folded in
The reading skill teaches agents to query the graph
spec:consumers.reading-on-ramp
behavior
4ready floor ready6 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
Authoring questions stay executable graph recipes
spec:consumers.agent-surface.authoring-recipes
behavior
4ready floor ready3 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
Composed intent hands off on one proposal shape
spec:consumers.intent-composition
behavior
4ready floor ready3 rules, 1 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing2 referencing
Recipes take parameters as data and ship as runnable files
spec:consumers.agent-surface.recipe-parameters
behavior
4ready floor ready8 rules, 3 keyed2 entries2 declarations0 questions1 decisions0 of 0 verifying examples bound4 implementing0 referencing
Plan and review files stop carrying the delivery record once the roadmap and the pull request do
spec:decisions.roadmap-over-plans
decision
4ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Architecturally significant units are annotated where they are realized
spec:model.structural-patterns
model
5ready floor ready0 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound3 implementing0 referencing
Components are designed ahead of their code
spec:model.planned-architecture
model
5ready floor ready0 rules6 entries1 declarations0 questions1 decisions3 of 3 verifying examples bound1 implementing1 referencing
3 example members folded in
An authored relation may carry its reason
spec:model.relation-reasons
rule
5ready floor ready7 rules5 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound2 implementing0 referencing
Carrier reification derives the one graph
spec:extraction.derive-graph
behavior
5ready floor ready9 rules6 entries4 declarations0 questions2 decisions0 of 0 verifying examples bound5 implementing0 referencing
A ready Spec rests only on settled dependencies
spec:validation.typed-dependency-floor
rule
5ready floor ready7 rules0 entries0 declarations0 questions0 decisions4 of 4 verifying examples bound1 implementing0 referencing
4 example members folded in
Oracle eligibility follows example-space ownership
spec:validation.oracle-target-eligibility
rule
5ready floor ready4 rules0 entries0 declarations0 questions0 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
Packs are coherent aggregates
spec:validation.pack-coherence
rule
5ready floor ready4 rules0 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
Each kind carries its own evidence
spec:validation.kind-evidence
rule
5ready floor ready11 rules0 entries0 declarations0 questions2 decisions5 of 5 verifying examples bound1 implementing0 referencing
4 example members folded in
The Spec Studio is a static HTML workbench over the one graph
spec:consumers.spec-studio
behavior
5ready floor ready11 rules, 4 keyed0 entries0 declarations0 questions4 decisions0 of 0 verifying examples bound3 implementing0 referencing
Designs are compared between a base commit and the working tree at entry grain
spec:consumers.design-diff
behavior
5ready floor ready11 rules8 entries4 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
The capability map reads every epic and its refinement descendants
spec:consumers.capability-map
behavior
5ready floor ready9 rules, 9 keyed10 entries4 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
CI run records are joined to verifiers in a view
spec:observation.run-evidence
behavior
5ready floor ready9 rules, 7 keyed7 entries5 declarations1 questions1 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
Markdown authoring enters the one graph
spec:carrier.markdown-authoring
behavior
6ready floor ready1 rules0 entries0 declarations0 questions2 decisions0 of 0 verifying examples bound1 implementing0 referencing
The Markdown envelope is explicit and bounded
spec:carrier.envelope-contract
contract
6ready floor ready8 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound2 implementing0 referencing
The Markdown parser reifies the ruled subset
spec:carrier.markdown-parser
behavior
6ready floor ready9 rules0 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound2 implementing0 referencing
1 example members folded in
The Markdown body accepts one closed form per section
spec:carrier.markdown-body-grammar
behavior
6ready floor ready16 rules, 12 keyed0 entries0 declarations0 questions2 decisions15 of 15 verifying examples bound2 implementing0 referencing
14 example members folded in
Inline code is content, never markup
spec:carrier.inline-code-spans
rule
6ready floor ready6 rules, 6 keyed0 entries0 declarations0 questions0 decisions4 of 4 verifying examples bound1 implementing0 referencing
4 example members folded in
Slot notation declares, binds, and refuses to guess
spec:carrier.slot-notation
rule
6ready floor ready7 rules, 7 keyed0 entries0 declarations0 questions0 decisions3 of 3 verifying examples bound2 implementing0 referencing
3 example members folded in
An example step may carry a key that survives rewording
spec:carrier.step-keys
rule
6ready floor ready12 rules, 8 keyed9 entries7 declarations0 questions1 decisions10 of 10 verifying examples bound7 implementing0 referencing
10 example members folded in
An open question may carry a key that addresses it
spec:model.open-question-keys
rule
6ready floor ready6 rules, 3 keyed0 entries0 declarations0 questions1 decisions3 of 3 verifying examples bound7 implementing0 referencing
3 example members folded in
An open question may name who decides it, its links, a provisional reading and a re-entry trigger
spec:model.open-question-fields
rule
6ready floor ready12 rules, 2 keyed7 entries1 declarations0 questions2 decisions1 of 1 verifying examples bound2 implementing0 referencing
1 example members folded in
A rule or flow entry may carry a key that addresses it
spec:model.rule-keys
rule
6ready floor ready7 rules10 entries6 declarations0 questions2 decisions0 of 0 verifying examples bound3 implementing0 referencing
A Model term may carry a key that addresses it
spec:model.term-addresses
rule
6ready floor ready9 rules, 7 keyed10 entries7 declarations0 questions2 decisions5 of 5 verifying examples bound9 implementing0 referencing
5 example members folded in
The build pipeline has one ordered flow
spec:extraction.build-pipeline
workflow
6ready floor ready8 rules, 4 keyed0 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound3 implementing0 referencing
1 example members folded in
Extraction exclusions are strict consumer input
spec:extraction.excludes
rule
6ready floor ready4 rules, 3 keyed0 entries0 declarations0 questions1 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
Graph claims retain their epistemic source
spec:extraction.claim-taxonomy
model
6ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound3 implementing0 referencing
The graph declares its schema version
spec:extraction.schema-versioning
rule
6ready floor ready2 rules, 1 keyed0 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
Bound examples execute their authored steps
spec:extraction.executable-examples
behavior
6ready floor ready4 rules, 4 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound6 implementing0 referencing
Serialization preserves authored entry order
spec:extraction.open-section-order
rule
6ready floor ready10 rules, 1 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
The graph records where each addressable entry is written
spec:extraction.entry-locations
behavior
6ready floor ready7 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound3 implementing1 referencing
The floor names what blocks the floor's next rung
spec:validation.next-rung-floor
rule
6ready floor ready5 rules0 entries0 declarations0 questions0 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
Mechanical code structure stays inferred and apart from curated intent
spec:consumers.impact-graph
behavior
6ready floor ready1 rules, 1 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
Runtime observations can close the liveness loop
spec:observation.runtime-overlay
behavior
6idea floor ideanext scoped:
  • kind-evidence-present · The kind's natural evidence is present (per-kind evidence table).
0 rules0 entries0 declarations1 questions, 1 blocking0 decisions0 of 0 verifying examples bound0 implementing0 referencing
A TypeScript-carried Spec can be converted to Markdown
spec:carrier.sdp-import
behavior
7ready floor ready9 rules2 entries2 declarations0 questions1 decisions1 of 1 verifying examples bound7 implementing0 referencing
1 example members folded in
Every prose value has one typed owner
spec:carrier.prose-ownership-rule
rule
7ready floor ready5 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
A Pack has a Markdown manifest carrier
spec:carrier.markdown-pack-authoring
behavior
7ready floor ready5 rules0 entries0 declarations0 questions2 decisions2 of 2 verifying examples bound3 implementing0 referencing
2 example members folded in
Gherkin authoring enters the one graph
spec:carrier.gherkin-authoring
behavior
7ready floor ready22 rules, 5 keyed1 entries0 declarations0 questions5 decisions13 of 13 verifying examples bound2 implementing0 referencing
13 example members folded in
The build derives step and space contracts from graph examples
spec:extraction.executable-contracts
behavior
7ready floor ready12 rules, 6 keyed6 entries5 declarations0 questions1 decisions7 of 7 verifying examples bound2 implementing0 referencing
3 example members folded in
Duplicate carrier IDs are excluded loudly
spec:validation.duplicate-ids
behavior
7ready floor ready2 rules0 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound2 implementing0 referencing
1 example members folded in
Every Spec id written in prose resolves
spec:validation.prose-mentions
rule
7ready floor ready11 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound2 implementing0 referencing
Graph claims and contracts stay distinct
spec:validation.claim-separation
rule
7ready floor ready2 rules0 entries0 declarations0 questions0 decisions2 of 2 verifying examples bound1 implementing0 referencing
2 example members folded in
A Spec shaped by a superseded decision warns
spec:validation.superseded-decision-signal
rule
7ready floor ready10 rules, 10 keyed10 entries7 declarations0 questions1 decisions9 of 9 verifying examples bound1 implementing0 referencing
9 example members folded in
File-level imports show where curation is missing
spec:consumers.impact-graph.curation-assist
behavior
7ready floor ready11 rules7 entries4 declarations0 questions1 decisions0 of 0 verifying examples bound3 implementing0 referencing
Exhaustive symbol reach waits for a language-neutral identity
spec:consumers.impact-graph.symbol-reach
behavior
7idea floor scopednext scoped: nothing blocks1 rules0 entries0 declarations1 questions, 1 blocking1 decisions0 of 0 verifying examples bound0 implementing0 referencing
Register questions stay executable graph recipes
spec:consumers.agent-surface.register-recipes
behavior
7ready floor ready12 rules, 2 keyed3 entries2 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
The Studio reads on a phone as on a desktop
spec:consumers.spec-studio.responsive
behavior
7ready floor ready1 rules3 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound2 implementing0 referencing
The Protocol authors and validates itself
spec:protocol.self-hosting
behavior
7ready floor ready2 rules0 entries0 declarations0 questions6 decisions0 of 0 verifying examples bound1 implementing0 referencing
The Design Review renders open-section entries as a list
spec:decisions.authored-entry-order
decision
7ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
The Design Review shows an open question's key
spec:decisions.question-key-rendering
decision
7ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
A bare .feature corpus can be imported
spec:carrier.sdp-import.feature-adapter
behavior
8idea floor ideanext scoped:
  • kind-evidence-present · The kind's natural evidence is present (per-kind evidence table).
0 rules0 entries0 declarations1 questions, 1 blocking0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Pinned declarations give an adopter a derived module to typecheck
spec:extraction.contract-declarations
behavior
8ready floor ready6 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound2 implementing0 referencing
A bound example runs its contract steps against a fresh world
spec:extraction.example-runner
behavior
8ready floor ready6 rules, 4 keyed1 entries1 declarations0 questions0 decisions2 of 2 verifying examples bound4 implementing0 referencing
2 example members folded in
A Pack node keeps its members in authored order
spec:extraction.pack-member-order
rule
8ready floor ready5 rules, 1 keyed0 entries0 declarations0 questions1 decisions1 of 1 verifying examples bound6 implementing0 referencing
1 example members folded in
The graph records where anchored source cites an entry address
spec:extraction.entry-citations
behavior
8ready floor ready10 rules, 10 keyed8 entries7 declarations0 questions0 decisions4 of 4 verifying examples bound4 implementing0 referencing
4 example members folded in
Design Review renders graph context without becoming a gate
spec:consumers.design-review
behavior
8ready floor ready12 rules, 4 keyed3 entries0 declarations0 questions5 decisions1 of 1 verifying examples bound2 implementing0 referencing
1 example members folded in
Authors move one Spec from intent to reviewed evidence
spec:consumers.authoring-on-ramp
behavior
8ready floor ready14 rules, 1 keyed0 entries0 declarations0 questions3 decisions0 of 0 verifying examples bound2 implementing0 referencing
Address resolution and dependency cycles stay executable graph recipes
spec:consumers.agent-surface.address-and-cycle-recipes
behavior
8ready floor ready9 rules, 4 keyed4 entries3 declarations0 questions0 decisions3 of 3 verifying examples bound1 implementing0 referencing
3 example members folded in
The engine's structural self-binding covers its architecturally significant units
spec:protocol.structural-self-binding
behavior
8ready floor ready8 rules, 8 keyed0 entries0 declarations0 questions2 decisions0 of 0 verifying examples bound1 implementing0 referencing
The Protocol organizes its own features in capability epics
spec:protocol.capability-epics
behavior
8ready floor ready4 rules, 4 keyed5 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
Enrichment keeps one Spec while its detail changes
spec:model.enrichment-lifecycle
model
9ready floor ready0 rules2 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
Derived runnable modules freeze the registrar interface
spec:extraction.runnable-modules
behavior
9ready floor ready16 rules7 entries5 declarations0 questions4 decisions0 of 0 verifying examples bound4 implementing0 referencing
One diagnostic currency, its location composed from structured fields
spec:validation.diagnostic-rendering
rule
9ready floor ready5 rules1 entries1 declarations0 questions0 decisions2 of 2 verifying examples bound4 implementing0 referencing
2 example members folded in
The package ships the Specs and on-ramps its skills cite
spec:consumers.shipped-protocol-corpus
behavior
9ready floor ready4 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
Derived readiness renders beside the stated rung and warns in one direction
spec:consumers.derived-readiness-banner
rule
9ready floor ready6 rules0 entries0 declarations0 questions0 decisions2 of 2 verifying examples bound1 implementing0 referencing
2 example members folded in
Views speak binding language, never the internal fact name
spec:consumers.binding-language-views
rule
9ready floor ready5 rules, 1 keyed0 entries0 declarations0 questions1 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
Every view run rewrites the view wholesale
spec:consumers.wholesale-view-rewrite
rule
9ready floor ready6 rules, 1 keyed0 entries0 declarations0 questions0 decisions4 of 4 verifying examples bound2 implementing0 referencing
4 example members folded in
The Pack context carries the Pack's design
spec:consumers.pack-design
behavior
9ready floor ready8 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
Validation re-runs while an author edits carriers
spec:consumers.validate-watch
behavior
9ready floor ready5 rules, 1 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A change proposal is addressed, based and checked before it lands
spec:consumers.intent-composition.proposal
contract
9ready floor ready9 rules7 entries2 declarations0 questions0 decisions0 of 0 verifying examples bound2 implementing0 referencing
The engine's architectural roles each name one pattern
spec:protocol.role-vocabulary
model
9ready floor ready0 rules5 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
What a Spec's design carries is derived, beside its readiness
spec:model.design-maturity
model
10ready floor ready0 rules0 entries0 declarations1 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
Corpus-authored rules run on the one validation path
spec:validation.corpus-rules
behavior
10ready floor ready16 rules, 10 keyed11 entries7 declarations0 questions1 decisions9 of 9 verifying examples bound3 implementing0 referencing
7 example members folded in
Census renders the runtime taxonomy without becoming a registry
spec:consumers.census-page
behavior
10ready floor ready13 rules0 entries0 declarations0 questions3 decisions0 of 0 verifying examples bound2 implementing0 referencing
Mermaid renders bounded one-hop and Pack diagrams without becoming a graph browser
spec:consumers.mermaid-view
behavior
10ready floor ready14 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound2 implementing0 referencing
Gherkin view renders any Spec as a disposable read shape
spec:consumers.gherkin-view
behavior
10ready floor ready10 rules0 entries0 declarations0 questions3 decisions0 of 0 verifying examples bound3 implementing0 referencing
An adopter learns graph homes, carrier grammar and shipped paths from the on-ramps
spec:consumers.adopter-on-ramp
behavior
10ready floor ready11 rules, 4 keyed0 entries0 declarations0 questions2 decisions0 of 0 verifying examples bound2 implementing0 referencing
The Studio renders from the reader's values and embeds only what its script reads
spec:consumers.spec-studio.data
contract
10ready floor ready4 rules, 4 keyed5 entries5 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
Design work reads its answers from catalog recipes
spec:consumers.agent-surface.design-recipes
behavior
10ready floor ready6 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A Pack is read from a named perspective
spec:consumers.review-perspectives
behavior
10ready floor ready8 rules, 1 keyed4 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
Recipe 49 renders a change proposal as the Markdown memo a person reviews
spec:consumers.intent-composition.proposal.memo
contract
10ready floor ready1 rules, 1 keyed5 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound2 implementing0 referencing
1 example members folded in
An Obsidian vault lets a person iterate on designs from the one graph
spec:consumers.obsidian-vault
behavior
10ready floor ready15 rules, 15 keyed13 entries5 declarations0 questions2 decisions9 of 9 verifying examples bound3 implementing0 referencing
9 example members folded in
The engine's accepted set covers its significant abstractions and only those
spec:protocol.significant-units-review
behavior
10ready floor ready7 rules, 7 keyed1 entries0 declarations0 questions2 decisions0 of 0 verifying examples bound1 implementing0 referencing
The Design Review's Pack page presents the Pack's design
spec:decisions.pack-design-page
decision
10ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing1 referencing
Declared architecture rules are checked against anchored structure
spec:validation.architecture-constraints
rule
11ready floor ready8 rules, 4 keyed6 entries3 declarations0 questions1 decisions3 of 3 verifying examples bound1 implementing0 referencing
3 example members folded in
A corpus checks the register tokens its prose cites
spec:validation.external-registers
behavior
11ready floor ready9 rules, 8 keyed8 entries7 declarations0 questions0 decisions2 of 2 verifying examples bound1 implementing0 referencing
2 example members folded in
Recipe answers fit an agent's context and explain their misses
spec:consumers.agent-surface.answer-shapes
behavior
11ready floor ready5 rules10 entries2 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing2 referencing
sdp studio publishes the Studio as one page set
spec:consumers.spec-studio.publisher
behavior
11ready floor ready10 rules, 10 keyed0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound5 implementing0 referencing
Five lenses read the graph as Packs, capabilities, architecture, tests and evidence
spec:consumers.spec-studio.lenses
behavior
11ready floor ready3 rules, 3 keyed1 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound4 implementing0 referencing
A composing panel on every page gathers scoped intent for an agent
spec:consumers.spec-studio.intent-panel
behavior
11ready floor ready11 rules, 8 keyed9 entries3 declarations0 questions0 decisions1 of 1 verifying examples bound5 implementing0 referencing
1 example members folded in
A page takes each recipe answer from the recipe's shipped body
spec:consumers.spec-studio.data.recipe-answers
contract
11ready floor ready2 rules, 2 keyed2 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing1 referencing
The glossary page lists every term the corpus's Specs define
spec:consumers.spec-studio.glossary-page
behavior
11ready floor ready4 rules, 4 keyed2 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
A Pack page shows where the Pack's design stands
spec:consumers.design-review.pack-design-page
behavior
11ready floor ready7 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing1 referencing
Example spaces report which values their examples cover
spec:consumers.agent-surface.example-space-coverage
behavior
11ready floor ready7 rules, 7 keyed7 entries5 declarations0 questions0 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
A context bundle is composed per invocation within a stated budget
spec:consumers.context-bundle
behavior
11ready floor ready19 rules, 9 keyed17 entries7 declarations0 questions1 decisions2 of 2 verifying examples bound1 implementing0 referencing
2 example members folded in
Every Spec, Pack, code unit and keyed term is a note, and every relation is a link
spec:consumers.obsidian-vault.notes
behavior
11ready floor ready12 rules, 12 keyed17 entries8 declarations0 questions0 decisions4 of 4 verifying examples bound3 implementing0 referencing
4 example members folded in
A Pack's members and the standing queries are tables over the reader's values
spec:consumers.obsidian-vault.bases
behavior
11ready floor ready6 rules, 6 keyed9 entries5 declarations0 questions0 decisions1 of 1 verifying examples bound2 implementing0 referencing
1 example members folded in
A design pass is followed and answered from the vault
spec:consumers.obsidian-vault.iteration
behavior
11ready floor ready6 rules, 6 keyed0 entries0 declarations0 questions0 decisions2 of 2 verifying examples bound3 implementing0 referencing
2 example members folded in
Delivery sessions route work from current graph state
spec:consumers.delivery-session-on-ramp
behavior
12ready floor ready10 rules, 1 keyed0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
The Studio's custom elements each hold one view the build renders
spec:consumers.spec-studio.components
contract
12ready floor ready6 rules, 5 keyed10 entries10 declarations0 questions3 decisions0 of 0 verifying examples bound11 implementing0 referencing
The Studio reads two named inputs beside the graph, a base graph and run records
spec:consumers.spec-studio.data.inputs
contract
12ready floor ready9 rules, 9 keyed2 entries2 declarations0 questions0 decisions2 of 2 verifying examples bound3 implementing0 referencing
2 example members folded in
sdp studio --watch rebuilds the page set on each carrier change
spec:consumers.spec-studio.publisher.watch
behavior
12ready floor ready1 rules, 1 keyed0 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The Packs lens groups every Spec by the Packs that hold it
spec:consumers.spec-studio.lenses.packs
behavior
12ready floor ready3 rules, 3 keyed1 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
The tests lens shows how far each Spec's verification reaches
spec:consumers.spec-studio.lenses.tests
behavior
12ready floor ready4 rules, 4 keyed3 entries0 declarations0 questions2 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The evidence lens names each source of runtime evidence and reads it as not tracked
spec:consumers.spec-studio.lenses.evidence
behavior
12ready floor ready3 rules, 3 keyed1 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
The vault skill teaches agents to keep an Obsidian vault of the graph
spec:consumers.vault-on-ramp
behavior
12ready floor ready7 rules, 7 keyed0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
Every verb answers --help, and one verb writes every projection root
spec:consumers.command-line
behavior
12ready floor ready6 rules, 6 keyed5 entries2 declarations0 questions1 decisions3 of 3 verifying examples bound4 implementing0 referencing
3 example members folded in
The next body of work is planned from the graph, not from a prose index
spec:consumers.graph-first-planning
behavior
13ready floor ready7 rules0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
The diff page shows what changed in the design since a base graph
spec:consumers.spec-studio.diff-page
behavior
13ready floor ready6 rules, 6 keyed4 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The runs page shows the run records the build was given, joined to test files
spec:consumers.spec-studio.runs-page
behavior
13ready floor ready7 rules, 7 keyed3 entries0 declarations0 questions1 decisions1 of 1 verifying examples bound2 implementing0 referencing
1 example members folded in
A diagram is laid out from graph values into SVG with a text equivalent
spec:consumers.spec-studio.diagrams
contract
13ready floor ready16 rules, 16 keyed14 entries4 declarations0 questions1 decisions3 of 3 verifying examples bound5 implementing0 referencing
3 example members folded in
The CLI names the engine that produced a result
spec:consumers.engine-provenance
behavior
13ready floor ready4 rules1 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound2 implementing0 referencing
An outside register is a named Studio input, so a cited token links to its entry
spec:consumers.spec-studio.register-input
behavior
13scoped floor scopednext defined:
  • no-blocking-open-questions · Spec has no blocking open question in intent.openQuestions.
3 rules, 3 keyed0 entries0 declarations3 questions, 2 blocking0 decisions0 of 0 verifying examples bound0 implementing0 referencing
A Studio build is stamped and shared from a static host
spec:consumers.spec-studio.sharing
behavior
14ready floor ready9 rules, 8 keyed9 entries3 declarations0 questions0 decisions1 of 1 verifying examples bound3 implementing0 referencing
1 example members folded in
The architecture lens draws components by context and layer, the planned beside the built
spec:consumers.spec-studio.lenses.architecture
behavior
14ready floor ready9 rules, 9 keyed5 entries1 declarations0 questions1 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The readiness planner orders the statements a person can make
spec:consumers.readiness-planner
behavior
14ready floor ready9 rules, 9 keyed6 entries4 declarations0 questions0 decisions4 of 4 verifying examples bound1 implementing0 referencing
4 example members folded in
The Studio chooses diagram kinds from graph values
spec:consumers.spec-studio.diagram-kinds
behavior
14ready floor ready5 rules, 5 keyed37 entries1 declarations0 questions1 decisions0 of 0 verifying examples bound9 implementing0 referencing
The Studio's shell frames every page with navigation, a rail and a canvas
spec:consumers.spec-studio.shell
behavior
15ready floor ready11 rules, 8 keyed5 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound4 implementing0 referencing
The architecture page lists each component's significant units by role
spec:consumers.spec-studio.lenses.architecture.unit-register
behavior
15ready floor ready5 rules, 5 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
Mermaid diagrams can be rooted at code units
spec:consumers.structural-mermaid
behavior
15scoped floor scopednext defined:
  • no-blocking-open-questions · Spec has no blocking open question in intent.openQuestions.
1 rules, 1 keyed0 entries0 declarations1 questions, 1 blocking1 decisions0 of 0 verifying examples bound0 implementing0 referencing
A diagram preserves readable labels before zoom
spec:consumers.spec-studio.diagram-kinds.legibility
contract
15ready floor ready2 rules, 2 keyed6 entries3 declarations0 questions0 decisions0 of 0 verifying examples bound3 implementing0 referencing
Edges route around boxes with deterministic orthogonal paths
spec:consumers.spec-studio.diagram-kinds.edge-routing
contract
15ready floor ready5 rules, 5 keyed6 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound2 implementing0 referencing
A refinement drawing follows the capability map
spec:consumers.spec-studio.diagram-kinds.capability-tree
behavior
15ready floor ready3 rules, 3 keyed5 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound2 implementing0 referencing
The maturity map is drawn as a grid of counts
spec:consumers.spec-studio.diagram-kinds.maturity-picture
behavior
15ready floor ready4 rules, 4 keyed6 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A requirement drawing separates intent from realization and verification
spec:consumers.spec-studio.diagram-kinds.requirement-trace
behavior
15ready floor ready3 rules, 3 keyed8 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound2 implementing0 referencing
A slice reads a Pack as one design, with the architecture it touches and what each member needs next
spec:consumers.design-slice
behavior
15ready floor ready18 rules, 18 keyed18 entries15 declarations0 questions2 decisions14 of 14 verifying examples bound1 implementing1 referencing
14 example members folded in
A roadmap orders the next bodies of work, and the graph says what each still needs
spec:consumers.roadmap
behavior
15ready floor ready17 rules, 17 keyed13 entries10 declarations0 questions1 decisions9 of 9 verifying examples bound1 implementing0 referencing
9 example members folded in
Roadmap views read releases, baselines and phases from git and the graph
spec:consumers.projections-model.roadmap-views
model
16scoped floor scopednext defined:
  • no-blocking-open-questions · Spec has no blocking open question in intent.openQuestions.
0 rules0 entries0 declarations1 questions, 1 blocking0 decisions0 of 0 verifying examples bound0 implementing0 referencing
The index says where the corpus stands and narrows every Spec
spec:consumers.spec-studio.index-page
behavior
16ready floor ready6 rules, 6 keyed7 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A Pack page shows the Pack's design as one card per member
spec:consumers.spec-studio.pack-page
behavior
16ready floor ready14 rules, 13 keyed7 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
Search finds a Spec, a Pack, an entry or a bound file by a word
spec:consumers.spec-studio.search
behavior
16ready floor ready8 rules, 5 keyed6 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound3 implementing0 referencing
A Spec page shows one Spec in collapsible panels, in a fixed order
spec:consumers.spec-studio.spec-page
behavior
16ready floor ready11 rules, 9 keyed10 entries0 declarations0 questions1 decisions1 of 1 verifying examples bound3 implementing0 referencing
1 example members folded in
The corpus's registers are pages a reviewer opens from a link
spec:consumers.spec-studio.registers
behavior
16ready floor ready9 rules, 9 keyed4 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The owner queue page orders the statements and questions only a person can settle
spec:consumers.spec-studio.owner-queue
behavior
16ready floor ready6 rules, 6 keyed2 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The upgrade kit shows a corpus what it could adopt
spec:consumers.upgrade-kit
behavior
16ready floor ready4 rules, 4 keyed2 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A dependency drawing shows the declared footing of a Spec set
spec:consumers.spec-studio.diagram-kinds.dependency
behavior
16ready floor ready5 rules, 5 keyed6 entries2 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A Spec set draws the architecture it touches
spec:consumers.spec-studio.diagram-kinds.scoped-architecture
behavior
16ready floor ready4 rules, 4 keyed5 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A roadmap renders as the forward section of a pull request description
spec:consumers.roadmap.memo
behavior
16ready floor ready7 rules, 7 keyed11 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound2 implementing0 referencing
A few custom elements filter, search, open and copy on a rendered page
spec:consumers.spec-studio.page-elements
contract
17ready floor ready5 rules, 5 keyed6 entries6 declarations0 questions1 decisions0 of 0 verifying examples bound7 implementing0 referencing
A Spec page's core shows the whole Spec, with an anchor for every entry
spec:consumers.spec-studio.spec-page.core
behavior
17ready floor ready9 rules, 8 keyed8 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
The panels for examples, targets, verifiers and evidence
spec:consumers.spec-studio.verification-panels
behavior
17ready floor ready6 rules, 6 keyed8 entries0 declarations0 questions2 decisions1 of 1 verifying examples bound2 implementing0 referencing
1 example members folded in
Every page of the page set is reached from the top navigation and the index
spec:consumers.spec-studio.navigation
behavior
17ready floor ready3 rules, 3 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound2 implementing0 referencing
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
17ready floor ready1 rules, 1 keyed1 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A Pack exports as one file, and every page prints as a document
spec:consumers.spec-studio.export
behavior
17ready floor ready8 rules, 8 keyed5 entries1 declarations0 questions0 decisions1 of 1 verifying examples bound4 implementing0 referencing
1 example members folded in
Capability adoption counts where each capability is used and where it could apply
spec:consumers.upgrade-kit.capability-adoption
behavior
17ready floor ready5 rules, 5 keyed6 entries4 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The rule-key proposal keys every unkeyed rule as a change proposal
spec:consumers.upgrade-kit.rule-key-proposal
behavior
17ready floor ready6 rules, 6 keyed9 entries6 declarations0 questions0 decisions2 of 2 verifying examples bound1 implementing0 referencing
2 example members folded in
The capability map page makes refinement readable by epic
spec:consumers.spec-studio.capability-map-page
behavior
17ready floor ready8 rules, 8 keyed6 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound4 implementing0 referencing
A slice page shows a Pack's design as one whole
spec:consumers.spec-studio.slice-page
behavior
17ready floor ready17 rules, 17 keyed12 entries0 declarations1 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
The roadmap page shows the upcoming work in priority order, split by what it needs
spec:consumers.spec-studio.roadmap-page
behavior
17ready floor ready13 rules, 13 keyed5 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A pinned declaration shows the words of each test line that cites it
spec:consumers.spec-studio.cited-line-text
behavior
17scoped floor scopednext defined:
  • no-blocking-open-questions · Spec has no blocking open question in intent.openQuestions.
3 rules, 3 keyed0 entries0 declarations2 questions, 1 blocking0 decisions0 of 0 verifying examples bound0 implementing0 referencing
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
17ready floor ready11 rules, 11 keyed3 entries2 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
The Studio skill teaches agents to publish, share and read the Spec Studio
spec:consumers.studio-on-ramp
behavior
18ready floor ready7 rules, 7 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A diagram offers Mermaid source as copyable text
spec:consumers.spec-studio.diagram-kinds.mermaid-source
behavior
18ready floor ready5 rules, 5 keyed6 entries0 declarations0 questions2 decisions0 of 0 verifying examples bound2 implementing0 referencing
The Protocol removes its frozen plans, review reports and superseded concept material
spec:protocol.delivery-record-cleanup
behavior
18idea floor ideanext scoped:
  • kind-evidence-present · The kind's natural evidence is present (per-kind evidence table).
0 rules0 entries0 declarations1 questions, 1 blocking1 decisions0 of 0 verifying examples bound0 implementing0 referencing

The architecture it touches

Anchored components and member designs

Arrows: uses (anchored).

The diagram as text
  • component:protocol.adapters: external runtime and source adapters, anchored, layer adapter, context protocol; satisfies members spec:extraction.executable-examples, spec:extraction.example-runner, spec:consumers.impact-graph, spec:consumers.impact-graph.curation-assist; references members none; code for rests on none; member designs none
  • component:protocol.cli: entry points, shared build and publication, anchored, layer edge, context protocol; satisfies members spec:carrier.sdp-import, spec:extraction.determinism, spec:extraction.build-pipeline, spec:extraction.regenerability, spec:validation.diagnostic-rendering, spec:validation.corpus-rules, spec:consumers.impact-graph.curation-assist, spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sink, spec:consumers.census-page, spec:consumers.mermaid-view, spec:consumers.gherkin-view, spec:consumers.authoring-on-ramp, spec:consumers.adopter-on-ramp, spec:consumers.wholesale-view-rewrite, spec:consumers.spec-studio, spec:consumers.spec-studio.publisher, spec:consumers.spec-studio.sharing, spec:consumers.spec-studio.data.inputs, spec:consumers.spec-studio.publisher.watch, spec:consumers.agent-surface.recipe-parameters, spec:consumers.engine-provenance, spec:consumers.validate-watch, spec:consumers.obsidian-vault, spec:consumers.obsidian-vault.iteration, spec:consumers.command-line; references members spec:decisions.vault-owned-folder; code for rests on none; member designs none
  • component:protocol.codegen: contracts and registrar output, anchored, layer application, context protocol; satisfies members spec:carrier.step-keys, spec:extraction.executable-examples, spec:extraction.executable-contracts, spec:extraction.runnable-modules; references members none; code for rests on none; member designs none
  • component:protocol.extract: the carrier and source pipeline, anchored, layer application, context protocol; satisfies members spec:carrier.markdown-authoring, spec:carrier.envelope-contract, spec:carrier.markdown-parser, spec:carrier.prose-ownership-rule, spec:carrier.markdown-pack-authoring, spec:carrier.markdown-body-grammar, spec:carrier.inline-code-spans, spec:carrier.gherkin-authoring, spec:carrier.step-keys, spec:model.anchors, spec:model.structural-patterns, spec:model.open-question-keys, spec:model.open-question-fields, spec:model.rule-keys, spec:model.relation-reasons, spec:model.term-addresses, spec:extraction.derive-graph, spec:extraction.determinism, spec:extraction.excludes, spec:extraction.claim-taxonomy, spec:extraction.open-section-order, spec:extraction.pack-member-order, spec:extraction.entry-locations, spec:extraction.entry-citations, spec:validation.duplicate-ids, spec:consumers.gherkin-view; references members spec:decisions.carrier-universality, spec:decisions.anchor-comment-form, spec:decisions.anchor-binding-grain, spec:decisions.roadmap-priority; code for rests on none; member designs none
  • component:protocol.graph: the one graph and its semantic decisions, anchored, layer domain, context protocol; satisfies members spec:extraction.derive-graph, spec:extraction.delivery-facts, spec:extraction.claim-taxonomy, spec:extraction.schema-versioning, spec:extraction.executable-examples, spec:extraction.executable-contracts, spec:extraction.entry-citations, spec:validation.prose-mentions, spec:validation.oracle-target-eligibility; references members spec:decisions.anchor-binding-grain; code for rests on none; member designs none
  • component:protocol.import: canonical conversion with a fidelity boundary, anchored, layer application, context protocol; satisfies members spec:carrier.sdp-import, spec:carrier.step-keys, spec:model.open-question-keys, spec:model.term-addresses; references members none; code for rests on none; member designs none
  • component:protocol.model: the authored contracts and stable ids, anchored, layer domain, context protocol; satisfies members spec:carrier.step-keys, spec:model.core-model, spec:model.spec-sections, spec:model.relations, spec:model.stable-ids, spec:model.pack-aggregate, spec:model.anchors, spec:model.open-question-keys, spec:model.term-addresses; references members spec:decisions.anchor-comment-form, spec:decisions.architectural-annotation, spec:decisions.roadmap-priority; code for rests on none; member designs none
  • component:protocol.notation: the leaf step codec, anchored, layer domain, context protocol; satisfies members spec:carrier.slot-notation; references members none; code for rests on none; member designs none
  • component:protocol.projections: read-only output, layout and owned publication, anchored, layer edge, context protocol; satisfies members spec:model.structural-patterns, spec:extraction.pack-member-order, spec:validation.diagnostic-rendering, spec:consumers.projections-model, spec:consumers.design-review, spec:consumers.census-page, spec:consumers.mermaid-view, spec:consumers.gherkin-view, spec:consumers.derived-readiness-banner, spec:consumers.binding-language-views, spec:consumers.spec-studio, spec:consumers.spec-studio.index-page, spec:consumers.spec-studio.pack-page, spec:consumers.spec-studio.publisher, spec:consumers.spec-studio.search, spec:consumers.spec-studio.data, spec:consumers.spec-studio.shell, spec:consumers.spec-studio.lenses, spec:consumers.spec-studio.spec-page, spec:consumers.spec-studio.spec-page.core, spec:consumers.spec-studio.verification-panels, spec:consumers.spec-studio.intent-panel, spec:consumers.spec-studio.components, spec:consumers.spec-studio.responsive, spec:consumers.spec-studio.data.recipe-answers, spec:consumers.spec-studio.data.inputs, spec:consumers.spec-studio.navigation, spec:consumers.spec-studio.lenses.packs, spec:consumers.spec-studio.lenses.architecture, spec:consumers.spec-studio.lenses.architecture.unit-register, spec:consumers.spec-studio.lenses.tests, spec:consumers.spec-studio.lenses.evidence, spec:consumers.spec-studio.pack-page.maturity-map, spec:consumers.spec-studio.registers, spec:consumers.spec-studio.owner-queue, spec:consumers.spec-studio.diff-page, spec:consumers.spec-studio.runs-page, spec:consumers.spec-studio.glossary-page, spec:consumers.spec-studio.diagrams, spec:consumers.spec-studio.export, spec:consumers.design-review.pack-design-page, spec:consumers.obsidian-vault, spec:consumers.obsidian-vault.notes, spec:consumers.obsidian-vault.bases, spec:consumers.obsidian-vault.iteration, spec:consumers.spec-studio.capability-map-page, spec:consumers.spec-studio.diagram-kinds, spec:consumers.spec-studio.diagram-kinds.legibility, spec:consumers.spec-studio.diagram-kinds.edge-routing, spec:consumers.spec-studio.diagram-kinds.mermaid-source, spec:consumers.spec-studio.diagram-kinds.dependency, spec:consumers.spec-studio.diagram-kinds.capability-tree, spec:consumers.spec-studio.diagram-kinds.scoped-architecture, spec:consumers.spec-studio.diagram-kinds.maturity-picture, spec:consumers.spec-studio.diagram-kinds.requirement-trace, spec:consumers.spec-studio.slice-page, spec:consumers.spec-studio.roadmap-page, spec:consumers.roadmap.memo, spec:observation.run-evidence; references members spec:consumers.spec-studio.data.recipe-answers, spec:consumers.design-review.pack-design-page, spec:consumers.design-slice, spec:decisions.studio-build-renders, spec:decisions.studio-diagram-renderer, spec:decisions.architectural-annotation, spec:decisions.pack-design-page, spec:decisions.vault-owned-folder; code for rests on none; member designs none
  • component:protocol.reader: the typed graph contract and body evaluator, anchored, layer application, context protocol; satisfies members spec:carrier.step-keys, spec:model.design-maturity, spec:extraction.contract-declarations, spec:extraction.pack-member-order, spec:extraction.entry-locations, spec:extraction.entry-citations, spec:validation.next-rung-floor, spec:consumers.agent-surface, spec:consumers.agent-surface.evaluation-sink, spec:consumers.reader, spec:consumers.spec-studio.search, spec:consumers.pack-design, spec:consumers.agent-surface.example-space-coverage; references members spec:extraction.entry-locations, spec:consumers.agent-surface.answer-shapes; code for rests on none; member designs none
  • component:protocol.runner: provider-neutral example execution, anchored, layer application, context protocol; satisfies members spec:carrier.step-keys, spec:extraction.executable-examples, spec:extraction.example-runner; references members none; code for rests on none; member designs none
  • component:protocol.studio-elements: optional browser behavior and proposal handoff, anchored, layer edge, context protocol; satisfies members spec:consumers.spec-studio.search, spec:consumers.spec-studio.page-elements, spec:consumers.spec-studio.intent-panel, spec:consumers.spec-studio.components, spec:consumers.spec-studio.responsive, spec:consumers.spec-studio.sharing, spec:consumers.spec-studio.diagrams, spec:consumers.spec-studio.export, spec:consumers.intent-composition.proposal, spec:consumers.intent-composition.proposal.memo, spec:consumers.spec-studio.capability-map-page, spec:consumers.spec-studio.diagram-kinds.legibility; references members spec:consumers.edit-model, spec:consumers.intent-composition, spec:decisions.studio-build-renders, spec:decisions.studio-diagram-renderer; code for rests on none; member designs none
  • component:protocol.testing: the generated registrar runtime, anchored, layer adapter, context protocol; satisfies members spec:extraction.executable-examples, spec:extraction.runnable-modules; references members none; code for rests on none; member designs none
  • component:protocol.validate: one finding currency and ordered checks, anchored, layer domain, context protocol; satisfies members spec:model.spec-sections, spec:model.anchors, spec:model.open-question-keys, spec:model.rule-keys, spec:model.term-addresses, spec:extraction.pack-member-order, spec:validation.readiness-floor, spec:validation.typed-dependency-floor, spec:validation.duplicate-ids, spec:validation.two-check-families, spec:validation.referential-integrity, spec:validation.prose-mentions, spec:validation.claim-separation, spec:validation.verification-linkage, spec:validation.unbound-example-posture, spec:validation.oracle-target-eligibility, spec:validation.pack-coherence, spec:validation.authored-honesty, spec:validation.warn-level-signals, spec:validation.kind-evidence, spec:validation.diagnostic-rendering, spec:validation.next-rung-floor, spec:validation.superseded-decision-signal; references members spec:decisions.anchor-binding-grain, spec:decisions.architectural-annotation; code for rests on none; member designs none
  • component:protocol.adapters uses component:protocol.runner · anchored
  • impl:protocol.example-runner-adapter uses impl:protocol.example-runner · anchored
  • component:protocol.cli uses component:protocol.adapters · anchored
  • component:protocol.cli uses component:protocol.codegen · anchored
  • component:protocol.cli uses component:protocol.extract · anchored
  • component:protocol.cli uses component:protocol.graph · anchored
  • impl:protocol.stamp-command uses impl:protocol.schema-version · anchored
  • component:protocol.cli uses component:protocol.import · anchored
  • component:protocol.cli uses component:protocol.model · anchored
  • component:protocol.cli uses component:protocol.projections · anchored
  • impl:protocol.vault-command uses component:protocol.projections · anchored
  • component:protocol.cli uses component:protocol.reader · anchored
  • component:protocol.cli uses component:protocol.validate · anchored
  • component:protocol.codegen uses component:protocol.graph · anchored
  • component:protocol.codegen uses component:protocol.notation · anchored
  • component:protocol.codegen uses component:protocol.reader · anchored
  • component:protocol.codegen uses component:protocol.validate · anchored
  • component:protocol.extract uses component:protocol.graph · anchored
  • impl:protocol.derive-graph uses impl:protocol.delivery-facts · anchored
  • component:protocol.extract uses component:protocol.model · anchored
  • component:protocol.extract uses component:protocol.notation · anchored
  • component:protocol.extract uses component:protocol.validate · anchored
  • component:protocol.graph uses component:protocol.model · anchored
  • component:protocol.graph uses component:protocol.notation · anchored
  • component:protocol.import uses component:protocol.extract · anchored
  • component:protocol.import uses component:protocol.notation · anchored
  • component:protocol.import uses component:protocol.validate · anchored
  • component:protocol.projections uses component:protocol.extract · anchored
  • impl:protocol.gherkin-view uses impl:protocol.gherkin-kind-policy · anchored
  • component:protocol.projections uses component:protocol.graph · anchored
  • component:protocol.projections uses component:protocol.model · anchored
  • component:protocol.projections uses component:protocol.notation · anchored
  • component:protocol.projections uses component:protocol.reader · anchored
  • impl:protocol.studio-recipes uses api:protocol.evaluate-body · anchored
  • impl:protocol.studio-recipes uses impl:protocol.reader · anchored
  • impl:protocol.vault-notes uses impl:protocol.reader · anchored
  • component:protocol.projections uses component:protocol.validate · anchored
  • component:protocol.reader uses component:protocol.graph · anchored
  • impl:protocol.reader uses impl:protocol.delivery-facts · anchored
  • component:protocol.reader uses component:protocol.model · anchored
  • component:protocol.reader uses component:protocol.notation · anchored
  • component:protocol.reader uses component:protocol.validate · anchored
  • impl:protocol.reader uses impl:protocol.next-rung-floor · anchored
  • component:protocol.runner uses component:protocol.notation · anchored
  • component:protocol.studio-elements uses component:protocol.projections · anchored
  • component:protocol.studio-elements uses component:protocol.reader · anchored
  • component:protocol.testing uses component:protocol.adapters · anchored
  • component:protocol.testing uses component:protocol.runner · anchored
  • component:protocol.validate uses component:protocol.graph · anchored
  • impl:protocol.authored-honesty-delivery-facts uses impl:protocol.delivery-facts · anchored
  • component:protocol.validate uses component:protocol.model · anchored
  • component:protocol.validate uses component:protocol.notation · anchored
  • impl:protocol.slimming-recipe implements spec:model.enrichment-lifecycle; no component
  • impl:protocol.structural-self-binding implements spec:model.structural-patterns; no component
  • impl:protocol.register-recipes implements spec:model.open-question-keys; no component
  • impl:protocol.planned-components-recipe implements spec:model.planned-architecture; no component
  • impl:protocol.curation-recipe references spec:model.planned-architecture; no component
  • impl:protocol.authoring-grammar-recipes implements spec:model.open-question-fields; no component
  • impl:protocol.authoring-grammar-recipes implements spec:model.rule-keys; no component
  • impl:protocol.authoring-grammar-recipes implements spec:model.relation-reasons; no component
  • impl:protocol.address-and-cycle-recipes implements spec:model.term-addresses; no component
  • impl:protocol.register-recipes implements spec:model.term-addresses; no component
  • impl:protocol.register-recipes implements spec:extraction.contract-declarations; no component
  • impl:protocol.entry-location-recipes implements spec:extraction.entry-locations; no component
  • impl:protocol.entry-citation-recipe implements spec:extraction.entry-citations; no component
  • impl:protocol.validator-probe-table implements spec:validation.validator-self-testing; no component
  • impl:protocol.validator-self-testing implements spec:validation.validator-self-testing; no component
  • impl:protocol.architecture-walk-recipe implements spec:validation.architecture-constraints; no component
  • impl:protocol.external-registers-recipe implements spec:validation.external-registers; no component
  • impl:protocol.curation-recipe implements spec:consumers.impact-graph.curation-assist; no component
  • impl:protocol.answer-shape-recipes implements spec:consumers.agent-surface.answer-shapes; no component
  • impl:protocol.authoring-grammar-recipes references spec:consumers.agent-surface.answer-shapes; no component
  • impl:protocol.authoring-on-ramp implements spec:consumers.authoring-on-ramp; no component
  • impl:protocol.reading-on-ramp implements spec:consumers.reading-on-ramp; no component
  • impl:protocol.delivery-session-on-ramp implements spec:consumers.delivery-session-on-ramp; no component
  • impl:protocol.authoring-recipes implements spec:consumers.agent-surface.authoring-recipes; no component
  • impl:protocol.register-recipes implements spec:consumers.agent-surface.register-recipes; no component
  • impl:protocol.graph-first-planning implements spec:consumers.graph-first-planning; no component
  • impl:protocol.adopter-on-ramp implements spec:consumers.adopter-on-ramp; no component
  • impl:protocol.shipped-protocol-corpus implements spec:consumers.shipped-protocol-corpus; no component
  • impl:protocol.address-and-cycle-recipes implements spec:consumers.agent-surface.address-and-cycle-recipes; no component
  • impl:protocol.studio-preview-workflow implements spec:consumers.spec-studio.sharing; no component
  • impl:protocol.studio-on-ramp implements spec:consumers.studio-on-ramp; no component
  • impl:protocol.recipe-parameters-catalog implements spec:consumers.agent-surface.recipe-parameters; no component
  • impl:protocol.design-recipes implements spec:consumers.agent-surface.design-recipes; no component
  • impl:protocol.example-space-coverage-recipe implements spec:consumers.agent-surface.example-space-coverage; no component
  • impl:protocol.perspective-filter-recipe implements spec:consumers.review-perspectives; no component
  • impl:protocol.context-bundle-recipe implements spec:consumers.context-bundle; no component
  • impl:protocol.design-diff-recipe implements spec:consumers.design-diff; no component
  • impl:protocol.proposal-schema-and-recipe implements spec:consumers.intent-composition.proposal; no component
  • impl:protocol.proposal-memo-recipe implements spec:consumers.intent-composition.proposal.memo; no component
  • impl:protocol.vault-on-ramp implements spec:consumers.vault-on-ramp; no component
  • impl:protocol.statement-queue-recipe implements spec:consumers.readiness-planner; no component
  • impl:protocol.upgrade-guide implements spec:consumers.upgrade-kit; no component
  • impl:protocol.capability-adoption-recipe implements spec:consumers.upgrade-kit.capability-adoption; no component
  • impl:protocol.rule-key-proposal-recipe implements spec:consumers.upgrade-kit.rule-key-proposal; no component
  • impl:protocol.capability-map-recipe implements spec:consumers.capability-map; no component
  • impl:protocol.design-slice-recipe implements spec:consumers.design-slice; no component
  • impl:protocol.roadmap-recipe implements spec:consumers.roadmap; no component
  • impl:protocol.roadmap-memo-recipe implements spec:consumers.roadmap.memo; no component
  • impl:protocol.run-evidence-recipe implements spec:observation.run-evidence; no component
  • impl:protocol.self-hosting implements spec:protocol.self-hosting; no component
  • impl:protocol.structural-self-binding implements spec:protocol.structural-self-binding; no component
  • impl:protocol.structural-self-binding implements spec:protocol.significant-units-review; no component
  • impl:protocol.role-vocabulary implements spec:protocol.role-vocabulary; no component
  • impl:protocol.capability-epics implements spec:protocol.capability-epics; no component
  • impl:protocol.roadmap-practice implements spec:protocol.roadmap-replaces-plans; no component
  • impl:protocol.capability-map-recipe references spec:decisions.epics-of-any-kind; no component
Mermaid source

Copyable source; the Studio draws static SVG.

Chosen syntax: block, with anchored component boxes and uses arrows.

Components the slice touches

ComponentLayer and contextReached through
component:protocol.adapters
external runtime and source adapters
adapter · protocolMembers its code satisfies: Bound examples execute their authored steps, A bound example runs its contract steps against a fresh world, Mechanical code structure stays inferred and apart from curated intent, File-level imports show where curation is missingMembers its code references: noneWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.cli
entry points, shared build and publication
edge · protocolMembers its code satisfies: A TypeScript-carried Spec can be converted to Markdown, Committed source derives byte-identical output, The build pipeline has one ordered flow, Generated artifacts are disposable projections, One diagnostic currency, its location composed from structured fields, Corpus-authored rules run on the one validation path, File-level imports show where curation is missing, Agents script a visible typed graph, The evaluation sink runs one body and prints its return, Census renders the runtime taxonomy without becoming a registry, Mermaid renders bounded one-hop and Pack diagrams without becoming a graph browser, Gherkin view renders any Spec as a disposable read shape, Authors move one Spec from intent to reviewed evidence, An adopter learns graph homes, carrier grammar and shipped paths from the on-ramps, Every view run rewrites the view wholesale, The Spec Studio is a static HTML workbench over the one graph, sdp studio publishes the Studio as one page set, A Studio build is stamped and shared from a static host, The Studio reads two named inputs beside the graph, a base graph and run records, sdp studio --watch rebuilds the page set on each carrier change, Recipes take parameters as data and ship as runnable files, The CLI names the engine that produced a result, Validation re-runs while an author edits carriers, An Obsidian vault lets a person iterate on designs from the one graph, A design pass is followed and answered from the vault, Every verb answers --help, and one verb writes every projection rootMembers its code references: The vault's generator owns one folder and synchronizes itWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.codegen
contracts and registrar output
application · protocolMembers its code satisfies: An example step may carry a key that survives rewording, Bound examples execute their authored steps, The build derives step and space contracts from graph examples, Derived runnable modules freeze the registrar interfaceMembers its code references: noneWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.extract
the carrier and source pipeline
application · protocolMembers its code satisfies: Markdown authoring enters the one graph, The Markdown envelope is explicit and bounded, The Markdown parser reifies the ruled subset, Every prose value has one typed owner, A Pack has a Markdown manifest carrier, The Markdown body accepts one closed form per section, Inline code is content, never markup, Gherkin authoring enters the one graph, An example step may carry a key that survives rewording, Source anchors bind code without carrying intent, Architecturally significant units are annotated where they are realized, An open question may carry a key that addresses it, An open question may name who decides it, its links, a provisional reading and a re-entry trigger, A rule or flow entry may carry a key that addresses it, An authored relation may carry its reason, A Model term may carry a key that addresses it, Carrier reification derives the one graph, Committed source derives byte-identical output, Extraction exclusions are strict consumer input, Graph claims retain their epistemic source, Serialization preserves authored entry order, A Pack node keeps its members in authored order, The graph records where each addressable entry is written, The graph records where anchored source cites an entry address, Duplicate carrier IDs are excluded loudly, Gherkin view renders any Spec as a disposable read shapeMembers its code references: Carrier universality is bounded by honest kind structure, The comment form is a second anchor representation, Bindings are optional, plural, and may reference a design, A roadmap states advisory priority in the graphWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.graph
the one graph and its semantic decisions
domain · protocolMembers its code satisfies: Carrier reification derives the one graph, Resolving bindings confer direct delivery facts, Graph claims retain their epistemic source, The graph declares its schema version, Bound examples execute their authored steps, The build derives step and space contracts from graph examples, The graph records where anchored source cites an entry address, Every Spec id written in prose resolves, Oracle eligibility follows example-space ownershipMembers its code references: Bindings are optional, plural, and may reference a designWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.import
canonical conversion with a fidelity boundary
application · protocolMembers its code satisfies: A TypeScript-carried Spec can be converted to Markdown, An example step may carry a key that survives rewording, An open question may carry a key that addresses it, A Model term may carry a key that addresses itMembers its code references: noneWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.model
the authored contracts and stable ids
domain · protocolMembers its code satisfies: An example step may carry a key that survives rewording, The Protocol models delivery with one enrichable Spec, Spec sections carry typed detail and direct verifier semantics, Specs declare typed directed relations, Stable IDs are the Protocol's durable join key, A Pack is a truth-free review aggregate, Source anchors bind code without carrying intent, An open question may carry a key that addresses it, A Model term may carry a key that addresses itMembers its code references: The comment form is a second anchor representation, Architectural significance is annotated where it is realized, A roadmap states advisory priority in the graphWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.notation
the leaf step codec
domain · protocolMembers its code satisfies: Slot notation declares, binds, and refuses to guessMembers its code references: noneWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.projections
read-only output, layout and owned publication
edge · protocolMembers its code satisfies: Architecturally significant units are annotated where they are realized, A Pack node keeps its members in authored order, One diagnostic currency, its location composed from structured fields, Projections fan out from one graph without becoming truth stores, Design Review renders graph context without becoming a gate, Census renders the runtime taxonomy without becoming a registry, Mermaid renders bounded one-hop and Pack diagrams without becoming a graph browser, Gherkin view renders any Spec as a disposable read shape, Derived readiness renders beside the stated rung and warns in one direction, Views speak binding language, never the internal fact name, The Spec Studio is a static HTML workbench over the one graph, The index says where the corpus stands and narrows every Spec, A Pack page shows the Pack's design as one card per member, sdp studio publishes the Studio as one page set, Search finds a Spec, a Pack, an entry or a bound file by a word, The Studio renders from the reader's values and embeds only what its script reads, The Studio's shell frames every page with navigation, a rail and a canvas, Five lenses read the graph as Packs, capabilities, architecture, tests and evidence, A Spec page shows one Spec in collapsible panels, in a fixed order, A Spec page's core shows the whole Spec, with an anchor for every entry, The panels for examples, targets, verifiers and evidence, A composing panel on every page gathers scoped intent for an agent, The Studio's custom elements each hold one view the build renders, The Studio reads on a phone as on a desktop, A page takes each recipe answer from the recipe's shipped body, The Studio reads two named inputs beside the graph, a base graph and run records, Every page of the page set is reached from the top navigation and the index, The Packs lens groups every Spec by the Packs that hold it, The architecture lens draws components by context and layer, the planned beside the built, The architecture page lists each component's significant units by role, The tests lens shows how far each Spec's verification reaches, The evidence lens names each source of runtime evidence and reads it as not tracked, A Pack page's maturity map places every member by its stated rung and its floor, The corpus's registers are pages a reviewer opens from a link, The owner queue page orders the statements and questions only a person can settle, The diff page shows what changed in the design since a base graph, The runs page shows the run records the build was given, joined to test files, The glossary page lists every term the corpus's Specs define, A diagram is laid out from graph values into SVG with a text equivalent, A Pack exports as one file, and every page prints as a document, A Pack page shows where the Pack's design stands, An Obsidian vault lets a person iterate on designs from the one graph, Every Spec, Pack, code unit and keyed term is a note, and every relation is a link, A Pack's members and the standing queries are tables over the reader's values, A design pass is followed and answered from the vault, The capability map page makes refinement readable by epic, The Studio chooses diagram kinds from graph values, A diagram preserves readable labels before zoom, Edges route around boxes with deterministic orthogonal paths, A diagram offers Mermaid source as copyable text, A dependency drawing shows the declared footing of a Spec set, A refinement drawing follows the capability map, A Spec set draws the architecture it touches, The maturity map is drawn as a grid of counts, A requirement drawing separates intent from realization and verification, A slice page shows a Pack's design as one whole, The roadmap page shows the upcoming work in priority order, split by what it needs, A roadmap renders as the forward section of a pull request description, CI run records are joined to verifiers in a viewMembers its code references: A page takes each recipe answer from the recipe's shipped body, A Pack page shows where the Pack's design stands, A slice reads a Pack as one design, with the architecture it touches and what each member needs next, The build renders every Studio view, and an element only enhances it, The engine lays out every Studio diagram as static SVG when the page set is built, Architectural significance is annotated where it is realized, The Design Review's Pack page presents the Pack's design, The vault's generator owns one folder and synchronizes itWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.reader
the typed graph contract and body evaluator
application · protocolMembers its code satisfies: An example step may carry a key that survives rewording, What a Spec's design carries is derived, beside its readiness, Pinned declarations give an adopter a derived module to typecheck, A Pack node keeps its members in authored order, The graph records where each addressable entry is written, The graph records where anchored source cites an entry address, The floor names what blocks the floor's next rung, Agents script a visible typed graph, The evaluation sink runs one body and prints its return, The reader bridges agent entry points to composable graph context, Search finds a Spec, a Pack, an entry or a bound file by a word, The Pack context carries the Pack's design, Example spaces report which values their examples coverMembers its code references: The graph records where each addressable entry is written, Recipe answers fit an agent's context and explain their missesWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.runner
provider-neutral example execution
application · protocolMembers its code satisfies: An example step may carry a key that survives rewording, Bound examples execute their authored steps, A bound example runs its contract steps against a fresh worldMembers its code references: noneWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.studio-elements
optional browser behavior and proposal handoff
edge · protocolMembers its code satisfies: Search finds a Spec, a Pack, an entry or a bound file by a word, A few custom elements filter, search, open and copy on a rendered page, A composing panel on every page gathers scoped intent for an agent, The Studio's custom elements each hold one view the build renders, The Studio reads on a phone as on a desktop, A Studio build is stamped and shared from a static host, A diagram is laid out from graph values into SVG with a text equivalent, A Pack exports as one file, and every page prints as a document, A change proposal is addressed, based and checked before it lands, Recipe 49 renders a change proposal as the Markdown memo a person reviews, The capability map page makes refinement readable by epic, A diagram preserves readable labels before zoomMembers its code references: Views compose scoped intent instead of patching canonical source, Composed intent hands off on one proposal shape, The build renders every Studio view, and an element only enhances it, The engine lays out every Studio diagram as static SVG when the page set is builtWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.testing
the generated registrar runtime
adapter · protocolMembers its code satisfies: Bound examples execute their authored steps, Derived runnable modules freeze the registrar interfaceMembers its code references: noneWhat the slice rests on, realized here: noneMember designs naming it: none
component:protocol.validate
one finding currency and ordered checks
domain · protocolMembers its code satisfies: Spec sections carry typed detail and direct verifier semantics, Source anchors bind code without carrying intent, An open question may carry a key that addresses it, A rule or flow entry may carry a key that addresses it, A Model term may carry a key that addresses it, A Pack node keeps its members in authored order, Stated readiness must clear its floor, A ready Spec rests only on settled dependencies, Duplicate carrier IDs are excluded loudly, Validation separates well-formedness from non-pretending, Every graph reference resolves, Every Spec id written in prose resolves, Graph claims and contracts stay distinct, Example verification and oracle bindings resolve honestly, An unbound example below ready is data, not a warning, Oracle eligibility follows example-space ownership, Packs are coherent aggregates, Machine truth is never authored, Missing connective evidence warns without failing, Each kind carries its own evidence, One diagnostic currency, its location composed from structured fields, The floor names what blocks the floor's next rung, A Spec shaped by a superseded decision warnsMembers its code references: Bindings are optional, plural, and may reference a design, Architectural significance is annotated where it is realizedWhat the slice rests on, realized here: noneMember designs naming it: none

Member component designs

None.

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

None.

Units bound to a member and to no component

Decisions in scope

DecisionRungIn the sliceShapesQuestions
Delivery nouns remain familiar without workflow gates
spec:decisions.adopt-the-nouns
ready floor readymemberAn open question may name who decides it, its links, a provisional reading and a re-entry trigger, The Protocol authors and validates itself0 open, 0 blocking
Adopted runnable registrars are committed
spec:decisions.adopted-registrars-committed
ready floor readymemberDerived runnable modules freeze the registrar interface0 open, 0 blocking
The agent front door is one evaluation sink over the exported reader
spec:decisions.agent-front-door
ready floor readymemberAgents script a visible typed graph, The evaluation sink runs one body and prints its return, The reader bridges agent entry points to composable graph context, The reading skill teaches agents to query the graph, Recipes take parameters as data and ship as runnable files, A context bundle is composed per invocation within a stated budget0 open, 0 blocking
Agents script the visible graph
spec:decisions.agent-surface-scripts-graph
ready floor readymemberAgents script a visible typed graph, The reader bridges agent entry points to composable graph context0 open, 0 blocking
Bindings are optional, plural, and may reference a design
spec:decisions.anchor-binding-grain
refines spec:decisions.shipped-projections-frozen
ready floor readymemberSource anchors bind code without carrying intent, Carrier reification derives the one graph, Design Review renders graph context without becoming a gate, Census renders the runtime taxonomy without becoming a registry, The reader bridges agent entry points to composable graph context, Authors move one Spec from intent to reviewed evidence, A slice reads a Pack as one design, with the architecture it touches and what each member needs next, The engine's structural self-binding covers its architecturally significant units, The engine's accepted set covers its significant abstractions and only those0 open, 0 blocking
The comment form is a second anchor representation
spec:decisions.anchor-comment-form
ready floor readymemberSpec sections carry typed detail and direct verifier semantics, Source anchors bind code without carrying intent, Derived runnable modules freeze the registrar interface, Authors move one Spec from intent to reviewed evidence0 open, 0 blocking
Architectural significance is annotated where it is realized
spec:decisions.architectural-annotation
refines spec:decisions.shipped-projections-frozen
ready floor readymemberSource anchors bind code without carrying intent, Architecturally significant units are annotated where they are realized, Components are designed ahead of their code, Declared architecture rules are checked against anchored structure, Corpus-authored rules run on the one validation path, File-level imports show where curation is missing, Design Review renders graph context without becoming a gate, Census renders the runtime taxonomy without becoming a registry, Authors move one Spec from intent to reviewed evidence, The architecture lens draws components by context and layer, the planned beside the built, The Pack context carries the Pack's design, A slice reads a Pack as one design, with the architecture it touches and what each member needs next, The engine's structural self-binding covers its architecturally significant units, The engine's accepted set covers its significant abstractions and only those, The engine's architectural roles each name one pattern0 open, 0 blocking
The Design Review renders open-section entries as a list
spec:decisions.authored-entry-order
refines spec:decisions.shipped-projections-frozen
ready floor readymemberDesign Review renders graph context without becoming a gate, A Spec page shows one Spec in collapsible panels, in a fixed order, A Spec page's core shows the whole Spec, with an anchor for every entry0 open, 0 blocking
Bindings state existence, not liveness
spec:decisions.binding-not-liveness
ready floor readymemberSource anchors bind code without carrying intent, Resolving bindings confer direct delivery facts, Derived runnable modules freeze the registrar interface, Machine truth is never authored, Views speak binding language, never the internal fact name, The panels for examples, targets, verifiers and evidence, The tests lens shows how far each Spec's verification reaches, The evidence lens names each source of runtime evidence and reads it as not tracked, The runs page shows the run records the build was given, joined to test files, CI run records are joined to verifiers in a view0 open, 0 blocking
Promoted evidence must carry its own evidence
spec:decisions.carried-evidence
ready floor readymemberStated readiness must clear its floor, Each kind carries its own evidence0 open, 0 blocking
Markdown is the default Spec carrier
spec:decisions.carrier-ruling
ready floor readymemberMarkdown authoring enters the one graph, A TypeScript-carried Spec can be converted to Markdown, The Markdown body accepts one closed form per section0 open, 0 blocking
Carrier universality is bounded by honest kind structure
spec:decisions.carrier-universality
refines spec:decisions.gherkin-carrier-option
ready floor readymemberGherkin authoring enters the one graph, Gherkin view renders any Spec as a disposable read shape0 open, 0 blocking
A Spec id written in prose is a checked mention
spec:decisions.checked-mentions
ready floor readymemberStable IDs are the Protocol's durable join key, An open question may carry a key that addresses it, A rule or flow entry may carry a key that addresses it, A Model term may carry a key that addresses it, Every Spec id written in prose resolves0 open, 0 blocking
Concept documents may dissolve after executable truth lands
spec:decisions.concept-docs-dissolve
ready floor readymemberThe Protocol authors and validates itself0 open, 0 blocking
Sections carry content while relations carry links
spec:decisions.content-only-sections
ready floor readymemberSpec sections carry typed detail and direct verifier semantics0 open, 0 blocking
Decision records state readiness from ratification evidence
spec:decisions.decision-readiness-posture
ready floor readymemberMissing connective evidence warns without failing, The reader bridges agent entry points to composable graph context, An adopter learns graph homes, carrier grammar and shipped paths from the on-ramps0 open, 0 blocking
The Protocol owns the envelope grammar
spec:decisions.envelope-grammar-posture
ready floor readymemberThe Markdown envelope is explicit and bounded0 open, 0 blocking
Capability epics keep kind independent of altitude
spec:decisions.epics-of-any-kind
ready floor readymemberThe capability map reads every epic and its refinement descendants, The Protocol organizes its own features in capability epics0 open, 0 blocking
Example realization stays evidence, not backlog work
spec:decisions.example-realization-posture
ready floor readymemberThe Protocol models delivery with one enrichable Spec0 open, 0 blocking
Consumer exclusions stay exact
spec:decisions.exclusion-contract
ready floor readymemberExtraction exclusions are strict consumer input0 open, 0 blocking
The Protocol is an executable meta-model
spec:decisions.executable-meta-model
ready floor readymemberThe Protocol authors and validates itself0 open, 0 blocking
Behavior and example Specs may use Gherkin canonically
spec:decisions.gherkin-carrier-option
refines spec:decisions.carrier-ruling
ready floor readymemberGherkin authoring enters the one graph0 open, 0 blocking
Readiness evidence follows the Spec kind
spec:decisions.kind-conditional-floor
ready floor readymemberStated readiness must clear its floor, Each kind carries its own evidence0 open, 0 blocking
MCP integration remains deferred
spec:decisions.mcp-deferred
ready floor readymemberProjections fan out from one graph without becoming truth stores0 open, 0 blocking
One Spec carries named delivery coordinates
spec:decisions.one-primitive
ready floor readymemberThe Protocol models delivery with one enrichable Spec0 open, 0 blocking
Validation follows one graph
spec:decisions.one-validation-path
ready floor readymemberCarrier reification derives the one graph, Validation separates well-formedness from non-pretending, The Protocol authors and validates itself0 open, 0 blocking
The Design Review's Pack page presents the Pack's design
spec:decisions.pack-design-page
refines spec:decisions.shipped-projections-frozen
ready floor readymemberA Pack page shows where the Pack's design stands0 open, 0 blocking
Packs have a Markdown manifest carrier
spec:decisions.pack-markdown-carrier
refines spec:decisions.carrier-ruling
ready floor readymemberA Pack has a Markdown manifest carrier, Gherkin authoring enters the one graph0 open, 0 blocking
Packs group review context without becoming truth
spec:decisions.pack-reified
ready floor readymemberA Pack is a truth-free review aggregate0 open, 0 blocking
Durable references lead with meaning
spec:decisions.plain-language-references
ready floor readymemberThe Protocol authors and validates itself0 open, 0 blocking
Planning truths live in ruled graph homes
spec:decisions.planning-truths-placement
ready floor readymemberSpecs declare typed directed relations, An open question may name who decides it, its links, a provisional reading and a re-entry trigger, A Spec shaped by a superseded decision warns, Exhaustive symbol reach waits for a language-neutral identity, Delivery sessions route work from current graph state, The next body of work is planned from the graph, not from a prose index, An adopter learns graph homes, carrier grammar and shipped paths from the on-ramps0 open, 0 blocking
Each example binds one point
spec:decisions.point-per-example
ready floor readymemberSpec sections carry typed detail and direct verifier semantics, The build derives step and space contracts from graph examples, Derived runnable modules freeze the registrar interface0 open, 0 blocking
Prose belongs to typed graph owners
spec:decisions.prose-ownership
ready floor readymemberEvery prose value has one typed owner, The Markdown body accepts one closed form per section, Gherkin authoring enters the one graph, An authored relation may carry its reason, Gherkin view renders any Spec as a disposable read shape0 open, 0 blocking
The meta-model is a software delivery protocol
spec:decisions.protocol-naming
ready floor readymemberThe Protocol authors and validates itself0 open, 0 blocking
The Design Review shows an open question's key
spec:decisions.question-key-rendering
refines spec:decisions.shipped-projections-frozen
ready floor readymemberDesign Review renders graph context without becoming a gate0 open, 0 blocking
Plan and review files stop carrying the delivery record once the roadmap and the pull request do
spec:decisions.roadmap-over-plans
refines spec:decisions.planning-truths-placement
ready floor readymemberThe Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests, The Protocol removes its frozen plans, review reports and superseded concept material0 open, 0 blocking
A roadmap states advisory priority in the graph
spec:decisions.roadmap-priority
refines spec:decisions.pack-markdown-carrier, spec:decisions.planning-truths-placement
ready floor readymemberA Pack has a Markdown manifest carrier, A Pack is a truth-free review aggregate, A Pack node keeps its members in authored order, Designs are compared between a base commit and the working tree at entry grain, A roadmap orders the next bodies of work, and the graph says what each still needs0 open, 0 blocking
Canonical Gherkin carriers use `.sdp.gherkin`
spec:decisions.sdp-gherkin-extension
refines spec:decisions.gherkin-carrier-option
ready floor readymemberGherkin authoring enters the one graph0 open, 0 blocking
Spec extensions identify the carrier without colliding with tests
spec:decisions.sdp-ts-extension
ready floor readymemberMarkdown authoring enters the one graph0 open, 0 blocking
The shipped projections stay frozen
spec:decisions.shipped-projections-frozen
ready floor readymemberAn example step may carry a key that survives rewording, A rule or flow entry may carry a key that addresses it, A Model term may carry a key that addresses it, Projections fan out from one graph without becoming truth stores, Design Review renders graph context without becoming a gate, Census renders the runtime taxonomy without becoming a registry, Mermaid renders bounded one-hop and Pack diagrams without becoming a graph browser, Gherkin view renders any Spec as a disposable read shape, The Spec Studio is a static HTML workbench over the one graph, sdp studio publishes the Studio as one page set, Mermaid diagrams can be rooted at code units, An Obsidian vault lets a person iterate on designs from the one graph, Every verb answers --help, and one verb writes every projection root, A diagram offers Mermaid source as copyable text0 open, 0 blocking
The build renders every Studio view, and an element only enhances it
spec:decisions.studio-build-renders
refines spec:decisions.studio-web-components
ready floor readymemberThe Spec Studio is a static HTML workbench over the one graph, The Studio's custom elements each hold one view the build renders0 open, 0 blocking
The engine lays out every Studio diagram as static SVG when the page set is built
spec:decisions.studio-diagram-renderer
refines spec:decisions.studio-web-components
ready floor readymemberThe Studio's custom elements each hold one view the build renders, A diagram is laid out from graph values into SVG with a text equivalent, The Studio chooses diagram kinds from graph values, A diagram offers Mermaid source as copyable text0 open, 0 blocking
The Studio renders HTML, and the HTML stays derived
spec:decisions.studio-html-surface
ready floor readymemberThe Spec Studio is a static HTML workbench over the one graph0 open, 0 blocking
The Studio is built from custom elements, not a framework
spec:decisions.studio-web-components
ready floor readymemberThe Spec Studio is a static HTML workbench over the one graph, A few custom elements filter, search, open and copy on a rendered page, The Studio's custom elements each hold one view the build renders0 open, 0 blocking
Floor-read sections are closed typed shapes
spec:decisions.typing-law
ready floor readymemberSpec sections carry typed detail and direct verifier semantics, Pinned declarations give an adopter a derived module to typecheck0 open, 0 blocking
The vault's generator owns one folder and synchronizes it
spec:decisions.vault-owned-folder
ready floor readymemberAn Obsidian vault lets a person iterate on designs from the one graph, The vault skill teaches agents to keep an Obsidian vault of the graph0 open, 0 blocking
Verification mode states posture, not realization
spec:decisions.verification-posture-not-realization
ready floor readymemberSpec sections carry typed detail and direct verifier semantics, The panels for examples, targets, verifiers and evidence, The tests lens shows how far each Spec's verification reaches0 open, 0 blocking

Open questions in scope

Where the slice meets the rest

Rests on (0)

None.

Rested on by (0)

None.

Verified by (0)

None.

Superseded by (0)

None.

Composing (0)

Composing needs the script.