Concepts

Reference pages state the contract. These pages explain why it looks the way it does — including the trade-offs, and where a design point is intentionally left open for something not yet built.

Topics

Problem & Solution

The problems NEXUS is built to solve, and the three ideas its design centers on.

Use Cases

Concrete scenarios built on NEXUS's three design ideas.

Architecture

How a hosted CLI agent, the local MCP server, the shared surfaces, and the cloud fit together.

Local-First

Why NEXUS keeps work on the machine and uses the cloud only for identity and entitlement.

Canvas Model

Why the canvas is Excalidraw-compatible, default-deny on roles, optimistic on concurrency, and strict on the reason field.

Agent Mesh

Why mesh delivery is asynchronous and mailbox-based, and why agents are addressed by a stable identifier.

Agent Mesh Messaging and Email

Why local Mesh mail is not internet email, and what a future remote transport must preserve.

Orchestration Governance

Why chains of agent actions are gated even though a single action never is, and why the gate needs two independent keys.