From b861b3ae36b8adbcf9157b4cfb0e8bde8693c26b Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 2 Nov 2026 18:19:01 +0100 Subject: [PATCH] Glossary: review aspect; playbook 01: a piece of state takes the bus storage form that fits it, and a form added to mesh-sdk is named to the operator with its cost --- 00-META/glossary.md | 5 +++++ 00-META/process/01-research.md | 5 ++++- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/00-META/glossary.md b/00-META/glossary.md index 39b86c5d..f4de9557 100644 --- a/00-META/glossary.md +++ b/00-META/glossary.md @@ -988,6 +988,11 @@ Not a domain of the mesh but of the way it is built, listed because its words me - **design** — a record of the knowledge base, named "design NN", with a **to-be** section (what is being built) and an **as-is** section (what runs), its owning repositories and its links to its decisions and other designs (ADR 0423). Until the move, a document in `03-DESIGN/`, in `01-to-be/` or `00-as-is/`. +- **review aspect** — one of the eight concerns a research effort's direction and a design are reviewed against + before they are proposed or merged: security, seams, running qualities, health, events and logs, testing, + upgrade and tools (playbook 01, *Review by aspect*; the operator, 2026-11-02). A reviewer judges whether the + settled direction is complete and sound in its aspects and never reopens a decision. + *Not:* ~~architectural domain~~ (a **domain** is an area of the mesh that owns words). - **design state** — of a design: proposed, designed, in progress or implemented, worked out by the knowledge base from the issues with a design link to it and whether their deliveries are done; never written by anyone (ADR 0424). diff --git a/00-META/process/01-research.md b/00-META/process/01-research.md index d07bc7a8..cb0a31fc 100644 --- a/00-META/process/01-research.md +++ b/00-META/process/01-research.md @@ -99,7 +99,10 @@ before a design is merged (playbook [02](02-graduation.md)), it is reviewed agai - **security**: who may call each new verb, how its grants are scoped, which credentials go or remain, what can be replaced or forged, and what enters from outside the mesh; - **seams**: where each piece of state lives on the bus, which seat, verb or event joins two parts, and any - link that is not NATS-native; + link that is not NATS-native. Each piece of state is kept in the bus storage form that fits it (a state, a + stream, an object bucket); a form the manifest lacks is added to mesh-sdk, and the review names that change + and its cost (a mesh-sdk change rebuilds every module) to the operator, never folds it in silently (the + operator, 2026-11-02); - **running qualities**: build capacity, speed, storage growth, and what happens while a part, the bus or the control-node is down; - **health**: what each part's health check says, which conditions are raised and cleared, and whether any