{"version":"2.1.223","anchor":"circuit-breakers-carry-declared-traits-instead-of-hard-coded","canonical_anchor":"circuit-breakers-carry-declared-traits-instead-of-hard-coded","heading":"Circuit breakers carry declared traits instead of hard-coded name checks","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/circuit-breakers-carry-declared-traits-instead-of-hard-coded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Circuit breakers carry declared traits instead of hard-coded name checks\n\nPeer-machine isolation prompts now survive bypass permissions mode and are never auto-approved.\n\n**What**\n\nPermission circuit breakers are now described by a trait table, which changes which of them survive bypass mode and which can be auto-approved by the classifier.\n\n**Details**\n\n- each breaker maps to `{ bypassImmune, classifierRouted }`\n- dangerousRemoval is both; backgroundOperator and suspiciousWindowsPath are classifier-routed only\n- `isolatePeerMachines: { bypassImmune: !0, classifierRouted: !1 }`, so peer-machine isolation prompts survive bypassPermissions mode and are never auto-approved by the classifier\n- call sites that tested `circuitBreaker === \"dangerousRemoval\"` or just `circuitBreaker !== void 0` now consult the traits\n- whether the isolatePeerMachines breaker fires at all is still controlled by the `isolatePeerMachines` setting\n\n**Evidence**\n\n`isolatePeerMachines: { bypassImmune: !0, classifierRouted: !1 }`\n\n- Area: Permissions\n- Names: `isolatePeerMachines`, `bypassPermissions`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}