--- name: journal-organization description: Load it when a ticket's work is split over domains and roles, or the organization's files change; or when a ticket's app is started, opened or stopped. The project's domains and the roles under them, read from files in the project. keywords: organization, organizations, hosting, hostings commands: organization, hosting --- # Organization The project's domains and the roles under them, read from files in the project. The organization lives in agentic-organization/ at the project root: domains//domain.toml names a domain (title, icon, description, responsible, not_responsible, lead), and domains//roles//role.toml a role under it (title, icon, description, responsible, not_responsible, skills, tools, inputs, outputs, cardinality, runs, model). Cardinality is one of worktree, plural, global, plan: worktree means one running instance per ticket, plural any number, global one for the whole journal, whose tasks wait their turn across every ticket, plan one agent for a whole plan, kept in the plan's one worktree and handed each next task. runs is agent for a role that works as a full agent of its own, such as a developer, or subagent (the default) for a short job. journal ticket organization shows what is read; a lead that is not one of its domain's roles, or an unknown cardinality or runs, is refused with the file that says it. A ticket's agent hands work to a domain with journal todo delegate "" [--role ] [--given ""]: the task becomes a to-do in the ticket's environment, tagged with its domain and role (the domain's lead when no role is named), and the command returns the brief to dispatch one subagent with. A role that is worktree queues its tasks one after another; a plural role takes them side by side. A task must name the role's inputs, and a report on it must mention every one of the role's outputs. The brief points at an AGENTS.md beside role.toml or domain.toml as the instructions to read first, and at every skills//SKILL.md in the role's folder (that role only) or the domain's (every role in it). Its lines and guards are for the main agent only; none reach a subagent. ## Ticket apps While a ticket is worked on, a copy of the project's app runs from the ticket's worktree. agentic-organization/hosting.toml names the app: run is the command, with {port} and {worktree} filled in; ready is the path that answers once it is up; idle_minutes is how long it keeps running after the ticket's agent stops. journal ticket host starts the ticket's app as a service in its worktree on a port of its own, journal ticket app gives its address and state, and journal ticket unhost stops it. An app whose ticket's agent has been gone idle_minutes is stopped by itself. Its lines and guards are for the main agent only; none reach a subagent.