From fb09134ba47cba49b5a1bd199b24331e68126643 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 03:07:53 +0100 Subject: [PATCH] Design 47 H2: H-A-460, a record-too-large finding names its record --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index 382a4f6b..27ffa7a2 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -744,3 +744,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl record shown as the head's fields with a count of movers per outcome, never the movers' entries themselves; the whole record stays readable through gate_record (one entry per thing, P3), and a view act of any record fits 64 KiB, so GT1's whole step stands as written. P3, P-failure-loud. +- **H-A-460 (a record-too-large finding names its record as its subject, 04:35)** ยง809, H-A-455 (3). (b): the finding's + subject id is the record's instance, its id stays the refused entry; the record's end clears every held + record-too-large whose subject is that record, read from the gate's own findings state, so nothing is kept in process + memory and no finding is cleared for another record. P-failure-loud, P3.