novox/hq
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

Browse Source 
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
still-unwritten decision record — reserved but never committed. Renumbered
around it rather than colliding.
This commit is contained in:
jschoubben
2026-09-25 20:29:22 +02:00
committed by jochen
parent 56669ee23b
commit 59c93dcfe4
3 changed files with 108 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
02-DECISIONS/README.md
+1
View File
@@ -124,6 +124,7 @@ python3 00-META/checks/index.py fail if stale
- **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)
- **0108** — [A route carries the policy applied to a request, and names a secret rather than holding one](0108-a-route-carries-the-policy-applied-to-a-request.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