AGENT ORCHESTRATOR
Delivery model

Delivery without pull requests.

Agent Studio integrates agent work without pull requests. A build and test gate, review aspects and a verifiable completion rule sit in front of the merge. People read verdicts and decide; the diff is opened on demand.

Delivery path

Checks in front of the merge

The run agent edits a worktree and does no git. The platform commits the run, publishes it as a fenced delivery, runs the gate and the review aspects, and integrates a passing delivery into the integration branch before a person sees the card.

IN FRONT OF THE MERGE AFTER THE VERDICTS REISSUE · AT MOST TWO AUTOMATIC ROUNDS 01 Coding run Agent edits a worktree. It does no git. 02 Fenced delivery Platform commit and an immutable result ref. 03 Build and test gate Suite against the current integration head. Fail-closed. 04 Review aspects Pass, Concerns or Block. Grade A to D as evidence. 05 Integration Merge into develop before a person sees the card. 06 Human Review lane Verdicts, evidence and integration state per card. Diff on demand. Conflict: rebase and retry. 07 Completed Only when the delivery is integrated, or with a recorded operator override. LATER Release develop to main is a manual promotion with its own gate. Content rescued from a dying run goes to a salvage ref and stays outside the review subject until someone adopts it.
01 · RUN

The agent edits files in a worktree. Branch, commit, push and merge are pipeline steps owned by the platform.

02 · DELIVER

The run's commits are attributed to the card and published as an immutable, fenced result ref. A stale attempt cannot overwrite a newer one's result record.

03 · GATE

The suite runs against the current integration head. The review outcome must be Pass and the build and test aspect must pass or be not applicable.

04 · REVIEW

Named review aspects return Pass, Concerns or Block with findings. A failed check reissues the card with the findings, at most twice automatically; then a person decides.

Completion rule

Integration state and the completed state

The card's integration state is recomputed from git ancestry of its attributed commits. Lane, pipeline success and prose do not change it.

Integration record

One of five values per card: integrated, partial, pending, conflict-skipped, no-branch. The board shows it next to the lane.

Completed state

A card reaches Completed only when its integration state is integrated. The exception is an operator override, set explicitly on the move and recorded with its reason.

Release

Integration, acceptance, release and stable freeze are four separate events. A task can be on develop while its card is still in review; the release manifest shows exactly which work moves to main.

Pull-request strategy

Repositories whose policy requires a named approver use the configured pull-request integration strategy. The delivery then stays in Human Review and is never reported as merged.

Human decision

What people read and decide

The Human Review lane holds cards with verdicts, evidence and integration state. Nothing leaves it automatically.

Verdicts, not diffs

Operators read the aspect verdicts, the grade and the integration record, and open the diff when a verdict is contested or the change is large.

Findings need a decision

Each finding leads to an action on the card: accept, requeue with instructions, or escalate. Lane moves and overrides are recorded in the card's timeline.

Gate configuration stays with the platform

Which aspects block and which overrides are allowed is project configuration on the platform side, outside the worktree the delivering agent edits.

Costs are measured

The platform reports stage durations and bounce rounds per project. The full suite per delivery is the largest compute-bound stage; a batch gate for delivery waves is a documented proposal.

Pattern write-up with sources and costs: ai-patterns.dev →