diff --git a/docs/development/V1-2_ANATOMICAL_SHEETS.md b/docs/development/V1-2_ANATOMICAL_SHEETS.md index dae9c21a..2fc42e0f 100644 --- a/docs/development/V1-2_ANATOMICAL_SHEETS.md +++ b/docs/development/V1-2_ANATOMICAL_SHEETS.md @@ -1940,6 +1940,10 @@ Residual risks: 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; +- production prerequisite (owner 2026-11-12, not blocking R2, TODO RR-14): no real password or secret in any log, + no real secret in process arguments, no real secret in test or CI/CD artifacts, and these three checked before + any deployment. Raised by the guardrails scan of `scripts/db-trial-check.sh:1340`, whose passwords are + fictitious and test-only; the harness is not changed and no secret is rotated now; - 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;