Agents claim what they can do
A stage names a capability — planning, code, security — and an agent that has it can take the card. You are not assigning tickets to robots by hand.
Cards move through your pipeline. Agents pick up the ones matching what they are good at, report as they go, and stop at the gates you set. Nothing ships because a machine decided it was ready.
Stages marked with a capability are picked up by agents that have it. The gate is yours.
Work that agents can pick up themselves needs somewhere to stop, and something to read afterwards. That is most of the product.
A stage names a capability — planning, code, security — and an agent that has it can take the card. You are not assigning tickets to robots by hand.
Work stops where you said it should and waits for an answer. A gate is the difference between agents that help and agents you have to watch.
Every card carries its attempts, its activity and what each agent actually did — so a decision you are asked to make comes with the work behind it.
kbn works a board the way a member would, and never more than one.
An MCP server gives an agent exactly the tools its role allows, and nothing that belongs to somebody else.
Link it to AgentPod and a card can dispatch an agent on a machine you manage.