Engineering Governance

---
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).
- Administrative stalls, scoped autonomy or merged roles: [lean execution](references/lean-execution.md).
- Watcher recovery, quota waits or unproven delivery: [operational health](references/operational-health.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.

The role/write limits are starter defaults. A project's explicitly adopted lean profile may assign bounded implementation or operational repairs to another role, with clear file ownership, invariants and task-level limits. Do not require a new acknowledgment for already-authorized ordinary work. Retain prospective scope/resource decisions and independent outcome checking. For expensive staged work, execution-integrity supplies exact-byte packets and durable attempt reservations; a preparation packet is never execution permission.

For cross-provider/physical-node execution, the optional distributed-orchestration skill supplies capability-based assignment and safe tail planning. For source evidence, literature-provenance supplies registry citation checks and exact offline quote location. These are complementary tools, not permission to acquire restricted sources or trust one provider's outputs. Registered runs must freeze executable criteria/tests before data and preserve failed verdicts; toolkit preregistration utilities require a protected anchor and serialized ledger authority.