From 39314c18b611351294a8cf2cf26a3c938425d12d Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 21 Oct 2026 21:10:22 +0200 Subject: [PATCH] chore(workplans): record founder decisions 18731e84 (approve) and 9f9d0d88 (A); 4fab263d deferred Co-Authored-By: Claude Opus 5.5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 17890@bnt-lap001 Assistant-Session: 7d96d43c-0154-4a22-af71-71c349ac6dc3 --- ...S-WP-0014-pdp-transport-and-responder-authentication.md | 7 +++++++ .../SECRETS-WP-0015-original-keycape-recovery-selector.md | 7 +++++++ 2 files changed, 14 insertions(+) diff --git a/workplans/SECRETS-WP-0014-pdp-transport-and-responder-authentication.md b/workplans/SECRETS-WP-0014-pdp-transport-and-responder-authentication.md index 4629a3a..aab22e8 100644 --- a/workplans/SECRETS-WP-0014-pdp-transport-and-responder-authentication.md +++ b/workplans/SECRETS-WP-0014-pdp-transport-and-responder-authentication.md @@ -148,6 +148,13 @@ Access's trust-file projection matches `decision_signature.load_trust`: the same keys, 32-byte base64url keys, and the same namespace. Its pin is access-engine `docs/native-signer-public-pin.json`. No format work remains here. +2026-10-21 founder decisions: +- Step 1 is done. The founder resolved 18731e84 as APPROVE for the CCR-2026-0050 scope; + execution also requires railiance-cluster's cluster-runtime-storage-owner review. +- The founder deferred step 3 (4fab263d) until Platform reports verified custody. +- Owners notified: railiance-platform, access-engine and railiance-cluster. +- Next gate: that storage review, then Platform's attended CAS0 creation. + ## Verify the admitted native consumer and rotation path ```task diff --git a/workplans/SECRETS-WP-0015-original-keycape-recovery-selector.md b/workplans/SECRETS-WP-0015-original-keycape-recovery-selector.md index 1f25d6f..fd98809 100644 --- a/workplans/SECRETS-WP-0015-original-keycape-recovery-selector.md +++ b/workplans/SECRETS-WP-0015-original-keycape-recovery-selector.md @@ -168,3 +168,10 @@ secrets15-nk49-readiness in the packet; do not strand the wait or invent a drive NK49-T40 carries the founder signature after T33. There is no pin drift: 0f44fbe..0aeb5a2 changed only this workplan, and the selector, service_auth.py and check tool hashes are unchanged. Do not edit those files before the attempt, because any edit forces an NK49 re-pin. + +2026-10-21: the founder resolved 9f9d0d88 as A. kc-tls is recovered by ACME +letsencrypt-prod reissue, chained to ISRG Root X1, with no self-signed substitute. +NK49 should rehearse on LE staging first. T33 no longer needs original kc-tls key +custody. net-kingdom and railiance-cluster were notified; railiance-cluster was asked +to re-scope RCLUSTER-WP-0018-T02 to the outage prerequisites. Remaining for T33: +the T35 metadata and the NK49 attempt assembly (deadline, receipt location, verifier).