The engine's structural self-binding covers its architecturally significant units

outcome

Structural recipes, the census and the Design Review answer architecture questions about the engine from its own anchors.

rule.criterion line 23 · specs/protocol/structural-self-binding.sdp.md:23

The engine applies the structural-patterns model's significance criterion: 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.

no example exercises it

rule.membership line 24 · specs/protocol/structural-self-binding.sdp.md:24

Every architecturally significant engine unit carries component membership through a realizing anchor; a helper with no realization target of its own is covered through the nearest realization anchor that consumes it.

no example exercises it

rule.architecturalUses line 25 · specs/protocol/structural-self-binding.sdp.md:25

An architectural dependency of the engine is declared as uses, normally from one engine component to another; a unit's own uses is optional.

no example exercises it

rule.componentUses line 26 · specs/protocol/structural-self-binding.sdp.md:26

A component-level uses declaration tracks real value or type imports from another component's source files; imports made only to author anchors through the stable-id or anchor-builder modules confer no edge.

no example exercises it

rule.acceptedSet line 27 · specs/protocol/structural-self-binding.sdp.md:27

The accepted set of architecturally significant engine units is an owner-reviewed declaration among the self-hosting suite's pinned expectations, never derived from imports or exports; the suite checks every accepted unit's declared membership and rejects unrostered membership edges.

no example exercises it

rule.layerAndContext line 28 · specs/protocol/structural-self-binding.sdp.md:28

Every engine component: anchor declares its layer and its context.

no example exercises it

rule.role line 29 · specs/protocol/structural-self-binding.sdp.md:29

Every architecturally significant engine unit carries a role.

no example exercises it

rule.decisionReferences line 30 · specs/protocol/structural-self-binding.sdp.md:30

A unit reaches the decisions that shape it through the Specs it satisfies and their decidedBy relations, and may reference a decision directly when it answers to that design. A unit satisfies a Spec when it realizes at least one promise of it, and the satisfying units together realize every promise; a unit that follows a design without realizing a promise references it. Code never satisfies a decision Spec. A design that builds on existing code states that through its own dependsOn or refines to the Spec the code satisfies.

no example exercises it

0 unkeyed rules.

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

• Bindings are optional, plural, and may reference a design

  On a code anchor, satisfies is optional and plural; on a test anchor, verifies is plural and non-empty. The constant form accepts one ref(…) or a fresh array literal of them. Each resolving target confers its fact, and implemented stays a whole-Spec fact. An anchored edge references runs from a CodeNode to a Spec, from references?: readonly SpecId[] on a code anchor; it may target any Spec, decisions included, confers no delivery fact, moves no readiness floor, and the drift alarm ignores it. It says this code answers to that design without claiming to realize it: the unit follows the design without realizing any of its promises, or realizes part of a Spec whose remaining promises no unit yet realizes, so a change to the design asks the code to follow. A design that builds on existing code states that by a typed relation to the Spec the code satisfies, never by a reference from the code. A target named in both satisfies and references is an error. An identity-only code anchor, with no satisfies and no references, is lawful: it mints a CodeNode for structure and for byFile, and nothing else.

• 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.

• 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.