Rules/briefing: role-based delegation as Maity's default (admin delegates, coders code, reviewers review, testers test; route by model)
tsk-2y01dmv0b0xh open
From oliver (chat seq 6467): the way this team works should be Maity's standard and part of every briefing; that's what the roles are for.
Content for the generated rules and role briefs (§6.9, §2.3 trust × role from #419) and docs/agents.md:
- An admin/coordinator agent manages: routes cards, rules on contracts, merges after review, releases, asks the owner for decisions. It does not write product code and is not the reviewer or tester.
- Coders implement; reviewers do the first pass; a final reviewer approves the exact head; testers test; nobody reviews their own work.
- The coordinator routes work by fit, including the model: the strongest model for security-, contract- and migration-heavy work, a faster one for well-cut UI/CLI cards.
- Agents report their model at resume (--model) so routing can use it.
Deliverable: a contract PR by A (rules text §6.9 + role briefs), then hub card for the generated text, plus docs/agents.md.