Architect
Keeps the platform and its decisions consistent.
- Designs the architecture and documents decisions
- Delivers criteria and dependencies, not deadlines
Doesn't plan the backlog or create others' tasks.
The company of AI agents
AshaCore doesn't build itself — but almost. Behind the platform stands a virtual software company of AI agents with clearly separated roles, a supervisor and a daily cadence.
The roles in detail
Keeps the platform and its decisions consistent.
Doesn't plan the backlog or create others' tasks.
The only planner — slices work into waves.
Doesn't write production code itself.
Distributes independent work in parallel, collision-free.
Doesn't merge anything into production.
Merges finished, green states.
Moves nothing to production without explicit human approval.
Reads the code and finds what isn't captured yet.
Changes no code — read and report only.
Watches the hand-offs and derives the next role.
Only routes (read-only) — does no work itself.
Two teams, a second opinion
Two agent teams work together: one builds, the other reviews independently against it. Four-eyes principle, only with machines — contentious points are escalated for a decision, not silently passed over.
How the company works
Every hand-off is a versioned file, not a lost chat. Every step is traceable and resumable from any machine.
A scheduler triggers a standup tick every morning: it checks the state, gathers open hand-offs and prepares the next steps — before the day begins.
The supervisor only routes (read-only). Everything outward-facing — deploy, production, DNS — stays a deliberate human decision.
Guardrails
What the company decides itself — and what deliberately stays with the human.
| Area | Agents may | Human decides |
|---|---|---|
| Plan & build | Slice tasks, build code, write tests | — |
| Hand-offs | Versioned file hand-offs, routing (read-only) | — |
| Production / deploy | Prepare finished, green states | Approval & release to production |
| Domains & DNS | Propose configuration as data | Outward-facing DNS changes |
| Accounts & access | Maintain the role model | Grant new accounts, tokens, permissions |
A day at the company
A scheduler triggers the standup: open hand-offs are gathered, the state is checked.
The project manager slices the next wave from findings and priorities.
The orchestrator distributes independent tasks — one isolated working copy each.
Workers build step by step, with tests and a green quality gate before every commit.
A second team reviews independently against it — four-eyes principle with machines.
The integrator takes over reviewed, green states — production stays human-approved.
The supervisor tracks the hand-offs and prepares the next step.