Research 031: a core that cannot fail silently #125

2026-10-06T00:10:05Z

mesh-admin commented

2026-10-06 00:10:05 +00:00

Opens research 031 for the operator's mandate of 2026-10-06: races, ignored commands, no feedback, no monitoring. The core has to be fully diagnosable, monitor and heal itself, and upgrade itself.

01-evidence: 48 core issues, mostly 175–267 plus 179, classified by class of failure rather than by component. For each: how long until it was noticed, and how. All 48 were noticed because a person or an agent looked. The mesh raised none of them on its own. Four faults came back after a fix (200→265, 230→264, 257→261→267, 175→184→248).
02-principles: nine principles, each listing what exists, what is missing and how it is checked: one writer; ordered and stale refused; acknowledged with a durable outcome; nothing dropped silently; a watchdog for every signal; continuous self-check sent outward; known failures heal under a brake; staged core upgrades with rollback; checks fed the real mesh's facts. It also lists the candidates that were not kept, with reasons.
03-mechanisms-and-roadmap: mechanisms M1–M9 and phases 0–5, ordered by how much risk each removes, each with its own done-when. It ends with the five largest risks today.

This is not graduated, and no ADR is written: the operator reviews it first. records.py, index.py and cycle.py pass.

Do not merge without operator approval.

Opens research 031 for the operator's mandate of 2026-10-06: races, ignored commands, no feedback, no monitoring. The core has to be fully diagnosable, monitor and heal itself, and upgrade itself. - **01-evidence**: 48 core issues, mostly 175–267 plus 179, classified by class of failure rather than by component. For each: how long until it was noticed, and how. All 48 were noticed because a person or an agent looked. The mesh raised none of them on its own. Four faults came back after a fix (200→265, 230→264, 257→261→267, 175→184→248). - **02-principles**: nine principles, each listing what exists, what is missing and how it is checked: one writer; ordered and stale refused; acknowledged with a durable outcome; nothing dropped silently; a watchdog for every signal; continuous self-check sent outward; known failures heal under a brake; staged core upgrades with rollback; checks fed the real mesh's facts. It also lists the candidates that were not kept, with reasons. - **03-mechanisms-and-roadmap**: mechanisms M1–M9 and phases 0–5, ordered by how much risk each removes, each with its own done-when. It ends with the five largest risks today. This is not graduated, and no ADR is written: the operator reviews it first. records.py, index.py and cycle.py pass. Do not merge without operator approval.

mesh-admin added 1 commit 2026-10-06 00:10:05 +00:00

Research 031: open the effort on a core that cannot fail silently 97ff655e34

The operator's mandate: races, ignored commands and silence keep recurring.
Classifies 48 recent issues by class, proposes nine checkable principles and
a phased roadmap, for review before anything graduates.

jschoubben added 1 commit 2026-10-06 00:31:23 +00:00

Research 031 graduates: ADR 0227 and to-be 45 0f163a3e7c

The operator approved the conclusion: the core must say when it is wrong
instead of waiting to be looked at. Record the nine rules with their
checks, and specify the parts and the six phases a build can take.

mesh-admin merged commit 213dcbafe9 into main

2026-10-06 00:32:16 +00:00

mesh-admin deleted branch research/031-a-core-that-cannot-fail-silently

2026-10-06 00:32:16 +00:00

mesh-admin commented

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

Delivery novox/hq@213dcbafe909 — 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#125 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@213dcbafe909` — **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#125 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 10:04:57 +00:00

ADR 0252: a module puts an account in a group, and the mesh says when a new login is needed #201

mesh-admin referenced this pull request

2026-10-08 11:24:01 +00:00

Issues 316-319: holds that never lift, holds walked past, and one module's wait stalling every walk #202

jschoubben referenced this issue from a commit

2026-10-09 14:53:59 +00:00

Issue 351: a held delivery whose module a backlog walk carried to every machine is never covered

mesh-admin referenced this pull request

2026-10-09 14:54:08 +00:00

Issue 351: a held delivery whose module a backlog walk carried to every machine is never covered #251