A case-only path collision withholds the whole contracts tree

outcome

Execute the all-or-nothing rule where two examples claim one case-folded contract path.

Examples

Given a parent spec whose example space declares the slot {dimension: "n"}
Given a refining example {exampleId: "spec:probe.create-order.same-case"} whose used step {binding: "binds"} that slot
Given a case-twin example {twinId: "spec:probe.create-order.same-Case"} whose contract path differs only by letter case
When the contracts are generated from the derived graph
Then the generated tree holds {fileCount: 0} files
Then the findings name {findingId: "contracts/case-colliding-path"}

Verifier bindings

• test:protocol.executable-contracts.case-colliding-path · the collision point verifies the all-or-nothing withholding · anchored · test anchor binding present · test/self-hosting-extraction.test.ts:593

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

  Test anchors: test:protocol.build-pipeline.same-invocation, test:protocol.example-runner.red-step-naming, test:protocol.example-runner.step-order, test:protocol.excludes.refused-path, test:protocol.excludes.segment-boundary, test:protocol.executable-contracts.case-colliding-path, test:protocol.executable-contracts.concreteness-refusal, test:protocol.executable-contracts.multi-entry-example, test:protocol.schema-versioning.declared-version. Specs verified by those bindings: spec:extraction.build-pipeline, spec:extraction.build-pipeline.same-invocation, spec:extraction.example-runner, spec:extraction.example-runner.red-step-naming, spec:extraction.example-runner.step-order, spec:extraction.excludes, spec:extraction.excludes.refused-path, spec:extraction.excludes.segment-boundary, spec:extraction.executable-contracts, spec:extraction.executable-contracts.case-colliding-path, spec:extraction.executable-contracts.concreteness-refusal, spec:extraction.executable-contracts.multi-entry-example, spec:extraction.schema-versioning, spec:extraction.schema-versioning.declared-version.

  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	One query invocation shares its extracted graph and validation result (spec:extraction.build-pipeline.same-invocation)	passed	16.91 ms
  executes the bound example against a fresh world	A prefix excludes its own tree and leaves a similar sibling standing (spec:extraction.excludes.segment-boundary)	passed	1.58 ms
  executes the bound example against a fresh world	A Windows-drive absolute path is refused rather than normalized (spec:extraction.excludes.refused-path)	passed	1.08 ms
  executes the bound example against a fresh world	A derived payload carries a schema version its consumer can read (spec:extraction.schema-versioning.declared-version)	passed	0.5 ms
  executes the bound example against a fresh world	An unbound slot in a used step earns no step contract (spec:extraction.executable-contracts.concreteness-refusal)	passed	2.41 ms
  executes the bound example against a fresh world	A second structured entry is named, never left silently inert (spec:extraction.executable-contracts.multi-entry-example)	passed	2.37 ms
  executes the bound example against a fresh world	A case-only path collision withholds the whole contracts tree (spec:extraction.executable-contracts.case-colliding-path)	passed	0.95 ms
  executes the bound example against a fresh world	A repeated step runs its one handler at each occurrence, in contract order (spec:extraction.example-runner.step-order)	passed	0.4 ms
  executes the bound example against a fresh world	A red step names itself before the assertion detail (spec:extraction.example-runner.red-step-naming)	passed	0.45 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.