coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record completed P04 recovery rollout and acceptance
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a092fe-13b1-7f12-ac74-7d258af4d79c
This commit is contained in:
codex 2026-09-13 21:19:13 +02:00
parent 9575b51d6e
commit a704a72b6e
1 changed files with 15 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/keycape-factor-recovery.md
View file

@ -1,4 +1,18 @@
# Attended lost-factor recovery
# Supported platform lost-factor recovery
Routine P04 recovery is now available at
https://users.coulomb.social/platform/factor-recovery. Sign in with recent MFA as
a platform operator. The private provider service verifies that signed identity;
no OpenBao login or provider credential handoff is required. Use the page to
preview an exact login/factor, confirm identity verification and shared scope,
apply recovery, and look up the audit result by support reference.
Release evidence: user-engine/docs/evidence/2026-09-13-p04-recovery.md.
The OpenBao/Kubernetes CLI described below is a historical implementation step,
not the supported routine P04 path. Its unperformed native acceptance was
cancelled when the signed-session service replaced it (KEY-WP-0036-T02).
# Historical attended owner procedure
Implementation tracked by KEY-WP-0036 and USER-WP-0030-T03. Provider-local
recovery passes isolated tests; the attended production wrapper and portal