Issue 179: dated "Recurred, 2026-10-05" (database moved, old admin password back, ~31,000 silent failures, fixed by hand ~23:55 the same way) and the safety nets as the fix; status located with fixed-by mesh-controller #70, mesh-host #28, mesh-catalog #80 — flip to resolved once merged and rolled out.
ADR 0224 (next free across main and branches): a provider announces a consumer it has failed for 5 min (provisioner.failing/recovered, permission derived for every provider), the controller keeps it and status/node show name it, breaking all-well; where a known cause is safely repairable the module repairs it (keycloak admin). With a how-it-is-checked table.
To-be 19 (module protocol), provisioning: amended with the rule and its check.
Checks: records.py, index.py (regenerated), cycle.py all pass.
- Issue 179: dated "Recurred, 2026-10-05" (database moved, old admin password back, ~31,000 silent failures, fixed by hand ~23:55 the same way) and the safety nets as the fix; status `located` with fixed-by mesh-controller #70, mesh-host #28, mesh-catalog #80 — flip to resolved once merged and rolled out.
- ADR 0224 (next free across main and branches): a provider announces a consumer it has failed for 5 min (`provisioner.failing`/`recovered`, permission derived for every provider), the controller keeps it and `status`/`node show` name it, breaking all-well; where a known cause is safely repairable the module repairs it (keycloak admin). With a how-it-is-checked table.
- To-be 19 (module protocol), provisioning: amended with the rule and its check.
Checks: records.py, index.py (regenerated), cycle.py all pass.
The identity provider's admin lost the mesh's password again when its database
moved, and 31,000 silent failures followed. Record the recurrence, the rule
that makes a failing provider visible in status, and the module's self-repair.
Deliverynovox/hq@88f7f79fbb36 — 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#119 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-delivery:view -->
**Delivery** `novox/hq@88f7f79fbb36` — **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#119 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`.
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.
locatedwith fixed-by mesh-controller #70, mesh-host #28, mesh-catalog #80 — flip to resolved once merged and rolled out.provisioner.failing/recovered, permission derived for every provider), the controller keeps it andstatus/node showname it, breaking all-well; where a known cause is safely repairable the module repairs it (keycloak admin). With a how-it-is-checked table.Checks: records.py, index.py (regenerated), cycle.py all pass.
Delivery
novox/hq@88f7f79fbb36— held since 2026-10-06T23:05:28ZHeld for a person: merged without a passing check: only a person decides that it goes on —
mesh-delivery.releasewith why lets it go on.Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.