Glossary: Uses lines, the thread's two records, the grant from ADR 0386 §4, the provisioner's harness, issue 872 for the seat-sense role (review round 1)

00-META/glossary.md

@@ -271,7 +271,7 @@ and Health and repair. **Decided by** ADR 0100, 0126, 0176, 0181, 0207, 0221, 02
 and the operator act. **Recorded by** the controller's `identity` and `licences` databases and the vault.
 **Upstream of** Provisioning, Change and delivery, and Operator and conversation.
 **Decided by** ADR 0085, 0113, 0183, 0225, 0234, 0386, 0387, 0388.
-**Uses:** module, node, operator, consumer (Provisioning), agent (Operator and conversation), tool (Module).
+**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**
   is the two ends of one credential, the consumer's and the provider's.
@@ -289,8 +289,8 @@ and the operator act. **Recorded by** the controller's `identity` and `licences`
 - **role** — what an identity may call, as a set of grants (ADR 0386). Not a seat: a bare *role* is a
   homonym (see [Homonyms](#homonyms)).
 - **grant** — one line of a role: an effect everywhere, an effect on one seat, or one named tool, and may be
-  limited to named machines; a dangerous tool is granted only by name (ADR 0386). A module's grants
-  come from what its manifest declares it calls, bounded by the provisions it requires (ADR 0225).
+  limited to named machines; a dangerous tool is granted only by name (ADR 0386). A module's role
+  is made from what its manifest declares it calls (ADR 0386 §4).
 - **effect** — a tool's mark, set by its module in its manifest: **reads**, **acts** or **dangerous**; a
   tool served without one counts as dangerous (ADR 0387).
 - **break-glass agent** — the one agent that holds every tool and never asks: sealed until the operator, or
@@ -520,7 +520,7 @@ trust. **Recorded by** the router (asks, warrants and the operator's identities)
 **Downstream of** Health and repair, Change and delivery, and Identity and access. An authorising
 answer acts in whichever domain asked, through that domain's own verb; the conversation owns the
 asking, never the act. **Decided by** ADR 0152, 0175, 0234, 0259, 0272, 0383, 0384, 0385, 0390.
-**Uses:** operator, person, proof (Identity and access), release (Change and delivery).
+**Uses:** operator, person, node, module, seat, tool (Module), proof and identity (Identity and access), release (Change and delivery).
 
 - **mesh MCP server** — the endpoint on a node's loopback through which every agent and person on that
   node reaches the mesh: the MCP server named `mesh`, with its five tools `mesh_overview`,
@@ -580,7 +580,7 @@ asking, never the act. **Decided by** ADR 0152, 0175, 0234, 0259, 0272, 0383, 03
   build seat's holder, whose seat name `node-build-agent` is an identifier to rename.
 - **thread** — one line of agent work, owned by the mesh: its turns, tool calls and results, its workspace
   and usage, kept whole for good on the bus by the thread seat; it outlives any session, node or front end
-  (ADR 0383).
+  (ADR 0383, ADR 0384).
 - **session** — one run of an agent harness on a thread.
 - **agent harness** — the program that runs an agent's sessions, its context manager and loop: Claude Code
   today (ADR 0384). Not the SDK harness (see [Homonyms](#homonyms)).
@@ -719,7 +719,8 @@ renaming one sense, the old sense moves to a *Not:* line and becomes mechanical.
 | | how much proof an ask needs | **assurance level** | Identity and access |
 | harness | the part of `mesh-sdk` that serves a tools bundle | **SDK harness** | Module |
 | | the program that runs an agent's sessions | **agent harness** | Operator and conversation |
-| role | what a seat names, at a scope | **seat** | Module |
+| | the TypeScript `provisioner` helper for database providers | **`provisioner`**, renamed by design 57 | Provisioning |
+| role | what a seat names, at a scope | **seat**; the bare word in older designs is tracked by issue 872 | Module |
 | | what an identity may call | **role** | Identity and access |
 | ask | a request for the operator's input | **ask** | Operator and conversation |
 | | an entry in the build queue | **build request** | Change and delivery |

00-META/repos.md

@@ -34,7 +34,7 @@ one-for-one — `mesh-catalog`, `mesh-sdk` and `mesh-tools` exist where the tabl
 | `mesh-foundation` | 1 | the four pinned services, as declarations |
 | `mesh-controller` | 2 | **exists.** The controller and its contexts — one of seven built (ADR 0006) |
 | `mesh-surfaces` | 3 | tools, web, cli |
-| `mesh-sdk` | — | the stable spine modules build against — the tool-serving harness, the messaging/event framework, the contracts and core primitives. Holds nothing per-module and nothing volatile (ADR 0039). |
+| `mesh-sdk` | — | the stable spine modules build against — the tool-serving SDK harness, the messaging/event framework, the contracts and core primitives. Holds nothing per-module and nothing volatile (ADR 0039). |
 | `mesh-lab` | — | **exists.** The lab — scenario lifecycle, networking, placement. Ships to nobody; runs on a workstation. |
 
 Tier 4's shape is open, and deliberately so: see ADR 0019 and