What a Spec's design carries is derived, beside its readiness

problem

A reviewer or an implementer cannot tell from readiness alone which Specs carry a settled design and which carry only intent, and the first adopter's owner asked for Specs whose key concepts are designed as stubs before code.

outcome

Show what design a Spec carries in values the graph derives, so the backlog and a review can tell a designed Spec from one that states only its intent.

assumptions

• The design columns tell a Spec with pinned declarations and keyed entries from one that states only its intent.

Open questions

• non-blocking · question.designColumnsSufficiency line 20 · specs/model/design-maturity.sdp.md:20 · If the first adopter's design passes show that the design columns cannot distinguish settled design from intent alone, should this representation be revisited?Decider: ownerProvisional: derive what design a Spec carries beside readiness without a new rung, floor clause or delivery fact

design columns line 25 · specs/model/design-maturity.sdp.md:25

The counts and lists the reader derives for a Spec beside its readiness under spec:consumers.pack-design; they are read on every pass and never stated.

designed stage line 26 · specs/model/design-maturity.sdp.md:26

The original design's readiness stage for a Spec whose key concepts were settled; it is not a Protocol rung.

Verifier bindings

• test:protocol.pack-design · the Pack context carries each member's design and the Pack's boundary · anchored · test anchor binding present · test/pack-design.test.ts:18

  External run evidence from test/pack-design.test.ts

  Test anchors: test:protocol.pack-design. Specs verified by those bindings: spec:consumers.pack-design, spec:model.design-maturity.

  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

  Name	Suite	Result	Duration
  keeps the manifest's order and every existing field	the Pack design on the Pack context	passed	16.56 ms
  names the stated next rung's unmet clauses, with the targets a dependency clause names	the Pack design on the Pack context	passed	3.72 ms
  reads an empty list where the floor already holds the stated next rung	the Pack design on the Pack context	passed	1.63 ms
  keeps the stated reading apart from the floor-reached reading	the Pack design on the Pack context	passed	2.77 ms
  names no next rung above ready	the Pack design on the Pack context	passed	1.78 ms
  counts the design columns: keyed entries, pinned declarations and questions	the Pack design on the Pack context	passed	2.72 ms
  exposes the same design columns on Spec context and Pack members	the Pack design on the Pack context	passed	2.35 ms
  lists the decisions a member names, unresolved when the target is no Spec	the Pack design on the Pack context	passed	5.17 ms
  carries each realizing and referencing unit with its component on the member and on the Spec context	the Pack design on the Pack context	passed	4.46 ms
  counts verifiers and verifying examples with how many are enabled	the Pack design on the Pack context	passed	3.5 ms
  counts a verifying Spec of another kind as a verifier, never as an example	the Pack design on the Pack context	passed	0.7 ms
  lists the boundary both ways, rows by id and members in authored order	the Pack design on the Pack context	passed	1.42 ms
  keeps verification and supersession outside restedOnBy, ignoring anchored verifiers	the Pack design on the Pack context	passed	2.13 ms
  marks an outside Spec that carries the implementation fact	the Pack design on the Pack context	passed	1.44 ms
  keeps an unresolved member's existing row and nothing more	the Pack design on the Pack context	passed	0.91 ms
  carries each Spec's location rows on its Spec context, sorted by entry	the Pack design on the Pack context	passed	1.61 ms
  is a pure function of the graph: two reads of one graph are equal	the Pack design on the Pack context	passed	3.34 ms
  joins many members to one outside Spec in one step each, members in authored order	the Pack design on the Pack context	passed	936.04 ms

Requirement drawing

• Declared verifying examples: no declared verifying example.

Decisions

No decision record named.

• component:protocol.reader · the typed graph contract and body evaluator · src/reader/reader.ts:671 · layer application · context protocol

  Uses

  • component:protocol.graph · the one graph and its semantic decisions · src/graph/schema.ts:34 · layer domain · context protocol
  • component:protocol.model · the authored contracts and stable ids · src/model/anchors.ts:100 · layer domain · context protocol
  • component:protocol.notation · the leaf step codec · src/notation/slots.ts:261 · layer domain · context protocol
  • component:protocol.validate · one finding currency and ordered checks · src/validate/validators.ts:72 · layer domain · context protocol
• impl:protocol.pack-design · the Pack design helpers and the Pack context assembly they serve · src/reader/reader.ts:499

  Component: component:protocol.reader · the typed graph contract and body evaluator · src/reader/reader.ts:671 · layer application · context protocol

  Uses

  None.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.