jschoubben
4bf7a35568
Playbook 02 and 04 were followed for the substance — decisions before design, design before build — and skipped for the bookkeeping. This closes that. 004 graduates. Its one open item was "not yet stood up"; the lab is stood up, and the substitution the effort turned on is now enforced by the validator before anything is raised rather than left as a thing to remember. Its certificate conclusion has a home in 01-end-to-end-testing and is designed but not built — implementation is a third axis, and an effort graduates on its conclusions. One item leaves 004 without a home and is recorded rather than lost: the reverse proxy does not set caServer, so it defaults to the production endpoint. The two lab designs read `designed` while running in production of a sort, so they become `in-progress`. And the lab gets an as-is document, which it did not have. It records what runs including the parts nobody would choose again: that `place:` is refused and the lab therefore raises EMPTY MACHINES, that the drawing shipped with no design document behind it, that a router is tagged as a machine for a reason found by a bug, and that the integration suite raises two of five scenarios while both faults found so far lived in the three it does not. 006 stays active, deliberately. Two of its open questions ARE the tier 0 design — whether absorbing six concerns makes the host too large, and whether an unprivileged node earns a place in the inventory. Playbook 04 is explicit that an open question is a reason to research, not to build around.
2.2 KiB
2.2 KiB
03-DESIGN / 00-as-is
The mesh as it stands. These documents describe what runs, including the parts nobody would choose again — an as-is layer that only records the good decisions is a brochure.
They are written from the implementation and from the operational record, not from intent. Where the two disagree, the implementation wins and the disagreement is stated.
| Document | Covers |
|---|---|
00-overview.md |
The whole in one pass — what a node is, what a module is, how work reaches it |
01-mesh-and-transport.md |
The mesh database, the broker, discovery, and how a call reaches another node |
02-modules-and-manifests.md |
The module, the manifest, and features as the unit of work |
03-provisioning.md |
Declared requirements, provisioners, credentials, and cross-node grants |
04-delivery.md |
Push to running: the three silos, levels, and what a green pipeline proves |
05-runtime-and-installation.md |
The node runtime, its modes, and how a node comes into being |
06-configuration-and-secrets.md |
Managed files, value resolution, and where secrets live |
07-knowledge.md |
The two knowledge stores, and what each is for |
08-agents-and-work.md |
Agents as employees, tasks, workflows, and the meeting model |
09-interfaces-and-observability.md |
How the mesh is reached and watched — tools, board, proxy, health, thoughts |
10-module-catalogue.md |
The catalogue's shape, and what its shape says |
11-the-lab.md |
The lab — the first piece of the new shape that exists, and what it does not yet do |
What these documents are not
They are not a runbook. Operational procedure — how to fix one occurrence of something — lives in the knowledge base, which is indexed on symptoms and is the right place to search when something is broken.
They are not exhaustive. A subsystem is described to the depth at which its design is visible; below that is code.