A Spec set draws the architecture it touches

outcome

Review a Pack, slice or roadmap's realized and planned seams together while seeing exactly why each component is present.

rule.scopeInput line 19 · specs/consumers/spec-studio.diagram-kinds.scoped-architecture.sdp.md:19

Read the design slice's architecture answer: components with how the slice reaches each, in words, members' satisfying code, members' referencing code or what the slice rests on; designs with their declared values, realization and comparison rows, each drawn as a planned box; uses with the unit edges behind each count and its outside mark; plannedUses; outside; and unplaced. The drawing resolves no unit to a component itself and recomputes none of them; the unplaced units remain listed apart.

no example exercises it

rule.separatePlans line 20 · specs/consumers/spec-studio.diagram-kinds.scoped-architecture.sdp.md:20

Draw anchored components and component designs as separate identities, even when the realization comparison joins them. Planned layer, context and uses stay declared; realized structure stays anchored; a difference is labelled rather than merged away.

no example exercises it

rule.boundary line 21 · specs/consumers/spec-studio.diagram-kinds.scoped-architecture.sdp.md:21

Draw only the uses boundary the supplied design-slice architecture answer includes; never traverse it in layout. Its uses includes anchored pairs between touched components and pairs with one immediate outside neighbour, marked outside: true, as spec:consumers.design-slice#rule.outsideNeighbors states. Fold supplied outside neighbours into one outside scope box per context and layer while keeping their identities and original unit edges in the text equivalent; never add pairs between two outside components. Planned uses remain separate and never increase an anchored count.

no example exercises it

rule.bound line 22 · specs/consumers/spec-studio.diagram-kinds.scoped-architecture.sdp.md:22

Apply the shared architecture folds by context then layer to this selected graph. If no component or planned design resolves, show the empty explanation and unassigned units instead of a blank or invented architecture.

no example exercises it

0 unkeyed rules.

layout line 25 · specs/consumers/spec-studio.diagram-kinds.scoped-architecture.sdp.md:25

Use the architecture grid's context columns and layer bands, with the legibility child's title-first boxes, cell wrapping and local scroll. Prefix planned boxes with planned; outside-scope boxes say outside scope.

edgeWords line 26 · specs/consumers/spec-studio.diagram-kinds.scoped-architecture.sdp.md:26

The legend distinguishes uses (anchored), plans to use (declared) and realizes (anchored) when present. A drawing containing uses and planned uses alone carries no per-edge label. When a realization correspondence is present, label the distinct relation families beside each link or through a keyed legend; realization stays apart from uses and confers no delivery fact.

textEquivalent line 27 · specs/consumers/spec-studio.diagram-kinds.scoped-architecture.sdp.md:27

List each component's full id, label, layer, context and the scoped Spec and binding kind that brought it in; list unassigned units, unreadable declarations, planned-to-realized comparisons and every original uses edge.

elementIds line 28 · specs/consumers/spec-studio.diagram-kinds.scoped-architecture.sdp.md:28

Use diagram.<subject>.architecture.text and .architecture.arrow; context and layer folds append their encoded full key before the suffix.

mermaidKind line 29 · specs/consumers/spec-studio.diagram-kinds.scoped-architecture.sdp.md:29

block with generic component boxes and uses arrows for a purely anchored grid; use flowchart TB with explicit declared and anchored labels when planned, comparison or folded edges cannot be preserved by block syntax. Architecture icons never infer deployment meaning.

no citation recorded

Verifier bindings

• test:protocol.studio-slice-architecture · anchored · test anchor binding present · test/studio-slice.test.ts:579

  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 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
  renders the complete answer in order, keeps held examples folded and independent examples separate	slice page	passed	41.17 ms
  keeps declared, unreadable and comparison words in their own design cells	slice page	passed	0.84 ms
  writes the slice's Pack id as text in exports instead of a relative file path	slice page	passed	0.62 ms
  names each manifest member that resolves to no Spec beside the summary	slice page	passed	10.28 ms
  uses singular summary nouns and captions that add to the section headings	slice page	passed	50.67 ms
  keeps every link inside the complete page set and gives every id one owner	slice page	passed	47.47 ms
  names empty architecture and empty sections without inventing bindings	slice page	passed	0.69 ms
  stacks the member's next rung before the labelled design and code runs on a phone	slice page	passed	8.77 ms
  preserves single-member depths and opens complete text when no height-reducing fold fits	slice dependency drawing	passed	1.47 ms
  aggregates boundary arrows before testing the bound, retaining every original relation in text	slice dependency drawing	passed	3.37 ms
  points from the Mermaid source disclosure to the full text equivalent	slice dependency drawing	passed	0.2 ms
  uses supplied depths, folds its boundary even below the bound, and retains full text and nonordering arrows	slice dependency drawing	passed	3.52 ms
  folds largest complete bands first and opens text when protected boundary boxes exceed the bound	slice dependency drawing	passed	1.82 ms
  gives repeated scopes distinct fold element ids through their drawing occurrence	slice dependency drawing	passed	2.52 ms
  keeps synthetic boundary identifiers out of the visible box identity line	slice dependency drawing	passed	0.76 ms
  gives context and layer folds distinct ids and preserves all original rows	scoped architecture drawing	passed	6.08 ms
  keeps planned and anchored identities apart, folds outside context and retains original unit edges	scoped architecture drawing	passed	5.56 ms
  names uses, planned uses and realization in the legend and labels links only when a realization is drawn	scoped architecture drawing	passed	5.33 ms
  renders question fields as linked prose and dependency titles as plain text	not recorded	passed	0.56 ms
  combines relations on one ordered pair while retaining every original text row	not recorded	passed	0.73 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-architecture · selected component grid with distinct planned identities and complete unit edges · src/projections/studio/diagrams/slice.ts:219

  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.