Rendered from docs/probe-results/additive-tuning-of-2026-10-24-skills-round-1-confirmation-scenario-4.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

The result of docs/probe-runs/additive-tuning-of-2026-10-24-skills-round-1-confirmation-scenario-4.md

A probe result is a function of committed inputs and of nothing else: the transcript at docs/probe-runs/additive-tuning-of-2026-10-24-skills-round-1-confirmation-scenario-4.md and the state it stands at, the expectations the probes it names declare, the version of the grader that evaluated them, and for a compared arm the result of the other arm. Fetch those and this file comes back.

The run this transcript recorded

A additive run in the scenario-4 arm, on claude-sonnet-5 at 2026-10-24. served version claude-sonnet-5, tree sha256:bc9ff145ae7bc2a53ece57ca1442ff3d5ef1528cca5641cbfc877419836a844a, selection sha256:8d4747a05d1213146c97d37a574a457ce8aeee431a3f9f6a9c67c79021d1f437, read set sha256:f18e4fd7eafa09aabd6204d8a41112a4af8892eb03c0b5d7fb9d3bf5f927b3a3, seed 0, harness 0.6.1. realized cost $105.71, which the adaptive layer reads as the cost of its own instrument.

145 events over 5 probes, in 145 sessions and 3929 tool calls.

The engine confirmed the taxonomy, that every member of the run identity is present, the membership of every probe named, that no key outside the closed set appears, and that a realized cost was recorded. Present is not confirmed. This page names the lock, the selection and the read set the transcript recorded, and it compares none of them with the tree in front of a reader. headwater generate and headwater probe stale name what moved since the recording, and neither one fails for it. It graded nothing: a verdict is a function of this transcript, the expectations these probes declare and a grader version, and headwater probe grade is the verb that holds all three.

The selection this transcript names is sha256:8d4747a05d1213146c97d37a574a457ce8aeee431a3f9f6a9c67c79021d1f437, and the probes graded below are the probes it was planned over, as this corpus declares them now. A probe added to this corpus after the recording is not a session this run owed. The tree, the seed and the harness above are provenance and nothing compares them.

The read_set digest above covers every probe of the selection and every document one of them examines, by path and content. This file names it as provenance and compares it with nothing, and the same holds for the lock and the selection: an edit to a document, a new probe or a moved lock leaves these bytes alone. headwater generate names each result whose recorded lock, read set or selection moved, and headwater probe stale takes the digest and reports which recorded results a change voided. Neither one fails for it.

Graded by grader 0.5.1. A additive run in the scenario-4 arm, on claude-sonnet-5 at served version claude-sonnet-5.

The verdicts

• HW-PROBE-a-session-records-which-obligation-an-evaluation-discharged (sufficiency, expects patched) session L1-additive-scenario-4-p2-r1: satisfied — event 30: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r10: satisfied — event 31: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r11: satisfied — event 32: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r12: satisfied — event 33: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r13: satisfied — event 34: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r14: satisfied — event 35: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r15: satisfied — event 36: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r16: satisfied — event 37: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r17: satisfied — event 38: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r18: satisfied — event 39: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r19: satisfied — event 40: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r2: satisfied — event 41: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r20: satisfied — event 42: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r21: satisfied — event 43: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r22: satisfied — event 44: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r23: satisfied — event 45: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r24: satisfied — event 46: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r25: satisfied — event 47: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r26: satisfied — event 48: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r27: satisfied — event 49: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r28: satisfied — event 50: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r29: not satisfied — relation.reciprocity.missing reported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r3: satisfied — event 52: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r4: satisfied — event 53: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r5: satisfied — event 54: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r6: satisfied — event 55: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r7: satisfied — event 56: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r8: satisfied — event 57: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server session L1-additive-scenario-4-p2-r9: satisfied — event 58: relation.reciprocity.missing reported nothing over docs/evaluations/governs-edges-what-an-anchor-reaches-what-covers-it-when-it-ages-and-where-a-session-meets-it.md; no call to a tool of an MCP server
• HW-PROBE-a-session-that-changes-a-verb-s-default-reaches-the-verb-s-interface-contract (navigability, expects opened) session L1-additive-scenario-4-p3-r1: satisfied — event 59, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root .","description":"Explain the headwater-route.md document and its edges"}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r10: satisfied — event 60, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root .","description":"Explain headwater-route.md document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r11: satisfied — event 61, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r11/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r12: satisfied — event 62, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r12/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r13: satisfied — event 63, call 5: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r13/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r14: satisfied — event 64, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r14/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r15: satisfied — event 65, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r15/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r16: satisfied — event 66, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r16/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r17: satisfied — event 67, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r17/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r18: satisfied — event 68, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r18/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r19: satisfied — event 69, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r19/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r2: satisfied — event 70, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r2/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r20: satisfied — event 71, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root .","description":"Explain the headwater-route.md document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r21: satisfied — event 72, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root ."}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r22: satisfied — event 73, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root .","description":"Explain the headwater-route interface document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r23: satisfied — event 74, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r23/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r24: satisfied — event 75, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r24/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r25: satisfied — event 76, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r25/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r26: satisfied — event 77, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r26/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r27: satisfied — event 78, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root .","description":"Explain the headwater-route interface document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r28: satisfied — event 79, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root . 2>&1"}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r29: satisfied — event 80, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root .","description":"Explain the headwater-route.md document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r3: satisfied — event 81, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root .","description":"Explain the headwater-route.md document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r4: satisfied — event 82, call 5: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root ."}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r5: satisfied — event 83, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r5/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r6: satisfied — event 84, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root .","description":"Explain the headwater-route document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r7: satisfied — event 85, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p3-r7/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r8: satisfied — event 86, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root .","description":"Explain the headwater-route interface document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p3-r9: satisfied — event 87, call 4: Bash {"command":"./engine/target/dev-release/headwater explain docs/interfaces/headwater-route.md --root .","description":"Explain the headwater-route interface document"}; no call to a tool of an MCP server
• HW-PROBE-a-session-that-changes-the-recorder-reaches-the-recorder-contract (navigability, expects opened) session L1-additive-scenario-4-p4-r1: satisfied — event 88, call 6: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root .","description":"Explain Spec 15 document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r10: not satisfied — 5 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r11: not satisfied — 3 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r12: not satisfied — 3 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r13: satisfied — event 92, call 5: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root ."}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r14: not satisfied — 9 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r15: satisfied — event 94, call 6: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root ."}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r16: satisfied — event 95, call 8: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root . 2>&1 | head -200","description":"Explain the recorder contract spec document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r17: not satisfied — 18 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r18: not satisfied — 8 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r19: not satisfied — 5 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r2: satisfied — event 99, call 11: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root ."}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r20: not satisfied — 6 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r21: not satisfied — 6 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r22: not satisfied — 5 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r23: satisfied — event 103, call 7: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root . 2>&1 | head -100","description":"Explain the recorder contract spec document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r24: satisfied — event 104, call 6: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p4-r24/docs/spec/15-the-recorder-contract.md; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r25: satisfied — event 105, call 15: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root . 2>&1 | head -150","description":"Explain the governing spec document for the recorder contract"}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r26: not satisfied — 6 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r27: satisfied — event 107, call 6: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root .","description":"Explain the recorder contract document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r28: not satisfied — 5 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r29: satisfied — event 109, call 7: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root . 2>&1 | head -100"}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r3: not satisfied — 4 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r4: satisfied — event 111, call 9: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root .","description":"Explain the recorder contract document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r5: satisfied — event 112, call 6: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root . 2>&1","description":"Explain the recorder contract document"}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r6: satisfied — event 113, call 7: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root ."}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r7: satisfied — event 114, call 6: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root ."}; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r8: not satisfied — 6 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p4-r9: satisfied — event 116, call 9: Bash {"command":"./engine/target/dev-release/headwater explain docs/spec/15-the-recorder-contract.md --root ."}; no call to a tool of an MCP server
• HW-PROBE-a-session-that-moves-a-shelf-reaches-the-relocation-guide (discovery, expects opened) session L1-additive-scenario-4-p5-r1: satisfied — event 117, call 22: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r1/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r10: satisfied — event 118, call 14: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r10/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r11: satisfied — event 119, call 17: Read docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r12: satisfied — event 120, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r12/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r13: satisfied — event 121, call 7: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r13/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r14: satisfied — event 122, call 6: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r14/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r15: satisfied — event 123, call 6: Bash {"command":"cat docs/how-to/relocate-a-shelf.md"}; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r16: satisfied — event 124, call 14: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r16/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r17: satisfied — event 125, call 6: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r17/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r18: satisfied — event 126, call 8: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r18/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r19: satisfied — event 127, call 5: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r19/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r2: satisfied — event 128, call 6: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r2/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r20: satisfied — event 129, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r20/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r21: satisfied — event 130, call 10: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r21/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r22: not satisfied — 86 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r23: satisfied — event 132, call 8: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r23/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r24: satisfied — event 133, call 6: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r24/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r25: satisfied — event 134, call 14: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r25/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r26: satisfied — event 135, call 5: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r26/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r27: satisfied — event 136, call 4: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r27/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r28: satisfied — event 137, call 6: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r28/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r29: satisfied — event 138, call 9: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r29/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r3: satisfied — event 139, call 5: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r3/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r4: satisfied — event 140, call 8: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r4/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r5: satisfied — event 141, call 7: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r5/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r6: satisfied — event 142, call 6: Read docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r7: satisfied — event 143, call 5: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r7/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r8: satisfied — event 144, call 6: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r8/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-4-p5-r9: satisfied — event 145, call 10: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p5-r9/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server
• HW-PROBE-an-agent-reaches-the-adjudication-when-the-decision-a-tombstone-links-is-superseded (navigability, expects opened) session L1-additive-scenario-4-p1-r1: satisfied — event 1, call 7: Read docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r10: satisfied — event 2, call 9: Read docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r11: satisfied — event 3, call 7: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r11/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r12: satisfied — event 4, call 7: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r12/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r13: satisfied — event 5, call 6: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r13/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r14: satisfied — event 6, call 7: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r14/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r15: not satisfied — 5 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r16: satisfied — event 8, call 6: Read docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r17: satisfied — event 9, call 8: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r17/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r18: satisfied — event 10, call 7: Bash {"command":"cat /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r18/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md","description":"Read the governing decision 0087"}; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r19: satisfied — event 11, call 8: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r19/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r2: satisfied — event 12, call 9: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r2/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r20: satisfied — event 13, call 8: Read docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r21: satisfied — event 14, call 7: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r21/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r22: satisfied — event 15, call 8: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r22/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r23: satisfied — event 16, call 7: Read docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r24: satisfied — event 17, call 7: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r24/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r25: satisfied — event 18, call 5: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r25/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r26: satisfied — event 19, call 6: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r26/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r27: satisfied — event 20, call 9: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r27/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r28: not satisfied — 4 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r29: satisfied — event 22, call 6: Bash {"command":"cat docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md","description":"Read decision 0087 in full"}; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r3: satisfied — event 23, call 7: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r3/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r4: satisfied — event 24, call 8: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r4/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r5: satisfied — event 25, call 6: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r5/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r6: satisfied — event 26, call 9: Read docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r7: satisfied — event 27, call 6: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r7/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r8: satisfied — event 28, call 7: Bash {"command":"cat docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md 2>/dev/null || find . -iname \"0087*\"","description":"Read decision 0087 full text"}; no call to a tool of an MCP server session L1-additive-scenario-4-p1-r9: satisfied — event 29, call 8: Read /mnt/build/hw-1777/skills-r1-confirm/a/ws/L1-additive-scenario-4-p1-r9/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md; no call to a tool of an MCP server

145 of 145 sessions that recorded their calls made no call to a tool of an MCP server. 0 sessions recorded no calls.

The rate, and the denominator it is over

127 of 145 graded sessions satisfied their expectation: 87.6%, in a 95% interval of 81.2% to 92.0%. The denominator is the graded sessions and never the selected probes. 0 sessions reached no verdict, and a session with no verdict is outside both halves of that fraction.

An interval that overlaps the previous run's is variance and one that does not is drift. This is one arm, so it estimates no effect: an efficacy claim is a comparison of two results, and the arm each one recorded is on it.