From 6141d7b5d1776a5f8d94c11b8a150036ae840e05 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 12:21:10 +0100 Subject: [PATCH] =?UTF-8?q?Design=2039=20parts:=20the=20lead's=20answers?= =?UTF-8?q?=20D1=20(the=20vault=20reading)=20and=20D2=20(=C2=A717's=20word?= =?UTF-8?q?ing)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 03-DESIGN/01-to-be/39-milestones/parts.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/03-DESIGN/01-to-be/39-milestones/parts.md b/03-DESIGN/01-to-be/39-milestones/parts.md index 3714011f..73e61e0b 100644 --- a/03-DESIGN/01-to-be/39-milestones/parts.md +++ b/03-DESIGN/01-to-be/39-milestones/parts.md @@ -214,3 +214,13 @@ main file and the glossary. No other module changes: every verb, event and provi - after the delivery the provisioner holds both retiring asks, and after the operator's call the database is gone (§13, §14); - the state directory holds none of the database's files (§15). + +## The lead's answers + +- **D1** (§12's vault reading, review round 1: no vault tool lists licence secrets, so `secret_holders` cannot show + `licence..grant` and `.access`): the reading that proves bus-and-switch §20's condition is, for every licence + `licences` answers, a rotation after the carry-over with no failure (`rotatedAt` later than `carried.postgres.at`, + `failures` 0), since a rotation reads the grant from the vault and puts both secrets back; and the vault's journal + handing `licence..access` to a bound node. Both go in the milestone file before the push (P3, P7). +- **D2** (§17's wording): the manager calls `seat:mesh-config.config` no more; the tools bundle does (§3). `invokes` + is the module's, so the manifest is unchanged (P8).