Design 47 H: H-A-359 and H-A-360, a bundle takes once; a module-wide own secret's name and caller
This commit is contained in:
@@ -2241,3 +2241,12 @@ Where two preparers disagreed, the chosen one is named.
|
||||
setting drain-bound (default 30); the applier writes KillMode=mixed and a stop timeout of drain-bound plus 15 s
|
||||
for a process that carries it (the 15 s for the runner to stop its bundles after its drain); no process is
|
||||
special-cased by its id. P3, P9 (the declaration carries what the unit needs; the applier reads no settings).
|
||||
- **H-A-359 (a bundle takes an ask once too, 23:09)** A bundle's kept state has no create-if-absent, so a bundle holder
|
||||
(the forge module, in TypeScript) cannot take an ask once by its id. The tool runner gains the state act create
|
||||
(with a TTL), the SDK's bundle state gains TakeOnce with its TypeScript twin, the same shape as the process side
|
||||
(P9: one shape on every side); built in mesh-tools beside the ask-id copy, and in mesh-sdk. P9, ADR 0668 §2.
|
||||
- **H-A-360 (the name and the caller of a module-wide own secret, 23:09)** (1) Stored as module/<module>/<name>;
|
||||
own-put's second step answers that full name; get takes the full name. (2) It is answered to a process of the module
|
||||
(the caller's account <node>.<module>) and to a call the tool runner makes on that module's bundle's behalf, judged
|
||||
the way the vault already judges a bundle's own-secret read today (the module named in the call, not the runner's
|
||||
account); the developer reads that path and reuses it, never a second judgement. P12, P3.
|
||||
|
||||
Reference in New Issue
Block a user