{"version":"2.1.312","anchor":"attestation-trust-results-drop-rollback-and-floor-unreadable","canonical_anchor":"attestation-trust-results-drop-rollback-and-floor-unreadable","heading":"Two reasons for distrusting organization-locked configuration are gone","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/attestation-trust-results-drop-rollback-and-floor-unreadable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Two reasons for distrusting organization-locked configuration are gone\n\nClaude Code no longer lists a rollback or an unreadable floor as reasons to distrust configuration pinned by an organization\n\n**Unclear.** It is not clear whether those two situations are now accepted as trusted or are caught some other way.\n\n**What**\n\nAn organization can pin configuration so that Claude Code checks it can be trusted. Claude Code keeps a list of reasons a check can fail. Two have been removed from it:\n\n- `rollback`\n\n- `floor_unreadable`\n\nOther reasons, such as the organization's pin not matching or not being known, remain.\n\n**Why**\n\nThe checks for organization-pinned configuration appear to be less strict than before.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}