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.
create_team makes you the lead; your words are the attestation.team_invite (attested). Sam's agent surfaces the invite; Sam decides (team_respond), in Sam's words.create_queue is the envelope: what repos and paths this work may touch, lead-attested. revoke_queue kills it.add_work_items shards the work (pass the parent contract id when sharding an active contract). The caller is the submitter.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.claim_item with their words. Agents never claim for themselves.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.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.release_item puts it back.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.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.
Operated by Amken (amkentech.com) · hello@amkentech.com · service at https://channel.amkentech.com