---
{
  "n": 51,
  "title": "Transportklok call on kanban and agent organization",
  "abstract": "Jesse, Remmer (Transportklok) and Bjarne on an orchestrated organization of agents, driven from a kanban",
  "refs": [
    "doc:37",
    "doc:40"
  ],
  "seen": [
    "agent",
    "system",
    "user"
  ],
  "data": {
    "environment": "main",
    "revisions": 1,
    "open_until": 1790169994.0519328,
    "draft_of": "",
    "kept": false
  },
  "created": 1790168162.906832,
  "updated": 1790179044.8272939,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "doc"
}
---
Call transcript dropped in dump 21, summarised. The functional proposal it led to is the companion doc.

## Summary
Jesse walked Remmer (Transportklok) and Bjarne through the journal. The conversation turned to where it should go next: an orchestrator mode where one agent delegates to named agents, each with its own skills, checks, rules and documents; a kanban as the place work starts; and outside sources such as Sentry creating work by themselves. Remmer and Bjarne said they would write the functional requirements down. That is the proposal filed beside this doc.

## Ideas raised
- An orchestrator mode: the main agent delegates to named agents instead of doing the work itself.
- Agent profiles: each agent has its own skills, checks, rules and docs, so its context stays small.
- A protocol resource that says how agents talk to each other, and a helicopter view of that traffic for the user.
- Domains, such as engineering and marketing, each with separate context.
- A kanban as the lead. Plans are cards that can be dragged, and a marker shows where a person is needed. Work flows from backlog to plan, and a + on the board adds a feature through a prompt template.
- One journal process per kanban item or environment, so items run in parallel.
- Errors from Sentry or a webhook open tickets by themselves.
- The journal hosted on a server as the one source of truth for a team.
- Availability checks, and working with the workflows plugin.

## Agreed
- Remmer and Bjarne write a functional requirements document first. It arrived as the kanban and agentic organization proposal in the same dump.
- The kanban becomes the starting point for new work, and the chat stays as it is.

## Open
- How agents address each other: through the orchestrator only, or directly.
- Whether the journal runs locally per developer or hosted for a team.
- Which connectors come first (Sentry was the example).
The proposal settles several of these; its open decisions are listed there.