What the coordinator actually coordinates
AGENTROY describes a team workflow: a coordinator keeps the task contract, workers own separate changes, and reviewers judge a frozen result against evidence. DSHREM provides the host-side task lifecycle. A model name in a menu is not proof that the model is installed, authenticated or available on that host.
On the reference host, policy is configured to request Codex GPT-6.1 Sol, optionally GPT-6 Astra for architectural escalation and Claude Opus 5.5 for advice. DSHREM ds41f is the configured API coordinator route. Subscription CLI sessions and API workers have different credentials, quotas and billing. Missing access must be visible; it must not silently turn a subscription task into a paid API call. Your host may differ; its verification receipt records actual availability.
Three, four, five or six roles
A triangle can mean coordinator, implementer and reviewer. Four roles can add a test owner; five can separate frontend and backend work; six can add an architect. These are planning examples, not a mathematical quality formula. Every extra participant needs a distinct responsibility, a non-overlapping file scope and a share of the same task budget. A larger polygon does not prove a better answer.
A review report should show the exact artifact version, checks run, failures, missing evidence and actual usage. Stars can summarize a named rubric; they cannot replace failing tests or manufacture an independent review. Light, dark and rainbow are presentation choices and do not change the verdict.
Understand the quote before paying
Example only: with an 8% managed-service markup, USD1.00 of provider cost would become USD1.08 before separately disclosed taxes or charges. This is an arithmetic example, not a current price offer. The accepted quote and its tariff version are authoritative; a guide does not activate a subscription, payment method or a new provider route.
Reserve the maximum authorized amount before work and reconcile it with provider receipts afterward. Display spent, reserved and remaining amounts separately. An unknown provider outcome must keep the reservation unresolved until reconciliation; a network error is not permission to retry a billable request blindly. Prepaid balance, a task cap and a daily provider cap are different controls.
When a team helps — and when it does not
Separate code ownership and an independent review can expose mistakes that one pass misses. Coordination, repeated context and reviews also consume time and tokens. Measure accepted changes, defects found and total verified cost on comparable tasks before claiming savings. Shared model agreement alone is not proof: correlated errors are possible.