Changelog

Edition 0.1.1 — 2026-08-19

· Chapter I rewritten for the runtime as it runs: a mission is a trade — booked the instant it fills, checked by a counterparty, settled at end of day; only breaks reach a person. The old offer → assemble → perform → verify → learn lifecycle, in which a mission waited for human validation, is retired.

· Chapter I opens with the developer path: drive xMesh from your coding agent by mission request over MCP; the API is the reference behind it.

· Chapter II published: Operating xMesh from the Station — the operator surface, distinct from the API. Every control named as the cockpit renders it.

Edition 0.1.0 — 2026-07-17

· Corrected Chapter I's close to remove the personal evaluation-bench instruction and distinguish executable single-mesh evidence from a reader-performable demonstration; enterprise deployment guidance remains with Chapter III.

· Removed the cover-page prerequisites block; deployment requirements remain with Chapter III, and the evaluation path remains in Chapter I.

· Publication scope: the published book is the CHAPTERS — Chapter I today, further chapters added to this edition in place. The migrated recipe set is retired from the published surface (preserved in the repository history; recipes return only if the founder publishes them).

· FIRST FORMAL PUBLICATION: Chapter I · The model — written by the mesh (a real xmesh mission), first-read by the CTO, published by founder ruling. Publication begins with Chapter I; further chapters are added to this edition in place as they are written, reviewed, and ruled.

· The Guidebook is born: the cookbook moves home to xmesh.bot and takes its institutional identity — education and knowledge transfer for IT leaders first, hands-on recipes as the proven executable core.

· Seven-chapter outline published after the mesh's structural review (verdict: AMEND, applied in place — this edition is unpublished and adjusted in situ): I The model · II Authority and trust · III Deployment and configuration · IV Agent permissions, budget, and blast radius · V Operating the mesh · VI Lifecycle: upgrades, recovery, and support · VII Becoming a narrative institution. Claims carry evidence labels; the recursion is honestly marked reasoned-not-yet-anchored.

· Recipe 11 — Deploy to Your Cloud: the deployment guide folds in, extended with the verify-ai-lane step (prove the enterprise AI lane before the first token).

· Recipe 12 — Establish Your Trust Root: the proven manual anchor procedure (mint the owner identity, custody the key, pin the anchor, seat operators), framed by the recursive topology — every mesh mints its owner; no global root.

· Positioning corrected: Team Mesh is licensed at a flat price per production team with unlimited users ("paid edition of the sym.day platform" retired); sym.day is the personal counterpart.