REVIEW BRIEF — phase6-probe-scope (Phase 6: the survivor scan counts the workload's own surface — F24)
REV: 12f1f839a140d56275a0b5b01840b9795db95f82
FINAL: 14b6862ded5ecb01982ffd24fdbc24124695bdfa
REVIEW ACCEPTANCE: scripts/check-scope 12f1f839a140d56275a0b5b01840b9795db95f82 14b6862ded5ecb01982ffd24fdbc24124695bdfa docs/research/phase6-probe-scope-brief.md
FOCUS: the scoping above all — does the scoped scan stop counting the unrelated carrier while still catching a live workload survivor, is the seam one surface rule rather than an exclusion list, and does F26's repoint-reading claim hold against the brief's text and the delivered probe.
SEVERITY SCALE: P0 blocks the step; P1 is serious; P2 is minor.
QUESTIONS TO ATTACK:

  F26 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
  The repoint instruction names the assertion as "the assertion inverted (the carrier alive, the scoped scan empty)". The probe's old line is `assert carrier.pid in found`; the reading taken is its precise inverse, `assert carrier.pid not in found` (the scoped scan is empty *of the carrier*), with the carrier's liveness asserted beside it. The parenthetical also admits a literal whole-scan `assert not found` reading, which would red on any live workload survivor — the F1/F20 class the brief says stays with the pins — and would couple this host-side probe to unrelated host state, the over-match brittleness F24 is about. Next action is the planner's: a later committed brief's text correction naming the assertion form.
  FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the repoint lands as delivered (carrier-pid inversion) and is green at FINAL.

  1. The scoping above all — the delivery's one question. Drive it live against FINAL on scratch copies diff-verified against git show 12f1f83:… before use: (a) the scoped scan stops counting the unrelated carrier — the review probe's assertion red at REV on the whole-table scan, green at FINAL on the scoped scan — re-drive both directions yourself and name the outcomes; (b) a live workload survivor is still counted — the F1/F20 pins green at FINAL over the changed helper — re-run the module battery and name the line; (c) the seam is one surface rule (the plan's executor-invocation argv pair) rather than an exclusion list — which pin goes red, and on which member, if the plan's command tuple changes shape (a second argv element added, the interpreter path moved)? Report each guarantee as falsified-with-reproducer or attacked-and-not-falsified with the method.

  2. F26's repoint-reading claim. The implementer's F26 says the brief's parenthetical admits both the precise inverse (`assert carrier.pid not in found`, taken) and a literal whole-scan (`assert not found`, refused as brittle). Verify against the brief's text and the delivered probe: does the parenthetical admit both readings, is the taken reading the only one consistent with the rest of the brief (the F1/F20 survivor class staying with the pins, the over-match brittleness F24 is about), and does the delivered probe assert exactly the taken form with the carrier's liveness beside it? If a second consistent reading stands, the step returns to planning; if the taken reading is the only consistent one, F26 carries as filed. File a finding per falsified class.

  3. The report's forms and counts (J-class). FINAL is the work commit 14b6862ded5ecb01982ffd24fdbc24124695bdfa, never the report commit 0e45fb4 — verify rather than taking the report's word. Re-run the brief's ACCEPTANCE lines at FINAL (fast suite 981 passed, 109 deselected; the batch3 module battery 13 passed; static gated clean with advisory Found 104 errors. unchanged; docs printed line with 0 errors — every figure the gate's own printed line, rule 14, never the REV line quoted in CONTEXT); TRIPPED: none matches check-scope's tripped: line and REVIEW ACCEPTANCE is green run first. git diff 12f1f839a140d56275a0b5b01840b9795db95f82 14b6862ded5ecb01982ffd24fdbc24124695bdfa --stat touches only the IN SCOPE files plus the brief (no committed test edit outside them — verify). SHAPES' none-claim with the split halves against rule 7: the carrier half as the repointed probe, the workload-survivor half as the F1/F20 pins — adjudicate whether the split buries a shape the suite should build as one. INHERITED's F24 fixed-close and F21/F22/F23/F26 carries against the received set. Every field of the report present and filled, nothing outside the template added. Standing battery: scripts/check-tests (your full run — record it in VERIFIED).

--- BEGIN BRIEF UNDER REVIEW (copy of docs/research/phase6-probe-scope-brief.md; the committed file is authoritative) ---
IMPLEMENTER BRIEF — phase6-probe-scope (Phase 6: the survivor scan counts the workload's own surface — F24)
GOAL: The survivor assertion counts the workload's own surface, not the host's argv: an unrelated process that merely carries the probe path in its command line is no longer counted a teardown survivor — pinned by `tests/test_batch3_execution.py` itself — and the review probe that holds the over-match shape is absorbed or repointed the way its own docstring names.
CONTEXT: The phase-6 chain stands delivered with non-terminal report rows ([record.md](../record.md#record): REV `d9c660e` latest); its accepted reviews converge (no P0/P1) but carry F24 (P2, ORIGIN: CODE): the module's `_probe_pids` (`tests/test_batch3_execution.py:178`–`:190`) scans the whole process table for any cmdline containing the literal `/work/probe.py`, so an unrelated process that merely carries that string in argv is counted a survivor — measured three times over, when this step's own commit message quoted the path and the invoking `bash -c '<commit>'` wrapper plus the `git commit` process failed the F1 pin with exactly two survivors until the message was reworded. The review probe that holds the shape (`tests/test_review_phase6_sandbox_sweep.py::test_the_probe_pid_scan_counts_an_unrelated_argv_carrier`, slow-marked, host-only guard) rides until this fix absorbs it: its own docstring names the absorption signal — when the delivered scan stops finding the carrier, the probe reddens, and the absorbing brief deletes the probe or repoints it at the scoped surface. `REV` names the step's base — the parent of this brief commit — and is not claimed to be `FINAL`'s parent.
INHERITED:

From `docs/research/phase6-sandbox-sweep-implementer.md`, its `INHERITED` block verbatim:

  From the brief's INHERITED block, the items still open, copied verbatim:

  F13 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
  The brief names the pin's red as "N consecutive grades of the known-good tree produce non-identical verdicts (PASS on one run, CANDIDATE_TIMEOUT on the next)". In this environment the known-good tree's `gate-check-tests` grade is stable well under the fixture's 60.0s deadline (ten pin runs, 50 grades, ~37–46s each, every grade PASS), so the pin passes at REV. The lottery's grade-flip needs a candidate whose suite fails — a failing tree's hypothesis tests shrink, and the shrinking varies the suite's wall — and the near-deadline flip is the neutralisation test's broken-source candidate (FAIL→CANDIDATE_TIMEOUT, 3/3 at REV). The pin's assertion and the seeded determinism are correct; the brief's stated candidate is simply not the one that flips here.
  FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the pin and the seed land as delivered.

  F14 (P2, ORIGIN: DOCUMENT, carried) — the F8 red evidence is load-borne and the implementer report does not say so; a later actor re-driving the red on an idle host sees green and may conclude the red is chimeric. Next action is the planner's: carry the load condition into the carried F8 block (or a later committed brief's correction), the seed and the pins stand as delivered.

  F15 (P2, ORIGIN: CODE, carried) — killed runs leak intermediate probe trees and no janitor reaps them; the shared tmpfs inode table filled to 3 free and the standing battery's first run died ENOSPC until 81 leaked trees were pruned by hand. Next action is the harness owner's (a tombstone/janitor keyed by the run identity) or a planner ruling that scratch hygiene is each session's duty.

  F16 (P2, ORIGIN: CODE, carried) — the seeded determinism is wall-bounded: at the fixture's 60.0s deadline the near-deadline candidate's seeded grade flips FAIL→CANDIDATE_TIMEOUT under host load (measured once mid-run and once at a 62.44s wall), so the pin's green determinism is stable-half evidence only. Next action is the fixture owner's: raise the grading deadline for near-deadline candidates (the 300.0 default gives a >=5x margin here) or an OWNER ruling that the deadline's load envelope is governed, not deterministic.

  F17 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
  The brief's boundary-fix instruction is internally inconsistent (FINDINGS, F17): the double-fork pin must leave no descendant alive after the exit while the F10 q1e boundary shape must survive the fix, and the two name one live shape (a session-escaped middleman spawning a session-escaped sleeper then exiting before the deadline, the sleeper adopted by init) that no container boundary can kill and spare at once. The GOAL reading was taken (F11/F12 fixed by the container boundary, both pins green at FINAL, no committed discriminating member changed verdict); the boundary this step retires is the named init-adopted orphan, and the new boundary is what the child never forked. Next action is the planner's: a later committed brief's text correction — the q1e-survival sentence, F12's "without also catching the documented boundary" clause, and the boundary sentence in the module docstring this step corrected in code.
  FIXED: no regression test — the reading is delivered in the work commit and its evidence is the two reds above and the FINAL battery above; the correction itself is a committed brief's prose, which has none.

  F21 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
  The implementer report's supervisor-module battery line records the module battery widened by the review module (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py tests/test_review_phase6_supervisor.py --durations=5` — `15 passed in 17.72s`) and never the brief's documented form (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py --durations=5`) with the documented form's own printed line. The wide form is a strict superset (the module's 13 pins plus the review module's 2 probes), green, and every figure it carries is its own printed line — nothing is evaded; but the brief's acceptance names the documented command, and the report's own template requires each claimed figure to name the command that actually ran while this acceptance line names both the documented form it did not run and the wide form it did. This review ran the documented form at FINAL — `13 passed in 12.46s` — so the figures stand; what carries is the report-text deviation from the brief's named battery.
  FIXED: no regression test — a document deviation in a committed report, which only a later step (or the planner's correction of the carried note) absorbs; the documented form's gate line is in this review's VERIFIED.

  F22 (P2, ORIGIN: BRIEF) — the brief's review-block copy of the carried F17 finding is truncated mid-sentence (the literal `(line truncated to 2000 chars)` marker), which rides as a carried text-correction to the planner.

  Then each finding marked carried by this step, with its ID:

  F23 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the brief's named REV red is not reproducible in a sandbox drive; see FINDINGS above).

  F24 | SEVERITY: P2 | ORIGIN: CODE | STATE: carried (the global `_probe_pids` scan matches any process carrying the probe path in argv; see FINDINGS above).

  Received-set dispositions kept: F19 fixed by the prior step's absorbed pin; F20 fixed by this step (above); F11/F12/F18 fixed as recorded in the reports that filed them; F13–F17, F21, F22 carried with their named owners.

From `docs/research/phase6-sandbox-sweep-review.md` — its `INHERITED` block, then each carried finding's block from its `FINDINGS` section, moved verbatim (rule 2 governs the planner's copy of this block; the review's received set is the sweep brief's carried F20/F21 plus its F19/F22, F19 fixed at FINAL by the prior step, F20 fixed by this step under the F23 repoint, F21/F22 carried):

  From the brief under review, the still-open items copied verbatim (the chain through the cleanup review's carried set), then the step's own carried findings:

  F13 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
  The brief names the pin's red as "N consecutive grades of the known-good tree produce non-identical verdicts (PASS on one run, CANDIDATE_TIMEOUT on the next)". In this environment the known-good tree's `gate-check-tests` grade is stable well under the fixture's 60.0s deadline (ten pin runs, 50 grades, ~37–46s each, every grade PASS), so the pin passes at REV. The lottery's grade-flip needs a candidate whose suite fails — a failing tree's hypothesis tests shrink, and the shrinking varies the suite's wall — and the near-deadline flip is the neutralisation test's broken-source candidate (FAIL→CANDIDATE_TIMEOUT, 3/3 at REV). The pin's assertion and the seeded determinism are correct; the brief's stated candidate is simply not the one that flips here.
  FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the pin and the seed land as delivered.

  F14 (P2, ORIGIN: DOCUMENT, carried) — the F8 red evidence is load-borne and the implementer report does not say so; a later actor re-driving the red on an idle host sees green and may conclude the red is chimeric. Next action is the planner's: carry the load condition into the carried F8 block (or a later committed brief's correction), the seed and the pins stand as delivered.

  F15 (P2, ORIGIN: CODE, carried) — killed runs leak intermediate probe trees and no janitor reaps them; the shared tmpfs inode table filled to 3 free and the standing battery's first run died ENOSPC until 81 leaked trees were pruned by hand. Next action is the harness owner's (a tombstone/janitor keyed by the run identity) or a planner ruling that scratch hygiene is each session's duty.

  F16 (P2, ORIGIN: CODE, carried) — the seeded determinism is wall-bounded: at the fixture's 60.0s deadline the near-deadline candidate's seeded grade flips FAIL→CANDIDATE_TIMEOUT under host load (measured once mid-run and once at a 62.44s wall), so the pin's green determinism is stable-half evidence only. Next action is the fixture owner's: raise the grading deadline for near-deadline candidates (the 300.0 default gives a >=5x margin here) or an OWNER ruling that the deadline's load envelope is governed, not deterministic.

  F17 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
  The brief's boundary-fix instruction is internally inconsistent (FINDINGS, F17): the double-fork pin must leave no descendant alive after the exit while the F10 q1e boundary shape must survive the fix, and the two name one live shape (a session-escaped middleman spawning a session-escaped sleeper then exiting before the deadline, the sleeper adopted by init) that no container boundary can kill and spare at once. The GOAL reading was taken (F11/F12 fixed by the container boundary, both pins green at FINAL, no committed discriminating member changed verdict); the boundary this step retires is the named init-adopted orphan, and the new boundary is what the child never forked. Next action is the planner's: a later committed brief's text correction — the q1e-survival sentence, F12's "without also catching the documented boundary" clause, and the boundary sentence in the module docstring this step corrected in code.
  FIXED: no regression test — the reading is delivered in the work commit and its evidence is the two reds above and the FINAL battery above; the correction itself is a committed brief's prose, which has none.

  F21 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
  The implementer report's supervisor-module battery line records the module battery widened by the review module (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py tests/test_review_phase6_supervisor.py --durations=5` — `15 passed in 17.72s`) and never the brief's documented form (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py --durations=5`) with the documented form's own printed line. The wide form is a strict superset (the module's 13 pins plus the review module's 2 probes), green, and every figure it carries is its own printed line — nothing is evaded; but the brief's acceptance names the documented command, and the report's own template requires each claimed figure to name the command that actually ran while this acceptance line names both the documented form it did not run and the wide form it did. This review ran the documented form at FINAL — `13 passed in 12.46s` — so the figures stand; what carries is the report-text deviation from the brief's named battery.
  FIXED: no regression test — a document deviation in a committed report, which only a later step (or the planner's correction of the carried note) absorbs; the documented form's gate line is in this review's VERIFIED.

  F22 (P2, ORIGIN: BRIEF) — the brief's review-block copy of the carried F17 finding is truncated mid-sentence (the literal `(line truncated to 2000 chars)` marker), which rides as a carried text-correction to the planner.

  F23 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
  The brief's named red at REV is not reproducible — "at REV, with the delivered single-capture _kill, the racing forker's final tail forks plus the double-forked sleeper survive teardown adopted out-of-tree". In a NAMESPACE_V1 drive the workload is the PID-namespace init, _descendants always captures it (descendants=128 namespace_inits=[…]), and its SIGKILL makes the kernel reap the whole namespace (init death kills the namespace; measured: 124 live descendants after a weakened kill, 0 after the init dies), so the delivered _kill already leaves no descendant alive and the pin passes at REV. The sweep lands as the brief's requested defense-in-depth port and the pin as a regression pin; the named red is chimeric for the sandbox, and the load-borne leak F20 measured rode the nested-grading/oracle path, not a standing sandbox-drive race.
  FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the sweep and the pin land as delivered, and the pin's red class is the kill-surface mutant above.

  F24 | SEVERITY: P2 | ORIGIN: CODE | STATE: carried
  The module's `_probe_pids` (`tests/test_batch3_execution.py`) scans the whole process table for any cmdline containing the literal probe path, so an unrelated process that merely carries that string in argv is counted a survivor. Measured: three `git commit` hook runs failed the F1 pin with exactly two survivors — the `bash -c '<commit>'` wrapper and the `git commit` process — whose command lines carried the path because this step's commit message quoted it; rewording the message cleared it. `scripts/check-tests`' `SERIAL_MODULES` isolation protects against sibling workers but not against the invoking command line.
  FIXED: no regression test — `_probe_pids` is reused verbatim as the brief instructs and is not edited; the named failing assertion at REV is the F1 pin's `assert survivors == [], f"escaped workload survived teardown: {survivors}"`, reproduced only when the invoking command line names the probe path.

Expected dispositions (rule 8 forms): F24 fixed with red evidence (named below — the scan stops counting the unrelated argv-carrier while still catching a live workload survivor, red on the whole-table scan, green at FINAL). F21/F22/F23 stay carried with their named owners and text corrections. F11/F12/F18/F19/F20/F25 stay fixed as recorded in the reports that filed them. F13–F17 stay carried with their named owners and text corrections.

IN SCOPE: tests/test_batch3_execution.py, tests/test_review_phase6_sandbox_sweep.py
RESIDUALS:

none — rule 3 selection for this brief's `IN SCOPE`: no `docs/residuals.md` trigger glob matches `tests/test_batch3_execution.py` or `tests/test_review_phase6_sandbox_sweep.py` (the `PILOT-R*` triggers name `planning_pilot.py`, `controller.py`, `reducer.py`, `decomposition.py`, `model.py`, and `derive_obligations.py`; the store is byte-verified against `docs/residuals.md` before this brief's commit, rule 2). No residual row rides, so the residual half of `scripts/check-scope` has nothing to carry here and it prints `tripped: none` — the line your report's `TRIPPED` field copies.

OUT OF SCOPE:
- Editing this brief file (`docs/research/phase6-probe-scope-brief.md`). A committed brief is never modified; a re-cut is a new file.
- `scripts/check-tests` in full: the gate script is delivered and frozen; the scoping rides as test code the module holds, not as a gate-script edit. If the gate script needs a code change, stop and report `IN SCOPE` as insufficient.
- `src/orchestrator/sandbox.py`, `src/orchestrator/sandbox_launcher.py`: the runner and launcher stand; no kill-surface, containment, or teardown change rides here. The sweep is delivered; this step scopes the scan that grades it.
- `scripts/supervise_run.py`, `tests/test_phase6_supervisor.py`, `tests/test_review_phase6_supervisor_boundary.py`: the supervisor chain is delivered; no supervisor, boundary, or leaf change rides here.
- `src/orchestrator/project_oracle.py`, `tests/test_phase3_project_oracle.py`, `tests/test_review_phase6_grading_seed.py`: the seed chain is closed; no grading-gate, deadline, or determinism change rides here.
- `src/orchestrator/oracle.py`, `src/orchestrator/experiment_phases.py`, `src/orchestrator/hidden_oracle.py`, `src/orchestrator/conformance.py`: no grading-runner, calibration, probe-shape, or trusted-gate change rides here. No new event type, no `docs/tables/*` change and no table regeneration, no `docs/event-catalogue.md` change.
- `docs/self-host.md`, `docs/residuals.md`, `docs/record.md`, `docs/method.md`, `docs/templates/`: the status edit, if any is owed, rides a later step; this step scopes the scan.
- Every committed test module except the two IN SCOPE modules — `tests/test_milestone3_sandbox.py`, `tests/test_axis2_robustness.py`, `tests/test_phase6_supervisor.py`, and every other committed module are read-only here. No committed test file outside IN SCOPE is edited. If a pin would have to change for acceptance to pass, stop and report `IN SCOPE` as insufficient.
- `tests/open_defects.yaml` and the registry's meta-tests: no registration rides (F24 is the open finding whose next brief is this one; no `test_bug_*` name — the open-defect registry would then own it).
- Registry and control files: `tests/counterexamples.yaml`, `tests/guard_mutation_matrix.yaml`, `tests/fixture_fidelity.yaml`, `tests/verifier_registry.yaml`, `tests/spend_paths.yaml`, `tests/invariants.py`, `tests/helpers.py`, `pytest.ini`, tool configuration.
- No new dependencies, no tooling configuration, no reformatting. No new exception class and no `*Executor`/`*ModelClient` class or provider-registry registration.

ACCEPTANCE: Commands (run every one and paste what each prints into `VERIFIED`; expected result is green, exit 0, for each):

    scripts/check-tests --fast
    .venv/bin/python -m pytest tests/test_batch3_execution.py --durations=5
    scripts/check-static
    scripts/check-docs
    scripts/check-scope 12f1f83 <FINAL> docs/research/phase6-probe-scope-brief.md

Every `pytest` line names `.venv/bin/python -m pytest` deliberately (the interpreter rule: the bare `pytest` on PATH has no `pytest-timeout` and `pytest.ini`'s `strict_config = true` rejects it — run these lines exactly as written and claim them under these names). The batch3 line rides because this brief's IN SCOPE touches files under `tests/` (rule: a brief that adds a file under `tests/` or `scripts/` also names `pytest tests/test_phase3_project_oracle.py`; this brief edits the batch3 pin module and the riding review probe, so the line is the step's own battery — the oracle line is not named because the pin runs no trial and no sandboxed suite beyond its own probe drives). The docs gate is expected green with 0 errors — and every count figure you write in `VERIFIED` is the gate's own printed line, never the REV line quoted in this brief's CONTEXT and never recomputed from memory (rule 14). The scope line is expected green, exit 0, printing `tripped: none` (and the `claimed:` line the parser prints). `REV` below names the step's base — the parent of this brief commit — and is not claimed to be `FINAL`'s parent.

The scan scoping (`tests/test_batch3_execution.py`, in place — `_probe_pids` only): the whole-table argv scan becomes a workload-surface scan — one seam over the surface the pins grade, not an enumerated list of exclusions (rule 13). The scan counts a pid only where its command line names the workload's own executor invocation (the delivered `/usr/bin/python3 /work/probe.py` argv pair the module's own `_probe_plan` and both pins drive — the plan's `command` tuple, matched as the pair, not as the path substring), so an unrelated process that merely carries the probe-path literal in argv is never counted, while a live workload survivor still is. The `finally` cleanup loops that reuse `_probe_pids` (`:233`, `:308`) inherit the scoping with no separate edit — they call the same helper. No new helper surface, no per-pin allowlist, no caller-side filtering: the helper itself is the seam. If the scoping cannot be delivered inside `_probe_pids` without touching the pins' assertions or the runner, stop and report `IN SCOPE` as insufficient.

The probe absorption (`tests/test_review_phase6_sandbox_sweep.py`, in place — the riding probe's own disposition, as its docstring names): when the delivered scan stops finding the carrier, the probe reddens on the first battery run after the fix — that red is the absorption signal, and this brief consumes it. Delete the probe module (the docstring's first named disposition), or repoint it at the scoped surface — exactly one of the two, named in `CHANGED`. Deletion needs no red (the docstring orders it; the scoped scan's own red below is the evidence). A repoint carries the same slow mark and host-only guard with the assertion inverted (the carrier alive, the scoped scan empty).

Red evidence at `REV` `12f1f83` (each unit must be replayable; the batch3 module is green at REV modulo the riding probe, so the red is the probe's own measured class re-driven at REV on a scratch copy diff-verified against `git show 12f1f83:…` before use). `FIXED` names the pin's node id, the command, the named failing assertion, and the delivered file's line numbers or none. Named reds to produce: F24's carrier red — at REV, with the delivered whole-table scan, a literal-retaining `bash -c` carrier alive beside a completed drive is counted a survivor (the named failing assertion is the probe's `assert carrier.pid in found` — the review's measured `1 passed in 0.24s` green on the over-match, inverted here: on the delivered scan the carrier is found; on the scoped scan it is not — so the red unit is the scoped scan failing the probe's assertion at REV, `1 failed`, the carrier counted where it must not be). An error or a hang is not red, the assertion must be the thing that failed. The F1/F20 pins stay green over the same change (the workload survivor still counted — the module battery at FINAL is the standing proof).

Named shapes to build — the list of shapes, not the number of tests. One shape needs at least one test, and every named shape needs one:

- `Scoped-scan shape` (F24): an unrelated argv-carrier is not counted a survivor while a live workload survivor still is — the scoped `_probe_pids`, red at REV on the whole-table scan (the probe's assertion), green at FINAL.

EXPECTED WALLS: the measured baseline at this brief's drafting: `scripts/check-tests --fast` — `981 passed, 109 deselected in 93.90s (0:01:33)`; `scripts/check-docs` — `395 Total / 180 Unique / 395 OK / 0 Errors` (this session's HEAD line); `scripts/check-static` — exit 0, gated `All checks passed!`, advisory `Found 104 errors.` unchanged; `.venv/bin/python -m pytest tests/test_batch3_execution.py --durations=5` — `13 passed in 4.87s` (sweep review's VERIFIED at FINAL `36cd049`: slowest `1.10s` racing pin, `0.88s` cancellation pin, `0.59s` F1 escape pin). The scoping changes no drive wall — the scan is a `/proc` walk either way — so no new timeout rides; the module's existing pins keep their marks.

REV: 12f1f83
CLOSE OUT: no
DIVERGENCES: none
REVIEW: one session — the scoping above all: does the scoped scan stop counting the unrelated carrier while still catching a live workload survivor (the probe's assertion red at REV on the whole-table scan, green-or-absorbed at FINAL), is the seam one surface rule rather than an exclusion list (rule 13), is the `IN SCOPE` line plain with scope green, are the docs figures the gate's own printed lines (rule 14), and does the step touch only the IN SCOPE files with every committed battery green and no committed test edit outside them. Whether anything remains open after this step — the brief-text corrections — is the loop's exit input: report findings and let the planner decide (cycle step 5).

You implement one brief. You do not plan, re-scope, or decide what the work is. Read every file
in IN SCOPE before editing it; if what you find contradicts the brief, report that instead of
guessing. Modify only what IN SCOPE names. If you find uncommitted changes in the tree, stop and say
so. A new module under tests/ that runs trials or sandboxed suites carries
pytestmark = pytest.mark.slow at module level: the oracle's internal gate runs the fast suite
(-m "not slow") and an unmarked trial-running module breaks it. Stop and report rather than
improvise when IN SCOPE is
insufficient, the brief contradicts the code, you have already failed twice at this goal, or the
requirement is ambiguous and no single reading is consistent with the rest of the brief. If exactly
one reading is consistent, take it and file a FINDING with ORIGIN: BRIEF that names the reading you
took. No new dependencies, no tooling configuration, no reformatting. Run every ACCEPTANCE command;
fix what is in scope and report what is not.

A defect in the brief is a FINDING, never METHOD FRICTION. METHOD FRICTION is only for the method and
its templates: any place you deviated from them, found them ambiguous, or found them silent. Report
friction you worked around — that is the section the method learns from.

Commit your own work. When ACCEPTANCE passes, commit the files you changed, and only those, in one
commit whose message ends with the trailer `Actor: IMPLEMENTER`. That commit's full sha is FINAL.
Then append docs/templates/report.txt verbatim, fill it in, write it to
docs/research/<phase>-<subject>-implementer.md, and commit it in a second commit with the same
trailer. Do not amend the first commit to add the report: FINAL must not change after the report
names it. If you cannot commit, stop and say so; do not leave work uncommitted for someone else to
commit.
--- END BRIEF UNDER REVIEW ---
You did not write this code and you will not fix it; a finding is output, not an action. The step's decision is the planner's (cycle step 5): report findings, never decisions. The commits under review carry the trailer Actor: IMPLEMENTER; if your session wrote any of them, stop and say so. Run REVIEW ACCEPTANCE first: it is the method's only gated check. The ACCEPTANCE lines inside the brief under review are the implementer's; re-run them to verify the delivery, and run scripts/check-tests as your standing battery — the full suite is your falsification ground — recording both in VERIFIED. The embedded brief is a convenience copy: if the standalone file it names differs, file a FINDING with ORIGIN: BRIEF and review against the committed file.
You may create new test files to prove a finding, and modify nothing else. If a failing test would need registering in tests/open_defects.yaml, say so in the report and leave the registration to the next implementer brief rather than editing that file; the registry owns test_bug_* pins only, and a test_review_* probe rides red until absorbed. Read pre-images with git show <rev>:..., not the implementation's account of them. Run every mutant on a scratch copy of the tree, and diff each mutant against git show <rev>:... before trusting its result. Attempt to falsify the brief, not only the code: a finding that the brief was wrong is a finding, and so is a defect the implementer filed only as friction. Answer every item under QUESTIONS TO ATTACK. Answers live in the form's fields — a finding in FINDINGS, a measurement in VERIFIED/SHAPES. An added review's QUESTIONS TO ATTACK come only from the implementer's report — never from another review's findings. Enumerate the shapes you probed that the existing suite does not build, as a list; zero with a stated reason is legitimate. Report each guarantee as falsified-with-reproducer or attacked-and-not-falsified with the method.
Commit your own work: your new test files and your report, together, in one commit whose message ends with the trailer Actor: REVIEWER. Append docs/templates/report.txt verbatim, fill it in, and write it to docs/research/<phase>-<subject>-review.md. If you cannot commit, stop and say so.
