Design slice: An adopter at full speed
pack:adopter-speed-v1Read the Pack member by member
The design as a whole
- 59 members; 42 example members counted in their parents.
- 58 relations among members; deepest depth 5; 0 cycles.
- 0 members held below their stated next rung; 0 waiting only for their author.
- 48 outside Specs the slice rests on; 0 hold a member; 36 outside Specs rest on it.
- 14 components touched: 10 through members' code, 14 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.
- 8 decisions in scope; 0 state below ready.
- 0 open questions; 0 blocking.
Members read with the ones others rest on first. The columns count the design each member carries beside its rung; they never judge whether it is enough. This page records no review and approves nothing.
How the members rest on each other
Depths are structural, never phases, dates or priority. Dashed relations order nothing. The text keeps every member and original relation.
Shown as text: this drawing exceeds the height budget of 2000 pixels after folding.
The diagram as text
- spec:consumers.agent-surface.evaluation-sink: The evaluation sink runs one body and prints its return, depth 1, stated ready, floor ready
- spec:consumers.agent-surface.evaluation-sink.exported-evaluator: A script holding a graph runs a shipped recipe through the exported evaluator, depth 2, stated ready, floor ready; example folded into spec:consumers.agent-surface.evaluation-sink
- spec:consumers.agent-surface.evaluation-sink.recipe-call: A body calls a shipped recipe and returns its answer unchanged, depth 2, 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 2, stated ready, floor ready; example folded into spec:consumers.agent-surface.evaluation-sink
- spec:validation.corpus-rules: Corpus-authored rules run on the one validation path, depth 2, stated ready, floor ready
- spec:validation.corpus-rules.params-edit-starts-a-cycle: Editing a parameter file starts a cycle that reads the new parameters, depth 3, 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 3, 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 3, stated ready, floor ready; example folded into spec:validation.corpus-rules
- spec:consumers.validate-watch: Validation re-runs while an author edits carriers, depth 1, stated ready, floor ready
- spec:consumers.agent-surface.address-and-cycle-recipes: Address resolution and dependency cycles stay executable graph recipes, depth 3, stated ready, floor ready
- spec:consumers.agent-surface.address-and-cycle-recipes.chain-reports-nothing: A dependency chain with no cycle yields no finding, depth 4, stated ready, floor ready; example folded into spec:consumers.agent-surface.address-and-cycle-recipes
- 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 4, 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 4, stated ready, floor ready; example folded into spec:consumers.agent-surface.address-and-cycle-recipes
- spec:validation.external-registers: A corpus checks the register tokens its prose cites, depth 3, stated ready, floor ready
- spec:validation.external-registers.uncited-on-request: A held token no Spec cites fails a rules run only when the caller asks, depth 4, stated ready, floor ready; example folded into spec:validation.external-registers
- spec:validation.external-registers.unknown-and-retired: A cited token the register lacks or retires fails a rules run, depth 4, stated ready, floor ready; example folded into spec:validation.external-registers
- spec:consumers.command-line: Every verb answers --help, and one verb writes every projection root, depth 1, 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 2, 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 2, 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 2, stated ready, floor ready; example folded into spec:consumers.command-line
- spec:carrier.step-keys: An example step may carry a key that survives rewording, depth 1, stated ready, floor ready
- spec:carrier.step-keys.conflicting-example-key-withheld: An example marker that disagrees with its vocabulary withholds the contract, depth 2, 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 2, 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 2, 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 2, 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 2, 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 2, stated ready, floor ready; example folded into spec:carrier.step-keys
- spec:carrier.step-keys.reworded-keyed-step-stays-bound: A keyed step reworded in its vocabulary and its example keeps its binding, depth 2, 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 2, 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 2, 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 2, stated ready, floor ready; example folded into spec:carrier.step-keys
- spec:extraction.executable-contracts: The build derives step and space contracts from graph examples, depth 2, stated ready, floor ready
- spec:extraction.runnable-modules: Derived runnable modules freeze the registrar interface, depth 3, stated ready, floor ready
- spec:model.term-addresses: A Model term may carry a key that addresses it, depth 2, stated ready, floor ready
- spec:model.term-addresses.keyed-term-resolves: A keyed term is reified and its address resolves, depth 3, 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 3, 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 3, 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 3, 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 3, stated ready, floor ready; example folded into spec:model.term-addresses
- spec:decisions.checked-mentions: A Spec id written in prose is a checked mention, depth 1, stated ready, floor ready
- spec:extraction.entry-citations: The graph records where anchored source cites an entry address, depth 1, 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 2, 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 2, 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 2, 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 2, stated ready, floor ready; example folded into spec:extraction.entry-citations
- spec:consumers.context-bundle: A context bundle is composed per invocation within a stated budget, depth 1, stated ready, floor ready
- spec:consumers.context-bundle.oversized-member-named: A member larger than the budget is named, and no part is returned, depth 2, stated ready, floor ready; example folded into spec:consumers.context-bundle
- spec:consumers.context-bundle.parts-cover-the-pack: A Pack too large for one bundle reads whole in parts, depth 2, stated ready, floor ready; example folded into spec:consumers.context-bundle
- spec:consumers.readiness-planner: The readiness planner orders the statements a person can make, depth 4, stated ready, floor ready
- spec:consumers.readiness-planner.cycle-shares-a-round: Waiting Specs that rest on each other share a round and report a cycle, depth 5, 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 5, stated ready, floor ready; example folded into spec:consumers.readiness-planner
- spec:consumers.readiness-planner.dependency-order: The Spec another rests on comes first in the queue, depth 5, 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 5, 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 1, stated ready, floor ready
- spec:consumers.upgrade-kit.capability-adoption: Capability adoption counts where each capability is used and where it could apply, depth 3, stated ready, floor ready
- spec:consumers.upgrade-kit.capability-adoption.counts-a-corpus: Capability adoption counts keyed rules and reasoned relations, depth 4, 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 2, stated ready, floor ready
- 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 3, stated ready, floor ready; example folded into spec:consumers.upgrade-kit.rule-key-proposal
- spec:consumers.upgrade-kit.rule-key-proposal.proposal-applies-clean: A rule-key proposal passes the proposal check and validates once applied, depth 3, stated ready, floor ready; example folded into spec:consumers.upgrade-kit.rule-key-proposal
- Outside this scope: spec:carrier.slot-notation: Slot notation declares, binds, and refuses to guess, stated ready, floor ready
- Outside this scope: spec:consumers.adopter-on-ramp: An adopter learns graph homes, carrier grammar and shipped paths from the on-ramps, stated ready, floor ready
- Outside this scope: spec:consumers.agent-surface: Agents script a visible typed graph, stated ready, floor ready
- Outside this scope: spec:consumers.agent-surface.design-recipes: Design work reads its answers from catalog recipes, stated ready, floor ready
- Outside this scope: spec:consumers.agent-surface.recipe-parameters: Recipes take parameters as data and ship as runnable files, stated ready, floor ready
- Outside this scope: spec:consumers.agent-surface.register-recipes: Register questions stay executable graph recipes, stated ready, floor ready
- Outside this scope: spec:consumers.authoring-on-ramp: Authors move one Spec from intent to reviewed evidence, stated ready, floor ready
- Outside this scope: spec:consumers.capability-map: The capability map reads every epic and its refinement descendants, stated ready, floor ready
- Outside this scope: spec:consumers.edit-model: Views compose scoped intent instead of patching canonical source, stated ready, floor ready
- Outside this scope: spec:consumers.graph-first-planning: The next body of work is planned from the graph, not from a prose index, stated ready, floor ready
- Outside this scope: spec:consumers.intent-composition: Composed intent hands off on one proposal shape, stated ready, floor ready
- Outside this scope: spec:consumers.intent-composition.proposal: A change proposal is addressed, based and checked before it lands, stated ready, floor ready
- Outside this scope: spec:consumers.projections-model: Projections fan out from one graph without becoming truth stores, stated ready, floor ready
- Outside this scope: spec:consumers.review-perspectives: A Pack is read from a named perspective, stated ready, floor ready
- Outside this scope: spec:consumers.roadmap: A roadmap orders the next bodies of work, and the graph says what each still needs, stated ready, floor ready
- Outside this scope: spec:consumers.spec-studio.publisher: sdp studio publishes the Studio as one page set, stated ready, floor ready
- Outside this scope: spec:consumers.wholesale-view-rewrite: Every view run rewrites the view wholesale, stated ready, floor ready
- Outside this scope: spec:decisions.adopted-registrars-committed: Adopted runnable registrars are committed, stated ready, floor ready
- Outside this scope: spec:decisions.agent-front-door: The agent front door is one evaluation sink over the exported reader, stated ready, floor ready
- Outside this scope: spec:decisions.anchor-comment-form: The comment form is a second anchor representation, stated ready, floor ready
- Outside this scope: spec:decisions.architectural-annotation: Architectural significance is annotated where it is realized, stated ready, floor ready
- Outside this scope: spec:decisions.binding-not-liveness: Bindings state existence, not liveness, stated ready, floor ready
- Outside this scope: spec:decisions.content-only-sections: Sections carry content while relations carry links, stated ready, floor ready
- Outside this scope: spec:decisions.one-validation-path: Validation follows one graph, stated ready, floor ready
- Outside this scope: spec:decisions.point-per-example: Each example binds one point, stated ready, floor ready
- Outside this scope: spec:decisions.shipped-projections-frozen: The shipped projections stay frozen, stated ready, floor ready
- Outside this scope: spec:extraction.build-pipeline: The build pipeline has one ordered flow, stated ready, floor ready
- Outside this scope: spec:extraction.claim-taxonomy: Graph claims retain their epistemic source, stated ready, floor ready
- Outside this scope: spec:extraction.contract-declarations: Pinned declarations give an adopter a derived module to typecheck, stated ready, floor ready
- Outside this scope: spec:extraction.derive-graph: Carrier reification derives the one graph, stated ready, floor ready
- Outside this scope: spec:extraction.determinism: Committed source derives byte-identical output, stated ready, floor ready
- Outside this scope: spec:extraction.entry-locations: The graph records where each addressable entry is written, stated ready, floor ready
- Outside this scope: spec:extraction.example-runner: A bound example runs its contract steps against a fresh world, stated ready, floor ready
- Outside this scope: spec:extraction.excludes: Extraction exclusions are strict consumer input, stated ready, floor ready
- Outside this scope: spec:extraction.executable-examples: Bound examples execute their authored steps, stated ready, floor ready
- Outside this scope: spec:model.anchors: Source anchors bind code without carrying intent, stated ready, floor ready
- Outside this scope: spec:model.open-question-fields: An open question may name who decides it, its links, a provisional reading and a re-entry trigger, stated ready, floor ready
- Outside this scope: spec:model.open-question-keys: An open question may carry a key that addresses it, stated ready, floor ready
- Outside this scope: spec:model.planned-architecture: Components are designed ahead of their code, stated ready, floor ready
- Outside this scope: spec:model.relation-reasons: An authored relation may carry its reason, stated ready, floor ready
- Outside this scope: spec:model.rule-keys: A rule or flow entry may carry a key that addresses it, stated ready, floor ready
- Outside this scope: spec:model.spec-sections: Spec sections carry typed detail and direct verifier semantics, stated ready, floor ready
- Outside this scope: spec:model.stable-ids: Stable IDs are the Protocol's durable join key, stated ready, floor ready
- Outside this scope: spec:validation.diagnostic-rendering: One diagnostic currency, its location composed from structured fields, stated ready, floor ready
- Outside this scope: spec:validation.next-rung-floor: The floor names what blocks the floor's next rung, stated ready, floor ready
- Outside this scope: spec:validation.prose-mentions: Every Spec id written in prose resolves, stated ready, floor ready
- Outside this scope: spec:validation.two-check-families: Validation separates well-formedness from non-pretending, stated ready, floor ready
- Outside this scope: spec:validation.typed-dependency-floor: A ready Spec rests only on settled dependencies, stated ready, floor ready
- 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.agent-surface.address-and-cycle-recipes dependsOn spec:decisions.checked-mentions · declared
- 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.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.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.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.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.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.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.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: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.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 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: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.executable-contracts dependsOn spec:carrier.step-keys · declared — a keyed step's contract key is its step key
- 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.executable-contracts · 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.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: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.validate-watch · declared — the watch loop reruns the named rules in each cycle
- 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.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:carrier.step-keys refines spec:carrier.slot-notation · declared — a key joins the step text the notation reads, ahead of its slots
- 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.agent-surface.evaluation-sink refines spec:consumers.agent-surface · declared
- spec:validation.corpus-rules refines spec:consumers.agent-surface · declared — a corpus scripts the graph through the evaluation sink to report its own findings
- spec:consumers.context-bundle refines spec:consumers.agent-surface · declared
- spec:validation.corpus-rules dependsOn spec:consumers.agent-surface · declared
- spec:consumers.context-bundle dependsOn spec:consumers.agent-surface.design-recipes · declared
- spec:validation.corpus-rules dependsOn spec:consumers.agent-surface.recipe-parameters · declared — validate takes `--params` in the sink's grammar
- spec:consumers.agent-surface.address-and-cycle-recipes dependsOn spec:consumers.agent-surface.recipe-parameters · declared — address resolution reads its addresses from params
- spec:validation.external-registers dependsOn spec:consumers.agent-surface.recipe-parameters · declared — the register arrives as data through `--params register=@PATH`
- spec:consumers.agent-surface.address-and-cycle-recipes refines spec:consumers.agent-surface.register-recipes · declared
- 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:consumers.validate-watch refines spec:consumers.authoring-on-ramp · declared
- 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 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.readiness-planner refines spec:consumers.graph-first-planning · declared — the planner is an advisory planning recipe that orders nothing the Protocol enforces
- 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.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.command-line refines spec:consumers.projections-model · declared — one verb publishes every projection root from one graph
- 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 dependsOn spec:consumers.roadmap · declared — the guide teaches advisory priority and the roadmap memo as planning records
- 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:extraction.runnable-modules decidedBy spec:decisions.adopted-registrars-committed · declared
- spec:consumers.agent-surface.evaluation-sink decidedBy spec:decisions.agent-front-door · declared
- spec:consumers.context-bundle decidedBy spec:decisions.agent-front-door · declared
- spec:extraction.runnable-modules decidedBy spec:decisions.anchor-comment-form · declared
- spec:validation.corpus-rules decidedBy spec:decisions.architectural-annotation · declared — architecture checks remain the corpus's own rules
- spec:extraction.runnable-modules decidedBy spec:decisions.binding-not-liveness · declared
- spec:decisions.checked-mentions dependsOn spec:decisions.content-only-sections · declared
- spec:consumers.validate-watch dependsOn spec:decisions.one-validation-path · declared
- spec:extraction.executable-contracts decidedBy spec:decisions.point-per-example · declared
- spec:extraction.runnable-modules decidedBy spec:decisions.point-per-example · 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:carrier.step-keys decidedBy spec:decisions.shipped-projections-frozen · declared — keys stay off the frozen projections, which read the step text unchanged
- spec:model.term-addresses decidedBy spec:decisions.shipped-projections-frozen · declared — term keys stay off the frozen projections, which read the definition unchanged
- spec:extraction.executable-contracts refines spec:extraction.build-pipeline · declared
- 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.entry-citations dependsOn spec:extraction.claim-taxonomy · declared — every citation carries the inferred claim
- spec:consumers.upgrade-kit.capability-adoption dependsOn spec:extraction.contract-declarations · declared — pinned declarations are counted where keyed Design entries are
- spec:extraction.entry-citations refines spec:extraction.derive-graph · declared
- spec:extraction.entry-citations constrainedBy spec:extraction.determinism · declared
- spec:model.term-addresses dependsOn spec:extraction.entry-locations · declared — adds a row per Model term to the location table
- 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: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:extraction.runnable-modules refines spec:extraction.example-runner · declared
- spec:consumers.validate-watch dependsOn spec:extraction.excludes · declared
- spec:extraction.executable-contracts refines spec:extraction.executable-examples · declared — typed contracts carry the authored steps and example space into execution
- spec:extraction.entry-citations dependsOn spec:model.anchors · declared — only a source file that carries an anchor is read for citations
- spec:consumers.readiness-planner dependsOn spec:model.open-question-fields · declared — the owner's questions are selected by their decider field
- 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.agent-surface.address-and-cycle-recipes dependsOn spec:model.rule-keys · declared — a rule address resolves through the Spec's rule keys
- spec:model.term-addresses dependsOn spec:model.rule-keys · declared — the term-key design follows the rule-entry address pattern
- 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.rule-key-proposal dependsOn spec:model.rule-keys · declared — a coined key follows the rule-key grammar and marker
- spec:model.term-addresses refines spec:model.spec-sections · declared — extends entry addresses to the terms a Model section defines
- spec:decisions.checked-mentions refines spec:model.stable-ids · declared
- spec:model.term-addresses dependsOn spec:model.stable-ids · declared — a term address extends the Spec entry-address grammar
- spec:validation.corpus-rules dependsOn spec:validation.diagnostic-rendering · declared — corpus findings use the shared diagnostic currency
- 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: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:validation.corpus-rules constrainedBy spec:validation.two-check-families · declared
- spec:consumers.readiness-planner dependsOn spec:validation.typed-dependency-floor · declared — the order reads the four typed relations the ready floor reads
What each member needs next
| Member | Depth | Rung | Next rung | Design carried | Code |
|---|---|---|---|---|---|
The evaluation sink runs one body and prints its returnspec:consumers.agent-surface.evaluation-sinkbehavior | 1 | ready floor ready | 10 rules, 5 keyed7 entries3 declarations0 questions1 decisions3 of 3 verifying examples bound | 2 implementing0 referencing | |
3 example members folded in
| |||||
Validation re-runs while an author edits carriersspec:consumers.validate-watchbehavior | 1 | ready floor ready | 5 rules, 1 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound | 1 implementing0 referencing | |
Every verb answers --help, and one verb writes every projection rootspec:consumers.command-linebehavior | 1 | ready floor ready | 6 rules, 6 keyed5 entries2 declarations0 questions1 decisions3 of 3 verifying examples bound | 4 implementing0 referencing | |
3 example members folded in
| |||||
An example step may carry a key that survives rewordingspec:carrier.step-keysrule | 1 | ready floor ready | 12 rules, 8 keyed9 entries7 declarations0 questions1 decisions10 of 10 verifying examples bound | 7 implementing0 referencing | |
10 example members folded in
| |||||
A Spec id written in prose is a checked mentionspec:decisions.checked-mentionsdecision | 1 | ready floor ready | 0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound | 0 implementing0 referencing | |
The graph records where anchored source cites an entry addressspec:extraction.entry-citationsbehavior | 1 | ready floor ready | 10 rules, 10 keyed8 entries7 declarations0 questions0 decisions4 of 4 verifying examples bound | 4 implementing0 referencing | |
4 example members folded in
| |||||
A context bundle is composed per invocation within a stated budgetspec:consumers.context-bundlebehavior | 1 | ready floor ready | 19 rules, 9 keyed17 entries7 declarations0 questions1 decisions2 of 2 verifying examples bound | 1 implementing0 referencing | |
2 example members folded in
| |||||
The upgrade kit shows a corpus what it could adoptspec:consumers.upgrade-kitbehavior | 1 | ready floor ready | 4 rules, 4 keyed2 entries1 declarations0 questions0 decisions0 of 0 verifying examples bound | 1 implementing0 referencing | |
Corpus-authored rules run on the one validation pathspec:validation.corpus-rulesbehavior | 2 | ready floor ready | 16 rules, 10 keyed11 entries7 declarations0 questions1 decisions9 of 9 verifying examples bound | 3 implementing0 referencing | |
3 example members folded in
| |||||
The build derives step and space contracts from graph examplesspec:extraction.executable-contractsbehavior | 2 | ready floor ready | 12 rules, 6 keyed6 entries5 declarations0 questions1 decisions7 of 7 verifying examples bound | 2 implementing0 referencing | |
A Model term may carry a key that addresses itspec:model.term-addressesrule | 2 | ready floor ready | 9 rules, 7 keyed10 entries7 declarations0 questions2 decisions5 of 5 verifying examples bound | 9 implementing0 referencing | |
5 example members folded in
| |||||
The rule-key proposal keys every unkeyed rule as a change proposalspec:consumers.upgrade-kit.rule-key-proposalbehavior | 2 | ready floor ready | 6 rules, 6 keyed9 entries6 declarations0 questions0 decisions2 of 2 verifying examples bound | 1 implementing0 referencing | |
2 example members folded in
| |||||
Address resolution and dependency cycles stay executable graph recipesspec:consumers.agent-surface.address-and-cycle-recipesbehavior | 3 | ready floor ready | 9 rules, 4 keyed4 entries3 declarations0 questions0 decisions3 of 3 verifying examples bound | 1 implementing0 referencing | |
3 example members folded in
| |||||
A corpus checks the register tokens its prose citesspec:validation.external-registersbehavior | 3 | ready floor ready | 9 rules, 8 keyed8 entries7 declarations0 questions0 decisions2 of 2 verifying examples bound | 1 implementing0 referencing | |
2 example members folded in
| |||||
Derived runnable modules freeze the registrar interfacespec:extraction.runnable-modulesbehavior | 3 | ready floor ready | 16 rules7 entries5 declarations0 questions4 decisions0 of 0 verifying examples bound | 4 implementing0 referencing | |
Capability adoption counts where each capability is used and where it could applyspec:consumers.upgrade-kit.capability-adoptionbehavior | 3 | ready floor ready | 5 rules, 5 keyed6 entries4 declarations0 questions0 decisions1 of 1 verifying examples bound | 1 implementing0 referencing | |
1 example members folded in
| |||||
The readiness planner orders the statements a person can makespec:consumers.readiness-plannerbehavior | 4 | ready floor ready | 9 rules, 9 keyed6 entries4 declarations0 questions0 decisions4 of 4 verifying examples bound | 1 implementing0 referencing | |
4 example members folded in
| |||||
The architecture it touches
Arrows: uses (anchored).
The diagram as text
- component:protocol.adapters: external runtime and source adapters, anchored, layer adapter, context protocol; satisfies members none; references members none; code for rests on spec:extraction.example-runner, spec:extraction.executable-examples; member designs none
- component:protocol.cli: entry points, shared build and publication, anchored, layer edge, context protocol; satisfies members spec:consumers.agent-surface.evaluation-sink, spec:validation.corpus-rules, spec:consumers.validate-watch, spec:consumers.command-line; references members none; code for rests on spec:consumers.adopter-on-ramp, spec:consumers.agent-surface, spec:consumers.agent-surface.recipe-parameters, spec:consumers.authoring-on-ramp, spec:consumers.spec-studio.publisher, spec:consumers.wholesale-view-rewrite, spec:extraction.build-pipeline, spec:extraction.determinism, spec:validation.diagnostic-rendering; member designs none
- component:protocol.codegen: contracts and registrar output, anchored, layer application, context protocol; satisfies members spec:carrier.step-keys, spec:extraction.executable-contracts, spec:extraction.runnable-modules; references members none; code for rests on spec:extraction.executable-examples; member designs none
- component:protocol.extract: the carrier and source pipeline, anchored, layer application, context protocol; satisfies members spec:carrier.step-keys, spec:model.term-addresses, spec:extraction.entry-citations; references members none; code for rests on spec:extraction.claim-taxonomy, spec:extraction.derive-graph, spec:extraction.determinism, spec:extraction.entry-locations, spec:extraction.excludes, spec:model.anchors, spec:model.open-question-fields, spec:model.open-question-keys, spec:model.relation-reasons, spec:model.rule-keys; member designs none
- component:protocol.graph: the one graph and its semantic decisions, anchored, layer domain, context protocol; satisfies members spec:extraction.executable-contracts, spec:extraction.entry-citations; references members none; code for rests on spec:extraction.claim-taxonomy, spec:extraction.derive-graph, spec:extraction.executable-examples, spec:validation.prose-mentions; member designs none
- component:protocol.import: canonical conversion with a fidelity boundary, anchored, layer application, context protocol; satisfies members spec:carrier.step-keys, spec:model.term-addresses; references members none; code for rests on spec:model.open-question-keys; member designs none
- component:protocol.model: the authored contracts and stable ids, anchored, layer domain, context protocol; satisfies members spec:carrier.step-keys, spec:model.term-addresses; references members none; code for rests on spec:model.anchors, spec:model.open-question-keys, spec:model.spec-sections, spec:model.stable-ids; member designs none
- component:protocol.notation: the leaf step codec, anchored, layer domain, context protocol; satisfies members none; references members none; code for rests on spec:carrier.slot-notation; member designs none
- component:protocol.projections: read-only output, layout and owned publication, anchored, layer edge, context protocol; satisfies members none; references members none; code for rests on spec:consumers.projections-model, spec:consumers.spec-studio.publisher, spec:validation.diagnostic-rendering; member designs none
- component:protocol.reader: the typed graph contract and body evaluator, anchored, layer application, context protocol; satisfies members spec:consumers.agent-surface.evaluation-sink, spec:carrier.step-keys, spec:extraction.entry-citations; references members none; code for rests on spec:consumers.agent-surface, spec:extraction.contract-declarations, spec:extraction.entry-locations, spec:validation.next-rung-floor; member designs none
- component:protocol.runner: provider-neutral example execution, anchored, layer application, context protocol; satisfies members spec:carrier.step-keys; references members none; code for rests on spec:extraction.example-runner, spec:extraction.executable-examples; member designs none
- component:protocol.studio-elements: optional browser behavior and proposal handoff, anchored, layer edge, context protocol; satisfies members none; references members none; code for rests on spec:consumers.intent-composition.proposal; member designs none
- component:protocol.testing: the generated registrar runtime, anchored, layer adapter, context protocol; satisfies members spec:extraction.runnable-modules; references members none; code for rests on spec:extraction.executable-examples; member designs none
- component:protocol.validate: one finding currency and ordered checks, anchored, layer domain, context protocol; satisfies members spec:model.term-addresses; references members none; code for rests on spec:model.anchors, spec:model.open-question-keys, spec:model.rule-keys, spec:model.spec-sections, spec:validation.diagnostic-rendering, spec:validation.next-rung-floor, spec:validation.prose-mentions, spec:validation.two-check-families, spec:validation.typed-dependency-floor; 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.address-and-cycle-recipes implements spec:consumers.agent-surface.address-and-cycle-recipes; no component
- impl:protocol.external-registers-recipe implements spec:validation.external-registers; 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.entry-citation-recipe implements spec:extraction.entry-citations; no component
- impl:protocol.context-bundle-recipe implements spec:consumers.context-bundle; 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
Mermaid source
Copyable source; the Studio draws static SVG.
Chosen syntax: block, with anchored component boxes and uses arrows.
Components the slice touches
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
impl:protocol.address-and-cycle-recipesimplements Address resolution and dependency cycles stay executable graph recipesimpl:protocol.external-registers-recipeimplements A corpus checks the register tokens its prose citesimpl:protocol.address-and-cycle-recipesimplements A Model term may carry a key that addresses itimpl:protocol.register-recipesimplements A Model term may carry a key that addresses itimpl:protocol.entry-citation-recipeimplements The graph records where anchored source cites an entry addressimpl:protocol.context-bundle-recipeimplements A context bundle is composed per invocation within a stated budgetimpl:protocol.statement-queue-recipeimplements The readiness planner orders the statements a person can makeimpl:protocol.upgrade-guideimplements The upgrade kit shows a corpus what it could adoptimpl:protocol.capability-adoption-recipeimplements Capability adoption counts where each capability is used and where it could applyimpl:protocol.rule-key-proposal-recipeimplements The rule-key proposal keys every unkeyed rule as a change proposal
Decisions in scope
Open questions in scope
None.
Where the slice meets the rest
Rests on (48)
Rested on by (36)
Verified by (7)
Superseded by (0)
None.
Composing (0)
Composing needs the script.