57/F4: The glossary gains the words of config and provisioning (issue 653) #351

Merged
mesh-admin merged 2 commits from pkg/57-f4-glossary-config-words into feat/57-config-and-provisioning 2026-10-13 23:56:12 +00:00
Contributor

What changed

Only 00-META/glossary.md.

  • A new domain section Config (ADR 0348 makes config a domain of its own): config value (anything a module reads that someone may change; the four sources: manifest default, mesh config, node config, module-assignment config), predefined key, preference (moved here from Module, reworded as a config value with a default; required for one without), mesh-config.
  • The setting entry is removed from Module; its ~~flavor~~ Not: line moves to config value unchanged (same scope, so the catalogue's retired-words copy is unchanged).
  • Provisioning (ADR 0349): provision gains that every value a module needs is a provision from its owning domain; new mesh-provisioner, provisioner client, collection (with collector, contributor, item), and the ownership words of a placed file owned, seed, managed (owner-at-runtime).
  • Every place the glossary itself said setting/settings now says config value/config (record mirror, Placement Uses and assignment, agent account, secret family, waiting, proposal, instruction section, Media).
  • kept region points at managed. walk untouched (issue 646 is separate).

What is deliberately NOT done: setting on a Not: line

Putting ~~setting~~ (hq) on config value's Not: line (tried in a scratch copy) makes words.py fail with 382 hits in 67 documents in force that use the word in running prose, not in quotations. Per the package brief the line is left out and nothing is mass-edited; the glossary says in prose that the word is older and checked by review until those documents are reworded. Consequently the second half of the Done-when (words.py fails on a planted "settings") is NOT met by this PR. The documents:

  • 00-META/process/06-writing-a-module.md
  • 03-DESIGN/00-as-is: 00-overview, 01-mesh-and-transport, 06-configuration-and-secrets, 07-knowledge, 10-module-catalogue, 11-the-lab, 13-the-console, 15-the-agent-and-its-licences
  • 03-DESIGN/01-to-be: README, 04, 05, 06, 07, 08, 09, 12, 16, 17, 18, 25, 26, 27, 28, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 52, 53, 54, 56
  • 04-ISSUES (opened since 2026-10-07): 285, 288, 294, 301 (report, diagnosis), 306 (diagnosis), 316 (report, diagnosis), 320, 335, 337 (diagnosis), 339 (report, diagnosis), 340 (report, diagnosis), 342, 343, 345 (report, diagnosis), 346 (report, diagnosis), 357

Two ways on, for the operator or a later package: reword those documents (the as-is ones only once the config work ships), or list them in 00-META/checks/words-allowed.md with a date, then add the Not: line.

Also for a later change: to-be 49 (the mesh in domains) does not list the Config domain yet.

How it is proven

  • MESH_CATALOG_DIR=<mesh-catalog at origin/feat/57-config-and-provisioning> sh merge-check.sh passes: records, index, cycle 436 documents, words "28 retired words and 2 identifiers, none in running prose; 70 daemons' lines, none written; 163 head words, each once" (catalogue copy compared, equal).
  • Scratch copy (not committed): a planted "The operator changes the settings of a module." in 00-META/context.md passes words.py with this glossary; with ~~setting~~ (hq) added it fails on the plant (00-META/context.md:46: 'settings' is retired) and on the 67 documents above.

Reviewer's checklist

  1. Does what issue 653 and design 57's F4 say, except the Not: line (explained above). Nothing outside the glossary. Yes.
  2. Done-when: merge-check passes; the planted-word failure is not met, by the brief's own rule. Partial, stated.
  3. Byte-identical composition: not applicable (no code, no manifest).
  4. No secret, no database change, no schema change. Yes.
  5. Strict parsers: not applicable.
  6. merge-check.sh passes (command above); no Go in this repository.
  7. Words follow the glossary; ADR numbers are given with what they decide. Yes.

Issue 653.

## What changed Only `00-META/glossary.md`. - A new domain section **Config** (ADR 0348 makes config a domain of its own): **config value** (anything a module reads that someone may change; the four sources: manifest default, **mesh config**, **node config**, **module-assignment config**), **predefined key**, **preference** (moved here from Module, reworded as a config value with a default; `required` for one without), **mesh-config**. - The **setting** entry is removed from Module; its `~~flavor~~` Not: line moves to config value unchanged (same scope, so the catalogue's `retired-words` copy is unchanged). - **Provisioning** (ADR 0349): **provision** gains that every value a module needs is a provision from its owning domain; new **mesh-provisioner**, **provisioner client**, **collection** (with collector, contributor, item), and the ownership words of a placed file **owned**, **seed**, **managed** (`owner-at-runtime`). - Every place the glossary itself said setting/settings now says config value/config (record mirror, Placement Uses and assignment, agent account, secret family, waiting, proposal, instruction section, Media). - **kept region** points at managed. **walk** untouched (issue 646 is separate). ## What is deliberately NOT done: `setting` on a Not: line Putting `~~setting~~ (hq)` on config value's Not: line (tried in a scratch copy) makes `words.py` fail with 382 hits in 67 documents in force that use the word in running prose, not in quotations. Per the package brief the line is left out and nothing is mass-edited; the glossary says in prose that the word is older and checked by review until those documents are reworded. Consequently the second half of the Done-when (words.py fails on a planted "settings") is NOT met by this PR. The documents: - 00-META/process/06-writing-a-module.md - 03-DESIGN/00-as-is: 00-overview, 01-mesh-and-transport, 06-configuration-and-secrets, 07-knowledge, 10-module-catalogue, 11-the-lab, 13-the-console, 15-the-agent-and-its-licences - 03-DESIGN/01-to-be: README, 04, 05, 06, 07, 08, 09, 12, 16, 17, 18, 25, 26, 27, 28, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 52, 53, 54, 56 - 04-ISSUES (opened since 2026-10-07): 285, 288, 294, 301 (report, diagnosis), 306 (diagnosis), 316 (report, diagnosis), 320, 335, 337 (diagnosis), 339 (report, diagnosis), 340 (report, diagnosis), 342, 343, 345 (report, diagnosis), 346 (report, diagnosis), 357 Two ways on, for the operator or a later package: reword those documents (the as-is ones only once the config work ships), or list them in `00-META/checks/words-allowed.md` with a date, then add the Not: line. Also for a later change: to-be 49 (the mesh in domains) does not list the Config domain yet. ## How it is proven - `MESH_CATALOG_DIR=<mesh-catalog at origin/feat/57-config-and-provisioning> sh merge-check.sh` passes: records, index, cycle 436 documents, words "28 retired words and 2 identifiers, none in running prose; 70 daemons' lines, none written; 163 head words, each once" (catalogue copy compared, equal). - Scratch copy (not committed): a planted "The operator changes the settings of a module." in 00-META/context.md passes words.py with this glossary; with `~~setting~~ (hq)` added it fails on the plant (`00-META/context.md:46: 'settings' is retired`) and on the 67 documents above. ## Reviewer's checklist 1. Does what issue 653 and design 57's F4 say, except the Not: line (explained above). Nothing outside the glossary. Yes. 2. Done-when: merge-check passes; the planted-word failure is not met, by the brief's own rule. Partial, stated. 3. Byte-identical composition: not applicable (no code, no manifest). 4. No secret, no database change, no schema change. Yes. 5. Strict parsers: not applicable. 6. merge-check.sh passes (command above); no Go in this repository. 7. Words follow the glossary; ADR numbers are given with what they decide. Yes. Issue 653.
mesh-admin added 1 commit 2026-10-13 23:45:55 +00:00
Give the glossary the words of config and provisioning (issue 653)
mesh/merge-gate head 1f6d1b30053b merged into trunk fc9edd5c75b3 — pass: the change touches no module of the mesh's graph
mesh/repo-check head 1f6d1b30053b merged into trunk fc9edd5c75b3 — pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request
1f6d1b3005
ADR 0348 makes config a domain of its own and ADR 0349 makes every value a
module needs a provision placed by mesh-provisioner, but the glossary had no
word for a config value, a predefined key, the provisioner client, a
collection or who owns a placed file. Add them in their domains, move
preference under Config, and use config value where the glossary itself said
setting. "setting" is not put on a Not: line: 67 documents in force still use
it in running prose, so retiring it now would fail words.py on all of them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Author
Contributor

Delivery novox/hq@21508a73483a — delivered since 2026-10-13T23:56:27Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

  • 2026-10-13 23:53 (new) → proposed (announced): novox/hq#351's head announced
  • 2026-10-13 23:54 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-13 23:54 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-13 23:56 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-13 23:56 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/hq@21508a73483a` — **delivered** since 2026-10-13T23:56:27Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-13 23:53 (new) → proposed (announced): novox/hq#351's head announced - 2026-10-13 23:54 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-13 23:54 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-13 23:56 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-13 23:56 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-admin left a comment
Author
Contributor

Verdict: CHANGES at 1f6d1b3005

Ran: MESH_CATALOG_DIR=<mesh-catalog at 8aa37e8> sh merge-check.sh -> exit 0 (records, index, cycle 436, words: 28 retired, 163 head words). Probe in a scratch copy: planted "settings" in 00-META/context.md passes; with ~~setting~~ (hq) on config value's Not: line words.py fails on the plant and on 69 files, one of them this glossary itself (finding 2). No Go here, so gofmt/vet/test do not apply. Leaving "setting" off the Not: line is accepted (design 57 R2, issue 683, rewords the documents).

Must change:

  1. 00-META/glossary.md:212 - record mirror now lists "config values" among the controller's records. ADR 0348 §9 says the controller holds no config value; mesh-config's own buckets replace the settings mirror (it changes ADR 0289 §7, §13, §22). The mechanical replace turned a mirror that held no values into one that holds them. Drop the item, or say the settings mirror stays only until each module moves.
  2. 00-META/glossary.md:124-126 - (a) The deferral names no issue. ADR 0244 §50 requires a deferral to name its tracking issue: say issue 683 (package R2). (b) The sentence itself uses setting and settings in italics, which words.py counts as running prose. The probe shows glossary.md:124 failing once the Not: line is added, so R2 would trip over this page. Put the words in quotation marks. (c) The prose is otherwise accurate: words.py does not catch the word today, and decision records keep their words (ADR 0244 §44).
  3. 00-META/glossary.md:320-326 - managed becomes a head word, but "managed" already has other senses on this page: "the managed instruction file" (:624) is rewritten whole, so in the new words it is owned, and there is also managed_settings. ADR 0244 §16 says a homonym goes in the Homonyms table. Add a row, or qualify the new word (for example managed file).
  4. 00-META/glossary.md:117, 142, 609 - Config uses trusted (ADR 0348 §8: a value that decides what runs or who can reach what), but nothing defines it. The page's only trusted is the operator-message sense in Operator and conversation. Define it in Config and add the homonym row.

Should (can follow):

  1. :111 - Config's "Decided by" should list ADR 0262 (preference moved here) and ADR 0277 (proposals for trusted values). Module's list still carries 0262.
  2. :226 - "assignment ... with the config values it is given there" still reads as if the controller's assignment holds values. Suggest: "a module put on a node; its own values there are module-assignment config (Config)".
  3. ADR 0348 §1 keeps settings, takes-settings and ${setting:<key>} as aliases until every module moves. These are identifiers, so an "Identifier until renamed" line (ADR 0244 §13, pointing at issue 630) would record them.
  4. Adding the Config domain: ADR 0244 §1 (as changed by ADR 0302) lists the domains, and no clause of ADR 0348 changes it; only the record's title says so. :8 points at to-be 49, which lacks Config (R2 will add it). Consider an insight to ADR 0348 or a follow-up issue so the domain list has a decision behind it.
  5. mesh config (a source level, :120) and mesh-config (the module, :141) differ only by a hyphen. Writing the module as mesh-config in a code span, or "the mesh-config module", would keep them apart.

Checked against ADR 0348 and ADR 0349 and found faithful: config value and its four sources, no module value for the whole mesh, predefined key, preference/required, mesh-config's role, provision's every-value clause (0349 §1), mesh-provisioner (§3), provisioner client (§4, §11), collection (§13), and owned/seed/managed (§5). The diff touches only the glossary.

Verdict: CHANGES at 1f6d1b30053b9918d4d1f66c583ff46e5d5bf1d2 Ran: `MESH_CATALOG_DIR=<mesh-catalog at 8aa37e8> sh merge-check.sh` -> exit 0 (records, index, cycle 436, words: 28 retired, 163 head words). Probe in a scratch copy: planted "settings" in 00-META/context.md passes; with `~~setting~~ (hq)` on config value's Not: line words.py fails on the plant and on 69 files, one of them this glossary itself (finding 2). No Go here, so gofmt/vet/test do not apply. Leaving "setting" off the Not: line is accepted (design 57 R2, issue 683, rewords the documents). Must change: 1. 00-META/glossary.md:212 - record mirror now lists "config values" among the controller's records. ADR 0348 §9 says the controller holds no config value; mesh-config's own buckets replace the settings mirror (it changes ADR 0289 §7, §13, §22). The mechanical replace turned a mirror that held no values into one that holds them. Drop the item, or say the settings mirror stays only until each module moves. 2. 00-META/glossary.md:124-126 - (a) The deferral names no issue. ADR 0244 §50 requires a deferral to name its tracking issue: say issue 683 (package R2). (b) The sentence itself uses *setting* and *settings* in italics, which words.py counts as running prose. The probe shows glossary.md:124 failing once the Not: line is added, so R2 would trip over this page. Put the words in quotation marks. (c) The prose is otherwise accurate: words.py does not catch the word today, and decision records keep their words (ADR 0244 §44). 3. 00-META/glossary.md:320-326 - **managed** becomes a head word, but "managed" already has other senses on this page: "the managed instruction file" (:624) is rewritten whole, so in the new words it is *owned*, and there is also `managed_settings`. ADR 0244 §16 says a homonym goes in the Homonyms table. Add a row, or qualify the new word (for example *managed file*). 4. 00-META/glossary.md:117, 142, 609 - Config uses *trusted* (ADR 0348 §8: a value that decides what runs or who can reach what), but nothing defines it. The page's only **trusted** is the operator-message sense in Operator and conversation. Define it in Config and add the homonym row. Should (can follow): 5. :111 - Config's "Decided by" should list ADR 0262 (preference moved here) and ADR 0277 (proposals for trusted values). Module's list still carries 0262. 6. :226 - "assignment ... with the config values it is given there" still reads as if the controller's assignment holds values. Suggest: "a module put on a node; its own values there are module-assignment config (Config)". 7. ADR 0348 §1 keeps `settings`, `takes-settings` and `${setting:<key>}` as aliases until every module moves. These are identifiers, so an "Identifier until renamed" line (ADR 0244 §13, pointing at issue 630) would record them. 8. Adding the Config domain: ADR 0244 §1 (as changed by ADR 0302) lists the domains, and no clause of ADR 0348 changes it; only the record's title says so. :8 points at to-be 49, which lacks Config (R2 will add it). Consider an insight to ADR 0348 or a follow-up issue so the domain list has a decision behind it. 9. *mesh config* (a source level, :120) and **mesh-config** (the module, :141) differ only by a hyphen. Writing the module as `mesh-config` in a code span, or "the mesh-config module", would keep them apart. Checked against ADR 0348 and ADR 0349 and found faithful: config value and its four sources, no module value for the whole mesh, predefined key, preference/`required`, mesh-config's role, provision's every-value clause (0349 §1), mesh-provisioner (§3), provisioner client (§4, §11), collection (§13), and owned/seed/managed (§5). The diff touches only the glossary.
mesh-admin added 1 commit 2026-10-13 23:53:28 +00:00
Answer review 237 of hq#351 (issue 653)
mesh/merge-gate head 21508a73483a merged into trunk fc9edd5c75b3 — pass: the change touches no module of the mesh's graph
mesh/repo-check head 21508a73483a merged into trunk fc9edd5c75b3 — pass: its merge-check.sh passed
mesh/delivery delivered
21508a7348
The controller holds no config value (ADR 0348 section 9), so the record
mirror and the assignment no longer say it does. Name issue 683 for the
Not: line, quote the old word, add the alias identifiers, define trusted,
and add the homonym rows for managed and trusted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mesh-admin left a comment
Author
Contributor

Verdict: APPROVE at 21508a7348

Ran in a worktree of the head: MESH_CATALOG_DIR=<mesh-catalog at ebf7f37> sh merge-check.sh -> exit 0 (records pass; index 6 topics; cycle 436 documents; words: 28 retired words and 4 identifiers, none in running prose; 164 head words, each once). The diff touches only 00-META/glossary.md. No Go here, so gofmt, vet and test do not apply.

Review 237, item by item:

  1. Answered. The record mirror (:222) no longer lists config values; the assignment (:236) says its values are mesh-config's, never the controller's; Config says the controller holds, mirrors and resolves no config value (ADR 0348 §9). I searched the page for other controller-held values and found none.
  2. Answered. Issue 683 is named (:126), and "setting"/"settings" are in quotation marks.
  3. Answered. A Homonyms row for managed (:785-786).
  4. Answered. trusted is defined in Config (:140-143), faithful to ADR 0348 §8, with a Homonyms row against the trusted sender (:787-788).
  5. Answered. Decided by ADR 0262, 0277, 0348 (:111).
  6. Answered (:236).
  7. Answered as agreed. takes-settings and ${setting:} are on an Identifier-until-renamed line naming issue 630 (:130). The sentence above it (:127-129) says the manifest field and the verb "settings" go on that line once issue 683 is done. It says when, clearly enough; see should 2 for the why.
  8. ADR 0354 (proposed, not in force; the knowledge base's review of version 2 asked for a home that cites it) agrees with the Config section: §1's words (config value, its four sources, predefined key, trusted, mesh-config) are all defined in Config, and per §2 Config defines no placement, secret, vault or delivery word, only uses them. Config's Decided by rightly does not cite 0354 while it is proposed.
  9. Answered. mesh-config is in a code span and its entry and config value's both set it apart from mesh config (:123-124, :150).

Should (can follow):

  1. 00-META/glossary.md:634 still says "the managed instruction file", the very sense the new Homonyms row (:786) says to name by the file's own name or "a file the mesh places". Suggest "the instruction file the mesh places".
  2. :127-129 and issue 683: the sentence does not say why bare settings waits (it is still in running prose in documents in force, which words.py would fail), and issue 683's note records only the Not: line, not adding settings to the Identifier line. Add a note on issue 683 so that step is not lost.
  3. :130: ${setting:} matches only that literal text in words.py (pattern() escapes it whole), so it never catches ${setting:<key>} in prose; it records the alias but checks nothing. Fine as a record, since words.py cannot match a placeholder with a key in any form; a reader should not take it as checked. The other Identifier lines link their issue; this one names issue 630 without a link.
Verdict: APPROVE at 21508a73483accd107306f4108e639a65d9c46bf Ran in a worktree of the head: `MESH_CATALOG_DIR=<mesh-catalog at ebf7f37> sh merge-check.sh` -> exit 0 (records pass; index 6 topics; cycle 436 documents; words: 28 retired words and 4 identifiers, none in running prose; 164 head words, each once). The diff touches only 00-META/glossary.md. No Go here, so gofmt, vet and test do not apply. Review 237, item by item: 1. Answered. The record mirror (:222) no longer lists config values; the assignment (:236) says its values are `mesh-config`'s, never the controller's; Config says the controller holds, mirrors and resolves no config value (ADR 0348 §9). I searched the page for other controller-held values and found none. 2. Answered. Issue 683 is named (:126), and "setting"/"settings" are in quotation marks. 3. Answered. A Homonyms row for managed (:785-786). 4. Answered. **trusted** is defined in Config (:140-143), faithful to ADR 0348 §8, with a Homonyms row against the trusted sender (:787-788). 5. Answered. Decided by ADR 0262, 0277, 0348 (:111). 6. Answered (:236). 7. Answered as agreed. `takes-settings` and `${setting:}` are on an Identifier-until-renamed line naming issue 630 (:130). The sentence above it (:127-129) says the manifest field and the verb "settings" go on that line once issue 683 is done. It says when, clearly enough; see should 2 for the why. 8. ADR 0354 (proposed, not in force; the knowledge base's review of version 2 asked for a home that cites it) agrees with the Config section: §1's words (config value, its four sources, predefined key, trusted, `mesh-config`) are all defined in Config, and per §2 Config defines no placement, secret, vault or delivery word, only uses them. Config's Decided by rightly does not cite 0354 while it is proposed. 9. Answered. `mesh-config` is in a code span and its entry and config value's both set it apart from mesh config (:123-124, :150). Should (can follow): 1. 00-META/glossary.md:634 still says "the managed instruction file", the very sense the new Homonyms row (:786) says to name by the file's own name or "a file the mesh places". Suggest "the instruction file the mesh places". 2. :127-129 and issue 683: the sentence does not say why bare `settings` waits (it is still in running prose in documents in force, which words.py would fail), and issue 683's note records only the Not: line, not adding `settings` to the Identifier line. Add a note on issue 683 so that step is not lost. 3. :130: `${setting:}` matches only that literal text in words.py (pattern() escapes it whole), so it never catches `${setting:<key>}` in prose; it records the alias but checks nothing. Fine as a record, since words.py cannot match a placeholder with a key in any form; a reader should not take it as checked. The other Identifier lines link their issue; this one names issue 630 without a link.
mesh-admin merged commit b7e22be7f5 into feat/57-config-and-provisioning 2026-10-13 23:56:12 +00:00
mesh-admin deleted branch pkg/57-f4-glossary-config-words 2026-10-13 23:56:12 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#351