From 87f86772f60fed4e03803f5b7bd4d7b4d6b596d3 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 00:57:58 +0100 Subject: [PATCH] Design 39 bus-and-switch: the lead's answer B43, a first view keeps a binding an event wrote after it was asked Claude-Session: https://claude.ai/code/session_01NcbgfHb9d4T9nq5Q6WqdiJ --- 03-DESIGN/01-to-be/39-milestones/bus-and-switch.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/03-DESIGN/01-to-be/39-milestones/bus-and-switch.md b/03-DESIGN/01-to-be/39-milestones/bus-and-switch.md index 3de391f7..1b77b45c 100644 --- a/03-DESIGN/01-to-be/39-milestones/bus-and-switch.md +++ b/03-DESIGN/01-to-be/39-milestones/bus-and-switch.md @@ -530,3 +530,5 @@ written; they are cited as "design 39 bus-and-switch B*n*". - **B42** (which first view `vault_first_view_again` asks again): a new argument `of` names the view by its owner's state (`mesh-delivery-assigner.assignments` or `claude-licence-manager.bindings`); absent, both are asked again, as the tool did before for its one view (P4). +- **B43** (B32 for a consumer absent from the first view): a `licence-bindings` key written by an event after the first + view was asked is kept; only a key written before it was asked, and absent from the view, is removed (P3). -- 2.54.0