Issue 276: the audit logger and the usage store retry, and lose no event #145

2026-10-06T16:37:36Z

mesh-admin commented

2026-10-06 16:37:36 +00:00

Records the operator's decision for the two consumers issue 276 left for their own change: the audit logger and the usage store must retry a failed write and never lose an event.

Report: new section The two consumers that took a failed write — thrown write, spool from the first failure (declared valuable, ADR 0233), last delivery taken from the spool, background replay, idempotent writes (trail skips a written id; usage keeps the reading observed latest), and a bound past which the last delivery is not taken so the bus raises max-deliveries (no module-level standing exists; ADR 0224's is a provider's). What it does not cover, and how it is checked. located-in gains the two modules.
Diagnosis: item 8 — the runtime passes no delivery count, so the module counts its own; why max-deliveries is the existing condition to borrow.

Status stays located: the code is mesh-catalog PR #94, not merged. records.py, index.py, cycle.py pass.

Records the operator's decision for the two consumers issue 276 left for their own change: the audit logger and the usage store must retry a failed write and never lose an event. - Report: new section *The two consumers that took a failed write* — thrown write, spool from the first failure (declared valuable, ADR 0233), last delivery taken from the spool, background replay, idempotent writes (trail skips a written id; usage keeps the reading observed latest), and a bound past which the last delivery is not taken so the bus raises `max-deliveries` (no module-level standing exists; ADR 0224's is a provider's). What it does not cover, and how it is checked. `located-in` gains the two modules. - Diagnosis: item 8 — the runtime passes no delivery count, so the module counts its own; why `max-deliveries` is the existing condition to borrow. Status stays `located`: the code is mesh-catalog PR #94, not merged. `records.py`, `index.py`, `cycle.py` pass.

mesh-admin added 1 commit 2026-10-06 16:37:36 +00:00

Issue 276: the audit logger and the usage store retry, and lose no event 72fcdc366f

The operator decided the two consumers that took a failed write must retry and never lose an event: record how (a thrown write, a spool that takes the last delivery and replays, idempotent writes, a bound that borrows max-deliveries), and why the module counts its own deliveries.

mesh-admin merged commit 3f32462434 into main

2026-10-06 16:38:08 +00:00

mesh-admin deleted branch issues/276-the-audit-logger-and-usage-store-retry

2026-10-06 16:38:08 +00:00

mesh-admin commented

2026-10-06 23:07:10 +00:00

Delivery novox/hq@3f32462434ab — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

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

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/hq#145 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@3f32462434ab` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/hq#145 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin referenced this pull request

2026-10-08 22:13:12 +00:00

ADR 0268: the login shell's execute is withheld on the control-node until a call to it needs a person's approval #235

mesh-admin referenced this pull request

2026-10-09 01:13:50 +00:00

Issue 341: a merge check judges the pull request's head, not what merging it makes #242

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#145