Research 044: what leaves the controller next #287

Merged
mesh-admin merged 1 commits from research/044-what-leaves-the-controller-next into main 2026-10-10 16:17:31 +00:00
Contributor

Opens research 044 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: group the last month's controller merges by ADR 0244's domains; rank domains by change rate times how little they need the core; test candidates (probes, conditions and the hand-act log as a monitoring module; asks, proposals and notification wording to the operator's channel; the network checks); what must stay (deciding what each node runs); how a domain moves out without a flag day; how the effect is measured afterwards (controller merges per week, time from merge to node).

Evidence cited (measured 2026-10-10 on the controller's main): 191 merges in 7 days; about 104k lines of non-test Go, 44k in one package that took about 60% of the week's file changes; issue 382 (45 minutes for a small fix to reach a node).

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. 044 and 045 were checked free against the forge's branches and open pull requests.

Only 01-RESEARCH/044-what-leaves-the-controller-next/00-overview.md is added. sh merge-check.sh (records, index, cycle, words) passes locally.

Opens research 044 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: group the last month's controller merges by ADR 0244's domains; rank domains by change rate times how little they need the core; test candidates (probes, conditions and the hand-act log as a monitoring module; asks, proposals and notification wording to the operator's channel; the network checks); what must stay (deciding what each node runs); how a domain moves out without a flag day; how the effect is measured afterwards (controller merges per week, time from merge to node). Evidence cited (measured 2026-10-10 on the controller's main): 191 merges in 7 days; about 104k lines of non-test Go, 44k in one package that took about 60% of the week's file changes; issue 382 (45 minutes for a small fix to reach a node). **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. 044 and 045 were checked free against the forge's branches and open pull requests. Only `01-RESEARCH/044-what-leaves-the-controller-next/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:38 +00:00
Open research 044: what leaves the controller next
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
c148066de4
Every controller change walks the core's tier and holds up every other walk
(issue 382), while most of the week's change sat in one package. Framed as
questions: which domain changes most and needs the core least.
Author
Contributor

Delivery novox/hq@c148066de446 — 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#287'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@c148066de446` — **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#287'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 3c323370b7 into main 2026-10-10 16:17:31 +00:00
mesh-admin deleted branch research/044-what-leaves-the-controller-next 2026-10-10 16:17:31 +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#287