novox/mesh-controller
8
0
Fork 0
Code Issues Pull Requests 8 Releases Wiki Activity
1,660 Commits 26 Branches 0 Tags
97a2d841c736c1d7d5420529f3356ba51d50f0dd
Commit Graph
2 Commits
Author SHA1 Message Date
mesh-tools 97a2d841c7 Land feature 57's controller work on its release branch 
The controller plans config, templates and moved providers' provisions,
hands bus accounts to the vault and judges the new manifest words, on the
feature's SDK and node-engine validator (feature 57, config and provisioning).
 2026-10-15 21:27:33 +00:00
mesh-adminandClaude Opus 5.5 c5fe7d4795 Stop a settings layer replacing what a provider serves (issue 696)
mesh/merge-gate head c5fe7d4795d7 merged into trunk dc36536e199e — pass: the change touches no module of the mesh's graph
Details
mesh/repo-check head c5fe7d4795d7 merged into trunk dc36536e199e — pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
mesh/delivery-group group pkg/57-f2b-served-keys delivered: every member is delivered
Details 
What a provider serves is its definition's (ADR 0348 clause 11): a layer
fills only the keys it asks for as ${setting:<key>}. Settle replaced any
served key a layer named, so a setting for one of a provider's files could
change what every consumer was told. influxdb on ace was the one live layer
relying on it and now serves its settings (mesh-catalog, merged first), so
grafana's data source composes byte for byte as before. UnusedSettings no
longer counts a literal served key as a place a setting lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-14 05:03:08 +00:00