Spec Studio

Design slice: Spec Studio

pack:spec-studio-v1

Read the Pack member by member

The design as a whole

  • 64 members; 23 example members counted in their parents.
  • 117 relations among members; deepest depth 10; 0 cycles.
  • 0 members held below their stated next rung; 0 waiting only for their author.
  • 45 outside Specs the slice rests on; 0 hold a member; 15 outside Specs rest on it.
  • 11 components touched: 4 through members' code, 11 through what the slice rests on, 0 named by member designs; 2 outside components shown for context.
  • 0 member component designs; 0 realized; 0 of those match.
  • 9 decisions in scope; 0 state below ready.
  • 1 open question; 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

Declared relations by depth

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

Shown as text: this drawing exceeds the height budget of 2000 pixels after folding.

The diagram as text
  • spec:consumers.spec-studio: The Spec Studio is a static HTML workbench over the one graph, depth 3, stated ready, floor ready
  • spec:decisions.studio-html-surface: The Studio renders HTML, and the HTML stays derived, depth 1, stated ready, floor ready
  • spec:consumers.spec-studio.data: The Studio renders from the reader's values and embeds only what its script reads, depth 4, stated ready, floor ready
  • spec:consumers.spec-studio.data.recipe-answers: A page takes each recipe answer from the recipe's shipped body, depth 5, stated ready, floor ready
  • spec:consumers.spec-studio.data.inputs: The Studio reads two named inputs beside the graph, a base graph and run records, depth 6, stated ready, floor ready
  • spec:consumers.spec-studio.data.inputs.graph-only: Without inputs the page set is the graph's alone, depth 7, stated ready, floor ready; example folded into spec:consumers.spec-studio.data.inputs
  • spec:consumers.spec-studio.data.inputs.both-given: Both inputs add their pages, named, and the same inputs write the same bytes, depth 7, stated ready, floor ready; example folded into spec:consumers.spec-studio.data.inputs
  • spec:consumers.spec-studio.publisher: sdp studio publishes the Studio as one page set, depth 5, stated ready, floor ready
  • spec:consumers.spec-studio.publisher.watch: sdp studio --watch rebuilds the page set on each carrier change, depth 6, stated ready, floor ready
  • spec:consumers.spec-studio.publisher.watch.matches-plain-run: Each watch cycle writes the page set a plain run writes, depth 7, stated ready, floor ready; example folded into spec:consumers.spec-studio.publisher.watch
  • spec:consumers.spec-studio.shell: The Studio's shell frames every page with navigation, a rail and a canvas, depth 7, stated ready, floor ready
  • spec:consumers.spec-studio.search: Search finds a Spec, a Pack, an entry or a bound file by a word, depth 8, stated ready, floor ready
  • spec:consumers.spec-studio.navigation: Every page of the page set is reached from the top navigation and the index, depth 9, stated ready, floor ready
  • spec:consumers.spec-studio.lenses: Five lenses read the graph as Packs, capabilities, architecture, tests and evidence, depth 5, stated ready, floor ready
  • spec:consumers.spec-studio.lenses.packs: The Packs lens groups every Spec by the Packs that hold it, depth 6, stated ready, floor ready
  • spec:consumers.spec-studio.index-page: The index says where the corpus stands and narrows every Spec, depth 8, stated ready, floor ready
  • spec:consumers.spec-studio.lenses.architecture: The architecture lens draws components by context and layer, the planned beside the built, depth 7, stated ready, floor ready
  • spec:consumers.spec-studio.lenses.architecture.unit-register: The architecture page lists each component's significant units by role, depth 8, stated ready, floor ready
  • spec:consumers.spec-studio.lenses.architecture.planned-apart: A component design no anchor realizes draws planned beside the built one, depth 8, stated ready, floor ready; example folded into spec:consumers.spec-studio.lenses.architecture
  • spec:consumers.spec-studio.lenses.tests: The tests lens shows how far each Spec's verification reaches, depth 6, stated ready, floor ready
  • spec:consumers.spec-studio.lenses.tests.coverage-row: A Spec's row on the tests lens counts its exercised keyed rules, depth 7, stated ready, floor ready; example folded into spec:consumers.spec-studio.lenses.tests
  • spec:consumers.agent-surface.example-space-coverage: Example spaces report which values their examples cover, depth 1, stated ready, floor ready
  • spec:consumers.agent-surface.example-space-coverage.uncovered-literal: A literal no example binds is reported uncovered, and an unbound child is named, depth 2, stated ready, floor ready; example folded into spec:consumers.agent-surface.example-space-coverage
  • spec:consumers.agent-surface.example-space-coverage.number-not-enumerable: A number slot is not enumerable and reports no uncovered value, depth 2, stated ready, floor ready; example folded into spec:consumers.agent-surface.example-space-coverage
  • spec:consumers.spec-studio.lenses.evidence: The evidence lens names each source of runtime evidence and reads it as not tracked, depth 6, stated ready, floor ready
  • spec:consumers.spec-studio.pack-page: A Pack page shows the Pack's design as one card per member, depth 8, stated ready, floor ready
  • spec:consumers.spec-studio.pack-page.maturity-map: A Pack page's maturity map places every member by its stated rung and its floor, depth 9, stated ready, floor ready
  • spec:consumers.spec-studio.spec-page: A Spec page shows one Spec in collapsible panels, in a fixed order, depth 8, stated ready, floor ready
  • spec:consumers.spec-studio.spec-page.cited-declaration: A pinned declaration shows the test line that cites it, depth 9, stated ready, floor ready; example folded into spec:consumers.spec-studio.spec-page
  • spec:consumers.spec-studio.spec-page.core: A Spec page's core shows the whole Spec, with an anchor for every entry, depth 9, stated ready, floor ready
  • spec:consumers.spec-studio.verification-panels: The panels for examples, targets, verifiers and evidence, depth 9, stated ready, floor ready
  • spec:consumers.spec-studio.verification-panels.rule-coverage: Each keyed rule shows the examples that exercise it, or that none does, depth 10, stated ready, floor ready; example folded into spec:consumers.spec-studio.verification-panels
  • spec:consumers.spec-studio.registers: The corpus's registers are pages a reviewer opens from a link, depth 8, stated ready, floor ready
  • spec:consumers.spec-studio.registers.blocking-first: The questions page lists the Specs with a blocking question first, depth 9, stated ready, floor ready; example folded into spec:consumers.spec-studio.registers
  • spec:consumers.spec-studio.owner-queue: The owner queue page orders the statements and questions only a person can settle, depth 8, stated ready, floor ready
  • spec:consumers.spec-studio.owner-queue.dependency-first: The owner queue lists a waiting statement after the one it rests on, depth 9, stated ready, floor ready; example folded into spec:consumers.spec-studio.owner-queue
  • spec:consumers.spec-studio.diff-page: The diff page shows what changed in the design since a base graph, depth 7, stated ready, floor ready
  • spec:consumers.spec-studio.diff-page.changed-entry: The diff page shows a changed entry's base and built values, depth 8, stated ready, floor ready; example folded into spec:consumers.spec-studio.diff-page
  • spec:consumers.spec-studio.runs-page: The runs page shows the run records the build was given, joined to test files, depth 7, stated ready, floor ready
  • spec:consumers.spec-studio.runs-page.external-evidence: The runs page shows a run as external evidence from a test file, depth 8, stated ready, floor ready; example folded into spec:consumers.spec-studio.runs-page
  • spec:observation.run-evidence: CI run records are joined to verifiers in a view, depth 1, stated ready, floor ready
  • spec:observation.run-evidence.absolute-path-joins: A test whose reporter wrote an absolute path joins its anchored file, depth 2, stated ready, floor ready; example folded into spec:observation.run-evidence
  • spec:observation.run-evidence.unanchored-file-unjoined: A test in a file with no test anchor is reported as unjoined, depth 2, stated ready, floor ready; example folded into spec:observation.run-evidence
  • spec:consumers.spec-studio.glossary-page: The glossary page lists every term the corpus's Specs define, depth 5, stated ready, floor ready
  • spec:consumers.spec-studio.glossary-page.same-word-twice: A word two Specs define appears once per Spec on the glossary page, depth 6, stated ready, floor ready; example folded into spec:consumers.spec-studio.glossary-page
  • spec:consumers.spec-studio.intent-panel: A composing panel on every page gathers scoped intent for an agent, depth 2, stated ready, floor ready
  • spec:consumers.spec-studio.intent-panel.refresh-keeps-intents: Refreshing a tab keeps every gathered intent, depth 3, stated ready, floor ready; example folded into spec:consumers.spec-studio.intent-panel
  • spec:consumers.intent-composition.proposal.memo: Recipe 49 renders a change proposal as the Markdown memo a person reviews, depth 1, stated ready, floor ready
  • spec:consumers.intent-composition.proposal.memo.shared: Recipe 49 and the composing panel write one memo for one proposal, depth 2, stated ready, floor ready; example folded into spec:consumers.intent-composition.proposal.memo
  • spec:consumers.spec-studio.components: The Studio's custom elements each hold one view the build renders, depth 5, stated ready, floor ready
  • spec:decisions.studio-web-components: The Studio is built from custom elements, not a framework, depth 1, stated ready, floor ready
  • spec:decisions.studio-build-renders: The build renders every Studio view, and an element only enhances it, depth 2, stated ready, floor ready
  • spec:decisions.studio-diagram-renderer: The engine lays out every Studio diagram as static SVG when the page set is built, depth 2, stated ready, floor ready
  • spec:consumers.spec-studio.diagrams: A diagram is laid out from graph values into SVG with a text equivalent, depth 6, stated ready, floor ready
  • spec:consumers.spec-studio.diagrams.within-bound: An architecture within the bound draws in one diagram, the same bytes twice, depth 7, stated ready, floor ready; example folded into spec:consumers.spec-studio.diagrams
  • spec:consumers.spec-studio.diagrams.folds-by-context: An architecture over the bound folds by context, depth 7, stated ready, floor ready; example folded into spec:consumers.spec-studio.diagrams
  • spec:consumers.spec-studio.diagrams.folds-by-layer: One context over the bound folds by layer, depth 7, stated ready, floor ready; example folded into spec:consumers.spec-studio.diagrams
  • spec:consumers.spec-studio.page-elements: A few custom elements filter, search, open and copy on a rendered page, depth 9, stated ready, floor ready
  • spec:consumers.spec-studio.responsive: The Studio reads on a phone as on a desktop, depth 4, stated ready, floor ready
  • spec:consumers.spec-studio.export: A Pack exports as one file, and every page prints as a document, depth 9, stated ready, floor ready
  • spec:consumers.spec-studio.export.self-contained: A Pack's export opens alone and keeps its links inside it, depth 10, stated ready, floor ready; example folded into spec:consumers.spec-studio.export
  • spec:consumers.spec-studio.sharing: A Studio build is stamped and shared from a static host, depth 6, stated ready, floor ready
  • spec:consumers.spec-studio.sharing.stamp-written-apart: The stamp is written beside the page set, and a later build removes it, depth 7, stated ready, floor ready; example folded into spec:consumers.spec-studio.sharing
  • spec:consumers.studio-on-ramp: The Studio skill teaches agents to publish, share and read the Spec Studio, depth 10, stated ready, floor ready
  • Outside this scope: spec:carrier.markdown-body-grammar: The Markdown body accepts one closed form per section, stated ready, floor ready
  • Outside this scope: spec:carrier.slot-notation: Slot notation declares, binds, and refuses to guess, stated ready, floor ready
  • Outside this scope: spec:consumers.agent-surface.design-recipes: Design work reads its answers from catalog recipes, stated ready, floor ready
  • Outside this scope: spec:consumers.agent-surface.evaluation-sink: The evaluation sink runs one body and prints its return, stated ready, floor ready
  • Outside this scope: spec:consumers.agent-surface.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.binding-language-views: Views speak binding language, never the internal fact name, stated ready, floor ready
  • Outside this scope: spec:consumers.derived-readiness-banner: Derived readiness renders beside the stated rung and warns in one direction, stated ready, floor ready
  • Outside this scope: spec:consumers.design-diff: Designs are compared between a base commit and the working tree at entry grain, 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.engine-provenance: The CLI names the engine that produced a result, 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.pack-design: The Pack context carries the Pack's design, stated ready, floor ready
  • Outside this scope: spec:consumers.projections-model: Projections fan out from one graph without becoming truth stores, stated ready, floor ready
  • Outside this scope: spec:consumers.reader: The reader bridges agent entry points to composable graph context, stated ready, floor ready
  • Outside this scope: spec:consumers.readiness-planner: The readiness planner orders the statements a person can make, stated ready, floor ready
  • Outside this scope: spec:consumers.reading-on-ramp: The reading skill teaches agents to query the graph, stated ready, floor ready
  • Outside this scope: spec:consumers.spec-studio.diagram-kinds.maturity-picture: The maturity map is drawn as a grid of counts, stated ready, floor ready
  • Outside this scope: spec:consumers.spec-studio.diagram-kinds.requirement-trace: A requirement drawing separates intent from realization and verification, stated ready, floor ready
  • Outside this scope: spec:consumers.validate-watch: Validation re-runs while an author edits carriers, 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.architectural-annotation: Architectural significance is annotated where it is realized, stated ready, floor ready
  • Outside this scope: spec:decisions.authored-entry-order: The Design Review renders open-section entries as a list, 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.shipped-projections-frozen: The shipped projections stay frozen, stated ready, floor ready
  • Outside this scope: spec:decisions.verification-posture-not-realization: Verification mode states posture, not realization, 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.delivery-facts: Resolving bindings confer direct delivery facts, 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-citations: The graph records where anchored source cites an entry address, 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.executable-contracts: The build derives step and space contracts from graph examples, stated ready, floor ready
  • Outside this scope: spec:extraction.pack-member-order: A Pack node keeps its members in authored order, stated ready, floor ready
  • Outside this scope: spec:extraction.regenerability: Generated artifacts are disposable projections, stated ready, floor ready
  • Outside this scope: spec:extraction.schema-versioning: The graph declares its schema version, 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.term-addresses: A Model term may carry a key that addresses it, 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
  • spec:consumers.agent-surface.example-space-coverage.number-not-enumerable refines spec:consumers.agent-surface.example-space-coverage · declared
  • spec:consumers.agent-surface.example-space-coverage.uncovered-literal refines spec:consumers.agent-surface.example-space-coverage · declared
  • spec:consumers.intent-composition.proposal.memo.shared refines spec:consumers.intent-composition.proposal.memo · declared
  • spec:consumers.spec-studio decidedBy spec:decisions.studio-build-renders · declared
  • spec:consumers.spec-studio decidedBy spec:decisions.studio-html-surface · declared
  • spec:consumers.spec-studio decidedBy spec:decisions.studio-web-components · declared
  • spec:consumers.spec-studio.components decidedBy spec:decisions.studio-build-renders · declared
  • spec:consumers.spec-studio.components decidedBy spec:decisions.studio-diagram-renderer · declared
  • spec:consumers.spec-studio.components decidedBy spec:decisions.studio-web-components · declared
  • spec:consumers.spec-studio.components dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.components dependsOn spec:consumers.spec-studio.intent-panel · declared — the panel element renders the gathered intents that Spec designs
  • spec:consumers.spec-studio.components refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.data refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.data.inputs dependsOn spec:consumers.spec-studio.publisher · declared — each input is named by a flag of the studio verb
  • spec:consumers.spec-studio.data.inputs dependsOn spec:observation.run-evidence · declared — the run records input is read only as run evidence
  • spec:consumers.spec-studio.data.inputs refines spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.data.inputs.both-given refines spec:consumers.spec-studio.data.inputs · declared
  • spec:consumers.spec-studio.data.inputs.graph-only refines spec:consumers.spec-studio.data.inputs · declared
  • spec:consumers.spec-studio.data.recipe-answers refines spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.diagrams decidedBy spec:decisions.studio-diagram-renderer · declared
  • spec:consumers.spec-studio.diagrams dependsOn spec:consumers.spec-studio.data · declared — a diagram is laid out from the values and recipe answers its page renders
  • spec:consumers.spec-studio.diagrams refines spec:consumers.spec-studio.components · declared
  • spec:consumers.spec-studio.diagrams.folds-by-context refines spec:consumers.spec-studio.diagrams · declared
  • spec:consumers.spec-studio.diagrams.folds-by-layer refines spec:consumers.spec-studio.diagrams · declared
  • spec:consumers.spec-studio.diagrams.within-bound refines spec:consumers.spec-studio.diagrams · declared
  • spec:consumers.spec-studio.diff-page dependsOn spec:consumers.spec-studio.data.inputs · declared — the base graph reaches the page as the build's named base input
  • spec:consumers.spec-studio.diff-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.diff-page.changed-entry refines spec:consumers.spec-studio.diff-page · declared
  • spec:consumers.spec-studio.export dependsOn spec:consumers.spec-studio.pack-page · declared — an export opens with its Pack page's content
  • spec:consumers.spec-studio.export dependsOn spec:consumers.spec-studio.publisher · declared — the export files are part of the page set the publisher writes
  • spec:consumers.spec-studio.export dependsOn spec:consumers.spec-studio.spec-page · declared — an export holds each member's Spec page content
  • spec:consumers.spec-studio.export refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.export.self-contained refines spec:consumers.spec-studio.export · declared
  • spec:consumers.spec-studio.glossary-page dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.glossary-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.glossary-page.same-word-twice refines spec:consumers.spec-studio.glossary-page · declared
  • spec:consumers.spec-studio.index-page dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.index-page dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.index-page refines spec:consumers.spec-studio.lenses.packs · declared — the index is the Packs lens and where a person lands
  • spec:consumers.spec-studio.intent-panel dependsOn spec:consumers.intent-composition.proposal.memo · declared — the panel writes the memo recipe 49 renders, byte for byte
  • spec:consumers.spec-studio.intent-panel.refresh-keeps-intents refines spec:consumers.spec-studio.intent-panel · declared
  • spec:consumers.spec-studio.lenses dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.lenses refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.lenses.architecture dependsOn spec:consumers.spec-studio.diagrams · declared — the lens's drawings are the architecture grid and the member diagrams
  • spec:consumers.spec-studio.lenses.architecture refines spec:consumers.spec-studio.lenses · declared
  • spec:consumers.spec-studio.lenses.architecture.planned-apart refines spec:consumers.spec-studio.lenses.architecture · declared
  • spec:consumers.spec-studio.lenses.architecture.unit-register refines spec:consumers.spec-studio.lenses.architecture · declared
  • spec:consumers.spec-studio.lenses.evidence refines spec:consumers.spec-studio.lenses · declared
  • spec:consumers.spec-studio.lenses.packs refines spec:consumers.spec-studio.lenses · declared
  • spec:consumers.spec-studio.lenses.tests dependsOn spec:consumers.agent-surface.example-space-coverage · declared — a row reads its example space's uncovered values from recipe 44
  • spec:consumers.spec-studio.lenses.tests dependsOn spec:observation.run-evidence · declared — with run records, a row adds the results recipe 45 joins from its verifiers' files
  • spec:consumers.spec-studio.lenses.tests refines spec:consumers.spec-studio.lenses · declared
  • spec:consumers.spec-studio.lenses.tests.coverage-row refines spec:consumers.spec-studio.lenses.tests · declared
  • spec:consumers.spec-studio.navigation dependsOn spec:consumers.spec-studio.index-page · declared — the routes extend the index's task list
  • spec:consumers.spec-studio.navigation dependsOn spec:consumers.spec-studio.lenses · declared — the lens entries keep the order the lenses take
  • spec:consumers.spec-studio.navigation dependsOn spec:consumers.spec-studio.shell · declared — the entries extend the shell's top navigation
  • spec:consumers.spec-studio.navigation refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.owner-queue dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.owner-queue dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.owner-queue refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.owner-queue.dependency-first refines spec:consumers.spec-studio.owner-queue · declared
  • spec:consumers.spec-studio.pack-page dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.pack-page dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.pack-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.pack-page.maturity-map refines spec:consumers.spec-studio.pack-page · declared
  • spec:consumers.spec-studio.page-elements decidedBy spec:decisions.studio-web-components · declared
  • spec:consumers.spec-studio.page-elements dependsOn spec:consumers.spec-studio.search · declared
  • spec:consumers.spec-studio.page-elements dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.page-elements refines spec:consumers.spec-studio.components · declared
  • spec:consumers.spec-studio.publisher dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.publisher refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.publisher.watch refines spec:consumers.spec-studio.publisher · declared
  • spec:consumers.spec-studio.publisher.watch.matches-plain-run refines spec:consumers.spec-studio.publisher.watch · declared
  • spec:consumers.spec-studio.registers dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.registers dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.registers refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.registers.blocking-first refines spec:consumers.spec-studio.registers · declared
  • spec:consumers.spec-studio.responsive refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.runs-page dependsOn spec:consumers.spec-studio.data.inputs · declared — the run records reach the page as the build's named runs input
  • spec:consumers.spec-studio.runs-page dependsOn spec:observation.run-evidence · declared — the page renders the run evidence recipe 45 joins from the run records
  • spec:consumers.spec-studio.runs-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.runs-page.external-evidence refines spec:consumers.spec-studio.runs-page · declared
  • spec:consumers.spec-studio.search dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.search refines spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.sharing dependsOn spec:consumers.spec-studio.publisher · declared — the stamp and the preview take the page set the publisher wrote
  • spec:consumers.spec-studio.sharing refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.sharing.stamp-written-apart refines spec:consumers.spec-studio.sharing · declared
  • spec:consumers.spec-studio.shell dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.shell dependsOn spec:consumers.spec-studio.lenses · declared — the top navigation opens each lens
  • spec:consumers.spec-studio.shell dependsOn spec:consumers.spec-studio.responsive · declared — the rail moves below the canvas under the phone breakpoint
  • spec:consumers.spec-studio.shell dependsOn spec:consumers.spec-studio.sharing · declared — the shell shows the stamp a publishing step writes beside the page set
  • spec:consumers.spec-studio.shell refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.spec-studio.diagrams · declared — the design view and impact panel draw requirement traceability and the one-hop trace graph
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.spec-studio.diff-page · declared — given a base graph, the header's change note links the Spec's row on the diff page
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.spec-studio.sharing · declared — a recorded file and line become a link only from a stamp's source template
  • spec:consumers.spec-studio.spec-page refines spec:consumers.spec-studio · declared
  • spec:consumers.spec-studio.spec-page.cited-declaration refines spec:consumers.spec-studio.spec-page · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:consumers.spec-studio.data · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:consumers.spec-studio.shell · declared
  • spec:consumers.spec-studio.spec-page.core refines spec:consumers.spec-studio.spec-page · declared
  • spec:consumers.spec-studio.verification-panels dependsOn spec:consumers.agent-surface.example-space-coverage · declared — the grid renders recipe 44's per-slot coverage
  • spec:consumers.spec-studio.verification-panels dependsOn spec:consumers.spec-studio.intent-panel · declared — each panel action gathers intent in the composing panel
  • spec:consumers.spec-studio.verification-panels dependsOn spec:observation.run-evidence · declared — with run records, a verifier's row adds the results recipe 45 joins from its test file
  • spec:consumers.spec-studio.verification-panels refines spec:consumers.spec-studio.spec-page · declared
  • spec:consumers.spec-studio.verification-panels.rule-coverage refines spec:consumers.spec-studio.verification-panels · declared
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.spec-studio.data.inputs · declared — the skill teaches the base graph and run records and where they may lie
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.spec-studio.export · declared — the skill teaches the Pack export and what it leaves out
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.spec-studio.intent-panel · declared — the skill teaches what the composing panel hands off and what stays scoped-intent text
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.spec-studio.publisher · declared — the skill teaches the verb, its watch and what each shared build removes
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.spec-studio.sharing · declared — the skill teaches the stamp, its lifetime and the pull-request preview workflow
  • spec:decisions.studio-build-renders refines spec:decisions.studio-web-components · declared — narrows where a view's values come from; the build writes them into the markup, so a host carries that markup and supplies no graph data
  • spec:decisions.studio-diagram-renderer refines spec:decisions.studio-web-components · declared — narrows how an element that shows a diagram renders it; the element only enhances an SVG the build drew
  • spec:decisions.studio-html-surface refines spec:consumers.spec-studio · declared, orders nothing
  • spec:decisions.studio-web-components refines spec:consumers.spec-studio · declared, orders nothing
  • spec:observation.run-evidence.absolute-path-joins refines spec:observation.run-evidence · declared
  • spec:observation.run-evidence.unanchored-file-unjoined refines spec:observation.run-evidence · declared
  • spec:consumers.spec-studio.glossary-page dependsOn spec:carrier.markdown-body-grammar · declared — the page splits a Model entry into its term and definition as the body grammar reads it
  • spec:consumers.agent-surface.example-space-coverage dependsOn spec:carrier.slot-notation · declared
  • spec:consumers.agent-surface.example-space-coverage refines spec:consumers.agent-surface.design-recipes · declared
  • spec:consumers.spec-studio.registers dependsOn spec:consumers.agent-surface.design-recipes · declared — the decisions page renders the decision register
  • spec:consumers.spec-studio.data.recipe-answers dependsOn spec:consumers.agent-surface.evaluation-sink · declared — the build composes recipe answers through the same body evaluation `sdp q` runs
  • spec:observation.run-evidence dependsOn spec:consumers.agent-surface.recipe-parameters · declared — the caller passes run records to the recipe as data
  • spec:consumers.spec-studio.registers dependsOn spec:consumers.agent-surface.register-recipes · declared — the questions page renders the open-question register
  • spec:consumers.spec-studio.index-page dependsOn spec:consumers.binding-language-views · declared
  • spec:consumers.spec-studio.pack-page dependsOn spec:consumers.binding-language-views · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.binding-language-views · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:consumers.binding-language-views · declared
  • spec:consumers.spec-studio.index-page dependsOn spec:consumers.derived-readiness-banner · declared
  • spec:consumers.spec-studio.pack-page dependsOn spec:consumers.derived-readiness-banner · declared
  • spec:consumers.spec-studio.pack-page.maturity-map dependsOn spec:consumers.derived-readiness-banner · declared — the map sets each stated rung beside the floor reached, as the banner reads them
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.derived-readiness-banner · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:consumers.derived-readiness-banner · declared
  • spec:consumers.spec-studio.data.inputs dependsOn spec:consumers.design-diff · declared — the base graph input is the design diff's base
  • spec:consumers.spec-studio.diff-page dependsOn spec:consumers.design-diff · declared — the page renders the design diff between the base graph and the graph built
  • spec:consumers.spec-studio dependsOn spec:consumers.edit-model · declared — wanted changes leave the view as intent for an ordinary source edit
  • spec:consumers.spec-studio.intent-panel dependsOn spec:consumers.edit-model · declared
  • spec:consumers.spec-studio.sharing dependsOn spec:consumers.engine-provenance · declared
  • spec:consumers.spec-studio.intent-panel refines spec:consumers.intent-composition · declared
  • spec:consumers.studio-on-ramp dependsOn spec:consumers.intent-composition · declared — a received proposal is checked and applied as the hand-off law states
  • spec:consumers.intent-composition.proposal.memo refines spec:consumers.intent-composition.proposal · declared
  • spec:consumers.spec-studio.intent-panel dependsOn spec:consumers.intent-composition.proposal · declared — the panel hands off a change proposal
  • spec:consumers.spec-studio.data dependsOn spec:consumers.pack-design · declared
  • spec:consumers.spec-studio.pack-page dependsOn spec:consumers.pack-design · declared — the page renders the Pack design the Pack context carries
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.pack-design · declared
  • spec:consumers.spec-studio refines spec:consumers.projections-model · declared
  • spec:observation.run-evidence refines spec:consumers.projections-model · declared — run records inform a view without becoming graph facts
  • spec:consumers.spec-studio dependsOn spec:consumers.reader · declared
  • spec:consumers.spec-studio.data dependsOn spec:consumers.reader · declared
  • spec:consumers.spec-studio.search dependsOn spec:consumers.reader · declared — the page matches with the reader's concept matching
  • spec:consumers.spec-studio.owner-queue dependsOn spec:consumers.readiness-planner · declared — the page renders the statement queue the planner orders
  • spec:consumers.studio-on-ramp refines spec:consumers.reading-on-ramp · declared — a Studio page is a person's reading of the one graph, and the skill sends an agent from a page to the graph behind it
  • spec:consumers.spec-studio.pack-page.maturity-map dependsOn spec:consumers.spec-studio.diagram-kinds.maturity-picture · declared — the map is drawn as the picture defines
  • spec:consumers.spec-studio.spec-page dependsOn spec:consumers.spec-studio.diagram-kinds.requirement-trace · declared — the Design view reads the selected set and claims the requirement drawing defines
  • spec:consumers.spec-studio.publisher.watch dependsOn spec:consumers.validate-watch · declared — the watch reruns on the carrier events validate's watch follows
  • spec:consumers.spec-studio.publisher dependsOn spec:consumers.wholesale-view-rewrite · declared — the Studio's root is written, invalidated and certified the way the shipped roots are
  • spec:consumers.spec-studio.diagrams dependsOn spec:decisions.architectural-annotation · declared — the architecture grid reads the layer and context a component anchor states
  • spec:consumers.spec-studio.lenses.architecture decidedBy spec:decisions.architectural-annotation · declared — the lens draws only what component anchors state, membership, uses, layer, context and role
  • spec:consumers.spec-studio.spec-page decidedBy spec:decisions.authored-entry-order · declared
  • spec:consumers.spec-studio.spec-page.core decidedBy spec:decisions.authored-entry-order · declared
  • spec:consumers.spec-studio.lenses.tests decidedBy spec:decisions.binding-not-liveness · declared
  • spec:consumers.spec-studio.lenses.evidence decidedBy spec:decisions.binding-not-liveness · declared
  • spec:consumers.spec-studio.verification-panels decidedBy spec:decisions.binding-not-liveness · declared
  • spec:consumers.spec-studio.runs-page decidedBy spec:decisions.binding-not-liveness · declared
  • spec:observation.run-evidence decidedBy spec:decisions.binding-not-liveness · declared
  • spec:consumers.spec-studio decidedBy spec:decisions.shipped-projections-frozen · declared
  • spec:consumers.spec-studio.publisher decidedBy spec:decisions.shipped-projections-frozen · declared — the Studio publishes to a root of its own beside the four frozen ones
  • spec:consumers.spec-studio.lenses.tests decidedBy spec:decisions.verification-posture-not-realization · declared
  • spec:consumers.spec-studio.verification-panels decidedBy spec:decisions.verification-posture-not-realization · declared
  • spec:consumers.spec-studio.responsive dependsOn spec:extraction.claim-taxonomy · declared
  • spec:consumers.spec-studio.registers dependsOn spec:extraction.contract-declarations · declared — the declarations page lists the pinned declarations recipe 24 reads
  • spec:observation.run-evidence dependsOn spec:extraction.delivery-facts · declared — the view reads verifier bindings while leaving their delivery facts unchanged
  • spec:decisions.studio-diagram-renderer dependsOn spec:extraction.determinism · declared — a diagram laid out from graph values alone keeps one graph to one set of bytes
  • spec:consumers.spec-studio constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.data constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.data.inputs constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.publisher constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.diagrams constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.export constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.sharing constrainedBy spec:extraction.determinism · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:extraction.entry-citations · declared — the design section shows the source lines that cite each entry
  • spec:consumers.spec-studio.registers dependsOn spec:extraction.entry-citations · declared — each declaration shows the source lines that cite its address
  • spec:consumers.spec-studio.data dependsOn spec:extraction.entry-locations · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:extraction.entry-locations · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:extraction.entry-locations · declared
  • spec:consumers.agent-surface.example-space-coverage dependsOn spec:extraction.executable-contracts · declared — its decoded slots and bound points reuse the space-contract interpretation
  • spec:consumers.spec-studio.verification-panels dependsOn spec:extraction.executable-contracts · declared
  • spec:consumers.spec-studio.data dependsOn spec:extraction.pack-member-order · declared
  • spec:consumers.spec-studio.lenses.packs dependsOn spec:extraction.pack-member-order · declared — the lens lists each Pack's members in the order its manifest gives
  • spec:decisions.studio-html-surface dependsOn spec:extraction.regenerability · declared — disposable HTML can be regenerated from the graph instead of committed as authored source
  • spec:consumers.spec-studio.sharing dependsOn spec:extraction.schema-versioning · declared
  • spec:consumers.spec-studio.pack-page dependsOn spec:model.open-question-fields · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:model.open-question-fields · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:model.open-question-fields · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:model.open-question-keys · declared
  • spec:consumers.spec-studio.intent-panel dependsOn spec:model.open-question-keys · declared
  • spec:consumers.spec-studio.lenses.architecture dependsOn spec:model.planned-architecture · declared — planned components come from the component designs recipe 43 reads
  • spec:consumers.spec-studio.spec-page dependsOn spec:model.relation-reasons · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:model.relation-reasons · declared
  • spec:consumers.spec-studio.lenses.tests dependsOn spec:model.rule-keys · declared — rule coverage counts the keyed rules examples exercise
  • spec:consumers.spec-studio.spec-page dependsOn spec:model.rule-keys · declared
  • spec:consumers.spec-studio.spec-page.core dependsOn spec:model.rule-keys · declared
  • spec:consumers.spec-studio.verification-panels dependsOn spec:model.rule-keys · declared
  • spec:consumers.spec-studio.spec-page dependsOn spec:model.term-addresses · declared — a keyed term's address names the element a glossary row links to
  • spec:consumers.spec-studio.glossary-page dependsOn spec:model.term-addresses · declared — a keyed term's address links it to its definition
  • spec:consumers.spec-studio.data dependsOn spec:validation.next-rung-floor · declared
  • spec:consumers.spec-studio.shell dependsOn spec:validation.prose-mentions · declared — a mention links where the validator resolves it

What each member needs next

MemberDepthRungNext rungDesign carriedCode
The Studio renders HTML, and the HTML stays derived
spec:decisions.studio-html-surface
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
Example spaces report which values their examples cover
spec:consumers.agent-surface.example-space-coverage
behavior
1ready floor ready7 rules, 7 keyed7 entries5 declarations0 questions0 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
CI run records are joined to verifiers in a view
spec:observation.run-evidence
behavior
1ready floor ready9 rules, 7 keyed7 entries5 declarations1 questions1 decisions2 of 2 verifying examples bound2 implementing0 referencing
2 example members folded in
Recipe 49 renders a change proposal as the Markdown memo a person reviews
spec:consumers.intent-composition.proposal.memo
contract
1ready floor ready1 rules, 1 keyed5 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound2 implementing0 referencing
1 example members folded in
The Studio is built from custom elements, not a framework
spec:decisions.studio-web-components
decision
1ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing0 referencing
A composing panel on every page gathers scoped intent for an agent
spec:consumers.spec-studio.intent-panel
behavior
2ready floor ready11 rules, 8 keyed9 entries3 declarations0 questions0 decisions1 of 1 verifying examples bound5 implementing0 referencing
1 example members folded in
The build renders every Studio view, and an element only enhances it
spec:decisions.studio-build-renders
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing6 referencing
The engine lays out every Studio diagram as static SVG when the page set is built
spec:decisions.studio-diagram-renderer
decision
2ready floor ready0 rules0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound0 implementing2 referencing
The Spec Studio is a static HTML workbench over the one graph
spec:consumers.spec-studio
behavior
3ready floor ready11 rules, 4 keyed0 entries0 declarations0 questions4 decisions0 of 0 verifying examples bound3 implementing0 referencing
The Studio renders from the reader's values and embeds only what its script reads
spec:consumers.spec-studio.data
contract
4ready floor ready4 rules, 4 keyed5 entries5 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
The Studio reads on a phone as on a desktop
spec:consumers.spec-studio.responsive
behavior
4ready floor ready1 rules3 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound2 implementing0 referencing
A page takes each recipe answer from the recipe's shipped body
spec:consumers.spec-studio.data.recipe-answers
contract
5ready floor ready2 rules, 2 keyed2 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing1 referencing
sdp studio publishes the Studio as one page set
spec:consumers.spec-studio.publisher
behavior
5ready floor ready10 rules, 10 keyed0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound5 implementing0 referencing
Five lenses read the graph as Packs, capabilities, architecture, tests and evidence
spec:consumers.spec-studio.lenses
behavior
5ready floor ready3 rules, 3 keyed1 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound4 implementing0 referencing
The glossary page lists every term the corpus's Specs define
spec:consumers.spec-studio.glossary-page
behavior
5ready floor ready4 rules, 4 keyed2 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The Studio's custom elements each hold one view the build renders
spec:consumers.spec-studio.components
contract
5ready floor ready6 rules, 5 keyed10 entries10 declarations0 questions3 decisions0 of 0 verifying examples bound11 implementing0 referencing
The Studio reads two named inputs beside the graph, a base graph and run records
spec:consumers.spec-studio.data.inputs
contract
6ready floor ready9 rules, 9 keyed2 entries2 declarations0 questions0 decisions2 of 2 verifying examples bound3 implementing0 referencing
2 example members folded in
sdp studio --watch rebuilds the page set on each carrier change
spec:consumers.spec-studio.publisher.watch
behavior
6ready floor ready1 rules, 1 keyed0 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The Packs lens groups every Spec by the Packs that hold it
spec:consumers.spec-studio.lenses.packs
behavior
6ready floor ready3 rules, 3 keyed1 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
The tests lens shows how far each Spec's verification reaches
spec:consumers.spec-studio.lenses.tests
behavior
6ready floor ready4 rules, 4 keyed3 entries0 declarations0 questions2 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The evidence lens names each source of runtime evidence and reads it as not tracked
spec:consumers.spec-studio.lenses.evidence
behavior
6ready floor ready3 rules, 3 keyed1 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
A diagram is laid out from graph values into SVG with a text equivalent
spec:consumers.spec-studio.diagrams
contract
6ready floor ready16 rules, 16 keyed14 entries4 declarations0 questions1 decisions3 of 3 verifying examples bound5 implementing0 referencing
3 example members folded in
A Studio build is stamped and shared from a static host
spec:consumers.spec-studio.sharing
behavior
6ready floor ready9 rules, 8 keyed9 entries3 declarations0 questions0 decisions1 of 1 verifying examples bound3 implementing0 referencing
1 example members folded in
The Studio's shell frames every page with navigation, a rail and a canvas
spec:consumers.spec-studio.shell
behavior
7ready floor ready11 rules, 8 keyed5 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound4 implementing0 referencing
The architecture lens draws components by context and layer, the planned beside the built
spec:consumers.spec-studio.lenses.architecture
behavior
7ready floor ready9 rules, 9 keyed5 entries1 declarations0 questions1 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The diff page shows what changed in the design since a base graph
spec:consumers.spec-studio.diff-page
behavior
7ready floor ready6 rules, 6 keyed4 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The runs page shows the run records the build was given, joined to test files
spec:consumers.spec-studio.runs-page
behavior
7ready floor ready7 rules, 7 keyed3 entries0 declarations0 questions1 decisions1 of 1 verifying examples bound2 implementing0 referencing
1 example members folded in
Search finds a Spec, a Pack, an entry or a bound file by a word
spec:consumers.spec-studio.search
behavior
8ready floor ready8 rules, 5 keyed6 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound3 implementing0 referencing
The index says where the corpus stands and narrows every Spec
spec:consumers.spec-studio.index-page
behavior
8ready floor ready6 rules, 6 keyed7 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
The architecture page lists each component's significant units by role
spec:consumers.spec-studio.lenses.architecture.unit-register
behavior
8ready floor ready5 rules, 5 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A Pack page shows the Pack's design as one card per member
spec:consumers.spec-studio.pack-page
behavior
8ready floor ready14 rules, 13 keyed7 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A Spec page shows one Spec in collapsible panels, in a fixed order
spec:consumers.spec-studio.spec-page
behavior
8ready floor ready11 rules, 9 keyed10 entries0 declarations0 questions1 decisions1 of 1 verifying examples bound3 implementing0 referencing
1 example members folded in
The corpus's registers are pages a reviewer opens from a link
spec:consumers.spec-studio.registers
behavior
8ready floor ready9 rules, 9 keyed4 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
The owner queue page orders the statements and questions only a person can settle
spec:consumers.spec-studio.owner-queue
behavior
8ready floor ready6 rules, 6 keyed2 entries0 declarations0 questions0 decisions1 of 1 verifying examples bound1 implementing0 referencing
1 example members folded in
Every page of the page set is reached from the top navigation and the index
spec:consumers.spec-studio.navigation
behavior
9ready floor ready3 rules, 3 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound2 implementing0 referencing
A Pack page's maturity map places every member by its stated rung and its floor
spec:consumers.spec-studio.pack-page.maturity-map
behavior
9ready floor ready1 rules, 1 keyed1 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing
A Spec page's core shows the whole Spec, with an anchor for every entry
spec:consumers.spec-studio.spec-page.core
behavior
9ready floor ready9 rules, 8 keyed8 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound1 implementing0 referencing
The panels for examples, targets, verifiers and evidence
spec:consumers.spec-studio.verification-panels
behavior
9ready floor ready6 rules, 6 keyed8 entries0 declarations0 questions2 decisions1 of 1 verifying examples bound2 implementing0 referencing
1 example members folded in
A few custom elements filter, search, open and copy on a rendered page
spec:consumers.spec-studio.page-elements
contract
9ready floor ready5 rules, 5 keyed6 entries6 declarations0 questions1 decisions0 of 0 verifying examples bound7 implementing0 referencing
A Pack exports as one file, and every page prints as a document
spec:consumers.spec-studio.export
behavior
9ready floor ready8 rules, 8 keyed5 entries1 declarations0 questions0 decisions1 of 1 verifying examples bound4 implementing0 referencing
1 example members folded in
The Studio skill teaches agents to publish, share and read the Spec Studio
spec:consumers.studio-on-ramp
behavior
10ready floor ready7 rules, 7 keyed0 entries0 declarations0 questions0 decisions0 of 0 verifying examples bound1 implementing0 referencing

The architecture it touches

Anchored components and member designs

Arrows: uses (anchored).

The diagram as text
  • component:protocol.cli: entry points, shared build and publication, anchored, layer edge, context protocol; satisfies members spec:consumers.spec-studio, spec:consumers.spec-studio.data.inputs, spec:consumers.spec-studio.publisher, spec:consumers.spec-studio.publisher.watch, spec:consumers.spec-studio.sharing; references members none; code for rests on spec:consumers.agent-surface.evaluation-sink, spec:consumers.agent-surface.recipe-parameters, spec:consumers.engine-provenance, spec:consumers.validate-watch, spec:consumers.wholesale-view-rewrite, spec:extraction.determinism, spec:extraction.regenerability; member designs none
  • component:protocol.codegen: contracts and registrar output, anchored, layer application, context protocol; satisfies members none; references members none; code for rests on spec:extraction.executable-contracts; member designs none
  • component:protocol.extract: the carrier and source pipeline, anchored, layer application, context protocol; satisfies members none; references members none; code for rests on spec:carrier.markdown-body-grammar, spec:extraction.claim-taxonomy, spec:extraction.determinism, spec:extraction.entry-citations, spec:extraction.entry-locations, spec:extraction.pack-member-order, spec:model.open-question-fields, spec:model.open-question-keys, spec:model.relation-reasons, spec:model.rule-keys, spec:model.term-addresses; member designs none
  • component:protocol.graph: the one graph and its semantic decisions, anchored, layer domain, context protocol; satisfies members none; references members none; code for rests on spec:extraction.claim-taxonomy, spec:extraction.delivery-facts, spec:extraction.entry-citations, spec:extraction.executable-contracts, spec:extraction.schema-versioning, spec:validation.prose-mentions; member designs none
  • component:protocol.import: canonical conversion with a fidelity boundary, anchored, layer application, context protocol; satisfies members none; references members none; code for rests on spec:model.open-question-keys, spec:model.term-addresses; member designs none
  • component:protocol.model: the authored contracts and stable ids, anchored, layer domain, context protocol; satisfies members none; references members none; code for rests on spec:model.open-question-keys, spec:model.term-addresses; member designs none
  • component:protocol.notation: the leaf step codec, anchored, layer domain, context protocol; satisfies members none; references members none; code for rests on spec:carrier.slot-notation; member designs none
  • component:protocol.projections: read-only output, layout and owned publication, anchored, layer edge, context protocol; satisfies members spec:consumers.spec-studio, spec:consumers.spec-studio.data, spec:consumers.spec-studio.data.recipe-answers, spec:consumers.spec-studio.data.inputs, spec:consumers.spec-studio.publisher, spec:consumers.spec-studio.shell, spec:consumers.spec-studio.search, spec:consumers.spec-studio.navigation, spec:consumers.spec-studio.lenses, spec:consumers.spec-studio.lenses.packs, spec:consumers.spec-studio.index-page, spec:consumers.spec-studio.lenses.architecture, spec:consumers.spec-studio.lenses.architecture.unit-register, spec:consumers.spec-studio.lenses.tests, spec:consumers.spec-studio.lenses.evidence, spec:consumers.spec-studio.pack-page, spec:consumers.spec-studio.pack-page.maturity-map, spec:consumers.spec-studio.spec-page, spec:consumers.spec-studio.spec-page.core, spec:consumers.spec-studio.verification-panels, spec:consumers.spec-studio.registers, spec:consumers.spec-studio.owner-queue, spec:consumers.spec-studio.diff-page, spec:consumers.spec-studio.runs-page, spec:observation.run-evidence, spec:consumers.spec-studio.glossary-page, spec:consumers.spec-studio.intent-panel, spec:consumers.spec-studio.components, spec:consumers.spec-studio.diagrams, spec:consumers.spec-studio.responsive, spec:consumers.spec-studio.export; references members spec:consumers.spec-studio.data.recipe-answers, spec:decisions.studio-build-renders, spec:decisions.studio-diagram-renderer; code for rests on spec:consumers.binding-language-views, spec:consumers.derived-readiness-banner, spec:consumers.projections-model, spec:consumers.spec-studio.diagram-kinds.maturity-picture, spec:consumers.spec-studio.diagram-kinds.requirement-trace, spec:extraction.pack-member-order; member designs none
  • component:protocol.reader: the typed graph contract and body evaluator, anchored, layer application, context protocol; satisfies members spec:consumers.spec-studio.search, spec:consumers.agent-surface.example-space-coverage; references members none; code for rests on spec:consumers.agent-surface.evaluation-sink, spec:consumers.pack-design, spec:consumers.reader, spec:extraction.contract-declarations, spec:extraction.entry-citations, spec:extraction.entry-locations, spec:extraction.pack-member-order, spec:validation.next-rung-floor; member designs none
  • component:protocol.studio-elements: optional browser behavior and proposal handoff, anchored, layer edge, context protocol; satisfies members spec:consumers.spec-studio.search, spec:consumers.spec-studio.intent-panel, spec:consumers.intent-composition.proposal.memo, spec:consumers.spec-studio.components, spec:consumers.spec-studio.diagrams, spec:consumers.spec-studio.page-elements, spec:consumers.spec-studio.responsive, spec:consumers.spec-studio.export, spec:consumers.spec-studio.sharing; references members spec:decisions.studio-build-renders, spec:decisions.studio-diagram-renderer; code for rests on spec:consumers.intent-composition.proposal; member designs none
  • component:protocol.validate: one finding currency and ordered checks, anchored, layer domain, context protocol; satisfies members none; references members none; code for rests on spec:extraction.pack-member-order, spec:model.open-question-keys, spec:model.rule-keys, spec:model.term-addresses, spec:validation.next-rung-floor, spec:validation.prose-mentions; member designs none
  • component:protocol.adapters: external runtime and source adapters, outside scope, anchored, layer adapter, context protocol
  • component:protocol.runner: provider-neutral example execution, outside scope, anchored, layer application, context protocol
  • component:protocol.cli uses component:protocol.adapters · anchored
  • component:protocol.cli uses component:protocol.codegen · anchored
  • component:protocol.cli uses component:protocol.extract · anchored
  • component:protocol.cli uses component:protocol.graph · anchored
  • impl:protocol.stamp-command uses impl:protocol.schema-version · anchored
  • component:protocol.cli uses component:protocol.import · anchored
  • component:protocol.cli uses component:protocol.model · anchored
  • component:protocol.cli uses component:protocol.projections · anchored
  • impl:protocol.vault-command uses component:protocol.projections · anchored
  • component:protocol.cli uses component:protocol.reader · anchored
  • component:protocol.cli uses component:protocol.validate · anchored
  • component:protocol.codegen uses component:protocol.graph · anchored
  • component:protocol.codegen uses component:protocol.notation · anchored
  • component:protocol.codegen uses component:protocol.reader · anchored
  • component:protocol.codegen uses component:protocol.validate · anchored
  • component:protocol.extract uses component:protocol.graph · anchored
  • impl:protocol.derive-graph uses impl:protocol.delivery-facts · anchored
  • component:protocol.extract uses component:protocol.model · anchored
  • component:protocol.extract uses component:protocol.notation · anchored
  • component:protocol.extract uses component:protocol.validate · anchored
  • component:protocol.graph uses component:protocol.model · anchored
  • component:protocol.graph uses component:protocol.notation · anchored
  • component:protocol.import uses component:protocol.extract · anchored
  • component:protocol.import uses component:protocol.notation · anchored
  • component:protocol.import uses component:protocol.validate · anchored
  • component:protocol.projections uses component:protocol.extract · anchored
  • impl:protocol.gherkin-view uses impl:protocol.gherkin-kind-policy · anchored
  • component:protocol.projections uses component:protocol.graph · anchored
  • component:protocol.projections uses component:protocol.model · anchored
  • component:protocol.projections uses component:protocol.notation · anchored
  • component:protocol.projections uses component:protocol.reader · anchored
  • impl:protocol.studio-recipes uses api:protocol.evaluate-body · anchored
  • impl:protocol.studio-recipes uses impl:protocol.reader · anchored
  • impl:protocol.vault-notes uses impl:protocol.reader · anchored
  • component:protocol.projections uses component:protocol.validate · anchored
  • component:protocol.reader uses component:protocol.graph · anchored
  • impl:protocol.reader uses impl:protocol.delivery-facts · anchored
  • component:protocol.reader uses component:protocol.model · anchored
  • component:protocol.reader uses component:protocol.notation · anchored
  • component:protocol.reader uses component:protocol.validate · anchored
  • impl:protocol.reader uses impl:protocol.next-rung-floor · anchored
  • component:protocol.runner uses component:protocol.notation · anchored
  • component:protocol.studio-elements uses component:protocol.projections · anchored
  • component:protocol.studio-elements uses component:protocol.reader · anchored
  • component:protocol.validate uses component:protocol.graph · anchored
  • impl:protocol.authored-honesty-delivery-facts uses impl:protocol.delivery-facts · anchored
  • component:protocol.validate uses component:protocol.model · anchored
  • component:protocol.validate uses component:protocol.notation · anchored
  • impl:protocol.example-space-coverage-recipe implements spec:consumers.agent-surface.example-space-coverage; no component
  • impl:protocol.run-evidence-recipe implements spec:observation.run-evidence; no component
  • impl:protocol.proposal-memo-recipe implements spec:consumers.intent-composition.proposal.memo; no component
  • impl:protocol.studio-preview-workflow implements spec:consumers.spec-studio.sharing; no component
  • impl:protocol.studio-on-ramp implements spec:consumers.studio-on-ramp; no component
Mermaid source

Copyable source; the Studio draws static SVG.

Preferred syntax: block; flowchart fallback because block cannot carry edge claims and counts.

Components the slice touches

ComponentLayer and contextReached through
component:protocol.cli
entry points, shared build and publication
edge · protocolMembers its code satisfies: The Spec Studio is a static HTML workbench over the one graph, The Studio reads two named inputs beside the graph, a base graph and run records, sdp studio publishes the Studio as one page set, sdp studio --watch rebuilds the page set on each carrier change, A Studio build is stamped and shared from a static hostMembers its code references: noneWhat the slice rests on, realized here: spec:consumers.agent-surface.evaluation-sink, spec:consumers.agent-surface.recipe-parameters, spec:consumers.engine-provenance, spec:consumers.validate-watch, spec:consumers.wholesale-view-rewrite, spec:extraction.determinism, spec:extraction.regenerabilityMember designs naming it: none
component:protocol.codegen
contracts and registrar output
application · protocolMembers its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:extraction.executable-contractsMember designs naming it: none
component:protocol.extract
the carrier and source pipeline
application · protocolMembers its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:carrier.markdown-body-grammar, spec:extraction.claim-taxonomy, spec:extraction.determinism, spec:extraction.entry-citations, spec:extraction.entry-locations, spec:extraction.pack-member-order, spec:model.open-question-fields, spec:model.open-question-keys, spec:model.relation-reasons, spec:model.rule-keys, spec:model.term-addressesMember designs naming it: none
component:protocol.graph
the one graph and its semantic decisions
domain · protocolMembers its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:extraction.claim-taxonomy, spec:extraction.delivery-facts, spec:extraction.entry-citations, spec:extraction.executable-contracts, spec:extraction.schema-versioning, spec:validation.prose-mentionsMember designs naming it: none
component:protocol.import
canonical conversion with a fidelity boundary
application · protocolMembers its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:model.open-question-keys, spec:model.term-addressesMember designs naming it: none
component:protocol.model
the authored contracts and stable ids
domain · protocolMembers its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:model.open-question-keys, spec:model.term-addressesMember designs naming it: none
component:protocol.notation
the leaf step codec
domain · protocolMembers its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:carrier.slot-notationMember designs naming it: none
component:protocol.projections
read-only output, layout and owned publication
edge · protocolMembers its code satisfies: The Spec Studio is a static HTML workbench over the one graph, The Studio renders from the reader's values and embeds only what its script reads, A page takes each recipe answer from the recipe's shipped body, The Studio reads two named inputs beside the graph, a base graph and run records, sdp studio publishes the Studio as one page set, The Studio's shell frames every page with navigation, a rail and a canvas, Search finds a Spec, a Pack, an entry or a bound file by a word, Every page of the page set is reached from the top navigation and the index, Five lenses read the graph as Packs, capabilities, architecture, tests and evidence, The Packs lens groups every Spec by the Packs that hold it, The index says where the corpus stands and narrows every Spec, The architecture lens draws components by context and layer, the planned beside the built, The architecture page lists each component's significant units by role, The tests lens shows how far each Spec's verification reaches, The evidence lens names each source of runtime evidence and reads it as not tracked, A Pack page shows the Pack's design as one card per member, A Pack page's maturity map places every member by its stated rung and its floor, A Spec page shows one Spec in collapsible panels, in a fixed order, A Spec page's core shows the whole Spec, with an anchor for every entry, The panels for examples, targets, verifiers and evidence, The corpus's registers are pages a reviewer opens from a link, The owner queue page orders the statements and questions only a person can settle, The diff page shows what changed in the design since a base graph, The runs page shows the run records the build was given, joined to test files, CI run records are joined to verifiers in a view, The glossary page lists every term the corpus's Specs define, A composing panel on every page gathers scoped intent for an agent, The Studio's custom elements each hold one view the build renders, A diagram is laid out from graph values into SVG with a text equivalent, The Studio reads on a phone as on a desktop, A Pack exports as one file, and every page prints as a documentMembers its code references: A page takes each recipe answer from the recipe's shipped body, The build renders every Studio view, and an element only enhances it, The engine lays out every Studio diagram as static SVG when the page set is builtWhat the slice rests on, realized here: spec:consumers.binding-language-views, spec:consumers.derived-readiness-banner, spec:consumers.projections-model, spec:consumers.spec-studio.diagram-kinds.maturity-picture, spec:consumers.spec-studio.diagram-kinds.requirement-trace, spec:extraction.pack-member-orderMember designs naming it: none
component:protocol.reader
the typed graph contract and body evaluator
application · protocolMembers its code satisfies: Search finds a Spec, a Pack, an entry or a bound file by a word, Example spaces report which values their examples coverMembers its code references: noneWhat the slice rests on, realized here: spec:consumers.agent-surface.evaluation-sink, spec:consumers.pack-design, spec:consumers.reader, spec:extraction.contract-declarations, spec:extraction.entry-citations, spec:extraction.entry-locations, spec:extraction.pack-member-order, spec:validation.next-rung-floorMember designs naming it: none
component:protocol.studio-elements
optional browser behavior and proposal handoff
edge · protocolMembers its code satisfies: Search finds a Spec, a Pack, an entry or a bound file by a word, A composing panel on every page gathers scoped intent for an agent, Recipe 49 renders a change proposal as the Markdown memo a person reviews, The Studio's custom elements each hold one view the build renders, A diagram is laid out from graph values into SVG with a text equivalent, A few custom elements filter, search, open and copy on a rendered page, The Studio reads on a phone as on a desktop, A Pack exports as one file, and every page prints as a document, A Studio build is stamped and shared from a static hostMembers its code references: The build renders every Studio view, and an element only enhances it, The engine lays out every Studio diagram as static SVG when the page set is builtWhat the slice rests on, realized here: spec:consumers.intent-composition.proposalMember designs naming it: none
component:protocol.validate
one finding currency and ordered checks
domain · protocolMembers its code satisfies: noneMembers its code references: noneWhat the slice rests on, realized here: spec:extraction.pack-member-order, spec:model.open-question-keys, spec:model.rule-keys, spec:model.term-addresses, spec:validation.next-rung-floor, spec:validation.prose-mentionsMember designs naming it: none

Member component designs

None.

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

Units bound to a member and to no component

Decisions in scope

DecisionRungIn the sliceShapesQuestions
Architectural significance is annotated where it is realized
spec:decisions.architectural-annotation
refines spec:decisions.shipped-projections-frozen
ready floor readyoutsideThe architecture lens draws components by context and layer, the planned beside the built0 open, 0 blocking
The Design Review renders open-section entries as a list
spec:decisions.authored-entry-order
refines spec:decisions.shipped-projections-frozen
ready floor readyoutsideA Spec page shows one Spec in collapsible panels, in a fixed order, A Spec page's core shows the whole Spec, with an anchor for every entry0 open, 0 blocking
Bindings state existence, not liveness
spec:decisions.binding-not-liveness
ready floor readyoutsideThe tests lens shows how far each Spec's verification reaches, The evidence lens names each source of runtime evidence and reads it as not tracked, The panels for examples, targets, verifiers and evidence, The runs page shows the run records the build was given, joined to test files, CI run records are joined to verifiers in a view0 open, 0 blocking
The shipped projections stay frozen
spec:decisions.shipped-projections-frozen
ready floor readyoutsideThe Spec Studio is a static HTML workbench over the one graph, sdp studio publishes the Studio as one page set0 open, 0 blocking
The build renders every Studio view, and an element only enhances it
spec:decisions.studio-build-renders
refines spec:decisions.studio-web-components
ready floor readymemberThe Spec Studio is a static HTML workbench over the one graph, The Studio's custom elements each hold one view the build renders0 open, 0 blocking
The engine lays out every Studio diagram as static SVG when the page set is built
spec:decisions.studio-diagram-renderer
refines spec:decisions.studio-web-components
ready floor readymemberThe Studio's custom elements each hold one view the build renders, A diagram is laid out from graph values into SVG with a text equivalent0 open, 0 blocking
The Studio renders HTML, and the HTML stays derived
spec:decisions.studio-html-surface
ready floor readymemberThe Spec Studio is a static HTML workbench over the one graph0 open, 0 blocking
The Studio is built from custom elements, not a framework
spec:decisions.studio-web-components
ready floor readymemberThe Spec Studio is a static HTML workbench over the one graph, The Studio's custom elements each hold one view the build renders, A few custom elements filter, search, open and copy on a rendered page0 open, 0 blocking
Verification mode states posture, not realization
spec:decisions.verification-posture-not-realization
ready floor readyoutsideThe tests lens shows how far each Spec's verification reaches, The panels for examples, targets, verifiers and evidence0 open, 0 blocking

Open questions in scope

  • non-blocking · question.freshness · spec:observation.run-evidence · How does a view say a run is stale: by its commit against the commit being read, or by whether the bound files changed between the two?Decider: ownerProvisional: Display the run and source commit identifiers when they differ, as the differing-commit rule requires; whether freshness also follows changes to bound files remains open.

Where the slice meets the rest

Rests on (45)
SpecRungImplementation bindingJoined membersHolds
The Markdown body accepts one closed form per section
spec:carrier.markdown-body-grammar
ready floor readypresentdependsOn: The glossary page lists every term the corpus's Specs definenone
Slot notation declares, binds, and refuses to guess
spec:carrier.slot-notation
ready floor readypresentdependsOn: Example spaces report which values their examples covernone
Design work reads its answers from catalog recipes
spec:consumers.agent-surface.design-recipes
ready floor readypresentrefines: Example spaces report which values their examples coverdependsOn: The corpus's registers are pages a reviewer opens from a linknone
The evaluation sink runs one body and prints its return
spec:consumers.agent-surface.evaluation-sink
ready floor readypresentdependsOn: A page takes each recipe answer from the recipe's shipped bodynone
Recipes take parameters as data and ship as runnable files
spec:consumers.agent-surface.recipe-parameters
ready floor readypresentdependsOn: CI run records are joined to verifiers in a viewnone
Register questions stay executable graph recipes
spec:consumers.agent-surface.register-recipes
ready floor readypresentdependsOn: The corpus's registers are pages a reviewer opens from a linknone
Views speak binding language, never the internal fact name
spec:consumers.binding-language-views
ready floor readypresentdependsOn: The index says where the corpus stands and narrows every Spec, A Pack page shows the Pack's design as one card per member, A Spec page shows one Spec in collapsible panels, in a fixed order, A Spec page's core shows the whole Spec, with an anchor for every entrynone
Derived readiness renders beside the stated rung and warns in one direction
spec:consumers.derived-readiness-banner
ready floor readypresentdependsOn: The index says where the corpus stands and narrows every Spec, A Pack page shows the Pack's design as one card per member, A Pack page's maturity map places every member by its stated rung and its floor, A Spec page shows one Spec in collapsible panels, in a fixed order, A Spec page's core shows the whole Spec, with an anchor for every entrynone
Designs are compared between a base commit and the working tree at entry grain
spec:consumers.design-diff
ready floor readypresentdependsOn: The Studio reads two named inputs beside the graph, a base graph and run records, The diff page shows what changed in the design since a base graphnone
Views compose scoped intent instead of patching canonical source
spec:consumers.edit-model
ready floor readynonedependsOn: The Spec Studio is a static HTML workbench over the one graph, A composing panel on every page gathers scoped intent for an agentnone
The CLI names the engine that produced a result
spec:consumers.engine-provenance
ready floor readypresentdependsOn: A Studio build is stamped and shared from a static hostnone
Composed intent hands off on one proposal shape
spec:consumers.intent-composition
ready floor readynonerefines: A composing panel on every page gathers scoped intent for an agentdependsOn: The Studio skill teaches agents to publish, share and read the Spec Studionone
A change proposal is addressed, based and checked before it lands
spec:consumers.intent-composition.proposal
ready floor readypresentrefines: Recipe 49 renders a change proposal as the Markdown memo a person reviewsdependsOn: A composing panel on every page gathers scoped intent for an agentnone
The Pack context carries the Pack's design
spec:consumers.pack-design
ready floor readypresentdependsOn: The Studio renders from the reader's values and embeds only what its script reads, A Pack page shows the Pack's design as one card per member, A Spec page shows one Spec in collapsible panels, in a fixed ordernone
Projections fan out from one graph without becoming truth stores
spec:consumers.projections-model
ready floor readypresentrefines: The Spec Studio is a static HTML workbench over the one graph, CI run records are joined to verifiers in a viewnone
The reader bridges agent entry points to composable graph context
spec:consumers.reader
ready floor readypresentdependsOn: The Spec Studio is a static HTML workbench over the one graph, The Studio renders from the reader's values and embeds only what its script reads, Search finds a Spec, a Pack, an entry or a bound file by a wordnone
The readiness planner orders the statements a person can make
spec:consumers.readiness-planner
ready floor readypresentdependsOn: The owner queue page orders the statements and questions only a person can settlenone
The reading skill teaches agents to query the graph
spec:consumers.reading-on-ramp
ready floor readypresentrefines: The Studio skill teaches agents to publish, share and read the Spec Studionone
The maturity map is drawn as a grid of counts
spec:consumers.spec-studio.diagram-kinds.maturity-picture
ready floor readypresentdependsOn: A Pack page's maturity map places every member by its stated rung and its floornone
A requirement drawing separates intent from realization and verification
spec:consumers.spec-studio.diagram-kinds.requirement-trace
ready floor readypresentdependsOn: A Spec page shows one Spec in collapsible panels, in a fixed ordernone
Validation re-runs while an author edits carriers
spec:consumers.validate-watch
ready floor readypresentdependsOn: sdp studio --watch rebuilds the page set on each carrier changenone
Every view run rewrites the view wholesale
spec:consumers.wholesale-view-rewrite
ready floor readypresentdependsOn: sdp studio publishes the Studio as one page setnone
Architectural significance is annotated where it is realized
spec:decisions.architectural-annotation
ready floor readynonedependsOn: A diagram is laid out from graph values into SVG with a text equivalentdecidedBy: The architecture lens draws components by context and layer, the planned beside the builtnone
The Design Review renders open-section entries as a list
spec:decisions.authored-entry-order
ready floor readynonedecidedBy: A Spec page shows one Spec in collapsible panels, in a fixed order, A Spec page's core shows the whole Spec, with an anchor for every entrynone
Bindings state existence, not liveness
spec:decisions.binding-not-liveness
ready floor readynonedecidedBy: The tests lens shows how far each Spec's verification reaches, The evidence lens names each source of runtime evidence and reads it as not tracked, The panels for examples, targets, verifiers and evidence, The runs page shows the run records the build was given, joined to test files, CI run records are joined to verifiers in a viewnone
The shipped projections stay frozen
spec:decisions.shipped-projections-frozen
ready floor readynonedecidedBy: The Spec Studio is a static HTML workbench over the one graph, sdp studio publishes the Studio as one page setnone
Verification mode states posture, not realization
spec:decisions.verification-posture-not-realization
ready floor readynonedecidedBy: The tests lens shows how far each Spec's verification reaches, The panels for examples, targets, verifiers and evidencenone
Graph claims retain their epistemic source
spec:extraction.claim-taxonomy
ready floor readypresentdependsOn: The Studio reads on a phone as on a desktopnone
Pinned declarations give an adopter a derived module to typecheck
spec:extraction.contract-declarations
ready floor readypresentdependsOn: The corpus's registers are pages a reviewer opens from a linknone
Resolving bindings confer direct delivery facts
spec:extraction.delivery-facts
ready floor readypresentdependsOn: CI run records are joined to verifiers in a viewnone
Committed source derives byte-identical output
spec:extraction.determinism
ready floor readypresentdependsOn: The engine lays out every Studio diagram as static SVG when the page set is builtconstrainedBy: The Spec Studio is a static HTML workbench over the one graph, The Studio renders from the reader's values and embeds only what its script reads, The Studio reads two named inputs beside the graph, a base graph and run records, sdp studio publishes the Studio as one page set, A diagram is laid out from graph values into SVG with a text equivalent, A Pack exports as one file, and every page prints as a document, A Studio build is stamped and shared from a static hostnone
The graph records where anchored source cites an entry address
spec:extraction.entry-citations
ready floor readypresentdependsOn: A Spec page shows one Spec in collapsible panels, in a fixed order, The corpus's registers are pages a reviewer opens from a linknone
The graph records where each addressable entry is written
spec:extraction.entry-locations
ready floor readypresentdependsOn: The Studio renders from the reader's values and embeds only what its script reads, A Spec page shows one Spec in collapsible panels, in a fixed order, A Spec page's core shows the whole Spec, with an anchor for every entrynone
The build derives step and space contracts from graph examples
spec:extraction.executable-contracts
ready floor readypresentdependsOn: Example spaces report which values their examples cover, The panels for examples, targets, verifiers and evidencenone
A Pack node keeps its members in authored order
spec:extraction.pack-member-order
ready floor readypresentdependsOn: The Studio renders from the reader's values and embeds only what its script reads, The Packs lens groups every Spec by the Packs that hold itnone
Generated artifacts are disposable projections
spec:extraction.regenerability
ready floor readypresentdependsOn: The Studio renders HTML, and the HTML stays derivednone
The graph declares its schema version
spec:extraction.schema-versioning
ready floor readypresentdependsOn: A Studio build is stamped and shared from a static hostnone
An open question may name who decides it, its links, a provisional reading and a re-entry trigger
spec:model.open-question-fields
ready floor readypresentdependsOn: A Pack page shows the Pack's design as one card per member, A Spec page shows one Spec in collapsible panels, in a fixed order, A Spec page's core shows the whole Spec, with an anchor for every entrynone
An open question may carry a key that addresses it
spec:model.open-question-keys
ready floor readypresentdependsOn: A Spec page shows one Spec in collapsible panels, in a fixed order, A composing panel on every page gathers scoped intent for an agentnone
Components are designed ahead of their code
spec:model.planned-architecture
ready floor readypresentdependsOn: The architecture lens draws components by context and layer, the planned beside the builtnone
An authored relation may carry its reason
spec:model.relation-reasons
ready floor readypresentdependsOn: A Spec page shows one Spec in collapsible panels, in a fixed order, A Spec page's core shows the whole Spec, with an anchor for every entrynone
A rule or flow entry may carry a key that addresses it
spec:model.rule-keys
ready floor readypresentdependsOn: The tests lens shows how far each Spec's verification reaches, A Spec page shows one Spec in collapsible panels, in a fixed order, A Spec page's core shows the whole Spec, with an anchor for every entry, The panels for examples, targets, verifiers and evidencenone
A Model term may carry a key that addresses it
spec:model.term-addresses
ready floor readypresentdependsOn: A Spec page shows one Spec in collapsible panels, in a fixed order, The glossary page lists every term the corpus's Specs definenone
The floor names what blocks the floor's next rung
spec:validation.next-rung-floor
ready floor readypresentdependsOn: The Studio renders from the reader's values and embeds only what its script readsnone
Every Spec id written in prose resolves
spec:validation.prose-mentions
ready floor readypresentdependsOn: The Studio's shell frames every page with navigation, a rail and a canvasnone
Rested on by (15)
SpecRungImplementation bindingJoined membersHolds
Every verb answers --help, and one verb writes every projection root
spec:consumers.command-line
ready floor readypresentdependsOn: sdp studio publishes the Studio as one page setnone
A roadmap renders as the forward section of a pull request description
spec:consumers.roadmap.memo
ready floor readypresentdependsOn: Recipe 49 renders a change proposal as the Markdown memo a person reviewsnone
The capability map page makes refinement readable by epic
spec:consumers.spec-studio.capability-map-page
ready floor readypresentrefines: Five lenses read the graph as Packs, capabilities, architecture, tests and evidencedependsOn: The index says where the corpus stands and narrows every Specnone
A pinned declaration shows the words of each test line that cites it
spec:consumers.spec-studio.cited-line-text
scoped floor scopednonerefines: The Spec Studio is a static HTML workbench over the one graphdependsOn: The corpus's registers are pages a reviewer opens from a linknone
The Studio chooses diagram kinds from graph values
spec:consumers.spec-studio.diagram-kinds
ready floor readypresentrefines: A diagram is laid out from graph values into SVG with a text equivalentdecidedBy: The engine lays out every Studio diagram as static SVG when the page set is builtnone
Edges route around boxes with deterministic orthogonal paths
spec:consumers.spec-studio.diagram-kinds.edge-routing
ready floor readypresentrefines: A diagram is laid out from graph values into SVG with a text equivalentnone
A diagram preserves readable labels before zoom
spec:consumers.spec-studio.diagram-kinds.legibility
ready floor readypresentrefines: A diagram is laid out from graph values into SVG with a text equivalentdependsOn: The Studio reads on a phone as on a desktopnone
A diagram offers Mermaid source as copyable text
spec:consumers.spec-studio.diagram-kinds.mermaid-source
ready floor readypresentdependsOn: A few custom elements filter, search, open and copy on a rendered pagedecidedBy: The engine lays out every Studio diagram as static SVG when the page set is builtnone
A requirement drawing separates intent from realization and verification
spec:consumers.spec-studio.diagram-kinds.requirement-trace
ready floor readypresentdependsOn: The Studio renders from the reader's values and embeds only what its script readsnone
A Spec set draws the architecture it touches
spec:consumers.spec-studio.diagram-kinds.scoped-architecture
ready floor readypresentdependsOn: The architecture lens draws components by context and layer, the planned beside the builtnone
An outside register is a named Studio input, so a cited token links to its entry
spec:consumers.spec-studio.register-input
scoped floor scopednonerefines: The Spec Studio is a static HTML workbench over the one graphdependsOn: The Studio reads two named inputs beside the graph, a base graph and run recordsnone
The roadmap page shows the upcoming work in priority order, split by what it needs
spec:consumers.spec-studio.roadmap-page
ready floor readypresentrefines: The Spec Studio is a static HTML workbench over the one graphdependsOn: The Studio renders from the reader's values and embeds only what its script reads, sdp studio publishes the Studio as one page set, The Studio's shell frames every page with navigation, a rail and a canvasnone
A slice page shows a Pack's design as one whole
spec:consumers.spec-studio.slice-page
ready floor readypresentrefines: The Spec Studio is a static HTML workbench over the one graphdependsOn: A page takes each recipe answer from the recipe's shipped body, A Pack page shows the Pack's design as one card per member, A diagram is laid out from graph values into SVG with a text equivalentnone
Mermaid diagrams can be rooted at code units
spec:consumers.structural-mermaid
scoped floor scopednonedependsOn: The architecture lens draws components by context and layer, the planned beside the builtnone
The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests
spec:protocol.roadmap-replaces-plans
ready floor readypresentdependsOn: CI run records are joined to verifiers in a view, Recipe 49 renders a change proposal as the Markdown memo a person reviewsnone
Verified by (0)

None.

Superseded by (0)

None.

Composing (0)

Composing needs the script.