Recovery of the registry delivery (issue 1966), the operator's bootstrap of 2026-11-07.
The registry milestone renamed what distribution offers (ADR 0632 section 3). The node-engine running on every node predates it and finds the store through the provision artifact-store, so it can fetch no new build, its own successor included, and keeps running what it ran. ADR 0632 section 2's hold, which should have kept the old name while engines read it the old way, lives in the new indexer, which the running one predates.
This offers artifact-store again (provides and serves on 5000, byte-equal to the manifest before the milestone) beside distribution's new roles: against ADR 0632 section 3 for a limited time, at the operator's word, no new record. Removed in the next change to distribution once every node-engine runs the milestone's build.
Quick vs thorough: quick, this one manifest; the thorough fix is the tier order of milestone 47/G (issue 1921 note 80), which delivers the node-engine before a role it reads is renamed.
Checked locally: checks/manifests, readable, credentialform, requiredmodules pass; the reviewer ran the manifest validator at mesh-sdk 396511b7 on trunk and change (144 modules, 0 refused) and confirmed the old node-engine reads Serves[artifact-store] again.
Reviewed-by: mesh-code-reviewer@shanks at 80b8002a94 (one finding, ADR 0632 section 3 named, done in this message)
Recovery of the registry delivery (issue 1966), the operator's bootstrap of 2026-11-07.
The registry milestone renamed what distribution offers (ADR 0632 section 3). The node-engine running on every node predates it and finds the store through the provision artifact-store, so it can fetch no new build, its own successor included, and keeps running what it ran. ADR 0632 section 2's hold, which should have kept the old name while engines read it the old way, lives in the new indexer, which the running one predates.
This offers artifact-store again (provides and serves on 5000, byte-equal to the manifest before the milestone) beside distribution's new roles: against ADR 0632 section 3 for a limited time, at the operator's word, no new record. Removed in the next change to distribution once every node-engine runs the milestone's build.
Quick vs thorough: quick, this one manifest; the thorough fix is the tier order of milestone 47/G (issue 1921 note 80), which delivers the node-engine before a role it reads is renamed.
Checked locally: checks/manifests, readable, credentialform, requiredmodules pass; the reviewer ran the manifest validator at mesh-sdk 396511b7 on trunk and change (144 modules, 0 refused) and confirmed the old node-engine reads Serves[artifact-store] again.
Reviewed-by: mesh-code-reviewer@shanks at 80b8002a94f78fa8d2fc95fa8372f4f1191f5890 (one finding, ADR 0632 section 3 named, done in this message)
https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
The registry milestone renamed what distribution offers (container-image-registry, oci-artifact-registry,
mesh-artifact-store), as ADR 0632 section 3 decides. The node-engines running on every node are the ones
from before it: they find the store through the provision artifact-store, so they fetch no new build,
including their own successor, and keep running what they ran. ADR 0632 section 2's guarantee (no node loses
the store while its engine reads it the old way) lives in the new indexer's hold, which the running indexer
predates. So this goes against ADR 0632 section 3 for a limited time, at the operator's word (bootstrap of
2026-11-07, no new record): offered again beside the new roles until every node-engine runs the registry
milestone's build, then removed in the next change to distribution.
Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
Deliverynovox/mesh-catalog@80b8002a94f7 — merged since 2026-11-07T17:46:41Z
Source — source.main moved to novox/mesh-catalog@bac7f503f0. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
Transitions
2026-11-07 16:03 (new) → proposed (announced): novox/mesh-catalog#625's head announced
2026-11-07 16:03 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-07 17:46 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@80b8002a94f7` — **merged** since 2026-11-07T17:46:41Z
**Source** — source.main moved to novox/mesh-catalog@bac7f503f0ae. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Transitions**
- 2026-11-07 16:03 (new) → proposed (announced): novox/mesh-catalog#625's head announced
- 2026-11-07 16:03 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
- 2026-11-07 17:46 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `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.
Recovery of the registry delivery (issue 1966), the operator's bootstrap of 2026-11-07.
The registry milestone renamed what distribution offers (ADR 0632 section 3). The node-engine running on every node predates it and finds the store through the provision artifact-store, so it can fetch no new build, its own successor included, and keeps running what it ran. ADR 0632 section 2's hold, which should have kept the old name while engines read it the old way, lives in the new indexer, which the running one predates.
This offers artifact-store again (provides and serves on 5000, byte-equal to the manifest before the milestone) beside distribution's new roles: against ADR 0632 section 3 for a limited time, at the operator's word, no new record. Removed in the next change to distribution once every node-engine runs the milestone's build.
Quick vs thorough: quick, this one manifest; the thorough fix is the tier order of milestone 47/G (issue 1921 note 80), which delivers the node-engine before a role it reads is renamed.
Checked locally: checks/manifests, readable, credentialform, requiredmodules pass; the reviewer ran the manifest validator at mesh-sdk 396511b7 on trunk and change (144 modules, 0 refused) and confirmed the old node-engine reads Serves[artifact-store] again.
Reviewed-by: mesh-code-reviewer@shanks at
80b8002a94(one finding, ADR 0632 section 3 named, done in this message)https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
Delivery
novox/mesh-catalog@80b8002a94f7— merged since 2026-11-07T17:46:41ZSource — source.main moved to novox/mesh-catalog@bac7f503f0. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.