Response Patterns verifiedimportant

A trigger selects by sending address, destination domain, tag and the text of the reply, with a precedence and a final flag deciding whether later patterns are still evaluated. Actions attach to a trigger as a list, each with its own order. The twelve actions are the reason this screen matters: pause delivery (optionally cluster-wide), add to the suppression list with a chosen code, retry the message after a delay — from the same address or any, to the same server or any, this message or all like it — add or remove a sending address, add or remove a tag, set or unset a property on the message, set or unset a property on the result, and JSON patches against either. The action that sets a result property is the most interesting for us: it writes into the object Hub reads from the result queue, which means the engine can annotate its own telemetry with our vocabulary before we ever see it. Whether these reactions live here or in Hub's policy engine is the open question below; by the logic of DECISIONS § 61 the answer leans towards Hub, with the engine keeping only the reflexes that must be immediate.