{"version":"2.1.300","anchor":"signed-policy-verification-status-vocabulary","canonical_anchor":"signed-policy-verification-status-vocabulary","heading":"Updated outcomes for checking signed managed settings and policy limits","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/signed-policy-verification-status-vocabulary","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Updated outcomes for checking signed managed settings and policy limits\n\nClaude Code's list of results for checking signatures on managed settings and policy limits has changed\n\n**Unclear.** Whether these signature checks run, and in which mode by default, is not stated.\n\n**What**\n\nManaged settings and policy limits are rules an organization sets for Claude Code. Claude Code keeps a list of possible results from checking the signature on them, a signature being proof the rules came from the organization unaltered. That list has changed. It now includes:\n\n- `bad_signature`\n\n- `rollback`\n\n- `org_pin_mismatch`\n\n- `stale`\n\nThe checking has two modes, `enforced` and `shadow`.\n\n**Why**\n\nThis points to signature checks on organization settings, with a shadow mode alongside an enforced one.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}