Design 47 H: H-A-385, the gate ledger's head and mover entries

This commit is contained in:
2026-11-22 00:08:02 +01:00
parent 48cff82289
commit cc556c857a
@@ -2428,3 +2428,12 @@ Where two preparers disagreed, the chosen one is named.
P-mesh-owns-the-truth.
- **H-A-379 (addendum, 00:24)** The install ask carries no artifact or fingerprint, so the delivery SDK's check takes an
install's end without them, naming module, commit and the archive (mesh-delivery 1767d7b4).
- **H-A-385 (the gate's ledger entries: what each keeps, 00:34)** §809, GT1. (1) The head entry `<branch>.<source>`
keeps every field about the record as a whole: group, trace, acts, away, recovery, call, the pull requests' heads,
with its outcome, the movers' count and §810's times; nothing per module. (2) A mover entry
`<branch>.<source>.<module>` keeps that module's step outcomes per node (taken-in, built, checked, composed, wanted,
running-healthy, held, failed, away, each with why and event id) beside its pipeline, version, machines and running
times: §809 forbids an entry naming two modules, not a module's own detail, and delivery_status and show read them
there; the 64 KiB cap holds per entry. (3) The catalog half, when it moves, is a mover with an entry of its own
(`<branch>.<source>.mesh-catalog`, no node) and counts in the head's movers. (4) The month list (type held) stays
the way the ledger is listed; nothing changes it. One way per thing, P3; ADR 0595 §3.