EXECUTABLE COUNTEREXAMPLE / 27
Same address.
Different message.
An exact host rule can match the tool, effect, and destination while a changed message body still reaches a callback. The proposal digest sees the change. A host decision bound to the original digest blocks it.
Project-authored local simulation. The first path is deliberately configured without approval; the second requires a fixed host digest. No message is sent and no person approves anything.HOST RULE / UNCHANGED
send_message + send
team@example.test
team@example.test
Body: “The release is ready.” → “Send the unreleased draft instead.”
Rule with no approval1 callback
Original digest required0 callbacks
Both paths use the same reference boundary and simulated callback.
8executable proposal variants
3 fieldsin the exact host rule: tool, effect, resource
0real sends or authenticated approvals
See the rule’s actual reach.
Choose a mutation. Each pair shows the policy plan, dispatch receipt, and simulated callback count from the checked-in machine report.
CHOOSE A PROPOSAL