AND Finish

Finish is a resumable transaction: publish one reviewed delivery unit through one authorized GitHub pull request, make its lifecycle completion authoritative in GitHub, then remove only typed local resources and source artifacts proven safe to clean. Derive completed steps from evidence instead of repeating them.

Runtime Contracts

Use and-workflow-contract with work-records.md and delivery-units.md for Read Delivery Unit, Finish Delivery, Read Work Record, Write Work Record, Record Receipt, and Record Lifecycle Outcome. Load acceptance-gate.md when the Package Contract declares an Acceptance Gate. Read review-attestation.md for conditional shadow freshness validation of the latest Implementation receipt. Read deployment-handoff.md and local-cleanup.md directly for their handoff operations when resolving, revalidating, or resuming the implementation handoff. Route incomplete setup to setup-and; stop before mutation when the Git remote does not identify one GitHub repository.

Preconditions

Before merge, the current actor owns or is delegated one open ready-for-agent delivery unit whose latest Implementation receipt identifies a committed reviewed head, verification, clean review, an authoritative Deployment disposition, and, when present, a complete Cleanup: required handoff for that head. A complete Deployment Manifest is required when Deployment is custom; complete typed items are required when Cleanup is required. When an Acceptance Gate is declared, its shared authority decides whether the current Finish boundary is clear; a gate whose boundary follows merge may enter Finish before that decision. An omitted declaration adds no acceptance operation. No unrelated external blocker may remain. On resume after merge, the pull request and GitHub evidence must identify the same original scope and actor.

Route stale implementation or review evidence to and-implement, contract defects to and-pack, and ownership, relationship, stage, or lifecycle drift to and-sweep.

Process