The delegator
A stage before the workers. Hand it an idea, a bug list or a page of dictation and it comes back with separate briefs, one per session. The number you set is a ceiling, never a target, and nothing starts until you have read the list.
Release 0.7.844
One person.
A whole team.
You say what needs building. IXIOM cuts it into separate jobs you read before anything starts, gives every agent a branch of its own, has a reviewer read each result against your standards, and hands you only what passes.
9 slides · scroll, arrow keys or click · ESC to leave
Four roles, one repository
The lead
A session you promote. It sits on the branch everything flows back into, hands out the work, reviews what returns, merges and pushes. It creates no branch of its own.
The workers
One fresh session per task, each in its own worktree on its own branch. Three workers can edit the same file without colliding, because nothing is shared until the merge. Your repository rules go out with the briefing, before the first line is written.
The guardian
On by default. It reads a finished branch against the standards you wrote and sends back a numbered list: file, rule, fix. It may never edit, commit, push or merge, and there is exactly one route to the lead - through it.
What that gets you
- 01A board that reads git
- Five columns, from the workers through the guardian and the lead into done, with anything stopped pulled out into Needs you. Cards cannot be dragged: the column is derived from the repository, so a merge you did by hand in a terminal moves the card anyway.
- 02A review loop with a cap
- Two agents can disagree forever. When the rounds run out the branch still reaches the lead, marked NOT PASSED with the open findings attached. A blocked card says which files collide and what each side did to them.
- 03Rules up front, not findings afterwards
- Every worker is handed the rules for your repository in its briefing. A guardian that keeps reporting the same objection is reporting a rule nobody was told - said in advance it costs one briefing, found in review it costs a round.
- 04A summary written to be read
- Every role writes its own: a worker says what changed, a guardian what convinced it or what it objected to, a lead which branch landed and whether it is actually live. It sits on the card and at the bottom of the session that produced it.
- 05One profile per project
- Standards, models, backends and the way work reaches users are properties of one repository. Every team points at a profile of its own, so two projects never have to agree and nothing has to be switched over.
- 06Briefings you can read first
- Team Setup shows the exact text a worker, a lead and a report receive, rendered against a sample repository, before a team even exists. Editable, with your own rules appended last.
Shipped in v0.7.844
Ready to run one?
Teams ship in IXIOM v0.7.844 for Windows, macOS and Linux. Three days free, no card.