mesh-controller

4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	499ff5c218	Move the route proxy into its module and run it from the trust image, on mesh-sdk's public membership (issues 1633, 1634, 1635) mesh/repo-check out of date: judged beside mesh-catalog#434 at c948f3a61c74, it is now at 7451e7edf4e5; judged again on a recheck or when it is merged Details mesh/merge-gate group feat/r4d: composed again for the group's new heads Details mesh/delivery superseded: a newer head of the same pull request Details mesh/delivery-group group feat/r4d rejected: a member's own check failed Details mesh/check failed: unit: i3/cmd/i3-tools.TestTheMainFileAndEveryModulesContributionLoadTogether: manifest_test.go:247: expected the launcher, clipboar… A bundle is built only from its module's directory (ADR 0480 clause 4), so the proxy leaves examples/ and the controller's internal/broker; the broker keeps no second copy of what the proxy shares with mesh-sdk. The image and its Dockerfile go, and a test holds that only build-agent declares one (clause 11).	2026-10-22 09:53:56 +02:00
jochen	9372e80cec	Serve a trusted holder from a runtime of its own account, refuse it in the machine's runtime, and say while an agent can become root where it runs (hq ADR 0259 §8)	2026-10-09 13:48:56 +02:00
jochen	c9be75b13e	Carry a channel's capabilities on its claim and tell the router every kind, so an answer is judged by the controller's record and not the channel's word	2026-10-09 13:48:56 +02:00
jochen	f5f315cc95	Grant a seat's traffic by caller and by kind, so an ask's asker and a channel's kind are facts the bus enforces (hq ADR 0259)	2026-10-09 13:48:56 +02:00