How a request flows
- Classify. A fast agent reads your request and decides what kind of work it is.
- Plan. A managerial agent (architect, tech lead, release manager, or a QA / security lead) sketches the approach.
- Execute. An executor produces the actual output — code, document, decision.
- Verify. An acceptance agent checks the result against the original ask. Pass/fail, with deltas.
Why a team
- Specialization beats generalization. A planning agent uses different prompts and tools than an executor. Forcing one agent to do both leaves quality on the table.
- The right model for the work. Classification and verification are fast, well-structured tasks; building is where model quality shows. Amos decides per step, within the compute budget you pick.
- Escalation, not retry-spam. When a level can’t resolve a conflict, the work moves up — to a more capable agent — rather than burning attempts at the same level.
What you see
- A streamed view of every step. As an executor produces tokens, you see them live.
- An audit log of every classification, escalation, and verification decision.
- A cost breakdown per job, broken out by model.