Repository navigation
Rename chief-of-staff to coordinator and keep programs moving - #183
Merged
sreejithraman merged 5 commits intoNov 15, 2026
Merged
sreejithraman merged 5 commits into
sreejithraman merged 5 commits into
Conversation
The skill is now Coordinator, light by default: one request across threads is answered, routed to a running owner, or given a new one, with no record. Programs add a grant (start, land, resolve, what stays with the user, heartbeat), a T3 heartbeat that runs status --heartbeat, and an async Inbox in place of "Needs you". record.py gains status --heartbeat, which observes without committing and stays quiet while the digest holds, and a say: line for waiting turns. The renderer accepts grant and labels the tab Inbox. The chief record key stays, so running programs keep validating. Orchestration gets a Coordinator model row, idle-child supervision, and Inbox routing for decision requests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A tick now wakes on a forge note it has not seen, such as a base closing under provisional work, and says done only when the committed record is done. A live owner's sub-status stays out of the digest, a dependency names itself in the waiting line, and the saved prompt only runs the command. Light starts use an Orchestration brief, not the program kickoff. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A failed read wakes the heartbeat once and again when its row goes stale. Proposed work at its stop no longer holds a finished program in waiting. Implement's release gate and the one-coordinator check now apply to program work, so light owners land on their own finish line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Chief of Staff is now Coordinator, and it keeps programs moving without being pushed. This is layer 2 of the coordinator stack, on top of #182 (
feat/coordinator-record-commands), which added the record commands andstatus. The page (PR 3) and the Inbox prototype (PR 4) will stack above this one.A review of six real chief programs found these problems: chiefs that idled until pushed, autonomy granted one sentence at a time, idle owners nobody noticed, lost or bundled asks, chiefs running outdated rules, and times shown in UTC. This layer addresses each one.
Light by default. For one request across threads, the coordinator answers it, reuses a running owner, or starts one from an Orchestration brief. Nothing else is needed: no record, page, Inbox, grant, or heartbeat. A request that touches a program's work goes to that program's coordinator. The program layer applies only to two or more outcomes, or when the user asks for one.
Keep moving. The
statusverdict decides how each turn ends:A decision whose recommended option is reversible is built on provisionally instead of stopping work. The coordinator re-reads its
SKILL.mdon resume and on each heartbeat wake. Times shown to the user are in their local zone.Grant. Each program has one grant, set at the start and changed only on the user's word. It has five parts: start (
grant.start), land (the existinglandingAuthority), resolve (grant.resolveplus the existingapprovals), what stays with the user (grant.user), and the heartbeat (grant.heartbeat). Every kickoff carries it. Owners decide reversible method choices themselves. Only scope, irreversible, and taste calls come up.Heartbeat. In T3, a
schedule_taskinterval trigger (every 10 minutes,bindToCurrentThread: true) runsrecord.py status --heartbeatand follows its first line. A tick commits nothing. It stays quiet while the program is waiting or working with unchanged facts. It wakes the coordinator on:It says done only when the committed record is done too. What it last saw lives in the program's git directory, so the record stays clean.
Inbox. "Needs you" is now the Inbox, both on the page and in prose. The record key stays
decisions. Each item asks one question, with context, two or more options with their effects, one recommendation, optional visuals, what it blocks, what continues meanwhile, and when it was asked. Program asks never use a blocking question tool unless the user is in a live back-and-forth.Also:
Compatibility.
chiefrecord key and the Sites wire names (chief-version.json,chief-refresh.js) stay, so running records validate and open Sites keep refreshing.grantis optional.scripts/check.py. Host sync finds skill folders by name, so it removes the old link and adds the new one.Running programs
After this stack merges and the main checkout moves,
skills/chief-of-staffdisappears from both hosts. Send each running chief thread this message:Evidence
python3 scripts/check.pyon the head passes: 393 tests plus the skill and link checker.test_record.pycases cover:say:line;grant.--turn-endfails until the page is published, then passes and printssay: Waiting on Inbox A-D1 (8h13m). Nothing is runnable.;coordinator. The ninth, a five-feature spec, went toimplement, which offers Coordinator for that case. All 6 near misses went elsewhere.Merge Danger
Mostly a two-way door, contained to skills and their scripts. A revert restores
chief-of-staff. Programs migrated in the meantime keep validating under the old validator, except for agrantkey, which the old validator rejects. Dropgrantfromprogram.jsonbefore rolling back, and delete each program's heartbeat scheduled task. Running chief threads need the message above once the merge goes live. Until then, they keep working on the old path.🤖 Generated with Claude Code