Spec Studio

The graph declares its schema version

spec:extraction.schema-versioningBusiness Rule · storyready floor ready

Packs: pack:self-hosting-v1

Design: no design entries · no pinned declarations · no decisions

Findings: no errors, no warnings

specs/extraction/schema-versioning.sdp.md

No open questions and no blocking questions; implementation binding present, verifier binding present, and expected-outcome oracle none.

Intent
outcome
Let consumers identify the graph payload contract without premature migration machinery.
Rule
rule.declaredVersion line 15 · specs/extraction/schema-versioning.sdp.md:15
Every derived graph carries schemaVersion, which identifies its payload contract for consumers.

spec:extraction.schema-versioning.declared-version · enabled

rule line 16 · specs/extraction/schema-versioning.sdp.md:16
Additive payload fields, including optional fields, increment the schema minor version; incompatible shape or meaning changes increment the major version, while patch changes preserve the payload contract.

1 unkeyed rule.

Verifying examples

A derived payload carries a schema version its consumer can read · spec:extraction.schema-versioning.declared-version · ready floor ready

Executable Spec

Given a graph derived from the authored spec {specId: "spec:probe.schema-versioning"}
When the graph payload is serialized
Then the payload declares the schema version {schemaVersion: "0.12.0"}

Open example

Example space

Given a graph derived from the authored spec {specId:string}
When the graph payload is serialized
Then the payload declares the schema version {schemaVersion:string}
Verification

Verifier bindings

  • spec:extraction.schema-versioning.declared-version · A derived payload carries a schema version its consumer can read · declared · example enabled · specs/extraction/schema-versioning.declared-version.sdp.md

    External run evidence from test/self-hosting-extraction.test.ts

    Test anchors: test:protocol.build-pipeline.same-invocation, test:protocol.example-runner.red-step-naming, test:protocol.example-runner.step-order, test:protocol.excludes.refused-path, test:protocol.excludes.segment-boundary, test:protocol.executable-contracts.case-colliding-path, test:protocol.executable-contracts.concreteness-refusal, test:protocol.executable-contracts.multi-entry-example, test:protocol.schema-versioning.declared-version. Specs verified by those bindings: spec:extraction.build-pipeline, spec:extraction.build-pipeline.same-invocation, spec:extraction.example-runner, spec:extraction.example-runner.red-step-naming, spec:extraction.example-runner.step-order, spec:extraction.excludes, spec:extraction.excludes.refused-path, spec:extraction.excludes.segment-boundary, spec:extraction.executable-contracts, spec:extraction.executable-contracts.case-colliding-path, spec:extraction.executable-contracts.concreteness-refusal, spec:extraction.executable-contracts.multi-entry-example, spec:extraction.schema-versioning, spec:extraction.schema-versioning.declared-version.

    Run 1: external run evidence from vitest 4.1.10

    Build: CI 380 · Branch: feature/roadmap-and-slices-v0 · Commit: 34909918bf0be0e849959644401797191cae379f · Start: 2026-10-22T17:40:31.456Z · Stop: 2026-10-22T17:42:16.171Z

    NameSuiteResultDuration
    executes the bound example against a fresh worldOne query invocation shares its extracted graph and validation result (spec:extraction.build-pipeline.same-invocation)passed13.53 ms
    executes the bound example against a fresh worldA prefix excludes its own tree and leaves a similar sibling standing (spec:extraction.excludes.segment-boundary)passed1.19 ms
    executes the bound example against a fresh worldA Windows-drive absolute path is refused rather than normalized (spec:extraction.excludes.refused-path)passed0.66 ms
    executes the bound example against a fresh worldA derived payload carries a schema version its consumer can read (spec:extraction.schema-versioning.declared-version)passed0.42 ms
    executes the bound example against a fresh worldAn unbound slot in a used step earns no step contract (spec:extraction.executable-contracts.concreteness-refusal)passed1.07 ms
    executes the bound example against a fresh worldA second structured entry is named, never left silently inert (spec:extraction.executable-contracts.multi-entry-example)passed1.8 ms
    executes the bound example against a fresh worldA case-only path collision withholds the whole contracts tree (spec:extraction.executable-contracts.case-colliding-path)passed0.7 ms
    executes the bound example against a fresh worldA repeated step runs its one handler at each occurrence, in contract order (spec:extraction.example-runner.step-order)passed0.32 ms
    executes the bound example against a fresh worldA red step names itself before the assertion detail (spec:extraction.example-runner.red-step-naming)passed0.33 ms

Example space

  • specId · string · declared by a graph derived from the authored spec {specId}

Bound points

ExamplespecId
spec:extraction.schema-versioning.declared-version"spec:probe.schema-versioning"

Oracle binding: none

Coverage

specId: "spec:probe.schema-versioning" · spec:extraction.schema-versioning.declared-version · not enumerable

Unbound

  • specId: None
Design view

Requirement drawing

Requirement drawing for spec:extraction.schema-versioning
The diagram as text
  • spec:extraction.schema-versioning: The graph declares its schema version · declared Spec
  • spec:extraction.schema-versioning.declared-version: A derived payload carries a schema version its consumer can read · declared Spec
  • spec:extraction.derive-graph: Carrier reification derives the one graph · declared Spec
  • impl:protocol.schema-version: versioned graph nodes, claims, edges and located evidence · anchored code · src/graph/schema.ts:9
  • test:protocol.schema-versioning.declared-version: the declared-version point verifies the readable payload version · anchored test binding · binding present · test/self-hosting-extraction.test.ts:394
  • spec:extraction.schema-versioning refines spec:extraction.derive-graph · declared
  • spec:extraction.schema-versioning.declared-version refines spec:extraction.schema-versioning · declared
  • spec:extraction.schema-versioning.declared-version verifies spec:extraction.schema-versioning · declared
  • impl:protocol.schema-version satisfies spec:extraction.schema-versioning · anchored
  • test:protocol.schema-versioning.declared-version verifies spec:extraction.schema-versioning.declared-version · anchored
Mermaid source

Copyable source; the Studio draws static SVG.

Preferred and chosen syntax: requirementDiagram; exact refines, satisfies and verifies, with claim words in nodes and per-edge comments.

Decisions

No decision record named.

Runtime
  • component:protocol.graph · the one graph and its semantic decisions · src/graph/schema.ts:34 · layer domain · context protocol

    Uses

  • impl:protocol.schema-version · versioned graph nodes, claims, edges and located evidence · src/graph/schema.ts:9

    Component: component:protocol.graph · the one graph and its semantic decisions · src/graph/schema.ts:34 · layer domain · context protocol

    Uses

    None.

Runtime observation: not tracked.

Evidence

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.

Impact
Relations of spec:extraction.schema-versioning
  • E4: verifies · declared
The diagram as text
  • spec:consumers.spec-studio.sharing: A Studio build is stamped and shared from a static host
  • spec:extraction.derive-graph: Carrier reification derives the one graph
  • spec:extraction.schema-versioning: The graph declares its schema version
  • spec:extraction.schema-versioning.declared-version: A derived payload carries a schema version its consumer can read
  • spec:extraction.schema-versioning refines spec:extraction.derive-graph · declared
  • spec:consumers.spec-studio.sharing dependsOn spec:extraction.schema-versioning · declared
  • spec:extraction.schema-versioning.declared-version refines spec:extraction.schema-versioning · declared
  • spec:extraction.schema-versioning.declared-version verifies spec:extraction.schema-versioning · declared
Mermaid source

Copyable source; the Studio draws static SVG.

Preferred syntax: flowchart. Chosen syntax: labelled flowchart, preserving exact relations, claims and folds.

Rests on

Rested on by

Distance 1

Distance 2

Distance 3

Distance 4

Relations

Relation and directionOther endClaimReasonExercised keys
refines · outgoingCarrier reification derives the one graph
spec:extraction.derive-graph · resolves		declaredNoneNone
dependsOn · incomingA Studio build is stamped and shared from a static host
spec:consumers.spec-studio.sharing · resolves		declaredNoneNone
refines · incomingA derived payload carries a schema version its consumer can read
spec:extraction.schema-versioning.declared-version · resolves		declaredNoneNone
verifies · incomingA derived payload carries a schema version its consumer can read
spec:extraction.schema-versioning.declared-version · resolves		declaredNonedeclaredVersion

Bindings

Implementation binding: present

  • impl:protocol.schema-version · versioned graph nodes, claims, edges and located evidence · src/graph/schema.ts:9 · role contract · component component:protocol.graph · layer domain · context protocol

Design reference: none

Verifier binding: present

Expected-outcome oracle: none

Runtime observation: not tracked.

Run results: not recorded in the graph.

Findings

None.

Composing (0)

Composing needs the script.