A second structured entry is named, never left silently inert

outcome

Execute the one-point law where an example smuggles a second case into one document.

Examples

Given a parent spec whose example space declares the slot {dimension: "n"}
Given a refining example {exampleId: "spec:probe.create-order.multi"} whose used step {binding: "binds"} that slot
Given the example carries {entryCount: 2} structured entries
When the contracts are generated from the derived graph
Then the step contract for the example is emitted: {emitted: true}
Then the findings name {findingId: "contracts/multi-entry-example"}

Verifier bindings

• test:protocol.executable-contracts.multi-entry-example · the multi-entry point verifies the named second entry · anchored · test anchor binding present · test/self-hosting-extraction.test.ts:584

  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 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	One query invocation shares its extracted graph and validation result (spec:extraction.build-pipeline.same-invocation)	passed	13.53 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.19 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	0.66 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.42 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	1.07 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	1.8 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.7 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.32 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.33 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.