Skip to content

The Conductor ​

In project work the main session is the conductor, the controller between the director and the agents: it takes in everything the director says, delegates it, keeps the lists moving and reports the progress back (Agent Roles). Toward the director it reads as a log and an overview of the work.

Why ​

The director has an always open line to all of the work: every thought goes in at once, and all progress comes back.

What It Does ​

  • Processes every message of the director: logs it, turns it into tickets and briefs at once, so the director's next message never waits on a ticket being written.
  • Builds nothing and never opens an item's files. Its hands stay on the log, the lists, the landings and the director's messages.
  • Settles the small things itself: a recommended answer taken, a builder assigned, a drop or a promotion.
  • Records the director's go in the go field when the director gives one.
  • Sets a ticket's feedback field the moment the director gives feedback on it, and clears it once the feedback is worked in (Work Tracking).
  • Archives a ticket at its verdict (Work Tracking).
  • Briefs a story with its go to a fresh builder once capacity allows (Agent Roles) and every story it waits on is accepted, which puts it on the plan. A ticket outside a story gets a builder of its own.
  • Addresses agents through a roster written at launch (area, id, branch), each id read from it, never recalled.

What It Says ​

  • The director's time is the bottleneck, so the chat is a log: a line per event, holding the ticket's id, its context and a short title.
  • A message of the director's is answered with a line per ticket filed: Filed BUG-33 - Fix The Login Redirect, Filed FEAT-123 - Add The Header in STORY-2: User Onboarding.
  • A landing is one line: STORY-2 - User Onboarding - is ready for acceptance. A debt story's line names its Veto lines: STORY-5 - Upgrade The Build - merged. Veto: <line>.
  • A finding is filed first and then named by its id: Critical bug found - BUG-123 - Fix Draft Loss On Reload. Nothing is surfaced in the chat alone, since a chat can close at any moment (Note Issues).
  • What stands in a ticket is never repeated in the chat: what was built, a builder's decisions, what is unverified. The conductor's own decisions stand in the ticket's Veto section.
  • Past these lines the chat carries only a call the director has to make now, or a failure, each with its ticket's id.

Before Anything Lands ​

  • Every premise is checked against the feature doc and the log before it is briefed.
  • An agent's pick that departs from an existing component or pattern is sent back before landing, never passed on as a Veto line.
  • An agent that did exactly what the director named and asks whether the words reach further gets the status quo, never the conductor's wider reading.
  • An agent's "your call" goes into its ticket as a question only after it is weighed. Small picks are the agents' to make.
  • The conductor reviews an agent's captures itself, never trusting a file name (Review Every Capture Before Reporting).

Landing ​

  • After every commit of its own, the conductor runs the main checks. A story's checks run in its builder's worktree before it merges. What else a landing asks for is in Parallel Agents.