A rules file that empties its graph leaves the next file's graph whole

outcome

Execute the copy rule on two rules files, the first changing the graph it receives and the second reading its own.

assumptions

• The world writes the probe corpus of the error example. The first rules file's body sets the length of graph.nodes and of graph.edges to zero and returns { findings: [] }. The second rules file's body returns one warning finding when graph.nodes is empty and { findings: [] } otherwise. The world runs sdp validate on the probe root with the first file, then the second, named by --rules, and reads the exit code and standard output.

Examples

Given a probe corpus the Protocol's validators find clean
Given a first rules file that {first: "empties the graph it receives"}
Given a second rules file that returns one warning when the graph it receives holds no node
When the probe corpus is validated with the rules files named by --rules in that order
Then the command exits {exitCode: 0}
Then the Protocol summary line reads {protocolSummary: "validate: 0 errors · 0 warnings (conformance + honesty over the one graph)"}
Then the corpus summary line reads {corpusSummary: "corpus rules: 0 errors · 0 warnings · 0 of 2 files failed (the corpus's own rules)"}

Verifier bindings

• test:protocol.validation.corpus-rules.copies-contain-changes · anchored · test anchor binding present · test/self-hosting-corpus-checks.test.ts:318

  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 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
  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.24 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.29 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	3.72 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.36 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	16.29 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	3.85 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	3.28 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	10.85 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	5.28 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	4.57 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.