Research 045: a knowledge base the mesh writes (decisions, guidelines, policies) #288

Merged
mesh-admin merged 1 commits from research/045-a-knowledge-base-the-mesh-writes into main 2026-10-10 16:17:34 +00:00
Contributor

Opens research 045 through playbook 01, at the operator's request of 2026-10-10. The operator does the research itself on another machine; this pull request only registers the effort.

The overview frames the questions and answers none of them. Options to weigh: A, git stays the store and the records module gains write verbs (propose, amend as progressive insight, supersede, retire) that branch and open a pull request, numbered from the issue tracker's counters; B, a store is the truth and hq is its rendered public export, as for issues (ADR 0275). Questions: types and lifecycles; numbering from one counter; typed links; approval on a proving channel (ADR 0274); public versus private knowledge; the hq checks as refusals at write; import of the decision records; what review and history git gives that a store would rebuild.

The glossary has no word for guideline or policy in this sense (policy already names the upgrade policy); the overview says so and uses plain descriptions.

Numbering note. 043 is taken by open PR #282, and another session holds an unpushed local branch research/043-the-meshboard, so 043 may be claimed twice when that branch is pushed; it would need the next free number then. The overview cites this clash as an example of the numbering question.

Only 01-RESEARCH/045-a-knowledge-base-the-mesh-writes/00-overview.md is added. sh merge-check.sh (records, index, cycle, words) passes locally.

Opens research 045 through playbook 01, at the operator's request of 2026-10-10. The operator does the research itself on another machine; this pull request only registers the effort. The overview frames the questions and answers none of them. Options to weigh: A, git stays the store and the records module gains write verbs (propose, amend as progressive insight, supersede, retire) that branch and open a pull request, numbered from the issue tracker's counters; B, a store is the truth and hq is its rendered public export, as for issues (ADR 0275). Questions: types and lifecycles; numbering from one counter; typed links; approval on a proving channel (ADR 0274); public versus private knowledge; the hq checks as refusals at write; import of the decision records; what review and history git gives that a store would rebuild. The glossary has no word for guideline or policy in this sense (policy already names the upgrade policy); the overview says so and uses plain descriptions. **Numbering note.** 043 is taken by open PR #282, and another session holds an unpushed local branch `research/043-the-meshboard`, so 043 may be claimed twice when that branch is pushed; it would need the next free number then. The overview cites this clash as an example of the numbering question. Only `01-RESEARCH/045-a-knowledge-base-the-mesh-writes/00-overview.md` is added. `sh merge-check.sh` (records, index, cycle, words) passes locally.
mesh-admin added 1 commit 2026-10-10 16:14:42 +00:00
Open research 045: a knowledge base the mesh writes
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
72f940d2c7
The record is read-only and hand-written; numbers collide and private knowledge
has no home. Framed as questions, weighing git as the store against a store
with hq as its public export.
Author
Contributor

Delivery novox/hq@72f940d2c79e — delivered since 2026-10-10T16:17:51Z

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

Transitions

  • 2026-10-10 16:15 (new) → proposed (announced): novox/hq#288's head announced
  • 2026-10-10 16:15 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 16:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 16:17 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-10 16:17 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@72f940d2c79e` — **delivered** since 2026-10-10T16:17:51Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 16:15 (new) → proposed (announced): novox/hq#288's head announced - 2026-10-10 16:15 proposed → checked (checked): the verdict names this commit - 2026-10-10 16:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 16:17 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 16:17 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 merged commit 0cabe5d391 into main 2026-10-10 16:17:34 +00:00
mesh-admin deleted branch research/045-a-knowledge-base-the-mesh-writes 2026-10-10 16:17:34 +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#288