An adopter at full speed
pack:adopter-speed-v1specs/adopter-speed.pack.sdp.mdDownload this Pack as one file
Where the design stands
- 59 members in authored reading order; no unresolved members.
- No members held below their stated next rung.
- No members waiting only for their author's statement.
- 115 design entries and 75 pinned declarations.
- No open questions and no blocking questions.
- 16 members with an implementation binding.
- No members with a design reference.
- 48 outside Specs the Pack rests on; 36 outside Specs rest on the Pack; 7 outside Specs verify it; no outside Specs supersede it.
Maturity map
59 members at stated ready and floor ready: full member list.
Stated readiness by floor reached
Outlined diagonal: matches. Right of diagonal: floor above statement. Left of diagonal: statement above floor.
Maturity map as text
| Stated rung / floor reached | floor none | floor idea | floor scoped | floor defined | floor ready |
|---|---|---|---|---|---|
| stated idea | — | — | — | — | — |
| stated scoped | — | — | — | — | — |
| stated defined | — | — | — | — | — |
| stated ready | — | — | — | — | 59 |
stated ready, floor ready · 59 members
- The evaluation sink runs one body and prints its return ·
spec:consumers.agent-surface.evaluation-sink· ready floor ready - A script holding a graph runs a shipped recipe through the exported evaluator ·
spec:consumers.agent-surface.evaluation-sink.exported-evaluator· ready floor ready - A body calls a shipped recipe and returns its answer unchanged ·
spec:consumers.agent-surface.evaluation-sink.recipe-call· ready floor ready - A call to a recipe the catalog does not hold fails the body ·
spec:consumers.agent-surface.evaluation-sink.unknown-recipe· ready floor ready - Corpus-authored rules run on the one validation path ·
spec:validation.corpus-rules· ready floor ready - Editing a parameter file starts a cycle that reads the new parameters ·
spec:validation.corpus-rules.params-edit-starts-a-cycle· ready floor ready - Rewriting a rules file under node_modules starts a cycle that runs the new body ·
spec:validation.corpus-rules.rules-edit-starts-a-cycle· ready floor ready - A parameter file that stops being JSON fails only its own rules file, and the watcher runs on ·
spec:validation.corpus-rules.unreadable-params-fail-one-file· ready floor ready - Validation re-runs while an author edits carriers ·
spec:consumers.validate-watch· ready floor ready - Address resolution and dependency cycles stay executable graph recipes ·
spec:consumers.agent-surface.address-and-cycle-recipes· ready floor ready - A dependency chain with no cycle yields no finding ·
spec:consumers.agent-surface.address-and-cycle-recipes.chain-reports-nothing· ready floor ready - The shipped dependency-cycles file fails a rules run on a cycle ·
spec:consumers.agent-surface.address-and-cycle-recipes.cycle-fails-a-rules-run· ready floor ready - The shipped address-resolution file fails a rules run on an address that names no entry ·
spec:consumers.agent-surface.address-and-cycle-recipes.unresolved-address-fails-a-rules-run· ready floor ready - A corpus checks the register tokens its prose cites ·
spec:validation.external-registers· ready floor ready - A held token no Spec cites fails a rules run only when the caller asks ·
spec:validation.external-registers.uncited-on-request· ready floor ready - A cited token the register lacks or retires fails a rules run ·
spec:validation.external-registers.unknown-and-retired· ready floor ready - Every verb answers --help, and one verb writes every projection root ·
spec:consumers.command-line· ready floor ready - A root that fails its check is removed while sdp generate writes the others ·
spec:consumers.command-line.generate-check-failure· ready floor ready - One run of sdp generate leaves all five roots current ·
spec:consumers.command-line.generate-writes-every-root· ready floor ready - A publisher's --help prints its help and touches no root ·
spec:consumers.command-line.verb-help-touches-nothing· ready floor ready - An example step may carry a key that survives rewording ·
spec:carrier.step-keys· ready floor ready - An example marker that disagrees with its vocabulary withholds the contract ·
spec:carrier.step-keys.conflicting-example-key-withheld· ready floor ready - A keyed Gherkin step keeps its binding across a rewording ·
spec:carrier.step-keys.gherkin-keyed-step-stays-bound· ready floor ready - A step key equal to another step's skeleton withholds the contract ·
spec:carrier.step-keys.key-equal-to-a-skeleton-withheld· ready floor ready - A step marker whose key is off the grammar refuses the carrier ·
spec:carrier.step-keys.malformed-marker-refused· ready floor ready - Renaming a step key breaks the binding ·
spec:carrier.step-keys.renamed-key-breaks· ready floor ready - One key on two vocabulary steps refuses the carrier ·
spec:carrier.step-keys.repeated-key-refused· ready floor ready - A keyed step reworded in its vocabulary and its example keeps its binding ·
spec:carrier.step-keys.reworded-keyed-step-stays-bound· ready floor ready - The same rewording without a key breaks the binding ·
spec:carrier.step-keys.reworded-unkeyed-step-breaks· ready floor ready - Two keys on one step refuse the carrier ·
spec:carrier.step-keys.two-keys-on-one-step-refused· ready floor ready - A keyed TypeScript step keeps its key through import to Markdown ·
spec:carrier.step-keys.typescript-keyed-step-imports-keyed· ready floor ready - The build derives step and space contracts from graph examples ·
spec:extraction.executable-contracts· ready floor ready - Derived runnable modules freeze the registrar interface ·
spec:extraction.runnable-modules· ready floor ready - A Model term may carry a key that addresses it ·
spec:model.term-addresses· ready floor ready - A keyed term is reified and its address resolves ·
spec:model.term-addresses.keyed-term-resolves· ready floor ready - A term marker whose key is off the grammar refuses its carrier ·
spec:model.term-addresses.malformed-term-marker-refused· ready floor ready - A term key repeated in one Spec refuses its carrier ·
spec:model.term-addresses.repeated-term-key-refused· ready floor ready - A keyed TypeScript term keeps its address through import to Markdown ·
spec:model.term-addresses.typescript-term-imports-keyed· ready floor ready - An address that names a term key no term carries is an error ·
spec:model.term-addresses.unknown-term-key-refused· ready floor ready - A Spec id written in prose is a checked mention ·
spec:decisions.checked-mentions· ready floor ready - The graph records where anchored source cites an entry address ·
spec:extraction.entry-citations· ready floor ready - A code file's comment cites a declaration without reading as a test line ·
spec:extraction.entry-citations.code-comment-cites-declaration· ready floor ready - A test title in an anchored file cites a pinned declaration ·
spec:extraction.entry-citations.test-title-cites-declaration· ready floor ready - A file that carries no anchor is not read for citations ·
spec:extraction.entry-citations.unanchored-file-unread· ready floor ready - A citation of an entry its Spec lacks reports through the recipe, never as a Protocol finding ·
spec:extraction.entry-citations.unresolved-citation· ready floor ready - A context bundle is composed per invocation within a stated budget ·
spec:consumers.context-bundle· ready floor ready - A member larger than the budget is named, and no part is returned ·
spec:consumers.context-bundle.oversized-member-named· ready floor ready - A Pack too large for one bundle reads whole in parts ·
spec:consumers.context-bundle.parts-cover-the-pack· ready floor ready - The readiness planner orders the statements a person can make ·
spec:consumers.readiness-planner· ready floor ready - Waiting Specs that rest on each other share a round and report a cycle ·
spec:consumers.readiness-planner.cycle-shares-a-round· ready floor ready - A waiting decision comes before the Spec it shapes ·
spec:consumers.readiness-planner.decision-first· ready floor ready - The Spec another rests on comes first in the queue ·
spec:consumers.readiness-planner.dependency-order· ready floor ready - An owner's blocking question lists the Specs it holds ·
spec:consumers.readiness-planner.owner-question-holds· ready floor ready - The upgrade kit shows a corpus what it could adopt ·
spec:consumers.upgrade-kit· ready floor ready - Capability adoption counts where each capability is used and where it could apply ·
spec:consumers.upgrade-kit.capability-adoption· ready floor ready - Capability adoption counts keyed rules and reasoned relations ·
spec:consumers.upgrade-kit.capability-adoption.counts-a-corpus· ready floor ready - The rule-key proposal keys every unkeyed rule as a change proposal ·
spec:consumers.upgrade-kit.rule-key-proposal· ready floor ready - Two rules that coin one key stay apart, and a rule with no ASCII word stays unkeyed ·
spec:consumers.upgrade-kit.rule-key-proposal.collision-and-unkeyable· ready floor ready - A rule-key proposal passes the proposal check and validates once applied ·
spec:consumers.upgrade-kit.rule-key-proposal.proposal-applies-clean· ready floor ready
Mermaid source
Preferred syntax: block. Fixed categorical cells; membership appears in comments.
Framing
What a corpus needs to move onto the Protocol's capabilities at scale and keep designing fast. First the reach of a body and a rules file: shipped recipes called as functions, recipes that answer as rules files, rules and parameter files watched, outside registers checked by pattern, help on every verb and one verb that writes every projection root. Then keys that survive rewording, for example steps and for Model terms, and the test lines that cite a pinned declaration. Then reading material that fits a budget in parts. Last, the order a person makes the waiting statements in, and the kit that shows a corpus what it could adopt next. Each Spec is followed by the examples that verify it.
Changed since the base
Compared with the base graph base b5e0a8b. Read the diff.
Base input: schema 0.12.0, 456 Specs.
Changed members
None.
Added members
None.
Pack membership
No membership or order change.
Members
1. The evaluation sink runs one body and prints its returnbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
spec:consumers.agent-surface.evaluation-sink
Design
7 design entries · 3 pinned declarations
Decisions
Open questions
None.
Implementation binding: present
api:protocol.evaluate-body· evaluates bodies and shipped recipes over one in-memory reader, graph and report ·src/reader/evaluate-body.ts:120· role service · component component:protocol.reader· layer application · context protocolimpl:protocol.build-pipeline-query· runQuery reads one body, derives the graph once for the reader, raw graph and report, and prints the return or refuses on stderr ·src/cli/q-command.ts:212· role service · component component:protocol.cli· layer edge · context protocol
Design reference: none
Verifier binding: present
5 verifiers, 5 enabled · 3 verifying examples, 3 enabled
2. A script holding a graph runs a shipped recipe through the exported evaluatorexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.agent-surface.evaluation-sink.exported-evaluator
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
3. A body calls a shipped recipe and returns its answer unchangedexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.agent-surface.evaluation-sink.recipe-call
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
4. A call to a recipe the catalog does not hold fails the bodyexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.agent-surface.evaluation-sink.unknown-recipe
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
5. Corpus-authored rules run on the one validation pathbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
Design
11 design entries · 7 pinned declarations
Decisions
- Architectural significance is annotated where it is realized · stated ready
Open questions
None.
Implementation binding: present
impl:protocol.corpus-rule-runner· runs selected corpus rules and separates their failures ·src/cli/corpus-rules.ts:65· role service · component component:protocol.cli· layer edge · context protocolimpl:protocol.corpus-rules· runs copied rule bodies after Protocol validation and composes the separate corpus report, output and exit ·src/cli/validate-view-command.ts:79· role service · component component:protocol.cli· layer edge · context protocolimpl:protocol.validate-watch· watches carrier directories and coalesces events into a pending validation rerun ·src/cli/validate-watch.ts:591· role service · component component:protocol.cli· layer edge · context protocol
Design reference: none
Verifier binding: present
9 verifiers, 9 enabled · 9 verifying examples, 9 enabled
6. Editing a parameter file starts a cycle that reads the new parametersexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:validation.corpus-rules.params-edit-starts-a-cycle
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
7. Rewriting a rules file under node_modules starts a cycle that runs the new bodyexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:validation.corpus-rules.rules-edit-starts-a-cycle
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
8. A parameter file that stops being JSON fails only its own rules file, and the watcher runs onexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:validation.corpus-rules.unreadable-params-fail-one-file
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
9. Validation re-runs while an author edits carriersbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: present
impl:protocol.validate-watch· watches carrier directories and coalesces events into a pending validation rerun ·src/cli/validate-watch.ts:591· role service · component component:protocol.cli· layer edge · context protocol
Design reference: none
Verifier binding: present
2 verifiers, 2 enabled · no verifying examples, 0 enabled
10. Address resolution and dependency cycles stay executable graph recipesbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
spec:consumers.agent-surface.address-and-cycle-recipes
Design
4 design entries · 3 pinned declarations
Open questions
None.
Implementation binding: present
impl:protocol.address-and-cycle-recipes· asserts realization of the shipped address resolution and dependency cycle recipes ·test/recipes.test.ts:3568
Design reference: none
Verifier binding: present
4 verifiers, 4 enabled · 3 verifying examples, 3 enabled
11. A dependency chain with no cycle yields no findingexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.agent-surface.address-and-cycle-recipes.chain-reports-nothing
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
12. The shipped dependency-cycles file fails a rules run on a cycleexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.agent-surface.address-and-cycle-recipes.cycle-fails-a-rules-run
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
13. The shipped address-resolution file fails a rules run on an address that names no entryexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.agent-surface.address-and-cycle-recipes.unresolved-address-fails-a-rules-run
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
14. A corpus checks the register tokens its prose citesbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
spec:validation.external-registers
Design
8 design entries · 7 pinned declarations
Open questions
None.
Implementation binding: present
impl:protocol.external-registers-recipe· asserts realization of the shipped external-registers recipe ·test/external-registers.test.ts:9
Design reference: none
Verifier binding: present
2 verifiers, 2 enabled · 2 verifying examples, 2 enabled
15. A held token no Spec cites fails a rules run only when the caller asksexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:validation.external-registers.uncited-on-request
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
16. A cited token the register lacks or retires fails a rules runexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:validation.external-registers.unknown-and-retired
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
17. Every verb answers --help, and one verb writes every projection rootbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
Design
5 design entries · 2 pinned declarations
Decisions
- The shipped projections stay frozen · stated ready
Open questions
None.
Implementation binding: present
impl:protocol.adopter-help· SDP_HELP_TEXT indexes the shipped skills, recipe catalog, schema, walkthrough, glossary and specs/ by package-relative path ·src/cli/help.ts:167· role projection · component component:protocol.cli· layer edge · context protocolimpl:protocol.agent-surface-cli· CLI verb dispatcher and agent-surface front of the package CLI ·src/cli/sdp.ts:94· role service · component component:protocol.cli· layer edge · context protocolimpl:protocol.build-args· shared build arguments and corpus-rule inputs ·src/cli/build-args.ts:11· role codec · component component:protocol.cli· layer edge · context protocolimpl:protocol.generate-command· prepares all prior roots before one shared build and publishes with each verb's checks ·src/cli/generate-command.ts:34· role publisher · component component:protocol.cli· layer edge · context protocol
Design reference: none
Verifier binding: present
3 verifiers, 3 enabled · 3 verifying examples, 3 enabled
18. A root that fails its check is removed while sdp generate writes the othersexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.command-line.generate-check-failure
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
19. One run of sdp generate leaves all five roots currentexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.command-line.generate-writes-every-root
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
20. A publisher's --help prints its help and touches no rootexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.command-line.verb-help-touches-nothing
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
21. An example step may carry a key that survives rewordingrule · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
Design
9 design entries · 7 pinned declarations
Decisions
- The shipped projections stay frozen · stated ready
Open questions
None.
Implementation binding: present
impl:protocol.example-runner· plans and executes a bound example against the caller's world ·src/runner/index.ts:108· role service · component component:protocol.runner· layer application · context protocolimpl:protocol.example-space-decoding· shared example-space interpretation for contracts and reader contexts ·src/notation/example-space.ts:473· role codec · component component:protocol.reader· layer application · context protocolimpl:protocol.executable-contracts· derives step and example-space contracts from the graph ·src/codegen/contracts.ts:647· role projection · component component:protocol.codegen· layer application · context protocolimpl:protocol.key-markers· normalizes step and term markers across the three carriers ·src/extract/key-markers.ts:136· role codec · component component:protocol.extract· layer application · context protocolimpl:protocol.open-section-order· preserves authored open-section and model-term order and Pack field order ·src/extract/serialize.ts:105· role codec · component component:protocol.extract· layer application · context protocolimpl:protocol.sdp-import-markdown-emit· emits the Markdown document twin for an imported Spec ·src/import/emit-markdown.ts:253· role codec · component component:protocol.import· layer application · context protocolimpl:protocol.spec-sections· typed Spec section shapes ·src/model/sections.ts:138· role contract · component component:protocol.model· layer domain · context protocol
Design reference: none
Verifier binding: present
11 verifiers, 11 enabled · 10 verifying examples, 10 enabled
22. An example marker that disagrees with its vocabulary withholds the contractexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:carrier.step-keys.conflicting-example-key-withheld
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
23. A keyed Gherkin step keeps its binding across a rewordingexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:carrier.step-keys.gherkin-keyed-step-stays-bound
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
24. A step key equal to another step's skeleton withholds the contractexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:carrier.step-keys.key-equal-to-a-skeleton-withheld
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
25. A step marker whose key is off the grammar refuses the carrierexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:carrier.step-keys.malformed-marker-refused
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
26. Renaming a step key breaks the bindingexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:carrier.step-keys.renamed-key-breaks
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
27. One key on two vocabulary steps refuses the carrierexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:carrier.step-keys.repeated-key-refused
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
28. A keyed step reworded in its vocabulary and its example keeps its bindingexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:carrier.step-keys.reworded-keyed-step-stays-bound
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
29. The same rewording without a key breaks the bindingexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:carrier.step-keys.reworded-unkeyed-step-breaks
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
30. Two keys on one step refuse the carrierexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:carrier.step-keys.two-keys-on-one-step-refused
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
31. A keyed TypeScript step keeps its key through import to Markdownexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:carrier.step-keys.typescript-keyed-step-imports-keyed
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
32. The build derives step and space contracts from graph examplesbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
spec:extraction.executable-contracts
Design
6 design entries · 5 pinned declarations
Decisions
- Each example binds one point · stated ready
Open questions
None.
Implementation binding: present
impl:protocol.example-space· resolves example-space vocabulary for contracts and floors ·src/graph/example-space.ts:117· role decider · component component:protocol.graph· layer domain · context protocolimpl:protocol.executable-contracts· derives step and example-space contracts from the graph ·src/codegen/contracts.ts:647· role projection · component component:protocol.codegen· layer application · context protocol
Design reference: none
Verifier binding: present
7 verifiers, 7 enabled · 7 verifying examples, 7 enabled
33. Derived runnable modules freeze the registrar interfacebehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
spec:extraction.runnable-modules
Design
7 design entries · 5 pinned declarations
Decisions
- Adopted runnable registrars are committed · stated ready
- The comment form is a second anchor representation · stated ready
- Bindings state existence, not liveness · stated ready
- Each example binds one point · stated ready
Open questions
None.
Implementation binding: present
component:protocol.codegen· contracts and registrar output ·src/codegen/contracts.ts:633· role projection · layer application · context protocol component:protocol.testing· the generated registrar runtime ·src/testing/index.ts:38· role adapter · layer adapter · context protocol impl:protocol.example-testing-helpers· adapter-lifecycle and oracle-comparison helpers for bound examples ·src/testing/index.ts:50· role adapter · component component:protocol.testing· layer adapter · context protocolimpl:protocol.runnable-modules· derives and publishes runnable registrar modules from the graph ·src/codegen/contracts.ts:658· role projection · component component:protocol.codegen· layer application · context protocol
Design reference: none
Verifier binding: present
3 verifiers, 3 enabled · no verifying examples, 0 enabled
34. A Model term may carry a key that addresses itrule · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
Design
10 design entries · 7 pinned declarations
Decisions
- A Spec id written in prose is a checked mention · stated ready
- The shipped projections stay frozen · stated ready
Open questions
None.
Implementation binding: present
impl:protocol.address-and-cycle-recipes· asserts realization of the shipped address resolution and dependency cycle recipes ·test/recipes.test.ts:3568impl:protocol.entry-locations· builds the carrier entry location table ·src/extract/derive.ts:78· role extractor · component component:protocol.extract· layer application · context protocolimpl:protocol.key-markers· normalizes step and term markers across the three carriers ·src/extract/key-markers.ts:136· role codec · component component:protocol.extract· layer application · context protocolimpl:protocol.open-section-order· preserves authored open-section and model-term order and Pack field order ·src/extract/serialize.ts:105· role codec · component component:protocol.extract· layer application · context protocolimpl:protocol.prose-mentions· checks that prose mentions resolve and warns once per unbacked Spec pair ·src/validate/validators.ts:1370· role validator · component component:protocol.validate· layer domain · context protocolimpl:protocol.register-recipes· asserts realization of the shipped register recipes ·test/recipes.test.ts:2057impl:protocol.sdp-import-markdown-emit· emits the Markdown document twin for an imported Spec ·src/import/emit-markdown.ts:253· role codec · component component:protocol.import· layer application · context protocolimpl:protocol.spec-sections· typed Spec section shapes ·src/model/sections.ts:138· role contract · component component:protocol.model· layer domain · context protocolimpl:protocol.stable-ids· stable ID grammar parser ·src/ids.ts:173· role codec · component component:protocol.model· layer domain · context protocol
Design reference: none
Verifier binding: present
6 verifiers, 6 enabled · 5 verifying examples, 5 enabled
35. A keyed term is reified and its address resolvesexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:model.term-addresses.keyed-term-resolves
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
36. A term marker whose key is off the grammar refuses its carrierexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:model.term-addresses.malformed-term-marker-refused
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
37. A term key repeated in one Spec refuses its carrierexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:model.term-addresses.repeated-term-key-refused
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
38. A keyed TypeScript term keeps its address through import to Markdownexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:model.term-addresses.typescript-term-imports-keyed
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
39. An address that names a term key no term carries is an errorexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:model.term-addresses.unknown-term-key-refused
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
40. A Spec id written in prose is a checked mentiondecision · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding none
spec:decisions.checked-mentions
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: none
41. The graph records where anchored source cites an entry addressbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
spec:extraction.entry-citations
Design
8 design entries · 7 pinned declarations
Open questions
None.
Implementation binding: present
impl:protocol.entry-address-resolution· resolves entry addresses for prose validation and citation readers ·src/graph/entry-address.ts:6· role reader · component component:protocol.graph· layer domain · context protocolimpl:protocol.entry-citation-reader· resolves citations and joins file anchors with direct and example-based test verification ·src/reader/entry-citations.ts:19· role reader · component component:protocol.reader· layer application · context protocolimpl:protocol.entry-citation-recipe· asserts realization of Entry citations in docs/agent-surface/recipes.md ·test/recipes.test.ts:7008impl:protocol.entry-citation-scan· records prose-mention tokens with addresses in anchored source files ·src/extract/entry-citations.ts:6· role extractor · component component:protocol.extract· layer application · context protocol
Design reference: none
Verifier binding: present
4 verifiers, 4 enabled · 4 verifying examples, 4 enabled
42. A code file's comment cites a declaration without reading as a test lineexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:extraction.entry-citations.code-comment-cites-declaration
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
43. A test title in an anchored file cites a pinned declarationexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:extraction.entry-citations.test-title-cites-declaration
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
44. A file that carries no anchor is not read for citationsexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:extraction.entry-citations.unanchored-file-unread
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
45. A citation of an entry its Spec lacks reports through the recipe, never as a Protocol findingexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:extraction.entry-citations.unresolved-citation
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
46. A context bundle is composed per invocation within a stated budgetbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
Design
17 design entries · 7 pinned declarations
Decisions
Open questions
None.
Implementation binding: present
impl:protocol.context-bundle-recipe· realizes the context bundle in the shipped recipe catalog ·test/iteration-recipes.test.ts:765· role projection
Design reference: none
Verifier binding: present
3 verifiers, 3 enabled · 2 verifying examples, 2 enabled
47. A member larger than the budget is named, and no part is returnedexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.context-bundle.oversized-member-named
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
48. A Pack too large for one bundle reads whole in partsexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.context-bundle.parts-cover-the-pack
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
49. The readiness planner orders the statements a person can makebehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
spec:consumers.readiness-planner
Design
6 design entries · 4 pinned declarations
Open questions
None.
Implementation binding: present
impl:protocol.statement-queue-recipe· realizes the statement queue in the shipped recipe catalog ·test/self-hosting-readiness-planner.test.ts:74· role projection
Design reference: none
Verifier binding: present
4 verifiers, 4 enabled · 4 verifying examples, 4 enabled
51. A waiting decision comes before the Spec it shapesexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.readiness-planner.decision-first
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
52. The Spec another rests on comes first in the queueexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.readiness-planner.dependency-order
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
53. An owner's blocking question lists the Specs it holdsexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.readiness-planner.owner-question-holds
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
54. The upgrade kit shows a corpus what it could adoptbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
Design
2 design entries · 1 pinned declaration
Open questions
None.
Implementation binding: present
impl:protocol.upgrade-guide· realizes the shipped upgrade guide document ·test/upgrade-kit.test.ts:87
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
55. Capability adoption counts where each capability is used and where it could applybehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
spec:consumers.upgrade-kit.capability-adoption
Design
6 design entries · 4 pinned declarations
Open questions
None.
Implementation binding: present
impl:protocol.capability-adoption-recipe· realizes capability adoption in the shipped recipe catalog ·test/upgrade-kit.test.ts:514· role projection
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · 1 verifying example, 1 enabled
56. Capability adoption counts keyed rules and reasoned relationsexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.upgrade-kit.capability-adoption.counts-a-corpus
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
57. The rule-key proposal keys every unkeyed rule as a change proposalbehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding present · verifier binding present
spec:consumers.upgrade-kit.rule-key-proposal
Design
9 design entries · 6 pinned declarations
Open questions
None.
Implementation binding: present
impl:protocol.rule-key-proposal-recipe· realizes the rule-key proposal in the shipped recipe catalog ·test/upgrade-kit.test.ts:742· role projection
Design reference: none
Verifier binding: present
2 verifiers, 2 enabled · 2 verifying examples, 2 enabled
58. Two rules that coin one key stay apart, and a rule with no ASCII word stays unkeyedexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.upgrade-kit.rule-key-proposal.collision-and-unkeyable
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
59. A rule-key proposal passes the proposal check and validates once appliedexample · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present
spec:consumers.upgrade-kit.rule-key-proposal.proposal-applies-clean
Design
No design entries · no pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: present
1 verifier, 1 enabled · no verifying examples, 0 enabled
Boundary
Rests on (48)
Rested on by (36)
Verified by (7)
Superseded by (0)
None.
Members with no verifier binding
The graph records bindings and never runs. Decision records are left out: a decision never needs a verifier binding. The runs page, the tests lens and the Spec pages of the Specs their files verify show the run records as external evidence from test files.
None.
Findings
None.
Composing (0)
Composing needs the script.