Spec Studio

Example realization stays evidence, not backlog work

spec:decisions.example-realization-postureDecision Record · featureready floor ready

Packs: pack:self-hosting-v1

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

Findings: no errors, no warnings

specs/decisions/example-realization-posture.sdp.md

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

Intent
outcome
Keep implementation bindings direct while making the operational build backlog name work that can own a realization.
Decision
context
The raw ready ∧ ¬implemented query includes every ready example whose bound suite verifies its parent even though the example usually owns no implementation site distinct from that parent.
decision
Ready example Specs are verification evidence and are excluded from the canonical build-backlog recipe; implemented remains a direct, anchor-derived delivery fact with no propagation through refinement.
rationale
  • Deriving an example's implementation through its parent would introduce an inferred realization claim that no source binding asserted, while adding one anchor per example would turn evidence points into ceremonial implementation sites. Keeping the fact direct preserves the claim boundary and leaves a rare example that genuinely owns a distinct realization free to carry its own code anchor.
consequences
  • The unqualified raw ready ∧ ¬implemented expression remains literally true but is not the operational backlog definition because it includes example evidence.
  • The canonical backlog recipe and adopter guidance filter out examples and report both the excluded count and any excluded ready example missing verifier evidence.
  • Consumers that hand-roll the raw expression must opt into the example posture explicitly rather than assuming refinement confers implementation.
Verification

Verifier bindings

No verifier binding recorded.

Design view

Requirement drawing

  • Declared verifying examples: no declared verifying example.
  • Satisfying or referencing units: no recorded binding.
  • Test or oracle bindings: no recorded binding.
Requirement drawing for spec:decisions.example-realization-posture

Arrows: refines (declared).

The diagram as text
  • spec:decisions.example-realization-posture: Example realization stays evidence, not backlog work · declared Spec
  • spec:model.core-model: The Protocol models delivery with one enrichable Spec · declared Spec
  • spec:decisions.example-realization-posture refines spec:model.core-model · declared
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

No implementation neighborhood recorded.

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:decisions.example-realization-posture
The diagram as text
  • spec:decisions.binding-not-liveness: Bindings state existence, not liveness
  • spec:decisions.example-realization-posture: Example realization stays evidence, not backlog work
  • spec:model.core-model: The Protocol models delivery with one enrichable Spec
  • spec:decisions.example-realization-posture dependsOn spec:decisions.binding-not-liveness · declared
  • spec:decisions.example-realization-posture refines spec:model.core-model · declared
  • spec:model.core-model decidedBy spec:decisions.example-realization-posture · 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

Distance 5

Distance 6

Distance 7

Distance 8

Relations

Relation and directionOther endClaimReasonExercised keys
dependsOn · outgoingBindings state existence, not liveness
spec:decisions.binding-not-liveness · resolves		declaredNoneNone
refines · outgoingThe Protocol models delivery with one enrichable Spec
spec:model.core-model · resolves		declaredNoneNone
decidedBy · incomingThe Protocol models delivery with one enrichable Spec
spec:model.core-model · resolves		declaredNoneNone

Bindings

Implementation binding: none

Design reference: none

Verifier binding: none

Expected-outcome oracle: none

Runtime observation: not tracked.

Run results: not recorded in the graph.

Findings

None.

Composing (0)

Composing needs the script.