A Pack page shows the Pack's design as one card per member

outcome

Show where a Pack's design stands, member by member in reading order, on one page a reviewer scans quickly and opens where they need detail.

rule.header line 25 · specs/consumers/spec-studio.pack-page.sdp.md:25

The page opens with the Pack's title, its id and its carrier file as text with a copy action, and a link to the Pack's slice page, then the summary; the framing follows as prose under the heading Framing, with the vocabulary references, linked.

no example exercises it

rule.summary line 26 · specs/consumers/spec-studio.pack-page.sdp.md:26

The summary states each Pack total in one sentence that opens with its count, never as a table: the members and the unresolved ones, the members held below their stated next rung and those waiting only for their author, the design entries and pinned declarations, the open and blocking questions, the members with an implementation binding and with a design reference, and the boundary in each direction. The member sentence says in priority order when the Pack states order: priority, otherwise in authored reading order.

no example exercises it

rule.holds line 27 · specs/consumers/spec-studio.pack-page.sdp.md:27

The summary's held sentence links each held member to its card with its count of unmet clauses, and its waiting sentence names the members whose stated next rung waits only for their author's statement unless every member does; the page never presents a rung as approved.

no example exercises it

rule.memberCards line 28 · specs/consumers/spec-studio.pack-page.sdp.md:28

The members follow in authored order, one closed card each. A card's summary line shows the member's position, title and kind, its stated rung beside the floor reached, its stated next rung with nothing blocks or how many of its clauses are unmet, its open and blocking questions, and its implementation and verifier bindings as present or none.

no example exercises it

rule.cardBody line 29 · specs/consumers/spec-studio.pack-page.sdp.md:29

An open card shows the member's id, linked to its Spec page, then the parts the next five rules state, in their order.

no example exercises it

rule.cardHolds line 30 · specs/consumers/spec-studio.pack-page.sdp.md:30

A card lists each clause unmet for the member's stated next rung, with the targets the clause names and their stated rungs.

no example exercises it

rule.cardDesign line 31 · specs/consumers/spec-studio.pack-page.sdp.md:31

A card counts the member's design entries and pinned declarations, and links the decisions it names, each with its stated rung.

no example exercises it

rule.cardQuestions line 32 · specs/consumers/spec-studio.pack-page.sdp.md:32

A card lists each open question with its blocking flag in words, its address when it is keyed, linked to the question on the Spec page, its recorded line, its text, and its decider, links, provisional reading and trigger when present.

no example exercises it

rule.cardCode line 33 · specs/consumers/spec-studio.pack-page.sdp.md:33

A card lists each unit that implements the member and each that references it, by id, label, and recorded file and line as text with a copy action, with its role and its component's id, layer and context.

no example exercises it

rule.cardVerifiers line 34 · specs/consumers/spec-studio.pack-page.sdp.md:34

A card states the member's verifier binding as present or none and, when it has any, counts its verifiers and verifying examples, each beside how many are enabled.

no example exercises it

rule line 35 · specs/consumers/spec-studio.pack-page.sdp.md:35

An unresolved member's card says only that the manifest names an id the graph does not hold.

rule.boundary line 36 · specs/consumers/spec-studio.pack-page.sdp.md:36

The boundary follows in four closed sections, Rests on, Rested on by, Verified by and Superseded by, each headed with its count. Each row shows the outside Spec, linked, its stated rung, its implementation binding as present or none, and the members it joins under each relation type; an empty section reads None.

no example exercises it

rule.unboundVerifiers line 37 · specs/consumers/spec-studio.pack-page.sdp.md:37

Then come the members with no verifier binding, those stated ready first, under one sentence saying the graph records bindings and never runs; then the findings that name the Pack.

no example exercises it

rule.openAll line 38 · specs/consumers/spec-studio.pack-page.sdp.md:38

Open all and Close all open or close every card and section at once, and opening the page at a card's fragment opens that card.

no example exercises it

1 unkeyed rule.

headerBlock line 41 · specs/consumers/spec-studio.pack-page.sdp.md:41

the title as the page heading; below it the id and the carrier file, each with a copy action, and the link Read this Pack as one design to its slice page; then the summary; then the framing under a Framing heading, and the vocabulary references.

summaryList line 42 · specs/consumers/spec-studio.pack-page.sdp.md:42

the totals as a short list of sentences under a Where the design stands heading, each opening with its count, a zero written as No.

memberCard line 43 · specs/consumers/spec-studio.pack-page.sdp.md:43

a disclosure whose element id is the member's Spec id; its summary line reads <position>. <title>, then the kind, the rung badge, the floor in words, the next rung in words unless the member states ready, the question counts and the two binding values, all but the badge as plain text, wrapping onto further lines on a narrow screen.

cardBody line 44 · specs/consumers/spec-studio.pack-page.sdp.md:44

in order, the id link, the unmet clauses, the design counts and decisions, the open questions, the code, and the verifier binding.

questionItem line 45 · specs/consumers/spec-studio.pack-page.sdp.md:45

the blocking flag in words; for a keyed question, question.<key> as a link to its address with a copy action for the full address; line <n> when recorded; the text; then each present field on its own labelled line.

unitItem line 46 · specs/consumers/spec-studio.pack-page.sdp.md:46

the unit id as code, its label, <file>:<line> with a copy action, its role, and its component with layer and context.

boundaryTable line 47 · specs/consumers/spec-studio.pack-page.sdp.md:47

four columns, Spec, stated rung, implementation binding and joined members, the last listing each relation type with its members.

Verifier bindings

• test:protocol.roadmap-priority · checks Pack priority extraction, comparison and Studio change notes · anchored · test anchor binding present · test/roadmap-priority.test.ts:44

  External run evidence from test/roadmap-priority.test.ts

  Test anchors: test:protocol.roadmap-priority. Specs verified by those bindings: spec:carrier.markdown-pack-authoring, spec:consumers.design-diff, spec:consumers.spec-studio.diff-page, spec:consumers.spec-studio.pack-page, spec:extraction.pack-member-order, spec:model.pack-aggregate.

  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
  derives equal Markdown and TypeScript Pack nodes and edges, serializes order last, and exposes it through the reader	roadmap priority manifest	passed	47.3 ms
  refuses the invalid Markdown value reading	roadmap priority manifest	passed	1.58 ms
  refuses the invalid Markdown value arbitrary	roadmap priority manifest	passed	1.33 ms
  refuses the invalid Markdown value true	roadmap priority manifest	passed	1.28 ms
  refuses the invalid Markdown value null	roadmap priority manifest	passed	1.65 ms
  refuses the invalid Markdown value []	roadmap priority manifest	passed	1.21 ms
  refuses the invalid Markdown value {}	roadmap priority manifest	passed	1.24 ms
  refuses the invalid TypeScript value "reading"	roadmap priority manifest	passed	3.6 ms
  refuses the invalid TypeScript value "arbitrary"	roadmap priority manifest	passed	2.76 ms
  refuses the invalid TypeScript value true	roadmap priority manifest	passed	3.43 ms
  refuses the invalid TypeScript value null	roadmap priority manifest	passed	3.5 ms
  refuses the invalid TypeScript value []	roadmap priority manifest	passed	2.87 ms
  refuses the invalid TypeScript value {}	roadmap priority manifest	passed	3.83 ms
  refuses the invalid TypeScript value undefined	roadmap priority manifest	passed	2.78 ms
  refuses the invalid TypeScript value chosenOrder	roadmap priority manifest	passed	3.35 ms
  names a removed Pack by its order meaning (priority true)	roadmap priority design diff	passed	14.29 ms
  names a removed Pack by its order meaning (priority false)	roadmap priority design diff	passed	12.82 ms
  names an added roadmap and preserves manifest order in its member delta	roadmap priority design diff	passed	17.33 ms
  labels Pack membership by its order meaning (priority true)	roadmap priority design diff	passed	8.11 ms
  labels Pack membership by its order meaning (priority false)	roadmap priority design diff	passed	5.46 ms
  states order values when a change is not a known roadmap transition	roadmap priority design diff	passed	4.7 ms
  documents the order comparison fields, default and diagnostic in the recipe contract	roadmap priority design diff	passed	1.09 ms
  compares a priority transition to true without a membership edit	roadmap priority design diff	passed	3.05 ms
  compares a priority transition to false without a membership edit	roadmap priority design diff	passed	2.22 ms
  reads an absent order as reading order in a base schema that predates the field	roadmap priority design diff	passed	7.31 ms
  marks the absent side of an added or removed roadmap as null (true)	roadmap priority design diff	passed	2.44 ms
  marks the absent side of an added or removed roadmap as null (false)	roadmap priority design diff	passed	2.06 ms
  diagnoses an unknown order at the base without reporting an order change	roadmap priority design diff	passed	1.69 ms
  diagnoses an unknown order at the head without reporting an order change	roadmap priority design diff	passed	1.71 ms
  still compares membership and member order when the base order is unknown	roadmap priority design diff	passed	2.58 ms
  still compares membership and member order when the head order is unknown	roadmap priority design diff	passed	6.34 ms
  keeps an order-only change in the selected Pack's comparison scope	roadmap priority design diff	passed	3.01 ms
  shows no roadmap transition for a membership-only change (priority true)	roadmap priority design diff	passed	7.93 ms
  shows no roadmap transition for a membership-only change (priority false)	roadmap priority design diff	passed	6.63 ms
  shows the roadmap transition to true on the diff and Pack pages	roadmap priority design diff	passed	8.43 ms
  shows the roadmap transition to false on the diff and Pack pages	roadmap priority design diff	passed	6.96 ms

• test:protocol.studio-pages · anchored · test anchor binding present · test/studio-pages.test.ts:18

  External run evidence from test/studio-pages.test.ts

  Test anchors: test:protocol.studio-pages. Specs verified by those bindings: spec:consumers.spec-studio.index-page, spec:consumers.spec-studio.pack-page, spec:consumers.spec-studio.search, spec:consumers.spec-studio.shell, spec:consumers.spec-studio.spec-page.core.

  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
  rejects malformed page links: <div id="same"></div><div id="same"></div>	not recorded	passed	2.87 ms
  rejects malformed page links: <a href="missing.html">Missing</a>	not recorded	passed	0.59 ms
  rejects malformed page links: <a href="#missing">Missing</a>	not recorded	passed	0.4 ms
  rejects malformed page links: <a href="https://example.com">Outside</a>	not recorded	passed	0.3 ms
  renders Model definitions without exposing the derived term key map	Studio static pages	passed	14.48 ms
  frames every browsing page with a skip link, labelled search, rail, canvas, classic script and stamp	Studio static pages	passed	2.55 ms
  lists example-space owners only in Pack and Spec rails	Studio static pages	passed	0.42 ms
  shows a keyed question once with a copy action naming its full address	Studio static pages	passed	0.28 ms
  opens the index with counts, four task routes, every filter and stable section ids	Studio static pages	passed	0.75 ms
  gives each Spec row one rung badge and binding words	Studio static pages	passed	1 ms
  puts Pack totals before framing and folds holds into that summary	Studio static pages	passed	0.5 ms
  leaves member names out when every member waits only for its author	Studio static pages	passed	10.78 ms
  agrees each boundary verb with its count	Studio static pages	passed	15.83 ms
  shows only the Spec's own Packs in its rail and every Pack on the index	Studio static pages	passed	22.98 ms
  asserts every index summary sentence including fact-based verifier counts	Studio static pages	passed	6.98 ms
  renders code spans in titles on every page and strips them in document titles	Studio static pages	passed	13.13 ms
  orders rung filters by the ladder and uses none everywhere for an unmet idea floor	Studio static pages	passed	11.49 ms
  keeps navigation links outside Pack disclosure controls	Studio static pages	passed	0.21 ms
  labels next rungs, UI and finding links and avoids repeating absent bindings	Studio static pages	passed	0.34 ms
  renders Pack members in authored order, closed and with one colored badge per summary	Studio static pages	passed	0.46 ms
  renders the four Pack boundary sections and the verifier gap sentence once	Studio static pages	passed	0.2 ms
  shows the stated rung beside its floor and warns only in the dishonest direction	Studio static pages	passed	0.16 ms
  renders every section in order and every addressable entry with its key and recorded line	Studio static pages	passed	0.33 ms
  names the first unmet clause and renders a missing idea floor as none	Studio static pages	passed	3.23 ms
  shows question fields, code location, component, bindings and relations both ways	Studio static pages	passed	0.57 ms
  escapes authored text, reads only code spans and links resolving mentions	Studio static pages	passed	0.24 ms
  links validator-readable escaped mentions and preserves unequal code delimiters	Studio static pages	passed	0.19 ms
  shows findings on the index and only links page-bearing subjects	Studio static pages	passed	8.01 ms
  embeds the index only on search and supplies its element and no-script explanation	Studio static pages	passed	0.65 ms
  resolves all probe links including fragments in dynamic search results	Studio static pages	passed	6.99 ms
  keeps unresolved component bindings as text and resolves every remaining link	Studio static pages	passed	18.06 ms
  renders deterministically with no time or commit metadata	Studio static pages	passed	7.9 ms
  ships the native layout and focus stylesheet in the browser assets	Studio static pages	passed	0.22 ms
  resolves every page link and element fragment	Protocol Studio page set	passed	1313.79 ms
  contains the complete Spec prose without executing script	Protocol Studio page set	passed	77.84 ms

Requirement drawing

• Declared verifying examples: no declared verifying example.

Decisions

No decision record named.

• component:protocol.projections · read-only output, layout and owned publication · src/projections/design-review.ts:29 · layer edge · context protocol

  Uses

  • component:protocol.extract · the carrier and source pipeline · src/extract/index.ts:192 · layer application · context protocol
  • 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.reader · the typed graph contract and body evaluator · src/reader/reader.ts:671 · layer application · context protocol
  • component:protocol.validate · one finding currency and ordered checks · src/validate/validators.ts:72 · layer domain · context protocol
• impl:protocol.studio-pack-page · renders Pack members, maturity and boundary joins · src/projections/studio/pages/pack-page.ts:68

  Component: component:protocol.projections · read-only output, layout and owned publication · src/projections/design-review.ts:29 · layer edge · context protocol

  Uses

  None.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.