IMPLEMENTER BRIEF — GOAL: CONTEXT: <2-5 lines> INHERITED: <> IN SCOPE: RESIDUALS: <> OUT OF SCOPE: ACCEPTANCE: EXPECTED WALLS: REV: CLOSE OUT: yes | no DIVERGENCES: none | REVIEW: 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 multi-minute drive (a suite the 120s session ceiling would kill) runs through the background tooling: start it detached, capture its output to files, and read the printed lines from those files — the command line stays exactly as documented. A gate command that constructs sandboxes runs under `systemd-run --user --scope` where the session's own scope is not cgroup-delegated — a bare session fails `cgroup placement failed: Errno 13`, while the scope inherits your environment's PATH. 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/--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.