From ee02a157953bea4412f0cd9e30f7fcb26025c5c6 Mon Sep 17 00:00:00 2001 From: tegwick Date: Sat, 3 Oct 2026 21:14:31 +0200 Subject: [PATCH] Refresh provisioning coaching packet with completed owner gates Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a1029c-c003-7283-acc9-930b434e6cae --- .../2026-10-03-provisioning-window/OPERATOR.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/batches/2026-10-03-provisioning-window/OPERATOR.md b/docs/batches/2026-10-03-provisioning-window/OPERATOR.md index abcb5a8..b86659b 100644 --- a/docs/batches/2026-10-03-provisioning-window/OPERATOR.md +++ b/docs/batches/2026-10-03-provisioning-window/OPERATOR.md @@ -1,5 +1,17 @@ # Provisioning-window sitting — operator packet (hub decision D1) +Current follow-up, 2026-10-03: p01 is accepted; receipt is +`docs/evidence/2026-10-03-provisioning-window-p01-acceptance.json`. +The exclusion analysis below describes the original draft, not current gates. +MASON-WP-0007-T05 subsequently completed its attended seed run. Core Hub's +credential provisioning and private publisher admission are also complete: +RAPPCOREHUB-WP-0003 finished after Helm revision 31, 123/123 repositories with +zero errors and `repo_manager_projection: ok`; owner receipt is +`rapp-core-hub/docs/evidence/2026-10-03-private-publisher-admission.json`. +Do not repeat those provisioning steps. Secrets-engine service login still +requires KeyCape live registration/protected client custody; CCR-2026-0018 +coordinated disablement and the broader D1 remain separate owner records. + Hub decision: `62aa95e4-3ccc-4867-8806-5e3db005b483` (D1, attended OpenBao provisioning window), routed by CUST-WP-0075. The founder approves through informed-decision, not with a raw hub resolve.