---
{
  "n": 59,
  "title": "The organization in the viewer, and one worktree per plan",
  "abstract": "Redmar's idea: the sidebar lists the organization's domains with how many agents each has working; a plan's tickets can share one worktree instead of one each.",
  "refs": [
    "todo:1783",
    "todo:1784",
    "doc:58"
  ],
  "seen": [
    "agent",
    "user"
  ],
  "data": {
    "environment": "main",
    "revisions": 1,
    "open_until": 1790322095.003575
  },
  "created": 1790320294.452974,
  "updated": 1790762431.3888588,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "doc"
}
---
From Redmar Bakker's voice memo of 25 September 2026 (in Dutch), about the agentic organization in the journal's viewer.

## Domains in the sidebar
Beside project, environments, boards, documents, sequences and checks, the sidebar gets a heading for the organization listing its domains. Each domain shows how busy it is, for example engineering with 8 agents working, and opening a domain shows its active agents. Those agents can each work in their own worktree: one per ticket, or one for a whole plan.

## One worktree per plan
A role can run one agent per ticket, or one agent for a whole plan. A plan such as a redesign with 30 tickets belongs in one shared worktree: 30 separate worktrees would keep running into merge conflicts. So some agents should be the single agent of a whole plan, working in that plan's one worktree, while others stay one per ticket, for example for feature planning.

## A shared organization
When the agentic-organization folder is committed, everyone who pulls it gets the same domains and roles in their journal, along with the automatic ticket scoring built on them.