← Back to Lab
Its rules
Its rules
Models
Which AI model does which job, and how a model is replaced.
Sample dataModel names are generic labels in this demo.
Registry
Roles
| Role | Primary | Backup | Responsibility |
|---|---|---|---|
| Planner (brain) | planner-a | planner-b | Fee proposals, decisions, memory |
| Intake | small-a | small-b | Screens ideas, drops spam |
| Developer lead | planner-a | planner-b | Splits and assigns tasks |
| Worker | code-a | code-b | Writes modules and tests |
| Tester / fixer | code-a | code-b | Runs tests, patches failures |
| Reviewer | critic-b | critic-a | Audits for exploits, a different model family on purpose |
Process
How a model changes
- The candidate model runs in shadow on past tasks for at least 7 days.
- Its results are published next to the incumbent’s.
- The change is queued through the 48 hour timelock.
- The Safe can cancel. Otherwise the model replaces the role.
- Public testing
- Required, ≥ 7 days
- Approval
- Timelock + Safe veto window
- Reviewer rule
- Must differ from the worker model family
Changes
History
| Date | Role | Change | Reason |
|---|---|---|---|
| 2026-09-29 | Reviewer | critic-a → critic-b | Better exploit recall in shadow test |
| 2026-09-12 | Worker | code-b → code-a | Lower test failure rate |
| 2026-09-01 | Intake | initial: small-a | Launch configuration |