What. The glossary gains fix time and fix budget: the span from an issue's first move to fixing to its last fix delivered, held to five minutes for a leaf module and ten for a core one. An issue whose fixes move no module has no fix budget. The delivery time entry now says the delivery budget is a measure inside the fix budget, not the operator's target. It also gives the leaf delivery budget as three minutes, which ADR 0304 set; the entry still said five.
Why. ADR 0313's Consequences put the two new words, and the change to the delivery budget entry, in a pull request under issue 403. Design 47's paragraph (merged in f63e60a) already uses both words.
Checked.sh merge-check.sh passes: records, index, cycle and words (154 head words, each once).
Order. One delivery group with mesh-controller and mesh-catalog on fix/403-fix-time. It moves no module.
Part of issue 403. Not merged.
**What.** The glossary gains **fix time** and **fix budget**: the span from an issue's first move to `fixing` to its last fix delivered, held to five minutes for a leaf module and ten for a core one. An issue whose fixes move no module has no fix budget. The **delivery time** entry now says the delivery budget is a measure inside the fix budget, not the operator's target. It also gives the leaf delivery budget as three minutes, which ADR 0304 set; the entry still said five.
**Why.** ADR 0313's Consequences put the two new words, and the change to the delivery budget entry, in a pull request under issue 403. Design 47's paragraph (merged in f63e60a) already uses both words.
**Checked.** `sh merge-check.sh` passes: records, index, cycle and words (154 head words, each once).
**Order.** One delivery group with mesh-controller and mesh-catalog on `fix/403-fix-time`. It moves no module.
Part of issue 403. Not merged.
ADR 0313 makes the span from the move to fixing to delivered the operator's
target; the delivery budget stays a measure inside it, and its leaf figure is
three minutes since ADR 0304.
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Transitions
2026-10-12 13:51 (new) → proposed (announced): novox/hq#331's head announced
2026-10-12 13:51 proposed → checked (checked): the verdict names this commit
2026-10-12 13:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 19:38 ready → proposed (recheck): issue 403 group: the trunk moved since its check; judged again against the new trunk
2026-10-12 19:39 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-12 19:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 19:41 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-12 19:41 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@506d00cf7428` — **delivered** since 2026-10-12T19:41:40Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Group** `fix/403-fix-time`, in order: novox/hq@506d00cf7428 → novox/mesh-controller@daf52b3aeb79 → novox/mesh-catalog@005f802504fc
- novox/mesh-controller@daf52b3aeb79 before novox/mesh-catalog@005f802504fc: built by
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Transitions**
- 2026-10-12 13:51 (new) → proposed (announced): novox/hq#331's head announced
- 2026-10-12 13:51 proposed → checked (checked): the verdict names this commit
- 2026-10-12 13:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 19:38 ready → proposed (recheck): issue 403 group: the trunk moved since its check; judged again against the new trunk
- 2026-10-12 19:39 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-12 19:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 19:41 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-12 19:41 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`.
Independent review of issue 403 (ADR 0313) across the group fix/403-fix-time: mesh-controller #265, mesh-catalog #250 and this pull request.
The words are consistent. The glossary adds fix time and fix budget under the delivery entries. They read as ADR 0313 §1 and §2 say: the start is the first move to fixing and the end is the last fix delivered; the budgets are five minutes for leaf and ten for core, counted from that move; and an issue whose fixes move no module has no budget. The delivery time entry now says it is a measure inside the fix budget, not the operator's target, which is ADR 0313 §3. The words match those used in mesh-catalog #250's README and verbs (fix time, fix budget, class, phases).
The leaf delivery budget matches ADR 0304. It is now three minutes. That is ADR 0304 §4 ("A leaf module's delivery budget is three minutes", in force), and core stays at ten (ADR 0282). The old text still said five minutes for leaf, so this also corrects a stale fact.
Public-repo rules: the diff has no node names, addresses or paths.
Checks: I did not run merge-check.sh locally, because this session was refused a local clone. mesh/repo-check at 506d00cf74 says "its merge-check.sh passed", and mesh/merge-gate passes (it touches no module). mesh/delivery-group says "every member ready, and composed together they pass".
The group as a whole waits on mesh-catalog #250, where I requested a change. This glossary text does not depend on that change.
Verdict: approve at 506d00cf74287f9db0d73535d1f4d786e3278c36
Independent review of issue 403 (ADR 0313) across the group fix/403-fix-time: mesh-controller #265, mesh-catalog #250 and this pull request.
**The words are consistent.** The glossary adds **fix time** and **fix budget** under the delivery entries. They read as ADR 0313 §1 and §2 say: the start is the first move to `fixing` and the end is the last fix delivered; the budgets are five minutes for leaf and ten for core, counted from that move; and an issue whose fixes move no module has no budget. The *delivery time* entry now says it is a measure inside the fix budget, not the operator's target, which is ADR 0313 §3. The words match those used in mesh-catalog #250's README and verbs (fix time, fix budget, class, phases).
**The leaf delivery budget matches ADR 0304.** It is now three minutes. That is ADR 0304 §4 ("A leaf module's delivery budget is three minutes", in force), and core stays at ten (ADR 0282). The old text still said five minutes for leaf, so this also corrects a stale fact.
**Public-repo rules:** the diff has no node names, addresses or paths.
**Checks:** I did not run merge-check.sh locally, because this session was refused a local clone. mesh/repo-check at 506d00cf7428 says "its merge-check.sh passed", and mesh/merge-gate passes (it touches no module). mesh/delivery-group says "every member ready, and composed together they pass".
The group as a whole waits on mesh-catalog #250, where I requested a change. This glossary text does not depend on that change.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What. The glossary gains fix time and fix budget: the span from an issue's first move to
fixingto its last fix delivered, held to five minutes for a leaf module and ten for a core one. An issue whose fixes move no module has no fix budget. The delivery time entry now says the delivery budget is a measure inside the fix budget, not the operator's target. It also gives the leaf delivery budget as three minutes, which ADR 0304 set; the entry still said five.Why. ADR 0313's Consequences put the two new words, and the change to the delivery budget entry, in a pull request under issue 403. Design 47's paragraph (merged in
f63e60a) already uses both words.Checked.
sh merge-check.shpasses: records, index, cycle and words (154 head words, each once).Order. One delivery group with mesh-controller and mesh-catalog on
fix/403-fix-time. It moves no module.Part of issue 403. Not merged.
Delivery
novox/hq@506d00cf7428— delivered since 2026-10-12T19:41:40ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Group
fix/403-fix-time, in order: novox/hq@506d00cf74 → novox/mesh-controller@daf52b3aeb → novox/mesh-catalog@005f802504Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Verdict: approve at
506d00cf74Independent review of issue 403 (ADR 0313) across the group fix/403-fix-time: mesh-controller #265, mesh-catalog #250 and this pull request.
The words are consistent. The glossary adds fix time and fix budget under the delivery entries. They read as ADR 0313 §1 and §2 say: the start is the first move to
fixingand the end is the last fix delivered; the budgets are five minutes for leaf and ten for core, counted from that move; and an issue whose fixes move no module has no budget. The delivery time entry now says it is a measure inside the fix budget, not the operator's target, which is ADR 0313 §3. The words match those used in mesh-catalog #250's README and verbs (fix time, fix budget, class, phases).The leaf delivery budget matches ADR 0304. It is now three minutes. That is ADR 0304 §4 ("A leaf module's delivery budget is three minutes", in force), and core stays at ten (ADR 0282). The old text still said five minutes for leaf, so this also corrects a stale fact.
Public-repo rules: the diff has no node names, addresses or paths.
Checks: I did not run merge-check.sh locally, because this session was refused a local clone. mesh/repo-check at
506d00cf74says "its merge-check.sh passed", and mesh/merge-gate passes (it touches no module). mesh/delivery-group says "every member ready, and composed together they pass".The group as a whole waits on mesh-catalog #250, where I requested a change. This glossary text does not depend on that change.