git:20261019.e3e479c to git:20261020.61085b7

7 added, 1 removed. Audit A to A.

# Engineering agent agreement

Follow the user's task and this project's existing instructions. Read context/CURRENT_WORK.md and the specific thread assigned to your role; consult FACTS.md only for relevant environment facts. Re-check facts likely to have changed.

- Use the responsibilities the task needs: O coordinates and integrates, P proposes, I implements, C reviews, V independently verifies, W executes bounded commands. These role names do not choose a model or authorize delegation. The coordinator records owned files and integration strategy before concurrent writes.

+ Use the responsibilities the task needs: H is the human principal, O coordinates/integrates, F owns implementation, W runs bounded jobs, P researches, C critiques, V independently verifies, A supports an explicit assignment. I is a compatibility alias for F. In the governed profile only O/F own production code; V writes independent verification artifacts in an isolated workspace. Role names do not choose a model or authorize delegation. Record owned files before concurrent writes.

+ H's trusted decisions override agent consensus and project procedure within host constraints. Escalate material scope/budget deadlocks as `owner: H`, `status: blocked`; stop that branch until an actual human decision reassigns it. Never impersonate H or turn a procedural waiver into VERIFIED evidence.

+ When the governed profile is adopted, read context/GOVERNANCE.md and relevant NODES.md/HANDOFF.md records. Batch C/V reviews only at Pilot Readout, Pre-Main Launch and CLAIMS Entry. Use completion/scheduler receipts rather than idle model wakeups. Validate physical capabilities and transfer leases through source quiescence, target READY and target STARTED. Dispatcher node labels/locks are local routing, not distributed authorization.

+ W's default mechanical budget is one patch and one safe retry per stable task across nodes/wakes, recorded before editing and reviewed by O/F. Use `<role>-fix:` commits; no changes to equations, objectives, seeds, tolerances, search effort or criteria. Paths, initialization and pool settings are not automatically semantics-preserving. Quota exhaustion or uncertainty returns to O/F.

Keep one current owner in each discussion thread's frontmatter. Append a `### ROLE <timestamp>` entry with evidence read, work performed, exact revision/commands/output paths, limits and next action. Update the frontmatter owner on handoff; close or resolve finished work. Do not rewrite other agents' entries.

Use an isolated clone or worktree when other sessions write concurrently. Never pull or replace code underneath a running job. Stage only intended files; use the project's established review/integration flow. Dispatchers do not commit or push for you.

Inspect produced artifacts before claiming completion. Return reproducible failures to the owner; make only fixes within your assigned scope. An independent verifier must not be the result's author. Use context/CLAIMS.md for important conclusions and context/LESSONS.md for supported process lessons. A review may validly recommend no change.

Finish bounded tasks and exit. Do not run idle model calls or create background automation unless authorized. Do not change credentials, permissions or sandbox settings as a side effect of adopting this agreement.