MASON-WP-0005-T05: member check waits on a TOTP factor for tegwick

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 327203@bnt-lap001
Assistant-Session: 55028ae3-4914-4bd1-8f5c-815f3527aef0
This commit is contained in:
tegwick 2026-10-10 00:21:08 +02:00
parent 1bea4da92e
commit bc507455da

View file

@ -218,7 +218,7 @@ id: MASON-WP-0005-T05
status: progress
depends_on: [MASON-WP-0005-T04]
blocked_on: human
blocking_reason: "ops-mason checks and the non-member refusal pass (2026-10-09). Founder runs scripts/verify-fluid-telegram-lane.sh member as tegwick (MFA) and shares the receipt; fluid-telegram runs the salt create-once probe (FT-WP-0002)."
blocking_reason: "ops-mason checks and the non-member refusal pass (2026-10-09). tegwick has no MFA factor, so it cannot reach aal2: founder enrolls TOTP for tegwick in privacyIDEA self-service, then runs scripts/verify-fluid-telegram-lane.sh member; fluid-telegram runs the salt create-once probe (FT-WP-0002)."
priority: high
state_hub_task_id: "4c205be7-4f1f-5dd1-aafa-fc112fdd640e"
```
@ -255,6 +255,11 @@ the salt create-once probe by fluid-telegram (message `f966db1c`).
does not match any associated bound claim values" (receipt
`fluid-telegram-lane-non-member.txt`, 18:11Z). Member run as `tegwick` pending.
2026-10-10: the member run cannot pass yet: `tegwick` has no enrolled factor, so
KeyCape asks for an OTP it cannot satisfy, and the role requires `aal2` anyway.
`tegwick` enrolls TOTP through privacyIDEA self-service (net-kingdom
platform-root-custody.md steps 6-7, same procedure), then the member run.
## Hand off routing and keep the adapter lane separate
```task