Design 47 H: H-A-181, performed keeps the outcome; the act stays in the gate's stream

This commit is contained in:
2026-11-20 19:31:57 +01:00
parent d05384d696
commit 28a28283c6
@@ -951,3 +951,11 @@ Where two preparers disagreed, the chosen one is named.
with no holder placed, and none is placed now, it moves the module as H-A-177 says (without a point, the finding
raised), no operator's answer needed; where a holder is placed, the point is asked again once; a hold whose point
truly failed (a holder answered and failed) raises the operator's ask it was owed. P3, P7, ADR 0568 §4.
- **H-A-181 (`performed` keeps the outcome, the act stays in the gate's stream, 19:31)** Met at 18:58 (the
condition "kept data is filling up": 19,530 keys, 51 MB of the template's 64 MiB): the bridge keeps each owed event
whole in `performed` beside the outcome, at ten times the design's estimated rate. §163 stands as written: one key
per id with the outcome and when, nothing more; `bridge_owed_again` reads the act from the gate's stream `owed` on
its pull request's subject (`owed.<repository>.<number>`, the act's id from `performed`'s key), the gate's stream
being the one copy of the act (P12); no cap is raised (§163: the size its template fixes). `bridge_owed` answers
by pull request or id, never the whole state (P4). The rate itself (about 80 note acts per delivery record per pull
request) is a finding for H2 on the gate's acts. P7, P12, P4.