Apply the camera test to triggers — if a camera can't…

Design triggers using the camera test: if a video camera could not detect the exact moment the trigger fires, the trigger is too vague to fire reliably and must be replaced with an observable event.

When This Fires

When designing any new behavioral agent trigger
When debugging a trigger that isn't firing reliably — apply the camera test to diagnose vagueness
When reviewing trigger documentation (Document every agent with five components) for quality
As a complement to Agent triggers must be observable or measurable — vague… — this is the specific test for the general principle

Common Failure Mode

Designing triggers around completion of cognitive activities: "When I finish thinking about the problem" or "After I process the morning's inputs." These aren't camera-detectable because "finish thinking" has no observable boundary. Convert to observable proxies: "When I close the research tab and open a blank document" or "When I stand up from the desk after the morning email session."

The Protocol

(1) Write your proposed trigger. (2) Apply the camera test: "If a video camera was recording me, could it detect the exact moment this trigger fires?" (3) If yes → the trigger is specific enough. Proceed with agent design. (4) If no → the trigger is too vague. Find the nearest observable event that reliably co-occurs with the intended trigger moment. Replace the vague trigger with the observable one. (5) Common conversions: "When I feel..." → physiological signal or external event. "After I finish..." → specific physical action that marks completion. "When it's time to..." → clock time or alarm. (6) Re-test the converted trigger with the camera test before installing.