The architecture lens draws components by context and layer, the planned beside the built

outcome

Let a person see the components the code realizes and the components the design plans, grouped by bounded context and layer, with what each uses and what it holds.

rule.contextAndLayer line 25 · specs/consumers/spec-studio.lenses.architecture.sdp.md:25

The lens draws every component the anchors realize, from recipe 17's component rows and the attributes the componentRows entry adds to them, grouped by its recorded context and layer as the architecture grid of spec:consumers.spec-studio.diagrams places it, and folds above the bound as that Spec states.

spec:consumers.spec-studio.lenses.architecture.planned-apart · enabled

rule.membershipAndUses line 26 · specs/consumers/spec-studio.lenses.architecture.sdp.md:26

The lens draws component membership, as the member count in each box, and uses, as edges between components, and nothing else: no port, external system, runtime layer or import the impact graph infers.

no example exercises it

rule.usesTable line 27 · specs/consumers/spec-studio.lenses.architecture.sdp.md:27

Beside the architecture drawing comes the component uses table, read from recipe 17's component rows and their counts of unit uses edges: one row per realized component as the user and one column per realized component as the used. A nonzero cell holds the count of anchored unit uses edges behind the pair and links to that use in the row component's detail; a zero cell between two components shows ·, with no anchored use recorded as hidden text and the legend · means no anchored use recorded, and the cell where a component meets itself stays empty. Planned uses, unresolved endpoints and uses within one component stay in their own readings and never enter the table. The table is not a drawing, and it reads in full without script and in print.

no example exercises it

rule.plannedApart line 28 · specs/consumers/spec-studio.lenses.architecture.sdp.md:28

Each component design no anchor realizes, a row of recipe 43's unrealized list, draws in the same grid by its planned context and layer as a planned box, with the uses it plans drawn dashed to the components it names, and is listed again in a Designed, not built section apart from the realized components; a planned use naming a component the lens draws no box for draws no edge and stays listed in its design's row.

spec:consumers.spec-studio.lenses.architecture.planned-apart · enabled

rule.differences line 29 · specs/consumers/spec-studio.lenses.architecture.sdp.md:29

A realized component whose design differs from it lists each differing field, as recipe 43's differing rows give it, with its planned and realized values in its detail, and a design value recipe 43 cannot read lists in the Designed, not built section as unreadable.

no example exercises it

rule.componentDetail line 30 · specs/consumers/spec-studio.lenses.architecture.sdp.md:30

Each realized component has a detail section on the lens page whose element id is its id, which its box and every link to it from another page open: its id, label, layer, context and role; its recorded file and line as text with a copy action; its members, each with its id, label, role and recorded file and line; the components it uses and is used by, each with the count of unit edges; the Specs it and its members satisfy and reference, linked, a component design its anchor satisfies among them; and its member diagram, every value read from its recipe 17 row.

no example exercises it

rule.codeRootedHere line 31 · specs/consumers/spec-studio.lenses.architecture.sdp.md:31

A component diagram rooted at code units, the view spec:consumers.structural-mermaid asked for, is this lens's member diagram, and the shipped Mermaid root draws none.

no example exercises it

rule.unresolvedStructure line 32 · specs/consumers/spec-studio.lenses.architecture.sdp.md:32

A memberOf target the graph holds no component for, and a uses edge an end of which resolves to no component, list in an Unresolved structure section as recipe 17 reports them, never dropped.

no example exercises it

rule.lensSummary line 33 · specs/consumers/spec-studio.lenses.architecture.sdp.md:33

The page opens with sentences the build counts from the two recipes' answers: the components realized and planned, the contexts and layers they state, the uses edges between components, and the designs that differ from their components.

no example exercises it

0 unkeyed rules.

Verifying examples

Given component anchors that realize {realized: 1} components in the context {context: "orders"} and the layer {layer: "domain"}
Given component designs that plan {planned: 1} more components in that context and layer, which no anchor realizes
When the build renders the architecture lens
Then the context's column holds {boxes: 2} component boxes in the layer's band
Then the diagram marks {plannedBoxes: 1} boxes planned
Then the Designed, not built section lists {listed: 1} component designs

Example space

Given component anchors that realize {realized:number} components in the context {context:string} and the layer {layer:"edge"|"application"|"domain"|"adapter"|"infrastructure"}
Given component designs that plan {planned:number} more components in that context and layer, which no anchor realizes
When the build renders the architecture lens
Then the context's column holds {boxes:number} component boxes in the layer's band
Then the diagram marks {plannedBoxes:number} boxes planned
Then the Designed, not built section lists {listed:number} component designs

componentRows line 42 · specs/consumers/spec-studio.lenses.architecture.sdp.md:42

{ label: string | null; file: string | null; line: number | null; role: string | null; layer: string | null; context: string | null; referencedSpecs: string[]; usesCounts: { component: string; edges: number }[]; usedByCounts: { component: string; edges: number }[] }, the fields recipe 17 adds to each component row: the component's own label, file, line, role, layer and context as its CodeNode records them, each null when the node records none or no node declares the component; the Specs the component and its members reference, sorted; and, sorted by component, the count of unit uses edges behind each pair usesOut and usedBy name. Each member row gains role: string | null, and every field the recipe returns today keeps its meaning.

no citation recorded

architecturePage line 36 · specs/consumers/spec-studio.lenses.architecture.sdp.md:36

in order, the page title Architecture, the summary sentences, the architecture diagram or its fold with one section per context, the component uses table, the Designed, not built section, the component details in id order, and the Unresolved structure section when it has rows.

usesTable line 37 · specs/consumers/spec-studio.lenses.architecture.sdp.md:37

a table captioned Which components use which in a named, keyboard-focusable scroll region, one row header and one column header per realized component, both in one order: by layer from edge to infrastructure, unlayered components last, then by id; each header names the component's label with its id as code.

designedNotBuilt line 38 · specs/consumers/spec-studio.lenses.architecture.sdp.md:38

a table with one row per unrealized design in Spec id order: the component design's Spec, linked; the planned component's id as code; its planned context, layer and role, or not stated; the components it plans to use; and whether its component anchor exists without satisfying it; a design whose value recipe 43 cannot read adds a row naming the design, the key and the unreadable value.

componentDetail line 39 · specs/consumers/spec-studio.lenses.architecture.sdp.md:39

a heading with the component's id as code and its label, a line with its layer, context and role in words, its source binding apart from its members, then Members grouped by recorded role, Uses with supporting unit edges at the table's fragment targets, Used by, any design differences, Satisfies and References, an empty list reading None, then the member diagram.

Verifier bindings

• spec:consumers.spec-studio.lenses.architecture.planned-apart · A component design no anchor realizes draws planned beside the built one · declared · example enabled · specs/consumers/spec-studio.lenses.architecture.planned-apart.sdp.md

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

  Test anchors: test:protocol.studio-architecture-planned-apart, test:protocol.studio-coverage-literal, test:protocol.studio-coverage-number, test:protocol.studio-diagram-folds-context, test:protocol.studio-diagram-folds-layer, test:protocol.studio-diagram-within-bound, test:protocol.studio-lenses, test:protocol.studio-tests-coverage-row. Specs verified by those bindings: spec:consumers.agent-surface.example-space-coverage, spec:consumers.agent-surface.example-space-coverage.number-not-enumerable, spec:consumers.agent-surface.example-space-coverage.uncovered-literal, spec:consumers.spec-studio.data.recipe-answers, spec:consumers.spec-studio.diagrams, spec:consumers.spec-studio.diagrams.folds-by-context, spec:consumers.spec-studio.diagrams.folds-by-layer, spec:consumers.spec-studio.diagrams.within-bound, spec:consumers.spec-studio.lenses, spec:consumers.spec-studio.lenses.architecture, spec:consumers.spec-studio.lenses.architecture.planned-apart, spec:consumers.spec-studio.lenses.evidence, spec:consumers.spec-studio.lenses.packs, spec:consumers.spec-studio.lenses.tests, spec:consumers.spec-studio.lenses.tests.coverage-row.

  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
  bounds and folds 12 components	Studio diagrams	passed	21.4 ms
  bounds and folds 45 components	Studio diagrams	passed	4.18 ms
  bounds and folds 50 components	Studio diagrams	passed	10.57 ms
  keeps every edge in an open text fallback	Studio diagrams	passed	1.76 ms
  orders grid contexts and layers and wraps cells within the fixed width budget	Studio diagrams	passed	3.65 ms
  draws planned-use edges dashed independently of planned box outlines	Studio diagrams	passed	0.48 ms
  checks the edge bound even when boxes fit	Studio diagrams	passed	0.41 ms
  places folded contexts and layers in their own bands below the grid	Studio diagrams	passed	3.19 ms
  places outgoing relation bands above the subject and folds ties in relation order	Studio diagrams	passed	9.26 ms
  folds trace relation groups and leaves member overflow as text	Studio diagrams	passed	2.95 ms
  keeps recipe and diagram edges in code-unit order under forced Czech collation	Studio lenses	passed	116.83 ms
  publishes all five ordered lenses and honest evidence without script	Studio lenses	passed	33.06 ms
  reads verifier binding from the delivery fact and gives absent coverage its own filter value	Studio lenses	passed	18.02 ms
  labels a primitive-only space with no examples not measurable and hides it under covered	Studio lenses	passed	14.75 ms
  classifies 'number' with points [ '1' ] and mixed=false as 'not-measurable'	Studio lenses	passed	26.11 ms
  classifies 'string' with points [ '"a"' ] and mixed=false as 'not-measurable'	Studio lenses	passed	22.83 ms
  classifies 'boolean' with points [ 'true' ] and mixed=false as 'not-measurable'	Studio lenses	passed	11.69 ms
  classifies '"a"|"b"' with points [] and mixed=false as 'uncovered'	Studio lenses	passed	9.5 ms
  classifies '"a"|"b"' with points [ '"a"' ] and mixed=false as 'uncovered'	Studio lenses	passed	11.11 ms
  classifies '"a"|"b"' with points [ '"a"', '"b"' ] and mixed=false as 'covered'	Studio lenses	passed	15.58 ms
  classifies '"a"|"b"' with points [ '"a"' ] and mixed=true as 'uncovered'	Studio lenses	passed	16.25 ms
  classifies '"a"|"b"' with points [ '"a"', '"b"' ] and mixed=true as 'covered'	Studio lenses	passed	20.2 ms
  renders member subjects, code spans, used-by counts, differences and empty components	Studio lenses	passed	14.17 ms
  describes evidence sources as not tracked	Studio lenses	passed	2.87 ms
  executes the bound example against a fresh world	An architecture within the bound draws in one diagram, the same bytes twice (spec:consumers.spec-studio.diagrams.within-bound)	passed	13 ms
  executes the bound example against a fresh world	An architecture over the bound folds by context (spec:consumers.spec-studio.diagrams.folds-by-context)	passed	7.68 ms
  executes the bound example against a fresh world	One context over the bound folds by layer (spec:consumers.spec-studio.diagrams.folds-by-layer)	passed	8.85 ms
  executes the bound example against a fresh world	A component design no anchor realizes draws planned beside the built one (spec:consumers.spec-studio.lenses.architecture.planned-apart)	passed	26.33 ms
  executes the bound example against a fresh world	A Spec's row on the tests lens counts its exercised keyed rules (spec:consumers.spec-studio.lenses.tests.coverage-row)	passed	13.82 ms
  executes the bound example against a fresh world	A literal no example binds is reported uncovered, and an unbound child is named (spec:consumers.agent-surface.example-space-coverage.uncovered-literal)	passed	4.85 ms
  executes the bound example against a fresh world	A number slot is not enumerable and reports no uncovered value (spec:consumers.agent-surface.example-space-coverage.number-not-enumerable)	passed	3.01 ms
  reuses the build's reader and validation findings during Studio recipe evaluation	not recorded	passed	3.94 ms
  documents the component and member fields recipe 17 adds	not recorded	passed	1.22 ms
  evaluates each shipped recipe once for its assigned parameters and shares Pack totals, with base false	not recorded	passed	14.63 ms
  evaluates each shipped recipe once for its assigned parameters and shares Pack totals, with base true	not recorded	passed	20.61 ms
  keeps label lines bounded and orders member depths numerically with outside units last	not recorded	passed	2.32 ms
  labels planned uses, reports unreadable designs and keeps unknown structure visible	not recorded	passed	8.33 ms
  gives unstated context and layer folds addressable text descriptions	not recorded	passed	1.14 ms
  names a single edge relation once in the legend and preserves its text equivalent	not recorded	passed	1.75 ms
  names solid and planned uses once without repeating edge labels	not recorded	passed	0.63 ms

• test:protocol.studio-architecture-maturity-requirement · anchored · test anchor binding present · test/studio-panels.test.ts:35

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

  Test anchors: test:protocol.studio-architecture-maturity-requirement. Specs verified by those bindings: spec:consumers.spec-studio.diagram-kinds.maturity-picture, spec:consumers.spec-studio.diagram-kinds.requirement-trace, spec:consumers.spec-studio.lenses.architecture, spec:consumers.spec-studio.lenses.architecture.unit-register, spec:consumers.spec-studio.pack-page.maturity-map, spec:consumers.spec-studio.spec-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
  orders both matrix axes by layer and id, links counts to supporting unit edges and keeps zeros compact	architecture tables and register	passed	74.8 ms
  groups unfamiliar and omitted roles in code-unit order, with source rows and separate binding lists	architecture tables and register	passed	27.09 ms
  draws equal categorical cells, exact counts and marks with ordered complete lists and unresolved members apart	maturity picture	passed	38.78 ms
  places the map inside the page's expander so a cell link opens its member list	maturity picture	passed	21.01 ms
  puts a uniform map behind a closed disclosure and uses solid fill above the mark bound	maturity picture	passed	321.53 ms
  selects the subject, refiners and verifying examples and keeps declared and anchored claims separate	requirement drawing	passed	35.44 ms
  keeps a refining verifier in the examples band and outside Specs apart	requirement drawing	passed	11.64 ms
  offers requirement syntax for the supported exact relation subset	requirement drawing	passed	10.84 ms
  counts the subject example when reporting selected verifying examples	requirement drawing	passed	8.27 ms
  folds the largest exact relation group deterministically and keeps every original binding in text	not recorded	passed	6.82 ms
  keeps a sparse large uses matrix readable with one visible zero legend and hidden cell words	not recorded	passed	17.36 ms
  contains the matrix's hidden cell words inside their scroll region	not recorded	passed	0.48 ms
  does not assert missing bindings on a boundary Spec whose bindings are outside the selected set	not recorded	passed	9.21 ms
  lets full component ids wrap so every uses column fits the printed page	not recorded	passed	1.26 ms
  keeps roles out of the pinned search record while preserving them on graph units	not recorded	passed	3.1 ms
  lists a unit whose recorded component is missing in No component and in unresolved structure	not recorded	passed	4.23 ms
  uses the singular member in a one-member Pack's uniform sentence	not recorded	passed	8.51 ms
  states each absent requirement band without implying that a populated drawing is missing	not recorded	passed	5.53 ms
  breaks equal requirement fold groups by 'kind' in lexical order	not recorded	passed	3.79 ms
  breaks equal requirement fold groups by 'direction' in lexical order	not recorded	passed	1.83 ms
  breaks equal requirement fold groups by 'claim' in lexical order	not recorded	passed	1.31 ms
  offers only the active relation and member renderers after requirement replaces realization	not recorded	passed	0.25 ms
  applies the closed-source print rule to both requirement and maturity drawings	not recorded	passed	0.3 ms

Requirement drawing

Decisions

• Architectural significance is annotated where it is realized

  Architectural significance is annotated on the anchor of the unit that realizes it. A code anchor may carry role, the architectural pattern the unit plays; a component: anchor may additionally carry layer, one of edge, application, domain, adapter, or infrastructure, and context, its bounded context. The component: anchor is anchored architecture: it is the declared component, and there is no separate architecture file, because the anchor sits where the component is realized. It is not the original design's declared Component that could exist before code; an unrealized component lives in Specs and never as an invented CodeNode. A role is a free, corpus-owned vocabulary whose taxonomy the census renders with counts from the graph; service, decider, projection, read-model, codec, contract, barrel, and utility are the lineage set, not a closed list. layer is a closed set, and a value outside it is an envelope error; layer or context on a non-component anchor is an envelope error. All three attributes are optional, and omission is lawful.

• 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-architecture-lens · renders recipe component rows and planned designs as architecture and member diagrams · src/projections/studio/pages/architecture-page.ts:50

  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.