Reminder

Fields

Rule

When a reminder is anchored to a step, the `reminds:` CODE is mandatory; the reminder travels with the target Step's cone once that Step becomes active, and closing the target while the reminder is still open counts as a missed reminder. When the anchor is anything other than a step (architecture · law · quality · future), `returnTrigger:` is mandatory, because the event that will wake the reminder has to be written down. The anchors rank as follows: architecture comes distinctly before step; step comes before law and quality, and those come before future. This ranking is separate from the priority field. A completed record stays where it is; an obsolete one is deleted. The lifecycle moves through open, decided and then done or obsolete; decided is the moment the work enters the chain, and at that moment the `reminds:` Step CODE becomes mandatory. There are three legitimate ways to satisfy it: attach the reminder to an existing Step, open a new Step in between, or — if the target is already finished — update the code at the same time.