Design 47 H: H-A-380, the prune helper in a process, the keep's home, the tools' names
This commit is contained in:
@@ -2375,3 +2375,15 @@ Where two preparers disagreed, the chosen one is named.
|
||||
gain `install`: every pipeline ask ends in a step-ended naming its step, one way, and the archive object's name rides
|
||||
the install's end as §800 says. The contract part (mesh-contracts, regenerated) and the delivery SDK's check change
|
||||
together in the group; the Node build module's install answers it. P3.
|
||||
- **H-A-380 (the prune helper for a process, the keep's home, the tools' names, 00:08)** §812, S11. (1) A process's
|
||||
state write over the bus's key-value put answers a revision and no fill (the bundle side gets the Fill the runtime's
|
||||
put answer carries, DMC-14). The helper for a process reads the entry's figures once when it binds the state and once
|
||||
after each prune, and between those keeps a running sum of the bytes each write puts (an upper bound: the bucket's
|
||||
history bounds what an overwrite keeps); the sum passing `prune-mark` of the cap is the judgement. No read per
|
||||
write, no poll, no timer: H-A-227's "read it once", H-A-344 (7). (2) A keep lives in the pruned state itself, under
|
||||
the reserved prefix `.keep/<key>` with its until, never pruned and never counted as an entry by the readers; the
|
||||
prune reads the keeps once per prune and skips a key kept until a time still to come; the hand act is written in the
|
||||
hand-act log as §812 says (the audit trail, not the truth). Oldest first is by each key's current revision, lowest
|
||||
first. No new store per module (one store per thing, P3). (3) The tools are named as the generic tools are:
|
||||
`<module>_state_prune_now` and `<module>_state_keep` (stateobjects.Tools' form); §812's bare names are the tool
|
||||
kind. P3, P9, P-NATS-native.
|
||||
|
||||
Reference in New Issue
Block a user