Issue 273 and ADR 0232: a binding to a consumer's data moves only by a person #137

2026-10-06T13:22:11Z

mesh-admin commented

2026-10-06 13:22:11 +00:00

What this adds

Issue 273 is the incident on 2026-10-05/06. Issue 258's seat rule was written for the resolver. It re-bound the home server's five database consumers to the store holding the seat on the control node. Each got an empty database there, and the applications ran on empty data for about 20 h with nothing warning. No data was lost.
- It also records a read-only check of the other machines: none of their consumers were moved.
- It lists what remains on the control node's store.
- Status is located, fixed by novox/mesh-controller PR #86.
ADR 0232 decides two things:
- An offer says whether it keeps its consumers' data. If unsaid, a provider that grants each consumer a credential keeps it.
- Issue 258's rule applies only where nothing is kept. A binding to data is recorded on send and kept against any resolution. Only a pin moves it.
- Every kept move, pinned move and unasked move is said, as a condition and by a self-check probe.
- The ADR extends ADR 0110.
Issue 258 gets a note pointing to its sequel, per playbook 03.
The ADR index is regenerated.

Checks

records.py, index.py and cycle.py all pass.

Public-repo rule

The text uses role names only: home server and control node. No machine or application names appear.

## What this adds - **Issue 273** is the incident on 2026-10-05/06. Issue 258's seat rule was written for the resolver. It re-bound the home server's five database consumers to the store holding the seat on the control node. Each got an empty database there, and the applications ran on empty data for about 20 h with nothing warning. No data was lost. - It also records a read-only check of the other machines: none of their consumers were moved. - It lists what remains on the control node's store. - Status is `located`, fixed by novox/mesh-controller PR #86. - **ADR 0232** decides two things: - An offer says whether it keeps its consumers' data. If unsaid, a provider that grants each consumer a credential keeps it. - Issue 258's rule applies only where nothing is kept. A binding to data is recorded on send and kept against any resolution. Only a pin moves it. - Every kept move, pinned move and unasked move is said, as a condition and by a self-check probe. - The ADR extends ADR 0110. - **Issue 258** gets a note pointing to its sequel, per playbook 03. - **The ADR index** is regenerated. ## Checks `records.py`, `index.py` and `cycle.py` all pass. ## Public-repo rule The text uses role names only: home server and control node. No machine or application names appear.

mesh-admin added 1 commit 2026-10-06 13:22:11 +00:00

Issue 273 and ADR 0232: a binding to a consumer's data moves only by a person 732a17e112

Issue 258's seat rule, written for the resolver, re-bound a machine's database consumers to the store
holding the seat elsewhere, where each was made an empty database, and nothing said so. Record the
incident, limit 258's rule to provisions that keep nothing, and decide that a binding to data is
kept and moved only by a pin.

mesh-admin merged commit f197fcf146 into main

2026-10-06 13:22:43 +00:00

mesh-admin deleted branch issues/273-a-rule-for-the-resolver-moved-a-machines-databases

2026-10-06 13:22:43 +00:00

mesh-admin commented

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

Delivery novox/hq@f197fcf1460e — 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#137 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@f197fcf1460e` — **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#137 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 09:30:36 +00:00

Issue 315: a failed unit of a module was never raised #199

mesh-admin referenced this pull request

2026-10-08 15:28:24 +00:00

Issue 332: the service manager could neither clear a failed unit nor say what wants it #222

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#137