Design 39 parts: the lead's answers D1 (the vault reading) and D2 (§17's wording)

2026-11-12 12:21:10 +01:00
parent ac294e7b86
commit 6141d7b5d1
1 changed files with 10 additions and 0 deletions
@@ -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.<key>.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.<key>.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).