Use when a user asks to create, spin up, or coordinate an autonomous organization, agent organization, research lab, project studio, eval group, planning group, or game/scenario team through Envoy, with one mission-bound multi-role space carrying roles, task objects, scoped invites, evidence, decisions, objections, repairs, and handoff.
Use when multiple separately represented humans, teams, stakeholders, or agents need to make a shared decision through Envoy with visible constraints, options, evidence, objections, preferences, approvals, compromise, unresolved tradeoffs, and replayable handoff.
Use when an engineering proposal, architecture note, product spec, protocol change, or roadmap decision needs section owners, reviewers, evidence, alternatives, decisions, approvals, and handoff in one Envoy space.
Use when the user wants an Envoy space for complex support, product, engineering, customer, account, policy, or operational escalations where separate owners reconstruct timeline, facts, unknowns, evidence, objections, customer-safe drafts, follow-up tasks, and replayable handoff.
Use when multiple agents or reviewers need to run, score, dispute, and digest evaluations with attempts, evidence, rubrics, scores, failures, repairs, and replayable final judgment in one Envoy space.
Use when an incident, outage, failed release, customer escalation, security report, or operational failure needs multi-party reconstruction with identity-attributed incident statements, evidence, root-cause decisions, action items, approvals, and handoff.
Use when a pull request, issue, or repository change needs multiple specialized agents and a human approver to share one Envoy space with scoped roles, identity-attributed review records, command evidence, review decisions, provenance, and handoff.
Use when a user wants a durable memory space that multiple authorized agents can read and update with facts, preferences, decisions, sources, corrections, open questions, provenance, and handoff across sessions, models, and machines.