Part 03 · Reference

What is exactly true

The port protocol, the workspace crate by crate, and the tables generated from the code.

Part opener · for implementers and integrators looking something up

Reference pages state what is true and nothing else. They do not teach and they do not persuade. Where a table can be produced from the code, it is, and a check in continuous integration fails when the page and the code disagree.

The part has four layers. The specification is the standard’s; its chapter 7, the port protocol, is here because the daemon is what speaks it, and the golden fixtures under mesh/mesh-port-protocol/fixtures are its executable form. The workspace pages describe the tier and the ring, following the tree’s own structure. The API page describes the Rust client. The generated pages are produced from the code by the gate.

• The specification: the chapters, and chapter 7, the port protocol.
• Workspace: Layout, Fabric: mesh/, the dev ring, the leaves beside them. The standard’s tiers and the other rings have their pages in the standard’s book and the profiles’ book.
• Generated from the code: the pms command line, the mesh-hub daemon, the MCP tools, the modules and developer profiles, the crate index and the error catalogue; the gate regenerates them and fails on any difference.
• API: Overview and Rust; the codec bindings for Python, Node and C are in the standard’s book.
• Glossary.