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

Record deployed P06 policy and completed platform acceptance
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Account journey acceptance / journeys (push) Successful in 6s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a09cbb-87c6-7900-a145-4ce53ba9f1a6
This commit is contained in:
tegwick 2026-09-14 00:10:24 +02:00
parent baf7467613
commit 8d525d959e
8 changed files with 280 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

23
docs/platform-admin-acceptance.md
View file

@ -1,7 +1,7 @@
# Platform administrator acceptance
Priority workplan: USER-WP-0030. Platform administration requires the platform
operator role; membership in every tenant is not required. Ordinary tenant
operator role and MFA; policy changes and factor recovery require recent MFA. Membership in every tenant is not required. Ordinary tenant
administrators cannot read cross-tenant platform support records.
| Journey | Implemented acceptance | Remaining integrated evidence |
@ -10,8 +10,8 @@ administrators cannot read cross-tenant platform support records.
| P02 Tenant and first admin | Authority readback, local bootstrap rollback and retry without duplicate admin | Real first-admin sign-in depends on provider |
| P03 Tenant inspection | Exact identifier, ambiguous-name handling and selected scope | No new implementation gap |
| P04 Administrator recovery | Tenant restoration and recent-MFA lost-factor preview, proof attestation, signed scope confirmation, audited disable/readback/retry and replacement enrollment | Implemented and deployed; evidence: evidence/2026-09-13-p04-recovery.md |
| P05 Service operations | Capability availability, delivery failure/retry/readback, assisted setup guidance | Live factor credential renewal, provider health and actual mail receipt |
| P06 Authentication policy | Existing KeyCape optional/mandatory/step-up source tests; no portal policy-write control | Verified factor lookup, owner-approved effective policy rollout and rollback |
| P05 Service operations | Checked provider/credential/mail status, controlled selected delivery and uncertain-outcome recovery | Deployed; see evidence/2026-09-13-p05-service-operations.md. Actual customer inbox receipt remains a user journey. |
| P06 Authentication policy | Recent-MFA scoped policy preview/apply/audit/rollback; mandatory and optional-after-enrollment; application MFA wins | Deployed and persisted; see evidence/2026-09-13-p06-authentication-policy.md. |
| P07 Tenant lifecycle | Authority version/confirmation, stale-state rejection and recovery | Application propagation must be verified at the application |
| P08 Support investigation | Exact reference across audit/delivery records, tenant filter, safe metadata, unknown-evidence state and delivery drill-down | Provider actions require provider evidence; portal records alone cannot prove rollback |
@ -43,13 +43,13 @@ make test-browser-journeys
make test-journeys JOURNEY_ARGS="--role platform_admin --require-complete"
```
The platform selection includes the P04 recovery tests; the full regression suite runs
219 tests (all pass when disposable PostgreSQL is enabled). The isolated Chromium suite runs 19
checks. The final completeness command intentionally fails while P05/P06
retain external dependencies. The machine-readable matrix is
`tests/journey-coverage.json`; passing portal tests is not live factor acceptance.
The platform completeness selection now includes P04–P06 and must pass with
`--require-complete`. The portal regression suite has 232 tests with disposable
PostgreSQL enabled; 30 isolated Chromium checks pass. Installed-provider native
and browser acceptance is recorded separately in P06 evidence. Customer sign-in
and application access remain USER-WP-0028 / KEY-WP-0034 / VERGABE-WP-0019.
## Historical provider handoff (superseded for P04)
## Historical provider handoff (superseded for P04–P06)
KEY-WP-0035/NK-WP-0033 and USER-WP-0030-T03 retain the provider gap. The registered
`net-kingdom-privacyidea-admin-token` route was rechecked and remains
@ -64,3 +64,8 @@ P04 recovery now uses the signed platform session and private provider service.
Use Authenticator recovery for exact-login preview and support-reference readback.
No provider credential or OpenBao login is requested from the operator.
See evidence/2026-09-13-p04-recovery.md for the implemented boundary and acceptance.
RPF-WP-0040 supplies the dedicated factor-read credential and renewal contract.
P05 verified its operating recovery; P06 deployed scoped policy and guarded
onboarding. The historical resolver-credential incident remains NK-WP-0033,
not a gate on the completed platform journeys.