Run a team and a work queue

The same rules as one-to-one handoff, scaled to a group: one accountable human lead, attested membership, and no agent ever claims work on its own.

Setting up

• "Set up a team for the migration" — create_team makes you the lead; your words are the attestation.
• "Add @sam" — team_invite (attested). Sam's agent surfaces the invite; Sam decides (team_respond), in Sam's words.
• "Make a queue for the API work on repo X, paths Y" — create_queue is the envelope: what repos and paths this work may touch, lead-attested. revoke_queue kills it.

Work items

• "Break this into items" — add_work_items shards the work (pass the parent contract id when sharding an active contract). The caller is the submitter.
• Membership is not access. The submitter names who may see and claim a slice (grant_work_access on the item, or on the parent contract so stories inherit). An item grant may only narrow the epic grant. queue_status shows what you are allowed to see, not the whole scrum board.
• A granted person says "I'll take item 3" — their agent calls claim_item with their words. Agents never claim for themselves.
• Clarification while the slice is in flight: post_item_note with the human's words. It is hashed on the ledger. Granted agents are pinged; get_item is the read. Closed items do not take notes.
• Done working: return_item, references only, exactly like a contract return. The lead signing that off is done (disposition_item, attested) — not "accept the contract." Reject sends it back to the claimant; cancel drops it.
• Changed your mind: release_item puts it back.

Seeing the board

• my_teams — who is on the team and who holds what.
• queue_status — the items you may see: open, claimed, returned, with stale flags. The submitter also sees ungranted open items that have no workers yet.
• find_capacity — who in your contacts has signalled they are available for agent tasks.
• Everything also appears under swarm in my_work, and every claim, return, grant and disposition is a ledger row.

The lead is accountable for the queue the way an approver is accountable for a contract: every authorization carries a human's words, and the record shows whose.

All topics