A realized component that differs from its design gives one row per field

outcome

Execute the realization comparison on one realized component whose layer and uses differ from its design.

assumptions

• The world writes the probe root of the unrealized-design example and adds a comment-form anchor for the planned component that satisfies the design Spec and states the realized layer, with one impl: member whose anchor uses the member of the component the realized-uses slot names.

Examples

Given a component design for {componentId: "component:probe.history"} that plans the layer {plannedLayer: "domain"} and uses {plannedUses: "component:probe.kernel"}
Given the component anchor for that design {anchor: "satisfies the design"}
Given that anchor states the layer {realizedLayer: "application"} and its member uses {realizedUses: "component:probe.audit"}
When the realization comparison runs
Then the comparison lists {unrealized: 0} unrealized designs, {matching: 0} matching designs and {differing: 2} differing rows
Then the differing fields are {fields: "layer, uses"}

Verifier bindings

• test:protocol.model.planned-architecture.differing-layer-and-uses · anchored · test anchor binding present · test/self-hosting-corpus-checks.test.ts:367

  External run evidence from test/self-hosting-corpus-checks.test.ts

  Test anchors: test:protocol.model.planned-architecture.differing-layer-and-uses, test:protocol.model.planned-architecture.matching-design, test:protocol.model.planned-architecture.unrealized-design, test:protocol.validation.architecture-constraints.forbidden-layer-pair, test:protocol.validation.architecture-constraints.isolated-context-as-rule, test:protocol.validation.architecture-constraints.unstated-layer-unclassified, test:protocol.validation.corpus-rules.copies-contain-changes, test:protocol.validation.corpus-rules.error-finding-fails, test:protocol.validation.corpus-rules.malformed-finding-fails, test:protocol.validation.corpus-rules.warning-finding-informs. Specs verified by those bindings: spec:model.planned-architecture, spec:model.planned-architecture.differing-layer-and-uses, spec:model.planned-architecture.matching-design, spec:model.planned-architecture.unrealized-design, spec:validation.architecture-constraints, spec:validation.architecture-constraints.forbidden-layer-pair, spec:validation.architecture-constraints.isolated-context-as-rule, spec:validation.architecture-constraints.unstated-layer-unclassified, spec:validation.corpus-rules, spec:validation.corpus-rules.copies-contain-changes, spec:validation.corpus-rules.error-finding-fails, spec:validation.corpus-rules.malformed-finding-fails, spec:validation.corpus-rules.warning-finding-informs.

  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
  executes the bound example against a fresh world	A rules file that empties its graph leaves the next file's graph whole (spec:validation.corpus-rules.copies-contain-changes)	passed	21.88 ms
  executes the bound example against a fresh world	An error from a corpus rule fails validation and leaves the Protocol's line alone (spec:validation.corpus-rules.error-finding-fails)	passed	4.69 ms
  executes the bound example against a fresh world	A finding with no subject fails its rules file (spec:validation.corpus-rules.malformed-finding-fails)	passed	4.13 ms
  executes the bound example against a fresh world	A warning from a corpus rule informs and passes (spec:validation.corpus-rules.warning-finding-informs)	passed	3.83 ms
  executes the bound example against a fresh world	A domain member that uses an infrastructure member breaks a forbidden pair (spec:validation.architecture-constraints.forbidden-layer-pair)	passed	15.92 ms
  executes the bound example against a fresh world	The walk named as a rules file fails validation on an isolation breach (spec:validation.architecture-constraints.isolated-context-as-rule)	passed	4.55 ms
  executes the bound example against a fresh world	A component with no layer leaves its edge unclassified (spec:validation.architecture-constraints.unstated-layer-unclassified)	passed	2.97 ms
  executes the bound example against a fresh world	A realized component that differs from its design gives one row per field (spec:model.planned-architecture.differing-layer-and-uses)	passed	6.29 ms
  executes the bound example against a fresh world	A realized component that matches its design gives no row (spec:model.planned-architecture.matching-design)	passed	17.77 ms
  executes the bound example against a fresh world	A component design no anchor satisfies is listed as unrealized (spec:model.planned-architecture.unrealized-design)	passed	6.93 ms

Requirement drawing

• Satisfying or referencing units: no recorded binding.

Decisions

No decision record named.

No implementation neighborhood recorded.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.