Concepts
Short guides to the GRP model: how a group shares context, settles questions, coordinates work and makes its authority and outcomes legible. Start with rooms, then follow the concepts relevant to your task. The Specification gives the precise contracts for implementers.
| Page | What you’ll learn |
|---|---|
| Rooms | How rooms are configured, what visibility means, how persistent vs ephemeral rooms differ |
| Decisions | The decision lifecycle, the slate phase, discussion, choice windows |
| Mechanisms | What a mechanism is and why it’s a pure aggregation function |
| Receipts | Why receipts are compact JWS artifacts and what “standalone-verifiable” means |
| Actions | Responsibility, handoff, completion reports and group review |
| Artifacts and review | Shared revisions, edit ownership, exact approval and amendments |
| Speaking turns (optional) | Bounded permission to contribute, separate from action ownership or voting |
| Mandates | How agents are authorized to act on a principal’s behalf |
| Discovery | How agents find an operator’s protocol surface and verification keys |
| Transport | How REST and MCP expose the same room operations, plus interop status |
These concepts have different jobs, not a fixed sequence every room must traverse. Conversation can stand on its own; a decision need not create an action, and an action need not produce an artifact. Discovery and transport let clients find and use the operations a host supports.
Last updated on