docs(docs): record the aal2 token residual risk as a production prerequisite

This commit is contained in:
bchanot committed 2026-11-03 22:04:28 +01:00
1 parent 4657abf1e3
commit ee6decbe4e
1 file changed
+5
@@ -1837,6 +1837,11 @@ Residual risks:
- production prerequisite: the lost-factor recovery is not rehearsed and no
recovery code exists (`IDENTITY.md` §4.2); the runbook of §5.7.7 is rehearsed
on the sandbox and written before any production use of MFA-protected rights;
- production prerequisite (owner 2026-11-03, recorded at V1-2.6, not fixed): the catalogue and sheet RPCs and the
Storage policies check the token's `aal2` claim (`private.has_mfa()`), not the live session; only the platform
role and rights RPCs use `private.has_aal2_session()`. A JWT issued at `aal2` therefore keeps passing them after
a factor is removed (or the session is downgraded) until it expires. A live-session check or a revocation
strategy compatible with Supabase / GoTrue is studied before production; V1-2.6 changes no authentication;
- a capability holder can still ask Storage for a signed URL to a draft
drawing through the API; such a URL outlives a later revocation until it
expires;