Trigger / Automate

A rule or event starts a bounded action automatically, always with limits and exceptions.

Your blood pressure prescription needs a refill every 30 days, and the recurring failure is never the pharmacy; it is the remembering. You notice the empty bottle on day 31, skip a dose or two waiting for the refill, and your doctor sees the gaps in your numbers. The action is identical every month. Only the remembering ever fails.

TRIGGER / AUTOMATE is the relationship mode where a rule or event starts a bounded action automatically, always with limits and exceptions built in. It differs from delegation in that no one is deciding each time; a condition fires and a predefined action runs. The cue is a stable, repeating action whose only failure mode is human memory or timing. The operation has three parts: define the trigger precisely (day 25, refill request goes to the pharmacy; day 28, reminder to confirm pickup), bound what the automation may do (request refills of this one prescription; never accept substitutions or dosage changes), and route exceptions to a human (any pharmacy question, any change from the doctor, exits the automatic path immediately). What changes is that the gaps disappear from your chart without any improvement in your memory. The boundary: never automate what still requires judgment each time, and never build a trigger without its exception path, because an automation meeting a situation it was not built for keeps firing anyway.