Design 47 H: H-A-134 the indexer makes its own per-branch durables until H4b; H-A-135 old trunk revisions and current mark go

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-20 12:06:31 +01:00
parent 9f231e07a2
commit 73685d41b6
@@ -602,3 +602,16 @@ Where two preparers disagreed, the chosen one is named.
first views, so a bundle that never subscribes needs no follower (P7), and acknowledging before the bundle took the
event would lose the bundle's (P3). A lost event's picture catches up on the next one of its family; a re-ask on
that loss is a finding for H4. The machine's runtime keeps its own binding.
- **H-A-134 (the indexer makes its own per-branch durables, 12:08)** Met live: the grants part composes no per-branch
durable `<node>_<indexer>_<branch>` on the source-moved stream (H-A-30 named it the maker; the grants part's events
work is H4b), so the indexer never hears a source revision after its start and takes a merge in only at a restart.
Until H4b, the indexer makes that durable itself when its bind finds none, with the configuration the mesh gives a
module's seat-event consumer (mesh-sdk's SeatEventConsumerConfig, one message at a time, filtered to the branch), and
the grants part matches it as it matches a module's consumers. It is the indexer's own kept consumer (P12: a module
writes only its own); H-A-30 is read so. P1, P3.
- **H-A-135 (the earlier model's trunk revisions and current mark go at the first branch take-in, 12:08)** Met live:
the catalog-revisions object store keeps the earlier model's `trunk.<n>` objects and its `current` mark on the newest
of them beside the branch-keyed revisions (`main.1`), and the runner's first view hears "revision 528" while its
picture holds 1, forever behind. At a branch's take-in the indexer drops every `trunk.*` object no record pins and
the old `current` mark (the branch's newest revision is the current one, H §743); said in the journal, counted. The
stale readers' first views then agree. P3, P7.