agent-acceptance-gate

agent-acceptance-gate

Run the final read-only verification step for a multi-agent round. The gate checks declared criteria and produces acceptance evidence. It never merges, commits, retries, or silently converts a decline, cancellation, timeout, or failure into success.

Inputs

• current provider-neutral plan and success criteria;
• validated TaskCheckpoint and latest PolicyDecision;
• task results, evidence references, and raw-log paths;
• reconciliation report;
• repository diff and project-specific verification commands;
• prior human decision records, if any.

Historical provider fields may be read for migration only. Current checks use task IDs and roles (primary-agent, delegated-executor, reviewer, and synthesizer).

Mandatory preset routing

Run the matching preset when a staged diff:

• touches multiple locale variants of the same document stem;
• adds entries to a catalog; or
• changes a model-and-benchmark claim.

The bundled preset names are multi-locale-mirror-sync, catalog-entry-add, and fact-check-frontier-models.

Presets encode additional failure-mode checks; they do not replace independent review or factual source verification. If a preset cannot run, report a blocker or explicit degraded state. Never claim PASS.

Workflow

1. Validate the plan, checkpoint, and policy. Unreadable configured policy is a fail-closed blocker.
2. Inventory all tasks and required artifacts. Missing, null, declined, cancelled, timeout, degraded, and failed states remain distinct.
3. Verify each declared success criterion with a deterministic command, artifact check, or explicit manual-check requirement. Never invent missing criteria.
4. Compare changed files with declared task scopes and record unexplained drift as FAIL.
5. Check structured statuses, claimed tests, evidence references, reconciliation blockers, and unresolved high-severity risks.
6. Run triggered presets and applicable project invariants. For external facts, cite authoritative sources and mark whether evidence was locally verified.
7. Evaluate canonical policy after the gate cycle. Respect v2 action/slice/goal scope and eligible automatic slice continuation; v1 behavior is unchanged.
8. Write a new immutable acceptance evidence record. Do not overwrite a prior run or human decision.
9. Report acceptance to the primary-agent and user. The host checks existing authorization for delivery; do not demand a fresh approval solely because review, session, or slice changed. A genuinely new human gate still needs a separate recorded decision bound to the specific affected action.