outcomeA repeated step runs its one handler at each occurrence, in contract order
spec:extraction.example-runner.step-orderPacks: pack:self-hosting-v1
Design: no design entries · no pinned declarations · no decisions
Findings: no errors, no warnings
specs/extraction/example-runner.step-order.sdp.md
No open questions and no blocking questions; implementation binding none, verifier binding present, and expected-outcome oracle none.
Given
a contract whose given step repeats {occurrences: 2} times before one when step and one then stepWhen
the bound plan runs against a fresh world
Then
the world records the handler trace {trace: "given 2 | given 2 | when | then"}
the run {outcome: "completes"}Composing needs the script.
Intent
- Execute the contract-order and one-handler-per-step laws over a repeating given step.
Behavior
Examples
Given a contract whose given step repeats {occurrences: 2} times before one when step and one then step
When the bound plan runs against a fresh world
Then the world records the handler trace {trace: "given 2 | given 2 | when | then"}
Then the run {outcome: "completes"}Verification
Verifier bindings
- test:protocol.example-runner.step-order · the step-order point verifies contract order and the one handler per step · anchored · test anchor binding present ·
test/self-hosting-extraction.test.ts:789External run evidence from
test/self-hosting-extraction.test.tsTest 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
Design view
Requirement drawing
- Satisfying or referencing units: no recorded binding.
The diagram as text
- spec:extraction.example-runner.step-order: A repeated step runs its one handler at each occurrence, in contract order · declared Spec
- spec:extraction.example-runner: A bound example runs its contract steps against a fresh world · declared Spec
- test:protocol.example-runner.step-order: the step-order point verifies contract order and the one handler per step · anchored test binding · binding present ·
test/self-hosting-extraction.test.ts:789 - spec:extraction.example-runner.step-order refines spec:extraction.example-runner · declared
- spec:extraction.example-runner.step-order verifies spec:extraction.example-runner · declared
- test:protocol.example-runner.step-order verifies spec:extraction.example-runner.step-order · anchored
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred and chosen syntax: requirementDiagram; exact refines, satisfies and verifies, with claim words in nodes and per-edge comments.
Decisions
No decision record named.
Runtime
No implementation neighborhood recorded.
Runtime observation: not tracked.
Evidence
Runtime observation: not tracked.
Build attestations: not tracked.
Deployments: not tracked.
Bills of materials: not tracked.
Impact
- E2: verifies · declared
The diagram as text
- spec:extraction.example-runner: A bound example runs its contract steps against a fresh world
- spec:extraction.example-runner.step-order: A repeated step runs its one handler at each occurrence, in contract order
- spec:extraction.example-runner.step-order refines spec:extraction.example-runner · declared
- spec:extraction.example-runner.step-order verifies spec:extraction.example-runner · declared
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred syntax: flowchart. Chosen syntax: labelled flowchart, preserving exact relations, claims and folds.
Rests on
- refines · spec:extraction.example-runner · stated ready, floor ready
Rested on by
No Spec rests on this Spec.
Relations
| Relation and direction | Other end | Claim | Reason | Exercised keys |
|---|---|---|---|---|
| refines · outgoing | A bound example runs its contract steps against a fresh worldspec:extraction.example-runner · resolves | declared | None | None |
| verifies · outgoing | A bound example runs its contract steps against a fresh worldspec:extraction.example-runner · resolves | declared | None | contractOrder, oneHandlerPerStep |
Bindings
Implementation binding: none
Design reference: none
Verifier binding: present
- test:protocol.example-runner.step-order · the step-order point verifies contract order and the one handler per step · anchored ·
test/self-hosting-extraction.test.ts:789· test anchor
Expected-outcome oracle: none
Runtime observation: not tracked.
Run results: not recorded in the graph.
Findings
None.
Composing (0)
Composing needs the script.