A slice page shows a Pack's design as one whole

outcome

Give the Studio a page per Pack that shows its design slice: the members' dependency drawing, the components they touch, the decisions and open questions in scope, and each member's next rung.

Open questions

• non-blocking · question.exportCarriesSlice line 38 · specs/consumers/spec-studio.slice-page.sdp.md:38 · Does a Pack export also carry the Pack's slice page?Decider: delegatedProvisional: no; the export keeps the Pack page and its members, and the slice page stays one link away in the page set

rule.slicePerPack line 44 · specs/consumers/spec-studio.slice-page.sdp.md:44

The page set holds one slice page per Pack, slices/<name>.html, its name formed from the Pack's id as the Pack page's name is; it renders the build's design slice answer for that Pack in full and states no value the answer does not hold, apart from counts the build takes of it.

no example exercises it

rule.header line 45 · specs/consumers/spec-studio.slice-page.sdp.md:45

The page opens with the heading Design slice and the Pack's title, the Pack's id as text with a copy action, and a link back to the Pack page, then the summary and a reading note.

no example exercises it

rule.summary line 46 · specs/consumers/spec-studio.slice-page.sdp.md:46

The summary states each slice total in one sentence that opens with its count: the members and the examples counted in their parents; when the manifest names members that resolve to no Spec, how many and each one's id, so an incomplete Pack never reads as complete; the relations among members, the deepest depth and any cycle; the members held below their stated next rung and those waiting only for their author; the outside Specs the slice rests on, how many of them hold a member, and the outside Specs that rest on it; the components touched, through the members' code, through what the slice rests on, and named by member designs, with the outside components shown beside them; the member component designs, how many are realized and how many of those match; the decisions in scope and how many state below ready; and the open and blocking questions.

no example exercises it

rule.readingNote line 47 · specs/consumers/spec-studio.slice-page.sdp.md:47

The reading note says in words that members read with the ones others rest on first, that the design columns count what each member carries beside its rung and never judge whether it is enough, and that the page records no review and approves nothing.

no example exercises it

rule.dependencyDrawing line 48 · specs/consumers/spec-studio.slice-page.sdp.md:48

Under How the members rest on each other comes the slice's dependency drawing, spec:consumers.spec-studio.diagram-kinds.dependency given the slice's order: it consumes the answer's members, depths, rests-on links, structure edges, cycles and boundary rows and recomputes no scope, depth or order. Each member that is not a folded example is a box with its title, id, stated rung and floor, and its count of folded example members; every supplied relation keeps its type and direction, and a relation that orders nothing reads apart from one that orders. The drawing kind owns layout, bounded folding and the complete text equivalent, which lists every folded example with its refines; a fold changes no value of the answer.

no example exercises it

rule.memberTable line 49 · specs/consumers/spec-studio.slice-page.sdp.md:49

Under What each member needs next comes one row per member that is not a folded example, by depth and then in the scope's order: the member's title linked to its card on the Pack page with its id, its depth, its stated rung beside the floor reached, its stated next rung with nothing blocks or each unmet clause and the Specs it names with their stated rungs, then the design it carries, its rules with how many are keyed, its design entries, pinned declarations, open questions with how many block, decisions, and verifying examples with how many are bound, each count on its own line, and its implementation and reference bindings as counts; the table has no total row, and no count is combined with another.

no example exercises it

rule.exampleRows line 50 · specs/consumers/spec-studio.slice-page.sdp.md:50

A folded example member has no row of its own and stays readable in a disclosure within its parent's row, whose summary counts the folded examples and how many are held below their stated next rung; inside, each example shows its title linked to its card on the Pack page, its id, its own stated rung, floor reached and stated next rung with each unmet clause and the Specs it names. Folding lends the parent no rung, hold or binding, and the folded count stays apart from the count of examples that verify the parent.

no example exercises it

rule.architecture line 51 · specs/consumers/spec-studio.slice-page.sdp.md:51

Under The architecture it touches comes the scoped architecture drawing of the diagram kinds, given the answer's components, designs, uses, planned uses and outside components, then one row per touched component: its id linked to its detail on the architecture lens; its label, layer and context; and how the slice reaches it, the members whose code satisfies it, the members whose code references it, the Specs the slice rests on whose code it holds, and the member designs naming it, each on its own line in words.

no example exercises it

rule.designs line 52 · specs/consumers/spec-studio.slice-page.sdp.md:52

After the component rows comes one row per member component design: the design linked to its Spec page, the component it names, the layer, context, role and uses it declares, whether an anchor holds that component and whether that anchor satisfies the design, in words, and its differing rows with the declared and anchored values side by side and its unreadable rows; declared entries stay in the Declared cell, and every anchored value in the Comparison cell is labelled anchored.

no example exercises it

rule.outside line 53 · specs/consumers/spec-studio.slice-page.sdp.md:53

Then come the components outside the slice, each with how it is reached and whether an anchor holds it, under a heading that says they are shown for context and not counted as touched.

no example exercises it

rule.unplaced line 54 · specs/consumers/spec-studio.slice-page.sdp.md:54

After them come the units that implement or reference a member and belong to no component, reading None when empty.

no example exercises it

rule.noArchitecture line 55 · specs/consumers/spec-studio.slice-page.sdp.md:55

A slice that touches no component and holds no component design says so in one sentence and names, by count, the Specs it rests on that no code satisfies, so an empty architecture never reads as an architecture nobody needs.

no example exercises it

rule.decisions line 56 · specs/consumers/spec-studio.slice-page.sdp.md:56

Under Decisions in scope comes one row per decision: its title linked to its Spec page, its stated rung beside the floor reached, whether it is a member, the members it shapes, the decisions it refines or supersedes, and its open and blocking question counts.

no example exercises it

rule.questions line 57 · specs/consumers/spec-studio.slice-page.sdp.md:57

Under Open questions in scope comes each question, blocking ones first, with its blocking flag in words, its address linked to the question on its Spec page when it is keyed, its Spec, its text, its decider, links, provisional reading and trigger when present, and the members it holds.

no example exercises it

rule.boundary line 58 · specs/consumers/spec-studio.slice-page.sdp.md:58

Under Where the slice meets the rest come four closed sections, Rests on, Rested on by, Verified by and Superseded by, each headed with its count; a Rests on row shows the outside Spec linked, its stated rung beside the floor reached, its implementation binding as present or none, the members it joins under each relation type, and the members it holds.

no example exercises it

rule.bindingWords line 59 · specs/consumers/spec-studio.slice-page.sdp.md:59

The page speaks binding language: a unit implements or references a member, a verifier is bound, and no cell reads built, done, verified or approved.

no example exercises it

rule.openAll line 60 · specs/consumers/spec-studio.slice-page.sdp.md:60

Open all and Close all open or close every closed section and text equivalent at once, and the page reads in full without script.

no example exercises it

0 unkeyed rules.

criteria

• A person given only the slice page of the first adopter's history-view Pack names the member the most others rest on, the components the Pack's code touches and the outside Specs whose code the Pack builds on, from the page alone.
• The same person, given the slice page of a Pack whose members no code realizes yet, names the components the design will touch through what it rests on, and the members carrying pinned declarations while they state below defined.
• The same person, given the slice page of a Pack holding member component designs, says for each design whether code realizes it and where its declared values differ from the anchored ones, and reads no declared value as anchored.
• The same person, given the same page on a phone, names each member's stated next rung and what holds it without scrolling sideways, including an example member folded into its parent.

mode

manual

pagePath line 64 · specs/consumers/spec-studio.slice-page.sdp.md:64

slices/<name>.html, <name> formed from the Pack id as packs/<name>.html forms it, so the Pack page and its slice page share a name.

headerBlock line 65 · specs/consumers/spec-studio.slice-page.sdp.md:65

the page heading Design slice: <Pack title>; below it the Pack id with a copy action and the link Read the Pack member by member to its Pack page; then the summary under The design as a whole, then the reading note.

readingNoteText line 66 · specs/consumers/spec-studio.slice-page.sdp.md:66

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.

drawingIds line 67 · specs/consumers/spec-studio.slice-page.sdp.md:67

Both drawings take the Pack id as their subject and use their drawing kind's element-id contract. The dependency text and arrow ids are diagram.<pack id>.dependencies.text and diagram.<pack id>.dependencies.arrow; scoped architecture uses diagram.<pack id>.architecture.text and diagram.<pack id>.architecture.arrow. The kinds also own viewport, source, fold and occurrence suffixes; the page invents no singular dependency or scoped-architecture alias.

memberTable line 68 · specs/consumers/spec-studio.slice-page.sdp.md:68

a table in a scroll region with the columns Member, Depth, Rung, Next rung, Design carried and Code, so it fits a desktop column without scrolling; Member holds the title link, the id and the kind; Rung the rung badge and floor <rung>; Design carried six lines, <n> rules, <k> keyed, <n> entries, <n> declarations, <n> questions, <b> blocking, <n> decisions and <bound> of <n> verifying examples bound, each count a plain number, a zero written 0, and a zero part such as , 0 keyed left out; Code two lines, <n> implementing and <n> referencing. Below the phone breakpoint each member reads as a stacked block: its title, id and kind, its rung badge and floor, and its next rung with each unmet clause stay together at the top, and its depth, design counts and binding counts follow as labelled runs that wrap; no part of a member sits beyond a horizontal scroll.

foldedExamples line 69 · specs/consumers/spec-studio.slice-page.sdp.md:69

a row under the parent's row spanning the table, holding a closed disclosure whose summary reads <n> example members folded in, followed by , <h> held below the next rung when any is held; inside, one line per example with its title link, its id, its rung badge, floor <rung> and next <rung>: with nothing blocks or each unmet clause.

componentTable line 70 · specs/consumers/spec-studio.slice-page.sdp.md:70

a table with the columns Component, Layer and context and Reached through, the last listing each way the slice reaches the component on its own labelled line.

designTable line 71 · specs/consumers/spec-studio.slice-page.sdp.md:71

a table with the columns Design, Component, Declared, Anchor and Comparison; Declared one labelled line per key, not stated for a key the design leaves out; Anchor reads absent, present, does not satisfy the design or satisfies the design; Comparison reads not compared for a design no anchor satisfies, matches for a realized design with no differing or unreadable row, and otherwise one line per differing field as <field>: declared <value>; anchored <value>, a uses line reading uses: only declared <components>; only anchored <components> as the comparison names them, and one line per unreadable key as <key>: unreadable <value>, not compared.

outsideList line 72 · specs/consumers/spec-studio.slice-page.sdp.md:72

a list headed Outside the slice, shown for context and not counted as touched, each component with its id, linked when anchored, its label, anchored or not anchored, and how it is reached in words.

decisionTable line 73 · specs/consumers/spec-studio.slice-page.sdp.md:73

a table with the columns Decision, Rung, In the slice, Shapes and Questions.

questionItem line 74 · specs/consumers/spec-studio.slice-page.sdp.md:74

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; its Spec; the text; each present field on its own labelled line; then Holds: and the held members, or nothing for a question that holds none.

boundaryTable line 75 · specs/consumers/spec-studio.slice-page.sdp.md:75

five columns, Spec, rung, implementation binding, joined members and holds, the joined members listing each relation type with its members.

Verifier bindings

• test:protocol.studio-slice-page · anchored · test anchor binding present · test/studio-slice.test.ts:132

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

  Test anchors: test:protocol.studio-slice-architecture, test:protocol.studio-slice-dependency, test:protocol.studio-slice-page. Specs verified by those bindings: spec:consumers.spec-studio.diagram-kinds.dependency, spec:consumers.spec-studio.diagram-kinds.scoped-architecture, spec:consumers.spec-studio.slice-page.

  Run 1: external run evidence from vitest 4.1.10

  Build: CI 391 · Branch: cursor/media-plan-and-articles-09b1 · Commit: 076cd4f1f85640d8236e5cca1bffffa68ab79a33 · Start: 2026-10-31T15:32:20.471Z · Stop: 2026-10-31T15:34:02.073Z

  Name	Suite	Result	Duration
  renders the complete answer in order, keeps held examples folded and independent examples separate	slice page	passed	49.36 ms
  keeps declared, unreadable and comparison words in their own design cells	slice page	passed	0.79 ms
  writes the slice's Pack id as text in exports instead of a relative file path	slice page	passed	0.61 ms
  names each manifest member that resolves to no Spec beside the summary	slice page	passed	20.07 ms
  uses singular summary nouns and captions that add to the section headings	slice page	passed	48.54 ms
  keeps every link inside the complete page set and gives every id one owner	slice page	passed	59.19 ms
  names empty architecture and empty sections without inventing bindings	slice page	passed	0.56 ms
  stacks the member's next rung before the labelled design and code runs on a phone	slice page	passed	11.8 ms
  preserves single-member depths and opens complete text when no height-reducing fold fits	slice dependency drawing	passed	1.77 ms
  aggregates boundary arrows before testing the bound, retaining every original relation in text	slice dependency drawing	passed	4.59 ms
  points from the Mermaid source disclosure to the full text equivalent	slice dependency drawing	passed	0.25 ms
  uses supplied depths, folds its boundary even below the bound, and retains full text and nonordering arrows	slice dependency drawing	passed	6.63 ms
  folds largest complete bands first and opens text when protected boundary boxes exceed the bound	slice dependency drawing	passed	2.61 ms
  gives repeated scopes distinct fold element ids through their drawing occurrence	slice dependency drawing	passed	4.41 ms
  keeps synthetic boundary identifiers out of the visible box identity line	slice dependency drawing	passed	1.83 ms
  gives context and layer folds distinct ids and preserves all original rows	scoped architecture drawing	passed	13.49 ms
  keeps planned and anchored identities apart, folds outside context and retains original unit edges	scoped architecture drawing	passed	8.2 ms
  names uses, planned uses and realization in the legend and labels links only when a realization is drawn	scoped architecture drawing	passed	5.22 ms
  renders question fields as linked prose and dependency titles as plain text	not recorded	passed	0.59 ms
  combines relations on one ordered pair while retaining every original text row	not recorded	passed	0.7 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-slice-page · design slice summaries, member needs, architecture comparisons and boundary tables · src/projections/studio/pages/slice-page.ts:25

  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.