ADR 0289: the controller mirrors its records into buckets written only on a change (issue 419, research 036 G2) #303

Merged
mesh-admin merged 3 commits from decisions/0289-the-controller-mirrors-its-records-on-the-bus into main 2026-10-10 20:07:05 +00:00
Contributor

Graduates gap G2 of research 036 (everything over NATS). Issue 419 tracks the build; issue 420 tracks the conditions bucket, which breaks the new rule today.

  • ADR 0289: five record mirrors (nodes, assignments, walks, builds, settings). Each is a bucket the controller's lease holder writes from its store after the commit, and only when the value differs. Every write sends one event. The probe D17 audits each mirror against the store on every self-check run, raises mirror-drifted on any difference, and the healer H6 repairs it. The settings mirror holds no values (issue 342: passwords still travel as settings). The rule that a bucket is written only when what it describes changed (issue 326) holds for every bucket, and the runtime skips an equal put.
  • To-be 54 (new): the design.
  • To-be 45: a writers-table row, D17 and H6, and a note on the conditions bucket (issue 420).
  • To-be 25 §1: a pointer. ADR 0201: a dated note that put changed. Glossary: record mirror.
  • Research 036 stays active for G1, G3 and the views, and for G4, G5, G6 and G8 to G10. The overview says what was decided and what stays open.

Checks: records, index, words and cycle pass, and sh merge-check.sh passes locally.

Graduates gap G2 of research 036 (everything over NATS). Issue 419 tracks the build; issue 420 tracks the conditions bucket, which breaks the new rule today. - **ADR 0289**: five record mirrors (nodes, assignments, walks, builds, settings). Each is a bucket the controller's lease holder writes from its store after the commit, and only when the value differs. Every write sends one event. The probe D17 audits each mirror against the store on every self-check run, raises `mirror-drifted` on any difference, and the healer H6 repairs it. The settings mirror holds no values (issue 342: passwords still travel as settings). The rule that a bucket is written only when what it describes changed (issue 326) holds for every bucket, and the runtime skips an equal `put`. - **To-be 54** (new): the design. - **To-be 45**: a writers-table row, D17 and H6, and a note on the conditions bucket (issue 420). - **To-be 25** §1: a pointer. **ADR 0201**: a dated note that `put` changed. **Glossary**: *record mirror*. - **Research 036** stays active for G1, G3 and the views, and for G4, G5, G6 and G8 to G10. The overview says what was decided and what stays open. Checks: records, index, words and cycle pass, and `sh merge-check.sh` passes locally.
Author
Contributor

Delivery novox/hq@9be659b18cb4 — delivered since 2026-10-10T20:07:35Z

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

Transitions

  • 2026-10-10 20:05 (new) → proposed (announced): novox/hq#303's head announced
  • 2026-10-10 20:06 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 20:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 20:07 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 20:07 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@9be659b18cb4` — **delivered** since 2026-10-10T20:07:35Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 20:05 (new) → proposed (announced): novox/hq#303's head announced - 2026-10-10 20:06 proposed → checked (checked): the verdict names this commit - 2026-10-10 20:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 20:07 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 20:07 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`.
jschoubben force-pushed decisions/0289-the-controller-mirrors-its-records-on-the-bus from fd261f3642 to 1dfde70fed 2026-10-10 20:03:33 +00:00 Compare
jschoubben added 3 commits 2026-10-10 20:05:27 +00:00
Nodes, assignments, walks, builds and settings could be seen only by polling verbs, and a setting
changed with no event. Each becomes a record mirror: a bucket written from the store after the commit
and only when the value differs, one event per write, compared with the store on every self-check run
(D17, mirror-drifted, healer H6). The write-only-on-a-change rule from issue 326 now holds for every
bucket; the conditions bucket breaks it and issue 420 tracks that. The effort stays active for G1, G3
and the views.
Say how the writer tells its own lost acknowledgement from a former holder, list D16, and fix the settings heading (review of #303)
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
9be659b18c
jschoubben force-pushed decisions/0289-the-controller-mirrors-its-records-on-the-bus from 1dfde70fed to 9be659b18c 2026-10-10 20:05:27 +00:00 Compare
mesh-admin merged commit 1b84960179 into main 2026-10-10 20:07:05 +00:00
mesh-admin deleted branch decisions/0289-the-controller-mirrors-its-records-on-the-bus 2026-10-10 20:07:05 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#303