Write the operator's 13:10 answer: a restore asked is done, identity being the one check
mesh/delivery closed: a newer head of the same pull request
mesh/check checking e164a6636261 on cbafc7556a40

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
This commit is contained in:
2026-11-11 13:08:53 +01:00
parent caa7a9265c
commit e164a66362
@@ -72,7 +72,8 @@ are written into the lines of G-12 they name.*
says the wait and the watchman's `delivery-waits` raises it. says the wait and the watchman's `delivery-waits` raises it.
- **Who calls it.** `snapshot-kept` and `restore-kept` are called by a node-engine holder (`seat:node-engine`): the - **Who calls it.** `snapshot-kept` and `restore-kept` are called by a node-engine holder (`seat:node-engine`): the
recovery module takes a call only from an account the bus proves to be a node-engine's, and the identity of who recovery module takes a call only from an account the bus proves to be a node-engine's, and the identity of who
asked is the check (the operator, 13:06 CET); no want is read for it. asked is the check (the operator, 13:06 CET), every act logged; no want is read for it, since the operator,
2026-11-11 13:10 CET: "if something asks for a restore, you should do it; he'll have his reasons".
`kept-points` takes the default of a read (§391). The operator, 2026-11-11 13:06 CET at lead-47's terminal: setting `kept-points` takes the default of a read (§391). The operator, 2026-11-11 13:06 CET at lead-47's terminal: setting
aside is a move, not a removal, so deleting the live objects once their aside is whole and checked (§516) needs aside is a move, not a removal, so deleting the live objects once their aside is whole and checked (§516) needs
no person's warrant, the data staying in the aside until `discard-aside`; `aside-only` is the operator's hand tool no person's warrant, the data staying in the aside until `discard-aside`; `aside-only` is the operator's hand tool