From fe3b86d65f861c4d2bcb95a3ae85e9e82c56e177 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 23:31:45 +0100 Subject: [PATCH] Design 39 bus-and-switch: the lead's answer B25, the bindings verb answers the licence's key Claude-Session: https://claude.ai/code/session_01NcbgfHb9d4T9nq5Q6WqdiJ --- 03-DESIGN/01-to-be/39-milestones/bus-and-switch.md | 4 ++++ 1 file changed, 4 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 6b0d1e82..f863a31d 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 @@ -496,3 +496,7 @@ written; they are cited as "design 39 bus-and-switch B*n*". keys, the vault does not (P8). - **B24** (an equal generation in `licence-put`): with the same value it is unchanged; with a different value it is refused loudly as not newer (P3). +- **B25** (the vault matching a token's secret name to a binding it learned at start): the `bindings` verb answers + `key` beside the §3 fields, as `binding.changed` does (B7); the vault's `licence-bindings` keeps `licence`, `key` and + `generation`, and compares the secret's key with the binding's key. One form travels; the vault never computes §10's + key form (P1, P7).