The hackathon split: five engineers, five branches, five AI agents, one weekend. The canonical workflow doc is docs/PROCESS.md; the runtime architecture is docs/ARCHITECTURE.md. Each plan below conforms to the standard 7-heading template (Goal / Scope / Frozen contracts touched / Deliverables / Acceptance criteria / Risks & mitigations / Status).
| Plan | Branch | Owner | Status |
|---|---|---|---|
| Engine core & baseline | feat/engine-core |
A | Merged |
| Tournament & referee | feat/tournament |
B | Merged |
| Agents (strategist + builder) | feat/agents |
C | Merged |
| Frontend dashboard | feat/frontend |
D | Merged |
| Infra, API, orchestration, demo | feat/infra |
E | Merged |
| Plan | Branch | Status |
|---|---|---|
| Tournament concurrency + referee observability | followup/tournament-concurrency |
Merged |
| Builder quality gate + prompt fix | followup/builder-quality |
Merged |
Champion resume in run_generation_task |
followup/champion-resume |
Merged |
| Frontend: live-board streaming + termination badges | followup/frontend-polish |
Merged |
These define how the workstreams integrate. Do not change them without paging the team. See docs/ARCHITECTURE.md for full links.
- backend/darwin/engines/base.py — Engine Protocol
- backend/darwin/storage/models.py — SQLite schema
- backend/darwin/api/websocket.py + frontend/src/api/events.ts — WS event payloads
- Person A merges
feat/engine-core. Unblocks B and C. - Person B merges
feat/tournament. Unblocks E's full orchestration. - Person C merges
feat/agents. Unblocks E's real generation runs. - Person E merges
feat/infra. Unblocks D's switch from mocks to live. - Person D merges
feat/frontend. Demo-ready.
After D merges: eval, polish, demo rehearsal. Follow-ups land on the same one-branch / one-owner discipline.