{"version":"2.1.246","anchor":"workflow-pattern-matching-words-and-a-budget-starvation-prot","canonical_anchor":"workflow-pattern-matching-words-and-a-budget-starvation-prot","heading":"Workflow pattern-matching words and a budget-starvation protocol","tier":"internal","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/workflow-pattern-matching-words-and-a-budget-starvation-prot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Workflow pattern-matching words and a budget-starvation protocol\n\nWorkflow pattern matching gained variable binding and count matching, and starved agents now wait for budget.\n\n**What**\n\nThe workflow sandbox gained two pattern-matching words, one that binds a variable and one that matches at least N items, each with its own validation error, and rule callbacks now receive the bindings as a second argument. Separately, an agent whose run has exhausted its budget is parked as `starved` and waits for more instead of failing.\n\n**Details**\n\n- A starved agent resumes when a budget top-up arrives; the message tells the model to `put {topic:'budget', units:N} to continue`.\n- Starved rows are surfaced in the workflow status report.\n- All of this lives in the Workflow tool, which is only registered when it is present in the build.\n\n**Evidence**\n\n`put {topic:'budget', units:N} to continue`\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}