---
{
  "n": 56,
  "title": "Agent Kanban feedback from Redmar",
  "abstract": "",
  "refs": [
    "dump:22"
  ],
  "seen": [
    "agent",
    "user"
  ],
  "data": {
    "environment": "main",
    "revisions": 1,
    "open_until": 1790274865.105479,
    "kept": false
  },
  "created": 1790272929.173758,
  "updated": 1790283140.035122,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "doc"
}
---
Redmar's feedback of 24 September 2026 on the agent Kanban and the agent organization: a ticket is run by its own orchestrator agent instead of being assigned, and the domains show their roles, how many agents each has working and on which tickets.

## What Redmar said
Translated from Dutch, 24 September 2026:

- *19:24* — "You don't want an assign-to here. Instead, this ticket has an orchestrator agent by default, and it talks to the roles it needs to get its task done."
- *19:29* — "And if you have a group of domains here that you can fold open to see every role under that domain, with the number of active agents behind each role and a spinner, for example (3) with a spinner, so three active, then you can also see which tickets that agent is working on."

His sketch:

~~~
DOMAINS
+ Engineering
    + Developer              (3) [spinner]
        + An awesome ticket          (2)
        + Another awesome ticket     (1)
    + Reviewer               (1) [spinner]
    + Debugger               (0) [no spinner]
~~~

The pasted message ended in *Read more*, so there may be more that was cut off.

## A ticket has its own orchestrator
No manual assigning on a ticket card. Every ticket runs one orchestrator agent by default; that agent decides which roles it needs and hands them their parts itself (today's journal todo delegate to a domain or role), instead of the user picking an assignee.

## Domains and roles, with who is working
A collapsible tree on the board: domains, then the roles under each. Behind every role, the number of agents active in it and a spinner while any is working. Folding a role open lists the tickets those agents work on, each with its own count. A role with nobody active shows (0) and no spinner.

## What the screenshots show
Redmar was answering two screenshots, both attached. At 19:24 he looked at the ticket card's menu, where *Assign to* lists every role (Customer Success Manager, Architecture Decision, Bugfix, CTO / Tech Lead and more). That list is what he says should not exist, because the ticket's own orchestrator picks the roles. At 19:29 he looked at the sidebar (Environment, Project, Environments), where he pictures the *Domains* group with its roles and active agents.