How builds and reviews work
How Evermach plans, builds, reviews, and security-tests a change, and what the pull request it opens contains.
Start a build
An Admin or Engineer starts a build from a Request with Run cloud agent. A Request can have one build running at a time. Everything happens in your linked GitHub repository, and the result is always a pull request.
The stages
| Status | What happens |
|---|---|
| Queued, Provisioning | The build waits for capacity, then gets a fresh, isolated sandbox. |
| Implementing | The builder clones your repository, installs dependencies, and writes a plan. A separate read-only reviewer checks the plan for gaps (up to 2 rounds), then the builder implements it. |
| Reviewing code | An independent model reviews the diff for correctness, in a separate read-only sandbox. It sees the goal, the plan, and the diff, never the builder's reasoning. |
| Security review | Another independent model reviews the same diff for security vulnerabilities. |
| Fixing review findings | If either review has blocking findings, the builder fixes or disputes each one, and both reviews run again (up to 3 rounds by default). |
| Pushing, Opening PR | The reviewed diff is pushed to a new branch, and a pull request opens. |
When a finding blocks
A finding blocks the build when the reviewer is at least 80% confident and its severity isn't low. A reviewer that fails or returns an unusable result counts as a blocking finding: review fails closed, never open.
Ready or draft
The pull request opens ready for review when both reviews come back clean. It opens as a draft when:
- findings are still blocking after the last fix round;
- the run's spend cap cut the review loop short;
- a review or fix stage failed; or
- the diff was too large to review in full (over 150,000 characters).
Draft or not, what the reviewers saw is exactly what gets pushed, and your team decides what to merge.
What the pull request contains
- The Request's goal as the title.
- An Automated review section, with any unresolved findings and the full review history.
- The builder's summary of the change, the goal, and a diff summary.
- Steps to reproduce and a reviewer checklist.
Commits are authored by Evermach Agent <agent@evermach.dev>.
Limits on a run
- A time limit of 60 minutes by default, up to 120. A run that hits it ends as timed out.
- A cap on agent steps and a spend cap on model usage, metered as the run happens.
Broken-down Requests and stacked pull requests
When a Request is broken down into smaller ones, building the parent builds each piece in order. Every piece gets its own full build and review, starts from the previous piece's branch, and opens its own pull request. The pull requests are linked as a GitHub stack. If a piece fails, the sequence stops; pull requests already opened stay open.
Retries and security fixes
- After a failed run, or one that ended without a pull request, use Retry cloud agent. A run that was interrupted is marked failed rather than resumed.
- Scheduled security scans can open fix builds automatically, under per-project limits.
Questions about anything here? Email help@disruptica.com or book a demo.