0110 amends 0109: its seats are provisions, and moving npm takes a holdable seat

This commit is contained in:
jochen
2026-09-26 00:44:35 +02:00
parent e387c4bd0e
commit 0c5eac0218
@@ -163,6 +163,13 @@ On acceptance, each of these is amended by this record, not edited:
- [ADR 0084](0084-which-provider-serves-a-consumer.md): a requirement may name a seat, which its holder
answers; and where several providers remain and none is local, the choice is asked when the module is
assigned and recorded as a pin, rather than refused until someone pins it.
- [ADR 0109](0109-a-package-registry-seat-is-one-per-ecosystem.md): one provision per package
ecosystem stands. Where 0109 says *seat*, it means that provision. Only `npm-package-registry` is
also a seat in this set. A cargo or docker registry becomes one by a record, as any seat does.
"Gitea may hold several seats" reads: gitea may provide several ecosystems, and hold the seat of
each one that is a seat. Moving npm to verdaccio is not "assigning `npm-package-registry` to
verdaccio". It takes verdaccio's definition saying it can hold the seat, and then an assignment
holding it.
- [To-be 23](../03-DESIGN/01-to-be/23-choosing-a-provider.md): the same two changes, in the design
that describes choosing a provider.
- [To-be 21](../03-DESIGN/01-to-be/21-the-installation-in-full.md): genesis assigns the foundation's