Phase Gates¶

The governance lifecycle is a sequence of phase gates. No work advances without explicit approval at each gate.

Gate Sequence¶

PLAN → BUILD → REVIEW_ENG → REMEDIATE → REVIEW_ARCH → APPROVE

Gate	Purpose
`plan`	Agent proposes what it will do. Human reviews scope.
`build`	Agent executes the approved plan.
`review_eng`	Engineering review of the work product.
`remediate`	Agent addresses review findings.
`review_arch`	Architectural review of the remediated work.
`approve`	Final approval. Work is accepted.

Rules¶

Sequential only — Gates must be traversed in order. You cannot skip from plan to review_eng.
Explicit approval — Each gate requires an approved action from a named actor.
Rejection resets — A rejected action keeps the run at the current gate for rework.
Audit trail — Every gate transition is recorded with actor identity and evidence.

API Usage¶

Start a run¶

curl -X POST /api/v1/govern/start \
  -d '{"agentId": "uuid"}'

Approve current gate¶

curl -X POST /api/v1/govern/approve \
  -d '{"runId": "uuid", "actor": "[email protected]"}'

Submit gate with evidence¶

curl -X POST /api/v1/govern/gate \
  -d '{
    "runId": "uuid",
    "gate": "build",
    "action": "submitted",
    "actor": "agent-001",
    "evidence": {"commitHash": "abc123", "testsPass": true}
  }'

Customizing Gates¶

The default gate sequence follows the published MOIAS methodology. Custom gate sequences are planned for a future release.

Separation of Authority¶

The governance lifecycle enforces a core principle: no single actor holds both keys. The agent that produces work cannot be the same actor that approves it. Gate approvals require a distinct actor identity from the submitter.