Fix what the records review found
The glossary's authority page still named the controller's seat the-controller in two entries, contradicting its own seat section after ADR 0079; issue 058's heading kept the pre-renumber 059; 055's fixed-by named branches that stop existing after merge (now merge commits/PRs) and its located-in listed file paths where the convention wants repos; 056's located-in named mesh-host, which received no fix, instead of mesh-catalog; and the design layer never said the one-store/one-broker property is enforced — 07-the-foundation and the installation table now state the seats. https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
This commit is contained in:
@@ -23,6 +23,12 @@ decisions:
|
||||
|
||||
# The foundation
|
||||
|
||||
**One store, one broker — enforced, not conventional.** Each foundation module claims a
|
||||
mesh-scoped seat named after its server (`mesh-store`, `mesh-broker`, `mesh-controller` —
|
||||
[ADR 0079](../../02-DECISIONS/0079-the-foundation-seats-are-named-after-their-servers.md)), so
|
||||
assigning a second holder anywhere in the mesh is refused at resolution rather than silently
|
||||
raising a second server.
|
||||
|
||||
Tier 1. Defined the same way [the controller](06-the-controller.md) is, because the same
|
||||
gap applied: the word was load-bearing and unpinned.
|
||||
|
||||
|
||||
@@ -129,8 +129,8 @@ two.
|
||||
|
||||
| # | module | provides | note |
|
||||
|---|---|---|---|
|
||||
| 1 | `postgres` | `postgres-database` | **the controller's own records and every module's.** One server, not two |
|
||||
| 2 | `lavinmq` | `amqp` | the broker every node dials, and what modules are granted vhosts on |
|
||||
| 1 | `postgres` | `postgres-database` | **the controller's own records and every module's.** One server, not two — it *claims* the mesh-scoped `mesh-store` seat, so a second is refused |
|
||||
| 2 | `lavinmq` | `amqp` | the broker every node dials, and what modules are granted vhosts on — *claims* `mesh-broker`, one per mesh |
|
||||
| 3 | `mesh-controller` | *claims* `mesh-controller` | decides what runs where |
|
||||
| 4 | `distribution` | `artifact-store` | what the mesh built, pinned by digest — the module is the software (Distribution), the provision is the job |
|
||||
| 5 | `builder` | — | turns source into artifacts |
|
||||
|
||||
Reference in New Issue
Block a user