novox/mesh-controller

Archived

57/V2: The controller's secret verbs go to the vault for a module filled the new way (issue 675) #337

Closed

mesh-admin wants to merge 4 commits from pkg/57-v2-vault-verbs into feat/57-config-and-provisioning

Author	SHA1	Message	Date
mesh-adminandClaude Opus 5.5	65531d7375	Prove the vault's path of each secret verb, and today's for a module filled the old way (issue 675) mesh/delivery-group group pkg/57-v2-vault-verbs rejected: a member's own check failed Details mesh/merge-gate head 65531d737514 merged into trunk fcdecb436117 — pass: [release feat/57-config-and-provisioning, judged by its controller 39cc132d5d0f] t… Details mesh/repo-check head 65531d737514 merged into trunk fcdecb436117 — fail: [release feat/57-config-and-provisioning, judged by its controller 39cc132d5d0f] i… Details mesh/delivery stopped: the pull request closed unmerged Details Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 19:09:05 +00:00
mesh-adminandClaude Opus 5.5	698657176d	Carry a value into the vault sealed to its call, and prove both paths of the switch (issue 675) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 19:07:54 +00:00
mesh-adminandClaude Opus 5.5	234dea9d29	Promise the vault's intake verbs and let the controller ask them in its own name (issue 675) The vault takes a value only from the controller, which it knows from the subject that names its caller. The grant is composed from the records, as the issued tools' is, so the installer's first user list is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 19:07:04 +00:00
mesh-adminandClaude Opus 5.5	8a428e3e86	Send secret verbs to the vault for a module filled the new way (issue 675) ADR 0349 clauses 8 to 10 make accept, secret-ask, issued and rotate the vault's. A module still filled the old way gets its secrets only from the declaration the controller seals, so forwarding its verbs would report success and change nothing on its machine: the switch sends a module's verbs to the vault only once its secrets are filled the new way, and is off for every module until V4. What the controller carries it cannot open: the vault makes a key for each call; the terminal seals an accepted value to it, and the desk's prompt and a provider's tool seal theirs to it. The vault's seat promises the four verbs, optional until the vault that runs serves them, and the controller asks them in its own name, granted from the records as the issued tools are, so the installer's first user list is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 19:06:04 +00:00