MessageWeave/docs
anonsaber 94b6baf7bb docs: reframe SAF-DEBUG-ALLOWLIST as never a gap, not a risk acceptance
The PM's criterion: if the documented production posture already contains
the risk, it was never a code gap to begin with -- it was just a
description of current behavior. My previous wording said it was "closed
by risk acceptance", which implies an accepted open risk that someone
decided to live with. That is the wrong frame and reads worse than the
truth in a security review.

Reworded to state the actual reasoning: the exposure is contained by the
dual-factor debug gate and the Worker safelist, each sufficient alone,
so a third layer was never needed and nothing was accepted.

No behavior, code, or ID registration changed -- wording only.
GATE-DOCS 6/6: ANCHOR 270, SECTION-REF 226, PATH 394.
2026-09-29 20:02:15 +08:00
..
charter.md docs: close the Redis TLS blocker, confirmed live 2026-09-29 19:44:05 +08:00
deployment.md docs: rename roadmap.md to opengaps.md and drop completed items 2026-09-29 19:38:38 +08:00
design.md docs: reframe SAF-DEBUG-ALLOWLIST as never a gap, not a risk acceptance 2026-09-29 20:02:15 +08:00
opengaps.md docs: close SAF-DEBUG-ALLOWLIST by risk acceptance 2026-09-29 19:59:33 +08:00
reference.md config: persist business config regardless of client build, add preflight probe 2026-09-29 18:25:56 +08:00
retired.md docs: rename roadmap.md to opengaps.md and drop completed items 2026-09-29 19:38:38 +08:00