jochen
3ff38d2ee1
Both halves are on their main branches, so the seats stop being an intention. Writes the as-is document from the controller's code and the catalogue's manifests: the closed set of fourteen, the three refusals a claim meets, the holder being an assignment and nothing else, and the one place a seat changes resolution — which of several providers answers, never whether a requirement may go unanswered. Two things the as-is layer exists for are stated rather than smoothed over: a seat cannot answer before it is held, which is the standing condition issue 121 records; and capacity is not implemented at all, so the design's bench has no counterpart in the code.
33 lines
2.3 KiB
Markdown
33 lines
2.3 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 |
|
|
| [`11-the-lab.md`](11-the-lab.md) | The lab — the first piece of the new shape that exists, and what it does not yet do |
|
|
| [`12-the-seats.md`](12-the-seats.md) | The seats the mesh defines, who holds one, and where a seat changes resolution |
|
|
|
|
## 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.
|