Design 47 H2: H-A-422, the forge's tokens through the vault, a name per mint

This commit is contained in:
2026-11-22 01:15:13 +01:00
parent 6de57ebb11
commit a5fa22a4b8
@@ -449,3 +449,11 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
still defines publish, publish-part, versions and remove (D4a removed nothing), so the node-engine invokes `versions`
as before (the node-engine at `mesh-host` b305a5f0 reverts 845de026). Only (1) stands, and the lesson: a validator run whose request does
not resolve the definitions' includes judges nothing.
- **H-A-422 (the forge's tokens: both accounts through the vault, a name per mint, 01:21)** §808, C4. (1) §808 covers both
the tools account's token and the packages account's: one way per secret. No token file: a plain file in the runtime
state is a state (§808's "never plain in a state"), so the minter writes only through own-put, and the forge module's
Go bundles read their token through the vault seat's `get` at start and at secret-changed (the Go SDK's seal opens
it), the MESH_GITEA_*_TOKEN_FILE words going; the map's "the token file is read only by the forge module's processes"
missed those two readers, and the Go side is C4's. (2) A name per mint, `<account>-<generation>`: the minter mints the
new token, writes it through own-put, and only then deletes the replaced token at the forge by its id, so no moment
is without a valid token; a mint that fails leaves the old one standing. P-mesh-owns-the-truth, P3, P-failure-loud.