One run, seven stages, one gate.
The interesting part of an agent platform is not that the agent writes code. It is what the code has to survive before a person is asked to care about it.
- 01IntakeAn alert, a ticket, a message, a person, another agent.
- 02SandboxA disposable copy of the repo, scoped to one organization.
- 03Agent runTools come from the role, and a grant cannot exceed it.
- 04PreviewThe run’s own deployment, running and addressable.
- 05Pull requestA branch into your existing review and CI.
- 06gateVerificationApproved flows replay against that preview. Video, screenshots, per-step results.
- 07ReviewAn independent pass, with the run trail attached.
The gate runs at 06, on the pull request — not before it. A failed replay is recorded on the run with its video and per-step results, so a reviewer sees it before they read a line of the diff. It does not block the merge today; your reviewers still do. Making it blocking is the next step, and we would rather say that here than let the diagram imply it.
- 01
Intake
Work arrives as a task — filed by a person, posted by a system, or handed over by another agent.
What is enforcedEvery task belongs to exactly one organization from the moment it exists. There is no global queue to leak across.
What you seeThe task inbox shows what is queued, running, blocked and done, with the source it came from.
- 02
Sandbox
The run gets its own disposable environment with a copy of the repository at the branch point.
What is enforcedThe agent never has your repository — it has a copy, in a box that is thrown away. The blast radius of a bad run is a branch.
What you seeSandbox lifecycle, and the live view of what the agent is doing while it does it.
- 03
Agent run
The agent reads, plans, edits, runs commands, and records every step as it goes.
What is enforcedTools come from the agent’s role. Grants adjust the set inside that remit and denies always win — but a grant can never exceed the role itself.
What you seeThe run trail: tool calls, file reads, commands, timings, and which agent version executed.
- 04
Preview
The run stands the application up in its own deployment, running, that you can click.
What is enforcedPreview access is minted per run against your session and organization. Where the preview proxy is configured, the claim is carried in the hostname and verified before anything is forwarded.
What you seeA live preview link on the run, plus a recording of the session.
- 05
Pull request
The change lands as a branch and a pull request in your normal review process.
What is enforcedNothing merges itself. Delatura’s job ends where your review process begins.
What you seeThe PR, linked back to the run that produced it.
- 06
Verification
Every acceptance flow you approved for that repository replays against this run’s preview — a browser executing stored steps, with no model in the loop.
What is enforcedThe replay is deterministic, and a flow that asserts nothing after its last click is recorded as an error rather than a pass. To be exact about today: the result is recorded on the run, it does not block the merge.
What you seePer-step results, a video of that replay, and the screenshots it asserted on.
- 07
Review
An independent pass over the diff, and then yours.
What is enforcedReview starts from evidence rather than a guess about what the agent did. Your reviewers and your CI still gate the merge.
What you seeDiff, trail, and every check that already ran, in one place.
The same stages, on screen
Clips are recorded from the running product. Nothing here is a mockup, and anything staged is labelled.