{"version":"2.1.251","anchor":"model-switches-now-go-through-a-decision-check-before-being-","canonical_anchor":"model-switches-now-go-through-a-decision-check-before-being-","heading":"Model switches now go through a decision check before being applied","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/model-switches-now-go-through-a-decision-check-before-being-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Model switches now go through a decision check before being applied\n\nModel switches now pass a decision check first and can be rejected with an error.\n\n**What**\n\nWhat was already a rejected-switch telemetry path is now fed by a hook-style decision taken before the switch lands: anything other than proceed rejects it with an error, and a rejected system-prompt switch reports separately. Notices from the decision come back with a successful switch.\n\n**Details**\n\n- Always on this code path, not behind a flag.\n\n**Evidence**\n\n`model_switch_rejected`\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}