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

Close recovery acceptance and reconcile blocked workplans
Some checks are pending
CI Smoke / host-smoke (push) Waiting to run
Details
CI Smoke / container-smoke (push) Waiting to run
Details
Account journey acceptance / journeys (push) Successful in 10s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e38e-e5bb-7b50-968d-a738a0294997
This commit is contained in:
tegwick 2026-09-27 17:54:47 +02:00
parent b73f553c18
commit eca7c54748
9 changed files with 162 additions and 46 deletions
Download patch file Download diff file Expand all files Collapse all files

26
workplans/USER-WP-0027-account-journey-clarity.md
View file

@ -4,12 +4,12 @@ type: workplan
title: "Clear account state and complete user, tenant-admin and platform-admin journeys"
domain: communication
repo: user-engine
status: active
status: blocked
flavor: implementation
owner: codex
topic_slug: communication
created: "2026-09-13"
updated: "2026-09-22"
updated: "2026-09-27"
state_hub_workstream_id: "455300ca-ec1e-569e-a584-a8dcda2595cf"
---
@ -76,6 +76,18 @@ recovery and fresh login; resolve privileged portal policy. Only then configure
USER_ENGINE_MFA_MANAGEMENT_URL and accept U05–U08/P04–P06. Do not fake a status from
assurance claims, redirect return parameters or manual step completion.
2026-09-27: the missing credential/policy blocker above is superseded.
KEY-WP-0035 finished on September 14; RPF-WP-0040 delivered the renewable
factor-reader lane. NK-WP-0033 closed its separate historical incident on
September 23. P04 recovery and P06 optional policy are implemented and deployed;
see `docs/evidence/2026-09-13-p04-recovery.md` and
`docs/evidence/2026-09-13-p06-authentication-policy.md`.
Installed-provider fixtures prove activation, cancellation, old-session MFA and
recovery/replacement; they do not prove a real invited person's full OTP journey.
Remaining gate: attended U05–U08 enrollment/cancel/replacement/lost-factor and
fresh-login acceptance, plus verified portal setup handoff configuration. No new
credential request is required to resolve the historical blocker.
## Close tenant and platform administrator usability gaps
```task
@ -103,7 +115,7 @@ It does not accept those journeys.
```task
id: USER-WP-0027-T06
status: progress
status: wait
priority: high
state_hub_task_id: "550886ca-f916-5637-9639-b4134b0da939"
```
@ -120,3 +132,11 @@ USER-WP-0030 (platform admin), and USER-WP-0031 (automated acceptance). These
are live workplans, not residuals parked only in the journey document.
Implemented admin journeys and automated suites are deployed; see docs/evidence/2026-09-13-journey-release.md and its machine-readable report. Full acceptance remains incomplete for the named integration/provider gaps.
2026-09-27: blocked on the remaining acceptance dependencies, not ongoing
local implementation. USER-WP-0026-T02 now closes account-switch verification.
USER-WP-0035-T02 retains setup-link delivery; USER-WP-0028-T03 retains actual
OTP journeys; USER-WP-0026-T03/USER-WP-0028-T02 retain authoritative workload
access. VERGABE-WP-0019-T06 still needs the second user and setup-to-workflow
acceptance. Automated coverage remains an implementation check, not full live
acceptance. See `docs/evidence/2026-09-27-loose-ends-review.md`.