Name ADR 0305's check clause and the late binder's hour in to-be 24 (issue 526)

03-DESIGN/01-to-be/24-the-secrets-vault.md

@@ -160,9 +160,9 @@ its caller, for the value sealed to a key made for that one call. The tool answe
 controller opens the value, seals it to every consumer pair that does not hold it yet, under one stamp of its
 fingerprint, and to the operator, and forgets it; a pair that already holds it is left as it is, so asking
 again restarts nothing. The provider asks when it starts, when the software's value changes, and hourly; a
-consumer that binds in between holds a value the mesh made until the next ask. A change is recorded in the
+consumer that binds in between holds a value the mesh made, which the software refuses, for at most the hour until the next ask. A change is recorded in the
 hand-act log as a decision, not a repair, and `rotate` of such a provision is refused. *How it is checked:*
-the tests ADR 0305 §12 names, in both repositories; the live row is `hand-acts` showing `secret issued` for
+the tests ADR 0305 §13 names, in both repositories; the live row is `hand-acts` showing `secret issued` for
 the media server's provision once both walks are done.
 
 ## Beyond generate and hold