Design 47 H: H-A-344, H2's part after the second look

This commit is contained in:
2026-11-21 22:16:02 +01:00
parent 47515b8730
commit fbd39168f4
@@ -2124,3 +2124,20 @@ Where two preparers disagreed, the chosen one is named.
the seat's events family, so a wait by seat and event name is answered and nobody polls; the same for the builder's
and the indexer's events (ask-taken, version-reserved, H-A-338 (4)). Its check: the seat list carries the family;
mesh_wait on each name is answered in the whole-module test. P-NATS-native, map-onto-how-the-mesh-is-built.
- **H-A-344 (H2's part after the second look, 22:16)** (1) taken, unfinished, token-lease and every state whose
deleter the stores table names other than the prune are never pruned; such a store refuses when full, said in the
owner's journal. (2) A process refused at the forge first reads the vault's token; it takes the lease and mints only
when the refused token is the vault's current one (unit test: two processes, one holding the old token, mint one
token in all). (3) A foundation part (ADR 0619 §1, ADR 0666 §4) declares each of its stores (unfinished, publishes,
taken, dry-runs, the findings stream) in its old section with the same cap and life (H-A-229); every other owner
asks for it in requires by its template; so in the stores table and in §783. (4) assigner_keep_now (why) runs the
keeping of the assignment graph's revisions at once, written in the hand-act log; its row in the tools table.
(5) The findings stream: events template, max-bytes 8 MiB, max-age 7 days, in the stores table. (6) An ask untaken
past ask-unanswered-bound from asked-at ends could-not-run, naming the seat's holder as not taking (unit, runner),
never a slot held without end. (7) The fill is judged from the figures the write's own answer gives, no extra read.
(8) outputs and the install archives are deleted by the objects store's own max-age of 7 days (the bus deletes),
no sweep; the build module that keeps them is their owner (the line holds over H-A-341 (7)). (9) §799's third-run
why is fetch: <words> or publish: <words>, whichever met the fault; the kit's test expects publish: for the publish
case. (10) The forge module writes its token through the vault seat's own verb (named in §808), never into another
module's store (ADR 0596). The main file's and the H file's sizes stay with the reshaping run. P3, P12,
P-NATS-native, tools-are-how-a-module-is-spoken-to.