Apply the camera test to triggers — if a camera can't detect the exact firing moment, the trigger is too vague

Why This Is a Rule

The camera test is the operational version of Agent triggers must be observable or measurable — vague triggers like "when I feel ready" never fire reliably (observable triggers over subjective ones). It provides a vivid, immediately applicable diagnostic: imagine a video camera recording your environment. Could it detect the exact moment the trigger fires? "The alarm goes off at 9 AM" — yes, a camera could detect the sound. "I finish my morning coffee" — yes, a camera could see the cup being put down. "I feel ready to start working" — no, a camera can't detect internal readiness. "The afternoon slump hits" — no, a camera can't detect subjective energy levels.

The test works because it forces trigger specification to the level of physical observability. Anything a camera could detect is concrete enough to activate pre-attentive processing in your brain — you notice it automatically, without deliberation. Anything a camera can't detect requires cognitive assessment, which means deliberation, which means the trigger competes with whatever your working memory is currently handling.

Behavioral scientist B.J. Fogg uses a similar concept with his "anchor moment" principle: triggers must be tied to a specific, existing action or event that's already automatic. The camera test generalizes this: any physically observable event can serve as a reliable trigger.

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: Name, Trigger, Conditions, Actions, Success Criteria — undocumented agents degrade silently) for quality
• As a complement to Agent triggers must be observable or measurable — vague triggers like "when I feel ready" never fire reliably — 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.