{"version":"2.1.277","anchor":"hipaazdr-compliance-gates-tighten-cache-miss-defaults","canonical_anchor":"hipaazdr-compliance-gates-tighten-cache-miss-defaults","heading":"HIPAA\/ZDR compliance gates tighten cache-miss defaults","tier":"internal","area":"Compliance","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/hipaazdr-compliance-gates-tighten-cache-miss-defaults","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### HIPAA\/ZDR compliance gates tighten cache-miss defaults\n\nHIPAA\/ZDR compliance checks now default to blocking, not allowing, when the compliance cache is empty\n\n**What**\n\nThree compliance-gated capabilities change their behavior for when compliance status hasn't been cached yet (a cache miss):\n\n- `Projects` tool access now defaults to holding (pausing pending confirmation) instead of allowing\n\n- `Team onboarding` now defaults to holding instead of allowing\n\n- `Peer messaging` now defaults to denying outright instead of allowing\n\n**Why**\n\nThis makes these compliance-sensitive features fail closed rather than open when the system doesn't yet know an organization's HIPAA or zero-data-retention (ZDR) compliance status, reducing the risk of allowing something that should have been blocked while status is still unknown.\n\n- Area: Compliance\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}