Who does what, on one map.
Scroll or pinch to zoom, drag to move. Pick a role to see what it does.Scroll or pinch to zoom, drag to move. Pick a helper to see what it does.
Librarian
Librarian live, in the owner's sessionlive, in the conversation
the knowledge base.the owner's notebook.
Keeps the owner's knowledge base of what was learned, researched and decided, filing each finding on the right page and keeping the index current.Keeps the owner's notebook of what was learned, looked into and decided, so a conclusion from one conversation can be found in the next.
Updates a page rather than duplicating it, and dates and cites every entry. Unsettled conclusions are marked open.Adds to an existing page instead of starting a copy, and dates every entry with its source. Anything undecided is marked as open.
Gets from
- Orchestrator: something to keep or find
Intake
file-ticket skill live, in the owner's sessionlive, in the conversation · Registrar unattended, from ticketsalone, from the task tracker
every request filed once, deduplicated, in the right project.every request written down once, in the right place.
file-ticket skill live, in the owner's sessionlive, in the conversation
The session's mirror of the Registrar: it dedupes, then files each ticket by hand with its project, milestone and blocking edges set on creation.How a live conversation writes a task down: the same checks the front door runs, done by hand.
Never files a ticket without a project, without a milestone when the project has them, or as a sub-issue.Never files a task without its project and its place in the plan.
Registrar unattended, from ticketsalone, from the task tracker
Normalizes, deduplicates, assigns a project, attaches a measured forecast where evidence exists, and files dependency-linked Linear work.Files every request once, in the right project and order, with a time forecast when past work supports one.
Stays code, never an agent session, so no session is started on every request's critical path.Stays plain code, so no AI helper has to start up for every request.
Sends to
- the owner moves a ticket to Todothe owner approves a task: a ticket in Backloga task, waiting for a yes, unattendedalone
- Steward: a signup or credential walla login or signup, unattendedalone
Gets from
- Orchestrator: a ticket for each joba task for each job
- Planner: the tree, filed oncethe plan, written down
- Telegram, Alexa: a request, unattendedalone
- Ops: a finding, filed as a buga problem it noticed, unattendedalone
Analyst
Analyst live, in the owner's sessionlive, in the conversation
numbers with their queries.numbers, showing how it got each one.
Answers questions with numbers: player stats, production checks, studies. Every number carries the query or command behind it.Answers questions with numbers, like how players are doing or whether a problem is real, and shows how it got each one.
Read-only on production. Runs no simulation the owner has not approved.Only reads, never changes live data, and runs no simulation the owner has not approved.
Gets from
- Orchestrator: a question for numbers
- Builder: a script for a studynew code for a study
Orchestrator
Orchestrator live, in the owner's sessionlive, in the conversation
the main thread; writes briefs, starts agents, sends each build to its checks, then to Release.runs the conversation; writes the tasks, starts helpers, has the work checked, then hands it on.
The main thread of every interactive session. Answers quick questions inline and runs anything bigger in a background agent, so the owner can always interrupt.Runs the live conversation. It answers small things straight away and sends anything bigger to a helper in the background, so the owner never waits to be heard.
Never lets two running agents own the same files, and never guesses what only the owner can decide.Never lets two helpers work on the same files, and never guesses a decision that belongs to the owner.
Sends to
- Intake: a ticket for each joba task for each job
- Planner: a big aska big request
- Designer: an open directiona design to choose
- Builder: an owner-checked briefa task the owner agreed
- Copywriter: visible textwords people see
- Requirements auditor: a ticket to check before the builda task to check before building
- UX auditor: a visible changea change people see
- Release: a checked wavechecked work to put in place
- Analyst: a question for numbers
- Ops: hosting, servicessites and services
- Disk auditor: disk, RAM, CPUstorage and memory
- Librarian: something to keep or find
Gets from
- The owner: asks, decides
Planner
Session architect live, in the owner's sessionlive, in the conversation · Architect unattended, from ticketsalone, from the task tracker
a big ask into a settled design and a dependency-linked ticket tree.a big request into a plan and a set of linked tasks.
Session architect live, in the owner's sessionlive, in the conversation
Turns a big ask (several tickets or repos, or a new milestone) into a settled design and a dependency-linked ticket tree.Turns a big request into a plan and a set of linked tasks, in an order that can be built one task at a time.
Plans only and never writes code. Not the Architect, which runs unattended and asks through ticket comments.Only plans, never builds. Not the Architect, which plans with nobody watching and asks its questions on the tasks.
Architect unattended, from ticketsalone, from the task tracker
Turns a capability into a project-backed, dependency-linked ticket tree.Turns a goal into an ordered set of useful tickets.
Writes Linear structure, not repository code.Plans the work; it does not build code.
Sends to
- Intake: the tree, filed oncethe plan, written down
- Builder: the tree to buildthe tasks to build
Gets from
- Orchestrator: a big aska big request
- the owner moves a ticket to Todothe owner approves a task: a body of worksomething big, unattendedalone
Designer
Designer live, in the owner's sessionlive, in the conversation
directions to pick from, over real screenshots. Never builds.designs to choose from, drawn over real screenshots. Never builds.
Turns a brief into directions to pick from: a design canvas, mockups over real screenshots, and timed storyboards for anything that moves.Turns an idea into a few designs to choose from, drawn over real screenshots, with a frame-by-frame storyboard for anything that moves.
Never builds into the app and never judges the build.Never builds anything and never grades the finished result.
Gets from
- Orchestrator: an open directiona design to choose
- Builder: an open directiona design to choose
Builder
Developer live, in the owner's sessionlive, in the conversation · Delivery unattended, from ticketsalone, from the task tracker
turns a ticket into one commit, in its own worktree, checked before Release lands it.turns a task into one saved change, in its own copy of the code, checked before it goes in.
Developer live, in the owner's sessionlive, in the conversation
Turns a ticket into commits in its own worktree, one per ticket, running the tests that cover the change before and after.Turns a task into finished code in its own copy of the project, saving one change per task and running the checks that cover it.
Never pushes main or edits another agent's worktree. A choice that is the owner's comes back as a question.Never puts work live itself or touches another helper's copy. A choice that belongs to the owner comes back as a question.
Delivery unattended, from ticketsalone, from the task tracker
Takes one ready ticket per session by default and probes, builds, tests, documents and commits it in its own worktree, then closes it.Usually takes one task at a sitting and builds, checks, documents and saves it safely.
The only active role with repository write authority.The only specialist allowed to change code.
Sends to
- Designer: an open directiona design to choose
- Copywriter: visible textwords people see
- Analyst: a script for a studynew code for a study
- UX auditor: a visible changea change people see
- Requirements auditor: a built branchfinished work to check
- Steward: an account or credential walla login it needs, unattendedalone
Gets from
- Orchestrator: an owner-checked briefa task the owner agreed
- Planner: the tree to buildthe tasks to build
- Requirements auditor: a fail goes back once
- the owner moves a ticket to Todothe owner approves a task: a single changeone change, unattendedalone
- Steward: the vault entry, proventhe working login, unattendedalone
- Ops: a diagnosed failurea failure it explained, unattendedalone
Steward
Steward unattended, from ticketsalone, from the task tracker
account, credential and product-call walls, under its own identity.signups and logins, under its own name, never the owner's.
Handles account, credential, physical and product-call walls.Handles signups and credentials that should not wait for the owner.
Never uses the owner's identity or leaks credentials; authorization returns to the owner.Never pretends to be the owner or exposes passwords.
Sends to
- Builder: the vault entry, proventhe working login, unattendedalone
Gets from
- Intake: a signup or credential walla login or signup, unattendedalone
- Builder: an account or credential walla login it needs, unattendedalone
- Requirements auditor: verifies the Steward's stepschecks the Steward's steps
Copywriter
Copywriter live, in the owner's sessionlive, in the conversation
every line a player or reader sees.
Writes and reviews every line a player or reader sees: homepages, store listings, in-game text, release notes, the blog.Writes and checks every word someone outside the system reads: websites, app store pages, text inside the games, update notes, the blog.
Drafts against the owner's standing copy rules before showing a line.Checks every draft against the owner's writing rules before showing it.
Sends to
- UX auditor: copy on a screenwords on a screen
Gets from
- Orchestrator: visible textwords people see
- Builder: visible textwords people see
- Release: landed commits, for release noteswhat changed, for update notes
UX auditor
UX auditor live, in the owner's sessionlive, in the conversation
screens against their design, accessibility on every change, playtests for big ones.checks what people see, and has newcomers try big changes.
Checks every visible change against its design at phone and desktop widths with a before and after, checks accessibility every time, and runs blind playtests for big changes.Checks what players will see on a phone and a computer against the design, checks it works for everyone, and has newcomers try big changes.
A new screen, a style change or anything unasked waits for the owner's OK. Not the requirements auditor, which checks work against its ticket.A new screen, a new look or anything unasked waits for the owner's yes. Not the requirements auditor, which checks work against its task.
Sends to
- Playtester: a big change
Gets from
- Orchestrator: a visible changea change people see
- Copywriter: copy on a screenwords on a screen
- Builder: a visible changea change people see
Requirements auditor
Requirements auditor live, in the owner's sessionlive, in the conversation · Auditor unattended, from ticketsalone, from the task tracker
checks a ticket is clear enough to build, then that the built work meets it.checks a task is clear before building, then that the result does what was asked.
Requirements auditor live, in the owner's sessionlive, in the conversation
Before the build, reads the ticket and asks at most five questions if it cannot be built without guessing. After it, checks each line of the Definition of Done against live data where it exists: pass, fail or insufficient data, with its coverage.Before building, checks a task says enough to build without guessing, and asks at most five questions if not. After, checks each promise in the task against real data where it can: pass, fail or not enough to tell.
Read-only on code: never fixes what it judges and never widens the ticket. A fail goes back to the builder once; a second goes to the owner.Never edits the work it judges or adds to the task. A fail goes back once; a second fail goes to the owner.
Auditor unattended, from ticketsalone, from the task tracker
Checks a built branch, replayed onto main, against its ticket and live data, audits each milestone when its last ticket closes, and verifies the owner's and the Steward's steps the same way. States coverage in every verdict.Checks finished work against its task and real data, checks a finished batch once it is all done, and checks the owner's and the Steward's steps the same way.
Read-only and independent of the builder's report: it names a defect, never fixes it. One correction lap, then the owner.Checks for itself and cannot edit the answer. A fail goes back once; a second goes to the owner.
Sends to
- Builder: a fail goes back once
- the owner moves a ticket to Todothe owner approves a task: verifies the owner's stepschecks the owner's steps
- Steward: verifies the Steward's stepschecks the Steward's steps
Gets from
- Orchestrator: a ticket to check before the builda task to check before building
- Builder: a built branchfinished work to check
Release
Release live, in the owner's sessionlive, in the conversation
lands a checked wave after one full test run, closes its tickets and cleans up.puts checked work in place after one last full test, then closes the tasks and tidies up.
Takes a wave whose checks passed, runs one full suite, lands it by fast-forward, confirms every commit is on main, closes each ticket with what changed and how it was verified, and removes the worktrees.Takes work that passed its checks, runs every test once more, puts it in place, confirms it all arrived, closes each task with a short note, and tidies up.
Never lands a branch whose checks have not passed, except on the owner's recorded OK over a second failed check, and never force-pushes. Offers a deploy only where one is registered, and runs it only on the owner's OK.Never puts unchecked work in place, and never puts anything live without the owner's yes.
Sends to
- Copywriter: landed commits, for release noteswhat changed, for update notes
Gets from
- Orchestrator: a checked wavechecked work to put in place
Playtester
Playtester live, in the owner's sessionlive, in the conversation
one blind persona, sent by the UX auditor.plays as one kind of new player, sent by the UX auditor.
Plays a game build through a test harness as one blind persona, newcomer to expert, logging moments as they happen.Plays a game as one kind of player, from a beginner to an expert, and notes what happens as it goes.
Launched only by the playtest skill and given just its persona, the harness and a brief on driving it, so it starts knowing nothing.Only started for a playtest. It is told nothing about the game, so it starts like a new player.
Gets from
- UX auditor: a big change
Ops
DevOps live, in the owner's sessionlive, in the conversation · Operations unattended, from ticketsalone, from the task tracker
hosting and services in session; the control-plane sweep unattended.sites and services with the owner; a watcher that files problems, alone.
DevOps live, in the owner's sessionlive, in the conversation
Owns hosting and services: production hosts, the tunnel and DNS, background services, where each secret lives, why a dispatch failed.Keeps the websites and background services running, knows where everything is kept, and finds out why a job never started.
Reports and proposes. Fixes a cause in code or config when its brief allows; never restarts, rotates or deletes on its own.Explains and suggests. It fixes a cause only when asked, and never restarts, replaces or deletes anything itself.
Operations unattended, from ticketsalone, from the task tracker
Sweeps the control plane and diagnoses failed runs from evidence.Watches BigBrain and works out why a run failed.
Read-only: diagnoses rather than editing or rerunning work.Investigates; it does not change code.
Sends to
- Intake: a finding, filed as a buga problem it noticed, unattendedalone
- Builder: a diagnosed failurea failure it explained, unattendedalone
Gets from
- Orchestrator: hosting, servicessites and services
- Disk auditor: a cause to fix
Disk auditor
Disk auditor live, in the owner's sessionlive, in the conversation
disk, RAM and CPU; causes to Ops.storage, memory and speed; causes to Ops.
Finds where the disk, RAM and CPU went, ranks the biggest consumers, and proposes exact cleanup commands with what each frees.Finds what is filling the computer's storage and memory or keeping it busy, and lists what could be cleared and how much each frees.
Cleans on its own only a short approved list of safe leftovers and caches. Everything else waits for the owner's OK.Clears only a short list of safe leftovers the owner already approved. Anything else waits for the owner's yes.
Sends to
- Ops: a cause to fix
Gets from
- Orchestrator: disk, RAM, CPUstorage and memory
Key
Solid: in session. Dashed: unattended. Dotted: a check of someone else's steps.Solid: in the conversation. Dashed: working alone. Dotted: checking someone else's steps.
Session requests reach the Orchestrator; Telegram and Alexa reach Intake. Only unattended agents hold Linear identities; the Registrar is code.Conversation requests go to the one running it; Telegram and Alexa go to the front door. Only helpers working alone hold tasks. At Todo, a role label, else one model call, picks the role.Then a label, or a quick AI check, picks who.