---
{
  "n": 7,
  "title": "Share of plan 16",
  "abstract": "https://agent-journal-0512ab5482bda5ec20717479.tunler.jessegall.nl/s/db73f1a0-4d42-4cb8-829c-ad71ac07ff73",
  "refs": [],
  "seen": [
    "user"
  ],
  "data": {
    "target": "plan:16",
    "token": "db73f1a0-4d42-4cb8-829c-ad71ac07ff73",
    "expires": 1790887789.282825,
    "approved": true,
    "password": "",
    "comments": true,
    "environment": "main",
    "member": "owner"
  },
  "created": 1790282989.284058,
  "updated": 1790283041.447894,
  "deleted": 0.0,
  "completed": 1790283041.447835,
  "outcome": "",
  "type": "share"
}
---
Redmar's orchestration model (plan 16)
A ticket runs its own orchestrator agent instead of an assignee (todo 1655)
The board shows domains and roles with their active agents and tickets (todo 1656)
A role can be global, with one live agent per journal (todo 1686)
Work for a global role waits in one queue that every ticket shares (todo 1687)
A role says whether it runs as a full agent or a subagent (todo 1688)
Delegating a full-agent role starts an agent in the ticket's worktree (todo 1689)
Role agents show with their own chat and count in the roles tree (todo 1690)
A plan's phases hold board tickets (todo 1691)
Each plan gets a worker agent in a worktree of its own (todo 1692)
The plan agent starts the next phase's tickets once the last are merged (todo 1693)
The environment agent answers how a plan or ticket is going (todo 1694)
The skills and docs describe plans, tickets, roles and global agents (todo 1695)