novox/mesh-catalog
18
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mesh-vault: read which modules of a machine the vault judges handed, and why, with own_handed (issue 1966) #606

Merged
mesh-tools merged 1 commits from fix/handed-one-rule into main 2026-11-04 09:16:10 +00:00
Conversation 1 Commits 1 Files Changed 4
+111
1 Commits
Author SHA1 Message Date
jschoubben 237a534ca4 mesh-vault: read which modules of a machine the vault judges handed, and why, with own_handed (issue 1966)
mesh/delivery merged: source.main moved to novox/mesh-catalog@7a7db0166ad2
Details
mesh/delivery-group group fix/handed-one-rule merged: every member is merged
Details
mesh/check being carried to 237a534ca4d3 on 7a7db0166ad2 | from dd458cb155f5, mesh-host 4d47ff5ce743 
The vault leaves a handed module's own secrets out of `own`, judged by the plan in its assignment, and nothing read
that judgement: on 2026-11-04 the circle on ace (no plan, so not handed, so refused, so no plan) could be told only by
reading the provisioner's plans beside the node-engine's refusals. own_handed answers, per module the vault keeps an
own secret of on the machine or that is placed there, handed or not and why.

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig
 2026-11-04 02:29:37 +01:00