agent-acceptance-gate

To gate multi-agent outputs before merging, run an acceptance gate that evaluates per-task success criteria and reconciler input to compute a formal PASS or FAIL verdict and generate an acceptance report.

An acceptance gate is a final quality check that validates per-task success criteria, applies reconciler guidance, and verifies budget constraints to decide if multi-agent outputs are mergeable.

Validating per-task success criteria involves orchestrating checks across plan.yml and result.json files to verify that delegate tasks meet the required conditions before generating a formal acceptance report.

Yes, the acceptance gate supports conditional passes by applying reconciler guidance from reconciliation files to gate or block merges, optionally running prose audits and aggregating risks.

You should run the acceptance gate after all delegate tasks complete, allowing it to read plan.yml and reconciliation files to produce a final PASS or FAIL verdict and metadata.

Yes, the acceptance gate verifies budget constraints as part of its end-to-end gating process, ensuring multi-agent outputs respect defined limits before deciding mergability and generating the report.