THE GUIDEBOOK · UNDERSTAND IT, THEN RUN IT

The XMesh Guidebook

This is the manual for XMesh, for IT and platform leaders who need to understand it before they rely on it. It covers what XMesh does, why agent work needs checking and a lasting record, and how to run it. New here? Start with the developer quick start.

Published

Start · Developer quick start. Install XMesh, connect Claude Code or Codex, and run your first mission.

Deploy · Where XMesh runs. On your own machine first, then in one container for a team.

I · What XMesh does. How a task becomes coordinated work, mechanical checks, independent review and a durable mission record; how to drive it from a coding agent; and how independent nodes send each other typed summaries of their own state, never the state itself.

II · Operating XMesh from the Station. The Station is the operator’s console, separate from the API. We use it internally; it is not distributed publicly today. The guide covers asking the mesh, running and following missions, ruling on results, approvals, and stuck work.

Planned

III · Authority and trust. Each mesh creates its own owner, with no global root. Authority is earned through signed grants and outcomes the world confirms. Verdicts, attestations and an audit trail.

IV · Deployment and configuration. Enterprise model access, licensing and editions, backup and restore, and moving from lab to production.

V · Agent permissions, budget, and blast radius. What an agent can reach and how to limit it, secrets, where a person must decide, and spend limits.

VI · Lifecycle: upgrades, recovery, and support. Upgrades, mixed versions, disaster recovery, leaving with your data, and support.

VII · Becoming a narrative institution. The decision record as the organization’s memory, and adoption from one mesh to the whole organization.

About this edition

Edition 0.2.3 covers the XMesh pre-release line. For what a particular release can do, the runtime package version and its capability manifest are authoritative. Chapters are published one at a time, once the founder approves them, and every change is recorded in the changelog.

HOW CLAIMS ARE LABELLED
Executable claims are proven by a UI test against a real server, release after release. Reasoned claims follow from the design but are not tested yet. A planned feature ships only when a test proves it.

Licence

XMesh Developer Runtime is available from public npm as compiled proprietary software; its source remains private. Local development and non-production evaluation have no time limit. Production use is licensed annually per independently governed team mesh, with unlimited humans and agents. Licence-gated cross-organization federation endpoints ship today; enterprise fleet control, identity and SSO are planned. To scope a paid Organizational Cognition Pilot, contact us.