Update decision agents after every activation based…

When This Fires

• After every decision agent activation, regardless of whether the outcome was good or bad
• During weekly reviews when processing accumulated agent activations
• When an agent produces an unexpectedly bad outcome — immediate update opportunity
• When an agent produces an unexpectedly good outcome — opportunity to reinforce and broaden

Common Failure Mode

Only updating after failures: "The agent worked fine, no need to review." Successes are equally informative — they confirm which conditions the agent handles well, which expands your confidence in its applicability. And occasionally, a success reveals that the agent produced a good outcome for the wrong reasons — which means it will fail when circumstances shift.

The Protocol

(1) After each decision agent activation, note the outcome: did the decision produce good results? (2) If good outcome → reinforce: the criteria worked for this context. Note what context features mattered. (3) If bad outcome → diagnose: which criterion was wrong? Was it the trigger scope, the conditions, or the decision logic? (4) Update the agent: add the new condition, adjust the criterion weight, or narrow/broaden the scope based on the outcome. (5) Document the update in the agent's documentation (Document every agent with five components) so you can trace the agent's evolution over time. Each update makes the agent a slightly better model of your decision domain.