Define the operation
An operation begins with a concrete problem, a reason for selecting a specific Servitor and a boundary around what the work may not claim or control. State duration and completion criteria before activation.
A clear contract protects the operator from moving the goalposts. It also makes it possible to distinguish a useful symbolic practice from an open-ended promise.
Choose anchors and obligations
The symbolic anchor should point back to the function of the card. The mundane obligation is the real action that can produce information or change: research, a conversation, a prototype, a boundary or a documented review.
Feeding is best understood as a repeatable cue tied to that obligation. It must never replace medical, legal, financial or safety-critical action.
Review without manufacturing proof
At each review, separate events, interpretations and decisions. Record evidence that supports the working hypothesis and evidence that weakens it. Coincidence is not automatically causation.
Use a scheduled review instead of checking constantly. Frequent checking amplifies confirmation bias and turns the operation into a source of anxiety.
Close and archive
Closure acknowledges what was learned, ends the agreed cues and archives the record. Close when the completion criterion is met, when the deadline arrives or when the operation is no longer safe or relevant.
An operation that cannot end is not well designed. The final decision and responsibility remain human.