The pull request opens last.
A run moves through investigation, thesis, patch, preview, QA, and review, in that order. The pull request opens last, after the change has booted on a real machine and passed a browser test.
Investigation to pull request, seven stages.
Investigation and thesis decide what to fix. Patch, preview, and QA prove the fix works. Review checks the diff. The pull request opens last.
Three finder agents read the backlog, support desk, and repository. Each works blind.
3 finders, in parallelOne judge call reads every report, links candidates, and picks the problem to fix.
1 decisionA model writes search and replace hunks. A guardrail checks the diff before push.
2,500 line budgetThe branch boots on a real machine: secrets loaded, stack built, domain routed.
boots on real EC2A headless browser agent signs in and drives the change like a customer.
up to 40 stepsA separate model reads the diff and buckets findings before a fix cycle runs.
Blockers, Flags, NotesOpens after preview boots, QA runs, and review completes. A human always merges.
opens lastEvidence, guardrails, memory.
Every external call is logged. Every diff has a budget. Every run starts from what earlier runs proved.
Evidence
Every external call a run made is listed with source, status, and time. Each provider is marked real or fixture.
Source, status, timeGuardrails
A 2,500 changed-line budget caps every patch. A dedupe gate at 0.85 cosine similarity keeps an open Factory pull request from ever being duplicated.
0.85 cosine dedupeMemory
Cited repository documentation and lessons a run earns feed the next one, so later runs start from what already worked.
Cited to line ranges