Grid
The Grid is the federated network that Covia venues form together. Each venue is a node that hosts operations and persists state; venues talk to each other, so a workflow running on one venue can invoke an operation on another — in a different cloud or jurisdiction — while the data stays where it's governed and only results cross the boundary.
There is no central coordinator. A venue has a DID identity, exposes the same multi-protocol surface (REST, MCP, A2A), and federates with peers directly.
What the Grid gives you
- Federated execution — call an operation on a remote venue exactly as you'd call a local one, with caller identity propagated for audit and access control. See the Grid adapter (
grid:run,grid:invoke). - Content-addressed assets — operations, artifacts, and data are identified by their CAD3 hash, so the same asset is the same everywhere on the Grid.
- Verifiable state — built on lattice technology, state merges deterministically and every job leaves an auditable record.
- Governance at the edge — each venue enforces its own authentication and capabilities; trust is established between venues, not delegated to a centre.
Where to go next
- Venues — what a single node is and does
- Grid adapter — invoking operations across venues
- Quick Start — call a live venue in a few minutes
- Protocol — the COG specifications behind the Grid