Research 034: the mesh in domains (landed with #174; close) #170

2026-10-07T17:37:57Z

mesh-admin commented

2026-10-07 17:37:57 +00:00

Opens research 034 (status: active), from the operator's request of 2026-10-07 to develop the mesh domain-driven, with one shared vocabulary, because the same concept keeps arriving under different words.

This effort does not change the glossary. That happens at graduation.

00-overview: what is investigated, why, what it touches, findings so far, and the questions left for graduation (machine or node; domain or context; which documents the check covers; where the tool check runs).
01 — The concepts in use: what was read and counted: 225 decision records, 49 to-be and 17 as-is designs, 291 issues, and the 535 tools and 20 seats' verbs the running mesh serves (read-only). It covers the seven contexts of ADR 0006 as they stand, the glossary's two self-contradictions, and about 50 heavily used words it lacks.
02 — The domains: ten domains and the repository's own, each with a purpose, the concepts it owns, its words and its relations. The operator's six-domain guess is tested. Five domains hold. Health and alerts becomes health and repair. Four are added: Module, Core, Provisioning, and Identity and access.
03 — The clashes: twenty clashes with evidence from documents and tool descriptions, and a proposed word for each.
04 — How the glossary is checked: a proposed 00-META/checks/words.py, which reads Not: lines from the glossary, plus the same list applied to the catalogue's tool descriptions in its repository check. It also covers rules for new words and duplicates, and how homonyms are handled. Described only, not built.
05 — A glossary by domain: the proposed shape, and where each of today's entries would go. Described only.

records.py, cycle.py, index.py and merge-check.sh pass.

Opens research 034 (status: active), from the operator's request of 2026-10-07 to develop the mesh domain-driven, with one shared vocabulary, because the same concept keeps arriving under different words. This effort does not change the glossary. That happens at graduation. - **00-overview**: what is investigated, why, what it touches, findings so far, and the questions left for graduation (machine or node; domain or context; which documents the check covers; where the tool check runs). - **01 — The concepts in use**: what was read and counted: 225 decision records, 49 to-be and 17 as-is designs, 291 issues, and the 535 tools and 20 seats' verbs the running mesh serves (read-only). It covers the seven contexts of ADR 0006 as they stand, the glossary's two self-contradictions, and about 50 heavily used words it lacks. - **02 — The domains**: ten domains and the repository's own, each with a purpose, the concepts it owns, its words and its relations. The operator's six-domain guess is tested. Five domains hold. *Health and alerts* becomes *health and repair*. Four are added: Module, Core, Provisioning, and Identity and access. - **03 — The clashes**: twenty clashes with evidence from documents and tool descriptions, and a proposed word for each. - **04 — How the glossary is checked**: a proposed `00-META/checks/words.py`, which reads *Not:* lines from the glossary, plus the same list applied to the catalogue's tool descriptions in its repository check. It also covers rules for new words and duplicates, and how homonyms are handled. Described only, not built. - **05 — A glossary by domain**: the proposed shape, and where each of today's entries would go. Described only. records.py, cycle.py, index.py and merge-check.sh pass.

mesh-admin added 1 commit 2026-10-07 17:37:57 +00:00

Research 034: the mesh in domains

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery stopped: the pull request closed unmerged

Details

f2abbb042c

The operator asked for one language per domain because the same concept
keeps arriving under different words. Inventory the words in use, test a
domain split, list the clashes with evidence, and describe how the
glossary rule would be checked.

mesh-admin commented

2026-10-07 17:38:22 +00:00

Delivery novox/hq@f2abbb042c2f — stopped since 2026-10-07T23:04:47Z

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

Transitions

2026-10-07 17:38 (new) → proposed (announced): novox/hq#170's head announced
2026-10-07 17:38 proposed → checked (checked): the verdict names this commit
2026-10-07 17:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-07 23:04 ready → stopped (closed): the pull request closed unmerged

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

**Delivery** `novox/hq@f2abbb042c2f` — **stopped** since 2026-10-07T23:04:47Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-07 17:38 (new) → proposed (announced): novox/hq#170's head announced - 2026-10-07 17:38 proposed → checked (checked): the verdict names this commit - 2026-10-07 17:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-07 23:04 ready → stopped (closed): the pull request closed unmerged The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin referenced this pull request

2026-10-07 18:02:22 +00:00

ADR 0244: the mesh in domains, one word per thing, checked (graduates research 034) #174

mesh-admin changed title from ~~Research 034: the mesh in domains~~ to Research 034: the mesh in domains (landed with #174; close)

2026-10-07 18:24:04 +00:00

mesh-admin closed this pull request

2026-10-07 23:04:37 +00:00

mesh-admin referenced this pull request

2026-10-09 00:19:27 +00:00

Record hygiene: resolve issues 310, 312, 313, 314, 318, 325, 327, 330 and 337, whose fixes are merged and live #239

mesh-admin referenced this pull request

2026-10-10 01:53:55 +00:00