From c403487aad47c3cd7463d35c1fc076b1204a94a5 Mon Sep 17 00:00:00 2001 From: codex Date: Fri, 11 Sep 2026 10:12:08 +0200 Subject: [PATCH] docs: record factory sender provisioning and delivery continuation --- ...-09-08-helixforge-factory-critical-path.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/docs/assessments/2026-09-08-helixforge-factory-critical-path.md b/docs/assessments/2026-09-08-helixforge-factory-critical-path.md index dd7a2e6..618ca4a 100644 --- a/docs/assessments/2026-09-08-helixforge-factory-critical-path.md +++ b/docs/assessments/2026-09-08-helixforge-factory-critical-path.md @@ -158,3 +158,29 @@ parity work; these repairs do not establish that automatic synchronization is fi [Live issuer and synchronization receipt](2026-09-08-helixforge-factory/live-upstream-issuer-continuation.json) records the proof, cleanup, source/Hub parity and progress IDs. + + +### 2026-09-11 retry: sender credentials provisioned + +The user requested another attended login attempt. It succeeded: CCR21/22 +created independent version-1 custody and advanced the shared sender registry +with CAS 7→8, preserving existing senders and fields. The seed wrapper exited 0 +and confirmed self-revocation for that session. This clears first provisioning +for Approval Engine and Informed Decision. + +Platform's delivery helper now pins the reviewed manifests and verifies native +reader/namespace restrictions, exact ESO projection and receiver-registry +equality before reload. Seven delivery tests and 18 custody tests pass, +including 11 actual disposable OpenBao cases. A fresh attended delivery login +then failed before command handoff (exit 5; remote revocation unconfirmed), so +no delivery or reload is claimed. RPF-WP-0035-T08 waits for delivery login and +AUDIT-WP-0009-T09/T11 retain real producer acceptance. Do not repeat the approved +CCRs or reseed their credentials. + +Factory attempts and paid calls remain zero. The immediate sequence remains +delivery/receiver proof, native approval and Informed Decision policy/service/ +human admission, exact credential delivery and runtime/spend admission, then +the single bounded reuse-surface worker attempt. CCR19's existing operator-group +question remains separate; the customer UI product remains vergabe-teilnahme. +The successful seed and failed delivery attempt are separate metadata receipts +in the platform, Audit Core and factory project evidence directories.