To-be 45 §5: the operator-channel holder reads open state before it speaks (issue 271) #326

Merged
mesh-admin merged 5 commits from fix/271-channel-reads-open-state-before-it-speaks into main 2026-10-12 19:15:34 +00:00
Contributor

What

Amends to-be 45 §5 to say what the operator-channel holder's When: and Rate: now cover, under ADR 0318 (proposed, needs the operator's Approve): history is never news (it reads the controller's open conditions on start, every ten minutes, and on an old event, and acts only on what is newer than that reading and no more than ten minutes old by its own at); an end nobody was told is told quietly; a clearing of something never said says nothing; an urgent backlog is said once, together; a channel speaks in thirty-second bursts, one digest when several; the desktop keeps a gentler fifteen-minute rhythm than Telegram; the twenty-an-hour cap is said once, not re-announced per excess item; and a one-minute grace follows every start.

Why

Issue 271: the moment the controller made the operator-channel holder's durable consumer on 2026-10-06, the stream handed it 96 settled condition events from that morning. The holder said each as news — twenty desktop notifications in one second, the rest folded — while unassigned. §5 as written only named a rate cap, which bounds a flood but does not stop one. The fix shipped the same day as mesh-catalog PR #88 (merged); this closes the loop the issue's triage flagged: "the fix goes beyond to-be 45 §5 ... the design must be amended through playbook 02 before this resolves." ADR 0318 is reserved and proposed (knowledge-base.reserve/propose) for the decision playbook 02 requires; it cites issue 271 and issue 248 (the controller's own analogous replay) and rests on ADR 0227 and ADR 0253.

How it was checked

sh merge-check.sh locally: records, index, cycle and words all pass (cycle: 436 documents, chain holds; the catalogue-list comparison is skipped without MESH_CATALOG_DIR, as it is off the build seat). The behaviour itself is already checked by mesh-catalog's history_test.go (added in PR #88, replaying the controller's own recorded 96-event backlog) under mesh-catalog's own merge-check.sh; this PR only brings the design document in line with what shipped.

Open before this merges

ADR 0318 is proposed, not yet accepted — it needs the knowledge base's review and then the operator's Approve (needs-operator: true, since it changes what the operator sees in a notification). I have not resolved issue 271 yet; it stays fixing until the decision is accepted and this PR merges.

Fixes issue 271 (once ADR 0318 is accepted).

## What Amends to-be 45 §5 to say what the operator-channel holder's `When:` and `Rate:` now cover, under ADR 0318 (proposed, needs the operator's Approve): history is never news (it reads the controller's open conditions on start, every ten minutes, and on an old event, and acts only on what is newer than that reading and no more than ten minutes old by its own `at`); an end nobody was told is told quietly; a clearing of something never said says nothing; an urgent backlog is said once, together; a channel speaks in thirty-second bursts, one digest when several; the desktop keeps a gentler fifteen-minute rhythm than Telegram; the twenty-an-hour cap is said once, not re-announced per excess item; and a one-minute grace follows every start. ## Why Issue 271: the moment the controller made the operator-channel holder's durable consumer on 2026-10-06, the stream handed it 96 settled condition events from that morning. The holder said each as news — twenty desktop notifications in one second, the rest folded — while unassigned. §5 as written only named a rate cap, which bounds a flood but does not stop one. The fix shipped the same day as mesh-catalog PR #88 (merged); this closes the loop the issue's triage flagged: "the fix goes beyond to-be 45 §5 ... the design must be amended through playbook 02 before this resolves." ADR 0318 is reserved and proposed (knowledge-base.reserve/propose) for the decision playbook 02 requires; it cites issue 271 and issue 248 (the controller's own analogous replay) and rests on ADR 0227 and ADR 0253. ## How it was checked `sh merge-check.sh` locally: records, index, cycle and words all pass (cycle: 436 documents, chain holds; the catalogue-list comparison is skipped without `MESH_CATALOG_DIR`, as it is off the build seat). The behaviour itself is already checked by mesh-catalog's `history_test.go` (added in PR #88, replaying the controller's own recorded 96-event backlog) under mesh-catalog's own merge-check.sh; this PR only brings the design document in line with what shipped. ## Open before this merges ADR 0318 is proposed, not yet accepted — it needs the knowledge base's review and then the operator's Approve (needs-operator: true, since it changes what the operator sees in a notification). I have not resolved issue 271 yet; it stays `fixing` until the decision is accepted and this PR merges. Fixes issue 271 (once ADR 0318 is accepted).
mesh-admin added 1 commit 2026-10-12 11:30:02 +00:00
To-be 45 §5: say what the operator-channel holder now does about history (issue 271, ADR 0318)
mesh/merge-gate out of date: judged against a trunk it does not name, the trunk is now a0e51c061b5e; judged again on a recheck or when it is merged
mesh/repo-check out of date: judged against a trunk it does not name, the trunk is now a0e51c061b5e; judged again on a recheck or when it is merged
mesh/delivery superseded: a newer head of the same pull request
26fbade21a
PR #88 (merged 2026-10-06) already fixed the holder to read open state first,
coalesce bursts and hold a start grace minute, after a new consumer replayed a
morning's 96 settled events as fresh alerts. §5 still only said a rate cap; this
names the rules actually built, under ADR 0318.
Author
Contributor

Delivery novox/hq@d69c8929e9df — delivered since 2026-10-12T19:15:54Z

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

Transitions

  • 2026-10-12 19:13 (new) → proposed (announced): novox/hq#326's head announced
  • 2026-10-12 19:14 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-12 19:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-12 19:15 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:15 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@d69c8929e9df` — **delivered** since 2026-10-12T19:15:54Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-12 19:13 (new) → proposed (announced): novox/hq#326's head announced - 2026-10-12 19:14 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-12 19:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-12 19:15 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:15 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-12 19:07:40 +00:00
To-be 45 §5: match ADR 0318 version 10, so an urgent message is never folded and a backlog gets its answers (issue 271)
mesh/merge-gate head ac5bdeb17860 merged into trunk a0e51c061b5e — fail: head ac5bdeb17860 does not merge cleanly into trunk a0e51c061b5e: in conflict 03-D…
mesh/repo-check head ac5bdeb17860 merged into trunk a0e51c061b5e — fail: head ac5bdeb17860 does not merge cleanly into trunk a0e51c061b5e: in conflict 03-D…
mesh/delivery superseded: a newer head of the same pull request
ac5bdeb178
Author
Contributor

Merge check at ac5bdeb1
Judged: head ac5bdeb17860 merged into trunk a0e51c061b5e

  • mesh/merge-gate: FAIL — head ac5bdeb178 does not merge cleanly into trunk a0e51c061b: in conflict 03-DESIGN/01-to-be/45-a-core-that-cannot-fail-silently.md
  • mesh/repo-check: FAIL — head ac5bdeb178 does not merge cleanly into trunk a0e51c061b: in conflict 03-DESIGN/01-to-be/45-a-core-that-cannot-fail-silently.md

Run by the build seat on shanks as build-1791832068027521109 (builds --log build-1791832068027521109).

head ac5bdeb17860 does not merge cleanly into trunk a0e51c061b5e: in conflict 03-DESIGN/01-to-be/45-a-core-that-cannot-fail-silently.md
**Merge check** at `ac5bdeb1` Judged: head `ac5bdeb17860` merged into trunk `a0e51c061b5e` - `mesh/merge-gate`: **FAIL** — head ac5bdeb17860 does not merge cleanly into trunk a0e51c061b5e: in conflict 03-DESIGN/01-to-be/45-a-core-that-cannot-fail-silently.md - `mesh/repo-check`: **FAIL** — head ac5bdeb17860 does not merge cleanly into trunk a0e51c061b5e: in conflict 03-DESIGN/01-to-be/45-a-core-that-cannot-fail-silently.md Run by the build seat on shanks as `build-1791832068027521109` (`builds --log build-1791832068027521109`). ``` head ac5bdeb17860 does not merge cleanly into trunk a0e51c061b5e: in conflict 03-DESIGN/01-to-be/45-a-core-that-cannot-fail-silently.md ```
jschoubben added 2 commits 2026-10-12 19:09:31 +00:00
# Conflicts:
#	03-DESIGN/01-to-be/45-a-core-that-cannot-fail-silently.md
To-be 45 §5: say what the holder does while the controller cannot be read, and that every fold and hold is recorded (ADR 0318, issue 271)
mesh/merge-gate head c6d92446e697 merged into trunk a0e51c061b5e — pass: the change touches no module of the mesh's graph
mesh/repo-check head c6d92446e697 merged into trunk a0e51c061b5e — pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request
c6d92446e6
mesh-admin left a comment
Author
Contributor

Verdict: request changes at c6d92446e6

Independent review of the to-be 45 §5 amendment against ADR 0318 version 14, which is accepted and has eight clauses. The grace minute is clause 8.

What holds:

  • The frontmatter keeps every ADR from main and adds ADR 0318. The diff only adds lines.
  • Clauses 1, 2, 3, 7 and 8 are stated faithfully. These cover the reading and its two tests, the five seconds of clock slack, the controller-unreachable rule, the quiet close, the drop, the cap said once with answers kept, and the grace minute that holds even a fresh urgent event. Recording of every close, drop, fold and hold is stated once and covers clauses 2, 3, 5 and 7.
  • The digest shape (headlines, one line each, no answers) and the rule that an answer is never folded are stated.
  • The prose follows the house rules: no code, no node names, no real domains. merge-check.sh passes in a clean clone at this head (exit 0: records, index, cycle and words all pass). The catalogue comparison was not run because MESH_CATALOG_DIR is unset, which is expected.

Changes requested:

  1. The desktop rhythm (clause 6) now reads the wrong way. "a warning reaches it at most once every fifteen minutes, never an urgent one" can be read as "an urgent message never reaches the desktop". That contradicts the line above it, "Urgent goes to both channels", and it contradicts the clause itself, which says "an urgent message is never held to that rhythm". Suggested wording: "a warning reaches it at most once every fifteen minutes; an urgent message is never held to that rhythm."
  2. The urgent backlog (clause 4) is incomplete. The amendment says each open urgent condition is sent on its own "when the grace minute ends". The clause adds "or at once when the reading is not a start's", and it also says this happens "under clause 7's cap". As written, an urgent backlog found by the ten-minute reading, or by the re-read an old event triggers, has no grace minute to wait for and no stated time to be sent. Add both parts.

Minor, not blocking:

  • The sentence about an urgent item breaking the thirty-second quiet should say "except inside the grace minute". The previous bullet does say this, but the Rate bullet read on its own suggests otherwise.
  • One source line runs well past the others ("closed quietly: ... and a message"). Rewrap it.
Verdict: request changes at c6d92446e6973876477bfb9f876eba0780cb65ff Independent review of the to-be 45 §5 amendment against ADR 0318 version 14, which is accepted and has eight clauses. The grace minute is clause 8. What holds: - The frontmatter keeps every ADR from main and adds ADR 0318. The diff only adds lines. - Clauses 1, 2, 3, 7 and 8 are stated faithfully. These cover the reading and its two tests, the five seconds of clock slack, the controller-unreachable rule, the quiet close, the drop, the cap said once with answers kept, and the grace minute that holds even a fresh urgent event. Recording of every close, drop, fold and hold is stated once and covers clauses 2, 3, 5 and 7. - The digest shape (headlines, one line each, no answers) and the rule that an answer is never folded are stated. - The prose follows the house rules: no code, no node names, no real domains. merge-check.sh passes in a clean clone at this head (exit 0: records, index, cycle and words all pass). The catalogue comparison was not run because MESH_CATALOG_DIR is unset, which is expected. Changes requested: 1. The desktop rhythm (clause 6) now reads the wrong way. "a warning reaches it at most once every fifteen minutes, never an urgent one" can be read as "an urgent message never reaches the desktop". That contradicts the line above it, "Urgent goes to both channels", and it contradicts the clause itself, which says "an urgent message is never held to that rhythm". Suggested wording: "a warning reaches it at most once every fifteen minutes; an urgent message is never held to that rhythm." 2. The urgent backlog (clause 4) is incomplete. The amendment says each open urgent condition is sent on its own "when the grace minute ends". The clause adds "or at once when the reading is not a start's", and it also says this happens "under clause 7's cap". As written, an urgent backlog found by the ten-minute reading, or by the re-read an old event triggers, has no grace minute to wait for and no stated time to be sent. Add both parts. Minor, not blocking: - The sentence about an urgent item breaking the thirty-second quiet should say "except inside the grace minute". The previous bullet does say this, but the Rate bullet read on its own suggests otherwise. - One source line runs well past the others ("closed quietly: ... and a message"). Rewrap it.
jschoubben added 1 commit 2026-10-12 19:13:12 +00:00
To-be 45 §5: say urgent is never held to the desktop's rhythm, and give clause 4 its outside-a-start case and the cap (ADR 0318, review 97)
mesh/merge-gate head d69c8929e9df merged into trunk a0e51c061b5e — pass: the change touches no module of the mesh's graph
mesh/repo-check head d69c8929e9df merged into trunk a0e51c061b5e — pass: its merge-check.sh passed
mesh/delivery delivered
d69c8929e9
mesh-admin left a comment
Author
Contributor

Verdict: approve at d69c8929e9

This re-review checks the changes against review 97 and ADR 0318 version 14 (8 clauses, accepted).

All four points of review 97 are fixed:

  1. Clause 6 (the desktop's slower rhythm) now reads "a warning reaches it at most once every fifteen minutes; an urgent message is never held to that rhythm, and still goes to both channels". This matches the clause and the existing "Urgent goes to both channels".
  2. Clause 4 (the urgent backlog) now has both missing parts: "or at once when the reading is not a start's" and "under the cap".
  3. The Rate bullet now says an urgent item breaks the thirty-second quiet "except inside the grace minute", which matches clause 8.
  4. The overlong line is rewrapped.

Nothing else changed. Clauses 1, 2, 3, 5, 7 and 8 still state what ADR 0318 decides. The frontmatter keeps every ADR from main and adds ADR 0318.

Checks:

  • merge-check.sh passes (exit 0) in a clean clone at this head, which already contains main. The catalogue comparison was not run because MESH_CATALOG_DIR is unset.
  • mesh/merge-gate is green: the change touches no module.
  • mesh/repo-check is green: merge-check.sh passed.
  • mesh/delivery is green: it is ready to deliver once merged.
Verdict: approve at d69c8929e9df1f3394726a46ab16c59f90278326 This re-review checks the changes against review 97 and ADR 0318 version 14 (8 clauses, accepted). All four points of review 97 are fixed: 1. Clause 6 (the desktop's slower rhythm) now reads "a warning reaches it at most once every fifteen minutes; an urgent message is never held to that rhythm, and still goes to both channels". This matches the clause and the existing "Urgent goes to both channels". 2. Clause 4 (the urgent backlog) now has both missing parts: "or at once when the reading is not a start's" and "under the cap". 3. The Rate bullet now says an urgent item breaks the thirty-second quiet "except inside the grace minute", which matches clause 8. 4. The overlong line is rewrapped. Nothing else changed. Clauses 1, 2, 3, 5, 7 and 8 still state what ADR 0318 decides. The frontmatter keeps every ADR from main and adds ADR 0318. Checks: - merge-check.sh passes (exit 0) in a clean clone at this head, which already contains main. The catalogue comparison was not run because MESH_CATALOG_DIR is unset. - mesh/merge-gate is green: the change touches no module. - mesh/repo-check is green: merge-check.sh passed. - mesh/delivery is green: it is ready to deliver once merged.
mesh-admin merged commit 7e73284f21 into main 2026-10-12 19:15:34 +00:00
mesh-admin deleted branch fix/271-channel-reads-open-state-before-it-speaks 2026-10-12 19:15:35 +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#326