jschoubben
c0b35652d0
papa-hq reads 01 research -> 03 decision -> 02 design. The order is a scar, not a choice: 02-DESIGN existed from its initial commit, and when adr/ was finally promoted on 2026-07-13 it took the next free number rather than its place in the sequence. By then design was too settled to renumber. hal-hq was three commits old, so it is not. adr/ becomes 02-DECISIONS and 02-DESIGN becomes 03-DESIGN, and following the folder numbers now walks the process in the order it happens: research produces a decision, the decision authorises a design. 00-GENESIS becomes 00-META, matching papa's rename from the same restructure. Every path reference rewritten across documents, frontmatter, playbooks and skills. All links resolve; all 58 frontmatter blocks parse and their path fields still point at files that exist.
31 lines
2.1 KiB
Markdown
31 lines
2.1 KiB
Markdown
# 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`](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`](01-mesh-and-transport.md) | The mesh database, the broker, discovery, and how a call reaches another node |
|
|
| [`02-modules-and-manifests.md`](02-modules-and-manifests.md) | The module, the manifest, and features as the unit of work |
|
|
| [`03-provisioning.md`](03-provisioning.md) | Declared requirements, provisioners, credentials, and cross-node grants |
|
|
| [`04-delivery.md`](04-delivery.md) | Push to running: the three silos, levels, and what a green pipeline proves |
|
|
| [`05-runtime-and-installation.md`](05-runtime-and-installation.md) | The node runtime, its modes, and how a node comes into being |
|
|
| [`06-configuration-and-secrets.md`](06-configuration-and-secrets.md) | Managed files, value resolution, and where secrets live |
|
|
| [`07-knowledge.md`](07-knowledge.md) | The two knowledge stores, and what each is for |
|
|
| [`08-agents-and-work.md`](08-agents-and-work.md) | Agents as employees, tasks, workflows, and the meeting model |
|
|
| [`09-interfaces-and-observability.md`](09-interfaces-and-observability.md) | How the mesh is reached and watched — tools, board, proxy, health, thoughts |
|
|
| [`10-module-catalogue.md`](10-module-catalogue.md) | The catalogue's shape, and what its shape says |
|
|
|
|
## 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.
|