109: a package registry seat is one per ecosystem, not one for all of them

Extends ADR 0075. Surfaced fixing builder's hand-faked package-registry binding tonight: gitea's manifest declares the provision once with a single npm-path, conflating what should be independently assignable per ecosystem (npm/cargo/docker/...) the same way artifact-store and package-registry were themselves split. Cited in 22-the-work-ahead.md's Phase 2, where the target state this decision points at was already described a week ago. Numbered 109, not 108: route-proxy's policy feature (mesh-controller PR #58, merged today) already cites 'novox/hq ADR 0108' six times for its own still-unwritten decision record — reserved but never committed. Renumbered around it rather than colliding.
2026-09-25 16:52:26 +02:00
parent 226d556743
commit c5edf636d8
3 changed files with 108 additions and 0 deletions
@@ -123,6 +123,7 @@ python3 00-META/checks/index.py            fail if stale
 - **0094** — [A module may hold several secrets from one provider, each a pair of its own](0094-a-module-may-hold-several-secrets-from-one-provider.md)
 - **0095** — [The control plane is the way to ask a module](0095-the-control-plane-is-the-way-to-ask-a-module.md)
 - **0098** — [A fact a provider makes at first start is fetched from it, not carried in its manifest](0098-a-fact-a-provider-makes-at-first-start-is-fetched-from-it.md)
+- **0109** — [A package registry seat is one per ecosystem, not one for all of them](0109-a-package-registry-seat-is-one-per-ecosystem.md)

 ### What runs on them, and how it gets there