Glossary and design 47: the release's new words and the L3-L7 homes as decided (ADR 0563-0571), so readers find where each controller job now lives

00-META/glossary.md

@@ -242,7 +242,7 @@ every other domain has something to run on. **Recorded by** the controller and t
 **Purpose.** To decide, send and apply what each node runs, and to say why.
 **Recorded by** the controller's `inventory` database; from ADR 0567, by the seat `mesh-placement`, in its states on
 the bus. **Upstream of** Provisioning, Connectivity, Data
-and Health and repair. **Decided by** ADR 0100, 0126, 0176, 0181, 0207, 0221, 0252, 0261, 0411, 0539, 0549, 0559, 0567.
+and Health and repair. **Decided by** ADR 0100, 0126, 0176, 0181, 0207, 0221, 0252, 0261, 0411, 0539, 0549, 0559, 0567, 0571.
 **Uses:** node, machine, module, seat, manifest (Module), config value (Config), proposal (Operator and conversation).
 
 - **assignment** — a module put on a node. Its config values on that node (module-assignment config,
@@ -255,6 +255,10 @@ and Health and repair. **Decided by** ADR 0100, 0126, 0176, 0181, 0207, 0221, 02
 - **mesh-placement** — the seat, held once for the mesh by the assigner, that keeps placement: its states
   `placement`, `proposals` and `candidates`, and its seven verbs `placement`, `proposals`, `propose`, `withdraw`,
   `again`, `adopt` and `hand-back`. Only the holder writes its states (ADR 0567).
+- **seat holders** — the state `seat-holders` of the seat `mesh-placement`, written by its holder, the assigner: one
+  key per seat naming each holder and its node, composed from placement and the manifests' claims as the indexer
+  holds them, and rewritten only when a key differs. The tool runner and every other reader of who holds a seat
+  read it there, never the controller (ADR 0571 §6, §7).
 - **placement proposal** — a change to placement put forward through the verb `propose`: the changes, the revision
   of each key they were laid over, the nodes' answers, the verdict and the ask. It takes effect only on the operator's
   Approve, and is discarded if declined, expired or withdrawn. A kind of *proposal* (Operator and conversation).
@@ -389,7 +393,7 @@ and vault (Identity and access).
 **Purpose.** To issue, hold, rotate and check the credentials and grants by which modules, nodes, agents
 and the operator act. **Recorded by** the controller's `identity` and `licences` databases and the vault.
 **Upstream of** Provisioning, Delivery, and Operator and conversation.
-**Decided by** ADR 0085, 0113, 0183, 0225, 0234, 0386, 0387, 0388, 0411, 0413, 0414, 0550.
+**Decided by** ADR 0085, 0113, 0183, 0225, 0234, 0386, 0387, 0388, 0411, 0413, 0414, 0550, 0571.
 **Uses:** module, node, seat, tool (Module), operator, consumer and provision (Provisioning), agent and ask (Operator and conversation).
 
 - **credential** — anything that proves an identity: a password, a key, a token. A **pair credential**
@@ -427,7 +431,9 @@ and the operator act. **Recorded by** the controller's `identity` and `licences`
 - **root key** — the key at the top of the signed logins, which vouches for the signing keys: sealed in the
   vault and used only to replace them, on the operator's Approve (ADR 0388).
 - **bus account** and **membership** — a module's or a node's account on the bus, and the subjects it
-  is issued. The bus server calls its accounts *users*; the mesh says bus account.
+  is issued. The bus server calls its accounts *users*; the mesh says bus account. Each module's membership
+  is kept in the grants part's state `memberships` (seat `mesh-grants`), one key `<node>.<module>` written
+  only when it differs, and the runtime reads its membership there (ADR 0571 §10).
 - **rotate** — replacing a credential without a consumer holding one the provider does not know.
 - **licence** — a model-access account the licence manager holds and **binds** to a consumer, the
   coding agent on a node (ADR 0183).
@@ -449,7 +455,7 @@ and the operator act. **Recorded by** the controller's `identity` and `licences`
 back when it fails. The domain is continuous integration and delivery, named **delivery**, and its parts live in
 the repository `mesh-delivery` (ADR 0429 §2). **Recorded by** the `mesh-delivery` module (deliveries) and the
 controller (the planner, the rollout) until release 6 of ADR 0429; from each release on, by the parts it builds. **Downstream of** Module, Core, Health and repair and Data.
-**Decided by** ADR 0162, 0218, 0236, 0237, 0238, 0239, 0250, 0267, 0270, 0276, 0323, 0401–0408, 0428, 0429, 0444–0447, 0524–0530, 0539, 0548, 0551.
+**Decided by** ADR 0162, 0218, 0236, 0237, 0238, 0239, 0250, 0267, 0270, 0276, 0323, 0401–0408, 0428, 0429, 0444–0447, 0524–0530, 0539, 0548, 0551, 0571.
 **Uses:** module, node, declaration and send (Placement), health (Health and repair), person.
 
 - **merge check** — what a pull request carries before it may merge, judging the merge of its head into a
@@ -497,6 +503,12 @@ controller (the planner, the rollout) until release 6 of ADR 0429; from each rel
 - **build module** — the module of one language that does the build steps for it on a node (fetch, build, digest,
   test), claiming that language's build seat: `mesh-build-go`, `mesh-build-node` and `mesh-build-image`. It pulls the
   build requests of its language and writes each step's end on its own key (ADR 0525 §3, §6). Not the **builder**.
+- **build log** — the builder's own module log `build-log`, in ADR 0297's form, kept 30 days and keyed per
+  module: one entry when a build of a fingerprint starts and one when it ends (the module, the fingerprint, the
+  repository, the directory and the commit, the build node and the time, the build's manifest and its `against`,
+  and at the end the outcome and each artifact's digest). A build's duration is read from its two entries, and no
+  other part records durations; the builder's module tool `builder_builds_since` answers the builds a reader
+  missed from it (ADR 0571 §1, §12).
 - **package** — what code resolves when it is **compiled**: an npm/cargo/pypi dependency, by **version**.
   Served by the **package-registry** (gitea). Only a build module talks to it.
 - **artifact** — anything a build produces and the mesh delivers to a node by **digest**: an `image`, a
@@ -505,6 +517,13 @@ controller (the planner, the rollout) until release 6 of ADR 0429; from each rel
   (ADR 0156).
   An image is one kind of artifact, and a module is not an image. A package and an artifact are two
   protocols, not one store being weak (ADR 0075).
+- **artifact sweep** — letting go of the artifacts no one needs any more, the seat `mesh-artifact-sweep`, held
+  once for the mesh by artifact-store-tools beside the artifact store (ADR 0571 §2 to §4; named `artifact-store`
+  in the record before its progressive insight). Its keep set comes from the store's own listing, the wants and
+  the build log: a digest a want names is kept however old, and so are each module's five newest builds
+  (ADR 0526 §1). From the lease write it sweeps at each build's end and records each deletion in the hand-act
+  log; until then the controller sweeps. Not the artifact store itself, nor the registry's own collection of
+  unreferenced bytes (ADR 0189).
 - **build source** — the files one artifact is built from, in one or more repositories: for a Go program
   its import closure (the directories of its packages, its Go module files) and its recipe; for any other
   artifact the paths its manifest names, by default its module's own directory. Each artifact of a build
@@ -662,6 +681,8 @@ becomes a message). **Decided by** ADR 0227, 0231, 0240, 0252, 0283, 0564.
 - **probe** — one look at one thing's health, run by whoever owns the verdict; what a probe returns is a
   **finding**, before it becomes a condition. A finding is kept as a key `<scope>.<id>.<kind>` in its observer's
   bucket `findings` until it is no longer observed (ADR 0564 §2).
+- **node health report** — each node-engine's own report of its node's health, a key that node's engine writes
+  and the watchman reads (ADR 0564, as its progressive insight of 2026-10-29 has it); its layout is mesh-sdk's.
 - **observer** — a part that writes findings for the condition keeper: the watchman, the self-check and the
   healers (ADR 0564 §2). An observer never writes a condition.
 - **condition keeper** — the module mesh-conditions, holder of the seat `mesh-conditions`: the one writer of the
@@ -687,7 +708,7 @@ becomes a message). **Decided by** ADR 0227, 0231, 0240, 0252, 0283, 0564.
   operator's decision (ADR 0259).
   Not a drill: nothing is broken.
 - **hand-act** — a repair a person made by hand, recorded so the mesh knows it happened. The **hand-act log**
-  is the stream `acts` of the seat `mesh-hand-acts`, held once by the module mesh-hand-acts, which also records
+  is the module's log in ADR 0297's form, the stream `acts` of the seat `mesh-hand-acts`, held once by the module mesh-hand-acts, which also records
   who chose an ask (`warranted`); every recorder calls it, and the controller's own log is read beside it
   until the lease write (ADR 0565 §10, §11).
 - **take-over** — the operator's approved switch of a job from the controller to the part that replaces it, with a
@@ -702,7 +723,7 @@ becomes a message). **Decided by** ADR 0227, 0231, 0240, 0252, 0283, 0564.
 
 **Purpose.** To know every item of data a module holds, how precious it is, and to keep it recoverable.
 **Recorded by** the manifests' `data` declarations and every node's `node-backup` seat.
-**Upstream of** Delivery and Health and repair. **Decided by** ADR 0232, 0233, 0235.
+**Upstream of** Delivery and Health and repair. **Decided by** ADR 0232, 0233, 0235, 0571.
 **Uses:** module, node, provider and consumer (Provisioning), person.
 
 - **data class** — how precious an item of data is, ranked by the operator: `irreplaceable`,
@@ -712,6 +733,10 @@ becomes a message). **Decided by** ADR 0227, 0231, 0240, 0252, 0283, 0564.
   at one moment; **restore** — bringing it back beside the live data, never over it.
 - **stream snapshot** — the bus's own backup of each stream, taken by the module holding `mesh-broker`
   (ADR 0235).
+- **disk readings** — the size of each data item a node's modules declare, measured by its `measure` and kept
+  with its largest size in seven days by disk-load on that node, in its own state, one key
+  `<node>.<module>.<item>` written only when it changes; the holder of `node-backup`, mounts, nfs-server and the
+  self-check read them there, never the controller (ADR 0571 §5).
 - **sticky binding** — a consumer's tie to the data a provider keeps for it, which moves only by a
   person (ADR 0232).