From 922f7017b8f0c19963281ff24f1250bafd173e1e Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 03:49:56 +0100 Subject: [PATCH] Design 47 H: H-A-98, an old-form event is refused by each handler's strict decode Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index e3fb46cc..f8ec86e4 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -416,3 +416,7 @@ Where two preparers disagreed, the chosen one is named. from a scan of events), P3 (`since` is kept for the bound). The retired state `pending` was the pending revision of the manifest validation (ADR 0633 ยง1); this is not it. `indexer_take_in_pending` and `indexer_take_in_skip` are asks in the state `takeins`, the existing hand-act path. P7. +- **H-A-98 (runner developer, 03:50)** No shared follower exists, so in H1 each consumer's own handler refuses an + old-form event: the contract's strict decode (a required field such as `call` missing) is the refusal, the handler + writes one journal line naming the subject and ends the message. H-A-58's "shared follower" is read so for H1; a + shared shape, if any, is H4's with the wake-up rule. P3, P7.