Documentation
Engine architecture
Canonical diagram for the repair engine — shared by the CLI, hosted API, demo, and GitHub App.
Reference
Repairo architecture
Canonical diagram for the repair engine. Matches runRepair() in src/lib/engine/index.ts and the CLI repairo repair command (validation details differ by entry point — see below).
Engine graph (runRepair)
Orchestrator: one function — runRepair() — powers hosted /api/repair, the demo UI fixtures, and GitHub App repair flows.
CLI vs hosted validation
| Path | When validation runs | What runs |
|---|---|---|
Hosted / runRepair() | After buildPullRequest | validateInMemory on merged consumer files (no full checkout) |
repairo repair (local) | After patches are computed, before --apply / --create-pr | Writes temp tree → validateCodebase (tsc, Python/Go syntax, optional Pyright) with baseline-aware diff |
Neither path auto-merges when validation fails or when any fix is agent-proposed.
Surrounding product (not in the engine box)
Hosted deployment: Next.js on Vercel, Neon Postgres, encrypted GitHub tokens, GitHub App webhooks — see /docs/deploy and /security.
Related docs
- Self-host guide: /docs/deploy
- VC / diligence brief: technical-deep-dive-vc.md
- Documentation index: /docs