Stage 5: Two roles

The shape the earlier stages were building toward: a contributor worker that can write code but holds no merge authority, and a coordinator worker that holds the Coordinator Role and only ever merges. min goes through a real fork.

Voice-over

Now the real shape. A contributor worker that can write code but can't merge, and a coordinator worker that can merge but only answers merge ASKs. I post: implement min. The contributor claims it, forks mathkit, opens a Lane, and does the work in its fork. When it's done it ASKs the origin repo to merge. The coordinator picks up the Changeset, reviews it, merges it, updates the Ladder, and closes out the original ASK. Two agents, one protocol, nobody waiting on me.

OK, let's go faster.

On screen

A 2×2 grid: top-left zz top, top-right the coordinator's zz work, bottom-left the contributor's zz work, bottom-right a shell for posting Asks. Highlight each pane as it acts.

Run sheet

zz agent create dev1
zz repo grant @me/mathkit "@me[dev1]" contributor

Top-right (coordinator):

zz work @me/mathkit --as maint --scope all --provider groq

Correction -- changeset_review moved to open-scope, which changes what --scope can express here. Review used to be its own scope value, bundled together with merge under one "privileged, not open" filter. Now that any agent may submit a review opinion, review and ordinary open-scope work are the same bucket by scope alone -- there's no longer a single --scope value meaning "review and merge, never plain contributor work." --scope coordinator is too narrow (only the merge step); --scope committee deliberately excludes everything open-scope, which now excludes review too. --scope all is what actually works here, accepting that this worker would also claim a plain work Ask if one existed unclaimed -- not a concern in this specific run, since the contributor worker claims implement min first.

Bottom-left (contributor):

zz work @me/mathkit --as dev1 --scope contributor --provider groq

Bottom-right:

zz ask post @me/mathkit --remote --description "implement min(...numbers)"

Narrate as it happens: claim → fork into a shard → open a Lane in the shard → submit_changeset Ask back to the origin → coordinator reviews → merges → Ladder updated → original Ask closed. ctrl+/ inside the TUI drops into the shard's own shell if you want to show the fork on disk.

Checkpoint

min merged through a real fork; the shard shows up as its own repo under <dev1-identity>/mathkit[...].

No cleanup here — Stage 6 continues directly on this same mathkit repo and the maint/dev1 workers. Full cleanup is at Stage 7's checkpoint, the end of this chain (deleting dev1 there also removes its shard).