{"version":"2.1.221","anchor":"stop-details-refusal-categories-documented-as-an-open-set","canonical_anchor":"stop-details-refusal-categories-documented-as-an-open-set","heading":"Stop-details refusal categories documented as an open set","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/stop-details-refusal-categories-documented-as-an-open-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Stop-details refusal categories documented as an open set\n\nDocs now say refusal categories are an open list, so generated code stops assuming only two.\n\n**What**\n\nThe \"Stop details\" quick reference no longer presents `category: \"cyber\"|\"bio\"|null` as the complete set of values.\n\n**Details**\n\n- `category` is now described as an open set with additional examples, so generated code should not exhaustively switch on two values.\n\n**Evidence**\n\n`an open set, e.g. `\"cyber\"`, `\"bio\"`, `\"reasoning_extraction\"`, `\"frontier_llm\"`, or `null``\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}