ADR 0282 (proposed): a leaf fix runs healthy on every node within five minutes of its merge, a core module within ten #289

Merged
mesh-admin merged 3 commits from decisions/0282-a-leaf-fix-runs-healthy-everywhere-within-five-minutes-of-its-merge into main 2026-10-10 17:59:02 +00:00
Contributor

Issue 382 (a small fix takes 45 minutes to reach a node) and issue 338 (a module built from a shared repository moves on every merge to it).

The operator decides this one: do not merge without their word. The record is status: proposed.

What is in it

  • ADR 0282 (proposed): the measurement of 51 finished walks (2026-10-09 13:55 to 2026-10-10 17:32 UTC) split into phases, each lever weighed by what it would have saved, and the decision: leaf budget 5 minutes, core budget 10 minutes; no merge window for a lone merge; independent walks at once (one judgement per node, a core walk keeps its ground); judgement readings by class (core 3, leaf with a long-running resource 2, tools-only leaf 1); a tier's first nodes judged at once; every phase and delivery time recorded; delivery.<class>.over-budget condition; expected landing time. Reusing the merge gate's build is rejected: the merge gate builds no artifact today.
  • To-be 47: a section "The delivery budget", marked proposed, with who builds what (mesh-controller vs mesh-delivery) and five slices with acceptance sentences.
  • Glossary: core module / leaf module, delivery time, delivery budget.

Measured

  • Leaf walks (20): median 6.0 min, worst 66.0 (13.3 without the issue 362 incident); 7 of 20 within 5 min.
  • Core walks of one tier (13): median 5.6, worst 8.8. Controller walks dragging two catalogue tiers (18, issue 338): median 14.2, worst 20.5.
  • Largest leaf sinks: waiting behind another walk (47 % of leaf time), first-node judgement (27 %, 2.6 min per tier), the merge window (1.8 min per lone merge since it went live).
  • With the chosen levers applied to the same walks: leaf median 2.1, worst 5.3, 19 of 20 within 5 min.

On acceptance

  1. status: accepted on ADR 0282.
  2. ADR 0282 added to to-be 47's decisions:; the section's "proposed" line removed.
  3. ADR 0236 (decision 2) and ADR 0276 (decisions 1 and 4) gain a "The mechanism changed" note pointing here; ADR 0282 added to the Change and delivery domain's "Decided by" line.

Checks

records.py, index.py, cycle.py, words.py pass locally.

Issue 382 (a small fix takes 45 minutes to reach a node) and issue 338 (a module built from a shared repository moves on every merge to it). **The operator decides this one: do not merge without their word.** The record is `status: proposed`. ## What is in it - **ADR 0282** (proposed): the measurement of 51 finished walks (2026-10-09 13:55 to 2026-10-10 17:32 UTC) split into phases, each lever weighed by what it would have saved, and the decision: leaf budget 5 minutes, core budget 10 minutes; no merge window for a lone merge; independent walks at once (one judgement per node, a core walk keeps its ground); judgement readings by class (core 3, leaf with a long-running resource 2, tools-only leaf 1); a tier's first nodes judged at once; every phase and delivery time recorded; `delivery.<class>.over-budget` condition; expected landing time. Reusing the merge gate's build is rejected: the merge gate builds no artifact today. - **To-be 47**: a section "The delivery budget", marked proposed, with who builds what (mesh-controller vs mesh-delivery) and five slices with acceptance sentences. - **Glossary**: core module / leaf module, delivery time, delivery budget. ## Measured - Leaf walks (20): median 6.0 min, worst 66.0 (13.3 without the issue 362 incident); 7 of 20 within 5 min. - Core walks of one tier (13): median 5.6, worst 8.8. Controller walks dragging two catalogue tiers (18, issue 338): median 14.2, worst 20.5. - Largest leaf sinks: waiting behind another walk (47 % of leaf time), first-node judgement (27 %, 2.6 min per tier), the merge window (1.8 min per lone merge since it went live). - With the chosen levers applied to the same walks: leaf median 2.1, worst 5.3, 19 of 20 within 5 min. ## On acceptance 1. `status: accepted` on ADR 0282. 2. ADR 0282 added to to-be 47's `decisions:`; the section's "proposed" line removed. 3. ADR 0236 (decision 2) and ADR 0276 (decisions 1 and 4) gain a "The mechanism changed" note pointing here; ADR 0282 added to the Change and delivery domain's "Decided by" line. ## Checks `records.py`, `index.py`, `cycle.py`, `words.py` pass locally.
mesh-admin added 1 commit 2026-10-10 17:51:19 +00:00
ADR 0282 (proposed): a leaf fix runs healthy on every node within five minutes of its merge, a core module within ten
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 superseded: a newer head of the same pull request
9414855fbe
The operator asked that a bug fix land on every node in under five minutes. 51
walks measured from the controller's own records put a leaf walk at a median of
6.0 minutes (7 of 20 within five) and say where the time goes: waiting behind
another walk, the first-node judgement, the merge window. The record weighs each
lever by what it would have saved, keeps three readings for core modules (ten
minutes, the measured worst being 8.8), and proposes the measure and condition
that check it. To-be 47 gains the section, the owners and five slices; the
glossary gains delivery time, delivery budget, core and leaf module.
Author
Contributor

Delivery novox/hq@0a6172640cfb — delivered since 2026-10-10T17:59:19Z

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

Transitions

  • 2026-10-10 17:57 (new) → proposed (announced): novox/hq#289's head announced
  • 2026-10-10 17:58 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 17:58 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 17:59 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 17:59 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@0a6172640cfb` — **delivered** since 2026-10-10T17:59:19Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 17:57 (new) → proposed (announced): novox/hq#289's head announced - 2026-10-10 17:58 proposed → checked (checked): the verdict names this commit - 2026-10-10 17:58 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 17:59 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 17:59 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 added 1 commit 2026-10-10 17:53:38 +00:00
ADR 0282: a core send sets aside a leaf judgement; the window row says how it was split; the repository rule cites ADR 0276
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 superseded: a newer head of the same pull request
8b6c306cfd
From the independent review: a core delivery could wait on a leaf judgement past
its ten minutes, the window figure's split was not stated beside it, and the
one-repository rule was credited to the wrong issue.
jschoubben added 1 commit 2026-10-10 17:57:10 +00:00
Accept ADR 0282: the operator decided the delivery budgets on 2026-10-10
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
0a6172640c
To-be 47 lists the record among its decisions, ADR 0236 and ADR 0276 say
where their mechanism moves, and the glossary drops 'proposed'.
mesh-admin merged commit 8eca7b921e into main 2026-10-10 17:59:02 +00:00
mesh-admin deleted branch decisions/0282-a-leaf-fix-runs-healthy-everywhere-within-five-minutes-of-its-merge 2026-10-10 17:59:03 +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#289