{"version":"2.1.238","anchor":"groundwork-for-sparing-some-agents-from-a-stop-cascade","canonical_anchor":"groundwork-for-sparing-some-agents-from-a-stop-cascade","heading":"Groundwork for sparing some agents from a stop cascade","tier":"soon","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/groundwork-for-sparing-some-agents-from-a-stop-cascade","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Groundwork for sparing some agents from a stop cascade\n\nStopping one agent still stops them all, though the code to spare some is now present.\n\n**What**\n\nStopping an agent still stops every other running agent with it. New in this build is the machinery to exempt some of them: each other agent is tested against a list of exemption rules and, if exempt, added to a \"spared\" list instead of being killed. Nothing in this build ever adds a rule to that list, so no agent is ever spared and stops cascade exactly as before.\n\n**Details**\n\n- The exemption list lives on the shared registry of running agent tasks; the bundle contains its declaration and one place that reads it, and nothing that writes to it.\n- The spared list is announced through a `cascadeSpared` event that nothing in the build listens for.\n- There is no flag or setting; the feature is inert because the rule list is empty.\n\n**Evidence**\n\n`cascadeStopExemptions`\n\n- Area: Subagents\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}