Let a trusted file that names its keys hold only those keys at the terminal (hq issue 586, ADR 0329 §5)
mesh/merge-gate head 4c965e3cf6d5 merged into trunk 584ee991961c — fail: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; head 4…
mesh/repo-check head 4c965e3cf6d5 merged into trunk 584ee991961c — fail: head 4c965e3cf6d5 does not merge cleanly into trunk 584ee991961c: in conflict test…
mesh/delivery superseded: a newer head of the same pull request

A module with a trusted mergeable file had its whole layer refused through the
settings verb, because such a file took any key. Once a module's files name the
keys they take (ADR 0326), each file takes only those, so only a trusted file's
named keys are the terminal's: betterbird's tags, in a file nothing trusts, is set
through the verb, while its accounts and identities stay the terminal's or the
operator's warrant. A module whose files name no keys keeps the whole-layer rule.
This commit is contained in:
jochen
2026-10-13 02:16:15 +02:00
parent 4473bc7d73
commit 4c965e3cf6
4 changed files with 79 additions and 1 deletions
+1
View File
@@ -39,3 +39,4 @@
./internal/inventory TestAWalksRestIsReadFromEachMachinesOwnSend
./internal/inventory TestAStoredBuildWithASilentMergeableFileIsStillReadAndComposed
./cmd/mesh-controller TestPlanAndNodeListAnOptionalRequirementLeftUnbound
./cmd/mesh-controller TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb