What needs you
Overview puts questions and failures first, ahead of running work, pull requests and the day's log.
Tickets in. Reviewed commits on main out.
Holophyte claims a ticket from your board, has an agent implement it in an isolated git worktree, holds it to the ticket's verify commands and an independent review, and lands it on main.
One ticket, five steps
01Claim
The next Ready ticket whose dependencies have merged. Its body becomes the contract.
02Implement
An agent works and commits in its own git worktree, optionally in a container.
03Verify
The ticket's own verify commands run on the candidate.
04Review
An independent reviewer judges the diff and witnesses each criterion.
05Land
A merge to
main, or a pull request watched through its checks.
↺ changes requested back to implement with the findings
Merged. The store records the commit, the rounds and any follow-ups.
Not merged. The branch is kept and the run ends with its reason.
Open a pull request, look at its screenshots, steer a run
The console
A run in review
Progress by round, whether review witnessed each criterion, and the agent's chat with your steer notes.
A pull request, opened
Checks, rounds, what it waits on, diff size, and the screenshots and video the run captured.
Board
Cards move as the factory works: queued, implementing, on CI, parked on a pull request, asking, failed, merged.
Findings
Review findings across runs, worst first, with the follow-ups that become Backlog drafts when their pull request merges.
Built to be trusted unattended
Witnessed criteria
The reviewer marks each acceptance criterion met, not met or unwitnessed, and anything short of met blocks approval.
Adversarial review
Optionally, a second reviewer tries to break the candidate while the first checks it against the ticket.
Isolation
The implementer works in its own worktree, optionally in a container; the reviewer gets a read-only copy with no host credentials.
Steer a live run
Send a note from the run page or
holo steerand the agent reads it at its next turn.The store is the record
Every claim, round, finding, steer and merge is a row in one SQLite store per project, and the console renders from it.