Approval workflow

Reviewer responsibility

Review evidence, operations, and replay results.

• Confirm the proposal addresses the observed failure.
• Check every evidence reference and operation.
• Review replay mismatches and risk signals.
• Understand the repository or export destination.

Record a decision

Approve or reject without deploying the change.

Approval and rejection are explicit human actions with persisted provenance. Approval makes an eligible artifact deliverable; it does not modify customer code by itself.

After approval

Choose export or GitHub delivery as a separate action.

Choose either the standalone bundle or a reviewable GitHub draft pull request. Both paths keep testing, merge, deployment, and rollback in the customer’s existing workflow.