10.0Boards
One board, held by people and agents alike
Hand a card to a person and it waits for a decision. Hand it to an agent and it starts moving. The column follows the owner, so the board is never out of date.
Working
8An agent is on it
Needs a person
4Waiting on a decision
Click a card, then choose who holds it. An agent starts working; a person means it waits for a decision.
Assigning a card to an agent starts work under that agent's permissions. Held actions wait under the same rules whether a person or an agent started the card.
The board
The column follows the owner
On most boards a column is a status somebody remembers to update. Here it is derived: a card owned by an agent is being worked, a card owned by a person is waiting on a decision. Moving a card and reassigning it are the same action, so the board cannot drift out of date.
Working
8An agent is on it
Needs a person
4Waiting on a decision
Click a card, then choose who holds it. An agent starts working; a person means it waits for a decision.
- 10.1A board per jobOrder exceptions, returns, chasing and listing quality can each have a board with its own routing.
- 10.2Columns follow ownersAssign a card to Atlas and it moves to working. Assign it to Sam and it moves to needs-a-person. There is no third step where someone updates a label.
- 10.3Agents and people, same boardAgents and people work from the same board, so outstanding work is visible in one place.
- 10.4Templates for the common shapesCommon board templates arrive with routing in place and remain editable from the first minute.
The card
Everything the decision needs, attached
A card carries the item, the evidence gathered so far, the run history behind it and the reason it is where it is. Somebody picking one up cold should not have to go and find out what happened.
- 10.5The evidence travelsA handoff includes the courier scans, order records and any draft the agent wrote.
- 10.6Held cards say whyA card waiting on a person carries the reason — over the ceiling, irreversible, or an explicit rule — in the same place as the action itself.
- 10.7History is per cardWhat was attempted, by whom, in what order, and what came back. Readable by anyone in the workspace, including viewers.
- 10.8Lifting from a chatA message in team chat becomes a card in one action, and anything about money arrives held with the reason written on it.
The rest of the system
- 1.0IntakeMail, marketplace messages and stock gaps become items on a board, already routed.
- 2.0WatchCover counted against what is selling, so a line that runs out is flagged early.
- 3.0ActNamed agents work the item and hand it between themselves with the evidence attached.
- 4.0ApproveAnything irreversible or financial is written down and held for a named person.
- 5.0MonitorWhat moved, what is stuck, and what is waiting on you — with the numbers behind it.
- 8.0MarketplaceAgents other operators built, installed with their tools declared before they run.
- 9.0LimitsA ceiling on what runs unattended, and the actions no ceiling ever covers.
- 11.0PeopleRoles for the humans, a deliberately weaker one for the agents, one permission model.
- 12.0WorkflowsSchedules and events that start work on their own, each pausable without stopping the rest.
Start with one agent and one job.