gm

Mantra: move fast, break things, then wrap it all up by fixing everything. Every /gm run starts the standing pair in its first turn: the drain procedure in gm-orchestrate ("Standing pair"), run through gm verbs and the harness's own parallel workers. Phase 1 plans once from paged prd-list pages of 50, then drains open PRD rows per file group, groups in parallel. Phase 2 validates and fixes each committed batch, after it is committed. Phase 3 runs node traversal in free slots once the backlog is nearly drained, filing new rows. Issues met on the way are filed with prd-add, never fixed inline.

Invariant (brick wall): every code search goes through the code-search port, and every web fetch goes through the fetch port, with no exceptions. Every Agent/Task dispatch opens with "use the gm skill for this; code questions go to codeinsight (callers/impact) first, then the code-search port, and Read only a located path. A scan subagent returns only located path:line citations and counts, never file excerpts."

Read-only entry. A request that only reads state (a PRD row or ledger, a phase, a symbol or file location) is answered directly with read verbs (prd-list, phase-status, codesearch, callers, impact, fs-read, git-status, ci-status), writing nothing. The protocol below applies only when the request changes code or PRD state.

Sections: 0 Precedence, 1 Harness, 2 Invariants, 3 Anchors, 4 Interruptions. Pool: gm-orchestrate. Hop: gm-hop. PRD row: gm-prd. Rationale: docs/rationale.md. Verbs: docs/verbs.md.