engineering-governance git:20261020.61085b7A

Immutable. This exact content never changes and is served at /api/v1/blob/f2f606cd463a87e7.

---
name: engineering-governance
description: Apply human decision gates, milestone review, physical-node routing and bounded worker repairs in an authorized multi-agent engineering project. Use for costly jobs, cross-host handoffs, disputed scope or independent result verification; avoid imposing the full profile on routine single-agent fixes.
---

Apply the project's adopted governance profile within the user's authorization and host instructions. H is the human principal and highest project decision authority, never a model or simulated role. Human decisions override agent consensus and project procedure; they do not manufacture evidence or bypass host constraints.

Read the reference relevant to the task rather than loading the whole suite:
- Scope deadlock, budget stop or decision override: [human-gate.md](references/human-gate.md).
- Expensive runs, idle token cost or review scheduling: [milestone-mode.md](references/milestone-mode.md).
- Missing hardware, entitlement, network capability or cross-host migration: [node-affinity.md](references/node-affinity.md).
- Code ownership, worker self-fixes or blind verification: [role-boundaries.md](references/role-boundaries.md).

Use H/O/F/W/P/C/V/A for the governed profile. I is a compatibility alias for F in the basic walkthrough, not an extra writer. Preserve existing project roles unless the project adopts this profile. A skill does not start agents, enable watchers or expand permissions.

Before declaring a governance improvement, show the observable evidence. Token-reduction percentages require matched workload measurements; a new protocol or successful launch is not a verified outcome.