Architecturally significant units are annotated where they are realized

outcome

Annotate each architecturally significant unit on the anchor of the code that realizes it, with its role, its component's layer and bounded context, and the designs it references, and declare uses where a dependency is architectural, so the graph answers architecture questions from the code itself. Architectural significance adds no Spec kind, no node type, and no vocabulary registry.

architecturally significant unit line 18 · specs/model/structural-patterns.sdp.md:18

A code unit with exported public surface or cross-component reach whose contract or responsibility a designer or builder must understand; export status or import rank alone is insufficient. Ports, shared data shapes, pipeline stages, decision tables, catalogs, layout policies and adapters may qualify. Its anchor records component membership, a role and references to the designs it answers to. An architectural dependency is declared as uses, normally between components; a unit's own uses is optional.

structural attributes line 19 · specs/model/structural-patterns.sdp.md:19

role on any code anchor; layer and context on a component: anchor; they describe the unit's architecture and carry no readiness or delivery fact, and the census renders their taxonomy from the graph.

accepted set line 20 · specs/model/structural-patterns.sdp.md:20

The set of architecturally significant units in a corpus is an owner-reviewed declaration, never derived from imports or exports; anchors are curated, never a coverage quota.

Verifier bindings

• test:protocol.structural-self-binding · checks the accepted membership and helper coverage, authored uses, and pinned anchor roles, layers and contexts · anchored · test anchor binding present · test/self-hosting-graph.test.ts:88

  External run evidence from test/self-hosting-graph.test.ts

  Test anchors: test:protocol.self-hosting, test:protocol.structural-self-binding. Specs verified by those bindings: spec:model.structural-patterns, spec:protocol.self-hosting, spec:protocol.significant-units-review, spec:protocol.structural-self-binding.

  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
  traces changes to 'test/self-hosting-oracle/structural-e…' through its realizing anchor	the self-hosting corpus	passed	80.98 ms
  traces changes to 'test/helpers/validator-probes.ts' through its realizing anchor	the self-hosting corpus	passed	47.73 ms
  reifies the root corpus without an extraction finding	the self-hosting corpus	passed	0.46 ms
  reports exactly the retained verifier gaps and no unbacked prose mention	the self-hosting corpus	passed	41.83 ms
  holds the frozen corpus totals	the self-hosting corpus	passed	1.84 ms
  permits a named second diagram view in the authored element-id contract	the self-hosting corpus	passed	47.7 ms
  states the owner queue's reader lookup by Spec and question key	the self-hosting corpus	passed	39.89 ms
  names vault and stamp beside every other help verb in the authored contract	the self-hosting corpus	passed	35.48 ms
  rosters exactly the authored Spec, Pack, and anchor node ids	the self-hosting corpus	passed	1.78 ms
  carries the authored descriptors of the carrier family	the self-hosting corpus	passed	3.09 ms
  carries the authored descriptors of the protocol family	the self-hosting corpus	passed	0.63 ms
  carries the authored descriptors of the extraction family	the self-hosting corpus	passed	1.44 ms
  carries the authored descriptors of the validation family	the self-hosting corpus	passed	3.3 ms
  carries the authored descriptors of the model family	the self-hosting corpus	passed	1.61 ms
  carries the authored descriptors of the observation family	the self-hosting corpus	passed	0.44 ms
  carries the authored descriptors of the consumers family	the self-hosting corpus	passed	9.85 ms
  carries the authored descriptors of the decisions family	the self-hosting corpus	passed	1.35 ms
  leaves no authored Spec outside the families	the self-hosting corpus	passed	0.73 ms
  derives exactly the authored declared relations	the self-hosting corpus	passed	11.91 ms
  holds the frozen stated-readiness distribution	the self-hosting corpus	passed	0.38 ms
  derives the Pack membership edges from the manifest, in manifest order	the self-hosting corpus	passed	1.51 ms
  carries the Pack aggregate nodes exactly as authored	the self-hosting corpus	passed	0.26 ms
  derives the independent zero-to-many binding edge roster	the self-hosting corpus	passed	6.62 ms
  rosters exactly the accepted component set	the self-hosting corpus	passed	0.22 ms
  gives every owned impl/api CodeNode exactly one component	the self-hosting corpus	passed	18.95 ms
  derives exactly the sparse authored component uses edges	the self-hosting corpus	passed	1.6 ms
  covers every accepted architecturally significant unit	the self-hosting corpus	passed	929.96 ms
  gives every accepted unit a readable responsibility label	the self-hosting corpus	passed	13.58 ms
  detects a missing accepted member independently of the source	the self-hosting corpus	passed	7.56 ms
  detects extra unrostered membership independently of the source	the self-hosting corpus	passed	45.81 ms
  finds every converted comment anchor at its block's first line	the self-hosting corpus	passed	17.2 ms
  projects every anchor and code node at the line its declaration occupies	the self-hosting corpus	passed	97.45 ms
  rejects comment-only and string activation sites and accepts executable calls	the self-hosting corpus	passed	1.2 ms
  keeps every anchor beside the site it binds	the self-hosting corpus	passed	1381.89 ms
  derives the duplicate-ids delivery facts from the bindings, never from authoring	the self-hosting corpus	passed	1.28 ms
  derives sdp-import realization from its direct code and child verifier bindings	the self-hosting corpus	passed	0.32 ms

Requirement drawing

• Declared verifying examples: no declared verifying example.

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.extract · the carrier and source pipeline · src/extract/index.ts:192 · 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
• 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.anchor-extraction · anchor reification seam: the constant form and the comment form · src/extract/anchors.ts:121

  Component: component:protocol.extract · the carrier and source pipeline · src/extract/index.ts:192 · layer application · context protocol

  Uses

  None.

• impl:protocol.census-page · renders the derived census and runtime taxonomy projection · src/projections/census.ts:21

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

  Uses

  None.

• impl:protocol.structural-self-binding · realizes the declared significant-unit set and its structural self-binding · test/self-hosting-oracle/structural-edges.ts:76

  Uses

  None.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.