Rendered from docs/probe-results/additive-tuning-of-2026-10-24-base-re-measure-of-scenario-3.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-base-re-measure-of-scenario-3.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-base-re-measure-of-scenario-3.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-3 arm, on claude-sonnet-5 at 2026-10-23. served version claude-sonnet-5, tree sha256:cd4a129e2acc3a76d856cec427c5e93dcec1dc28f47cfa0f4ef1e00c2dee24cc, selection sha256:8d4747a05d1213146c97d37a574a457ce8aeee431a3f9f6a9c67c79021d1f437, read set sha256:f18e4fd7eafa09aabd6204d8a41112a4af8892eb03c0b5d7fb9d3bf5f927b3a3, seed 0, harness 0.6.1. realized cost $103.27, which the adaptive layer reads as the cost of its own instrument.
145 events over 5 probes, in 145 sessions and 3821 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-3 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-3-p2-r1: not satisfied —
relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r10: satisfied — event 31:relation.reciprocity.missingreported nothing overdocs/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-3-p2-r11: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r12: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r13: satisfied — event 34:relation.reciprocity.missingreported nothing overdocs/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-3-p2-r14: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r15: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r16: satisfied — event 37:relation.reciprocity.missingreported nothing overdocs/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-3-p2-r17: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r18: satisfied — event 39:relation.reciprocity.missingreported nothing overdocs/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-3-p2-r19: satisfied — event 40:relation.reciprocity.missingreported nothing overdocs/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-3-p2-r2: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r20: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r21: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r22: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r23: satisfied — event 45:relation.reciprocity.missingreported nothing overdocs/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-3-p2-r24: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r25: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r26: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r27: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r28: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r29: satisfied — event 51:relation.reciprocity.missingreported nothing overdocs/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-3-p2-r3: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r4: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r5: satisfied — event 54:relation.reciprocity.missingreported nothing overdocs/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-3-p2-r6: satisfied — event 55:relation.reciprocity.missingreported nothing overdocs/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-3-p2-r7: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r8: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; no call to a tool of an MCP server session L1-additive-scenario-3-p2-r9: not satisfied —relation.reciprocity.missingreported over each of the 1 produced artifact; 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-3-p3-r1: satisfied — event 59, call 9:
Bash {"command":"grep -n \"five\\|\\b5\\b\" docs/interfaces/headwater-route.md docs/interfaces/headwater-mcp.md engine/crates/cli/src/main.rs engine/crates/probe/tests/fixtures.rs 2>/dev/null"}; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r10: satisfied — event 60, call 7:Bash {"command":"grep -rn \"five\\|Budget { pointers\\|pointers: 5\\|default.*5\\|5 pointers\\|top five\\|top 5\\|rank.*of 5\" /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r10/docs/interfaces/headwater-route.md /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r10/docs/spec/05-ai-integration.md /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r10/docs/spec/glossary.md"}; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r11: satisfied — event 61, call 2:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r11/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r12: satisfied — event 62, call 21:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r12/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r13: satisfied — event 63, call 4:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r13/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r14: satisfied — event 64, call 2:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r14/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r15: satisfied — event 65, call 2:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r15/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r16: satisfied — event 66, call 2:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r16/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r17: satisfied — event 67, call 21:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r17/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r18: satisfied — event 68, call 5:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r18/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r19: satisfied — event 69, call 12:Bash {"command":"echo \"=== headwater-route.md ===\" && grep -n \"five\\|default.*budget\\|pointers.*default\\|budget.*default\" docs/interfaces/headwater-route.md\necho \"=== headwater-mcp.md ===\" && grep -n \"five\\|pointers\" docs/interfaces/headwater-mcp.md\necho \"=== 05-ai-integration.md ===\" && grep -n \"five\\|default.*pointer\\|pointer.*default\" docs/spec/05-ai-integration.md\necho \"=== decision 0070 ===\" && grep -n \"five\\|default\" docs/decisions/0070-the-matched-purposes-take-turns-at-a-route-budget-and-each-pointer-states-what-reached-it.md\necho \"=== README.md ===\" && grep -n \"five\\|pointers.*default\\|budget\" README.md\necho \"=== DEVELOPING.md ===\" && grep -n \"five\\|pointers.*default\\|budget\" DEVELOPING.md\n"}; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r2: satisfied — event 70, call 2:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r2/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r20: satisfied — event 71, call 6:Grep docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r21: satisfied — event 72, call 3:Bash {"command":"cat /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r21/docs/interfaces/headwater-route.md 2>/dev/null | head -200","description":"Show headwater-route interface doc"}; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r22: satisfied — event 73, call 2:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r22/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r23: satisfied — event 74, call 3:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r23/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r24: satisfied — event 75, call 5:Bash {"command":"cd /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r24\necho \"=== main.rs ===\"\ngrep -n \"5\\b\\|five\" engine/crates/cli/src/main.rs | grep -i \"route\\|budget\\|pointer\\|five\" \necho \"=== mcp.rs ===\"\ngrep -n \"5\\b\\|five\" engine/crates/query/src/mcp.rs | grep -i \"route\\|budget\\|pointer\\|five\"\necho \"=== headwater-route.md ===\"\ngrep -n \"5\\b\\|five\" docs/interfaces/headwater-route.md\n"}; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r25: satisfied — event 76, call 24:Bash {"command":"grep -n \"five\\|budget\\|withheld\\|pointers\" docs/interfaces/headwater-route.md"}; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r26: satisfied — event 77, call 6:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r26/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r27: satisfied — event 78, call 7:Bash {"command":"grep -n -i \"five\\|pointer\" docs/interfaces/headwater-route.md | head -40"}; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r28: satisfied — event 79, call 7:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r28/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r29: satisfied — event 80, call 4:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r29/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r3: satisfied — event 81, call 7:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r3/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r4: satisfied — event 82, call 2:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r4/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r5: satisfied — event 83, call 4:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r5/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r6: satisfied — event 84, call 7:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r6/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r7: satisfied — event 85, call 2:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r7/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r8: satisfied — event 86, call 3:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r8/docs/interfaces/headwater-route.md; no call to a tool of an MCP server session L1-additive-scenario-3-p3-r9: satisfied — event 87, call 6:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p3-r9/docs/interfaces/headwater-route.md; 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-3-p4-r1: 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-3-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-3-p4-r11: 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-3-p4-r12: not satisfied — 2 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server
session L1-additive-scenario-3-p4-r13: 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-3-p4-r14: 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-3-p4-r15: 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-3-p4-r16: not satisfied — 7 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server
session L1-additive-scenario-3-p4-r17: 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-3-p4-r18: not satisfied — 7 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server
session L1-additive-scenario-3-p4-r19: satisfied — event 98, call 8:
Grep /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p4-r19/docs/spec/15-the-recorder-contract.md; no call to a tool of an MCP server session L1-additive-scenario-3-p4-r2: 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-3-p4-r20: 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-3-p4-r21: 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-3-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-3-p4-r23: 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-3-p4-r24: not satisfied — 7 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p4-r25: 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-3-p4-r26: 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-3-p4-r27: 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-3-p4-r28: 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-3-p4-r29: 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-3-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-3-p4-r4: not satisfied — 7 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p4-r5: 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-3-p4-r6: 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-3-p4-r7: not satisfied — 2 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p4-r8: 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-3-p4-r9: not satisfied — 5 recorded calls, and none named any of the 1 document; 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-3-p5-r1: satisfied — event 117, call 5:
Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r1/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r10: satisfied — event 118, call 7:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r10/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r11: not satisfied — 76 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r12: satisfied — event 120, call 4:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r12/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r13: not satisfied — 84 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r14: satisfied — event 122, call 3:Bash {"command":"find docs/how-to -iname \"*relocate*\"; echo ---; cat docs/how-to/relocate-a-shelf.md 2>/dev/null","description":"Find and read the relocate-a-shelf how-to guide"}; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r15: satisfied — event 123, call 23:Bash {"command":"find docs -iname \"relocate-a-shelf*\"; cat docs/how-to/relocate-a-shelf.md 2>/dev/null"}; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r16: satisfied — event 124, call 13:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r16/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r17: satisfied — event 125, call 4:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r17/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r18: satisfied — event 126, call 6:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r18/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r19: satisfied — event 127, call 39:Bash {"command":"cat docs/how-to/relocate-a-shelf.md"}; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r2: satisfied — event 128, call 32:Bash {"command":"cat docs/how-to/relocate-a-shelf.md"}; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r20: satisfied — event 129, call 7:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r20/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r21: satisfied — event 130, call 8:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r21/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r22: not satisfied — 80 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r23: satisfied — event 132, call 5:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r23/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r24: satisfied — event 133, call 28:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r24/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r25: satisfied — event 134, call 22:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r25/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r26: not satisfied — 53 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r27: not satisfied — 72 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r28: not satisfied — 60 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r29: satisfied — event 138, call 58:Bash {"command":"cd /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r29\ngrep -n \"verifications\" docs/how-to/relocate-a-shelf.md\necho \"---\"\ngrep -n \"verifications\" docs/process/evaluations/the-build-order-as-a-multi-agent-system.md"}; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r3: not satisfied — 48 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r4: satisfied — event 140, call 6:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r4/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r5: satisfied — event 141, call 16:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r5/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r6: satisfied — event 142, call 16:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r6/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r7: satisfied — event 143, call 7:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p5-r7/docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r8: satisfied — event 144, call 7:Read docs/how-to/relocate-a-shelf.md; no call to a tool of an MCP server session L1-additive-scenario-3-p5-r9: satisfied — event 145, call 13:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-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-3-p1-r1: satisfied — event 1, call 5:
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-3-p1-r10: not satisfied — 1 recorded call, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r11: not satisfied — 1 recorded call, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r12: 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-3-p1-r13: not satisfied — 1 recorded call, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r14: not satisfied — 1 recorded call, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r15: not satisfied — 1 recorded call, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r16: not satisfied — 1 recorded call, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r17: 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-3-p1-r18: satisfied — event 10, call 3:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p1-r18/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-3-p1-r19: not satisfied — 1 recorded call, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r2: satisfied — event 12, call 6:Bash {"command":"cat \"/mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p1-r2/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md\"","description":"Read decision record 0087 that superseded 0069"}; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r20: satisfied — event 13, call 4:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p1-r20/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-3-p1-r21: satisfied — event 14, 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-3-p1-r22: not satisfied — 2 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r23: satisfied — event 16, call 3: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 | head -100"}; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r24: satisfied — event 17, call 4:Bash {"command":"cat \"/mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p1-r24/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md\"","description":"Read decision record 0087"}; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r25: satisfied — event 18, call 4:Bash {"command":"cat \"/mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p1-r25/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md\"","description":"Read decision record 0087"}; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r26: satisfied — event 19, call 6:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-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-3-p1-r27: satisfied — event 20, call 3:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-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-3-p1-r28: not satisfied — 1 recorded call, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r29: not satisfied — 2 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r3: not satisfied — 2 recorded calls, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r4: satisfied — event 24, call 4:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-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-3-p1-r5: satisfied — event 25, call 6:Bash {"command":"cat \"/mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p1-r5/docs/decisions/0087-no-paragraph-limit-joins-the-language-rule-because-most-paragraphs-past-six-sentences-hold-one-topic.md\" 2>/dev/null | head -100","description":"Read decision 0087 that supersedes 0069"}; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r6: not satisfied — 1 recorded call, and none named any of the 1 document; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r7: satisfied — event 27, call 4: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 record 0087"}; no call to a tool of an MCP server session L1-additive-scenario-3-p1-r8: satisfied — event 28, call 4:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-p1-r8/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-3-p1-r9: satisfied — event 29, call 4:Read /mnt/build/hw-1777/base-1/a/ws/L1-additive-scenario-3-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
76 of 145 graded sessions satisfied their expectation: 52.4%, in a 95% interval of 44.3% to 60.4%. 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.