Make every acceptance item a runnable command with an expected result, quote wording exactly, and add a RISKS section. Use when writing or amending a task's spec or acceptance.

5. **Audit at goal end.** When `factory task ready --goal G` is empty and every build task is done or cancelled, do not close the goal yourself. Create an audit task and spawn the pm: `factory task add --goal G --team <team> --role pm --title "Audit G-xxx (round n)" --spec -` (spec: the audit checkl

Director steps to sign off, close and reopen a goal after the pm audit. Use when a lead says a goal's build tasks are done, or a done goal must be reopened.

Detail text moved out of director.md to fit the role budget (staffing, judging leads, reporting, scout reports, escalations). Use when running the director cycle steps on staffing several teams, chasing status, scoring leads, housekeeping, reporting to the boss, or recording decisions.

Purpose: every active goal is delivered on time (D1-D5 in director.md). Owner order M7486, verbatim: "i want goals to be conpleted. Director shall find out and be accoontable for the delivery in time. It has all resources management and can spawn any agents needed to accomplish work either coding or

Run retries, stalls and the third attempt on a task. Use when a reviewer or QA FAIL or a judge reject comes back, when respawning a coder, when a task reaches attempt 2 or attempt 3, when a worker is lost, stopped or stalled, or when the findings are only nits.

Checklist for writing idiomatic, safe, stdlib-only Go under go/ with tests and the local toolchain. Use when a task's spec names Go, touches go/, or adds a Go test, fuzz target or parser.

Procedure for changing a guard so the PR fixes the whole bypass class and loosens nothing unplanned. Use when editing roles/hooks/*, a deny rule in roles/settings/*.json, a CLI refusal, or when retrying a PR after a reviewer or QA bypass finding.

Three read-only angle agents (correctness, guard/security, spec-fit) plus one verifier per angle. The output is input to your verdict, never the verdict.

Decide what the director settles itself, what goes to the owner and what defaults after 2 daytime hours (owner standing rule M833). Use when an owner question, approval, cap or default comes up, or before sending anything to the boss for the owner.

List every automated writer of a target before proposing a restriction, and say how each is affected. Use when proposing or approving branch protection, deny rules, caps, permission narrowing or any other repo or infra restriction.

Change a running worker's spec, acceptance or scope safely through the task DB. Use when a running worker's spec, acceptance or scope must change.

Checklist to run before every worker spawn so the brief is complete and safe. Use when about to spawn a pm, coder, qa, reviewer, judge or cleaner, or when writing or editing a worker's task spec.