The process reads its broker account, answers the seat mesh-recovery's verbs itself with the caller the bus proved, takes and restores streams through mesh-sdk's bussnap, keeps the digests in its state, names a kept data's bus objects from its catalog entry as mesh-sdk names them, learns the fingerprint a module runs at from the node-engine seat's running and the bus module's dumps from the backup holders' item events, each read whole at its start, and asks the backup holder on its node to bring the points directory back. A restore whose restore-started the bus did not acknowledge reads and sets aside nothing. Builds: design 47 G §554, §516, §551, §556, §563, §567, §655, A-107, A-112, A-121, A-123, A-126, A-132 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
mesh-recovery
Holds the seat mesh-recovery (design 47 G §554): the recovery module takes, sets aside and restores a module's kept
data on the live bus, one act at a time, each act in the hand-act log, its result said as an event under the act's id.
Go: one process (cmd/mesh-recovery) that answers the seat's verbs itself (A-107, A-115) and a tools bundle
(cmd/mesh-recovery-tools) whose recovery_* tools call those verbs and hold no grant of their own (§656).
Its data item points holds the restore points and the asides; the digests of the points are on the bus in its state
digests (§567). Its settings are points-cap, points-filling-mark, point-keep-days and dump-wait-minutes.