Skip to main content
architecture-and-design computer-science law medicine-and-health military-sciences psychology

Trigger rule pair

Description

The meta-criterion: a heuristic only earns its keep when it is paired with an identifiable invocation condition. A bare rule (“do X”) is not yet a trigger-rule pair — it’s an aspiration or an instruction that may never be retrieved at the moment it’s relevant. A trigger-rule pair has the form: “When [situation-shape S], apply [rule R].” The trigger is what makes the rule addressable at the right moment; without it, the rule sits inert in memory and fails to execute when the situation calls for it. This concept is directly architecturally relevant to any retrieval-driven reasoning system: the retrieval layer needs trigger patterns to know when to surface a concept or insight, not just what the insight says. A knowledge-base entry without trigger keywords or a “When it applies” section is an incomplete trigger-rule pair — it has the rule but lacks the invocation condition.

Triggers

User-initiated: User is writing or reviewing instructions, rules, heuristics, principles, or guidelines. Any time a rule is stated without a “when”: that’s the moment to surface the trigger-rule-pair concept and prompt for the invocation condition. Agent-initiated: Engine scans an insight or rule-like statement and detects a bare principle (rule without trigger). Candidate inference: “this heuristic is missing its invocation condition — what situation-shape should fire it?” Vocabulary cues: “heuristic,” “rule,” “principle,” “always,” “never,” “our convention is,” “best practice,” “standing instruction” — followed by a content statement but not preceded by a conditional (“when X,” “if X,” “in situations where”). Situation-shape signals: A document containing many bare rules (style guides, wikis, CLAUDE.md files) is a trigger-rule-pair audit target — each rule is a candidate for trigger-elicitation.

Exclusions

  • Truly unconditional rules — some invariants apply everywhere with no trigger needed (e.g., “never use plaintext for credentials”). The trigger is effectively “always” and stating it explicitly adds no information.
  • Exploratory context — in a brainstorm or divergent-thinking mode, pairing every heuristic with a trigger prematurely constrains exploration. The concept earns its keep when converging on operationalizable rules.
  • When the trigger is fully obvious from context — “when reviewing code, look for security vulnerabilities” — the trigger adds little if the document is already scoped to code review.

Structure

Internal structure of trigger-rule-pair: a table of its component slots and the concepts that fill them. The rule half is what gets executed; the surface half is what the situation must present for the rule to activate; cadence constrains when within a cycle the trigger fires (e.g., “at session start,” “when a new dependency is introduced,” “after each deployment”). Cadence is optional — some triggers are event-driven rather than cadence-driven.

Relationships

Relationship neighborhood of trigger-rule-pair: a graph of the concepts it connects to and the concepts it is a part of.
  • doctrinecreation relationship — trigger-rule-pair is the structural criterion that turns a doctrine fragment into a complete doctrine. Every complete doctrine is a trigger-rule pair; not every trigger-rule pair is elevated to doctrine status.
  • cadencecomposition relationship — cadence-driven triggers fire at temporal intervals (“at session start”) rather than event-based; the combination is trigger-rule-pair with a cadence-shaped trigger.
  • asymmetric-gatespecialization relationship — an asymmetric gate is a trigger-rule pair where the rule is “apply the expensive check” and the trigger is “when the cheap gate passes.” Trigger-rule-pair is the containing category.
  • active-gate-vs-passive-auditcomposition relationship — the “gate vs. audit” choice is a downstream decision from the trigger: what does the rule do when triggered? Gate (block) or audit (record)?

Examples

CLAUDE.md instructions · computer-science

“Read X before doing Y” is a trigger-rule pair; “write good code” is not. The quality of CLAUDE.md files correlates with trigger-rule-pair density.

Cognitive science: production rules in ACT-R have the same structure (condition → action). The trigger half corresponds to the condition side of a production. · psychology

Cognitive science: production rules in ACT-R have the same structure (condition → action). The trigger half corresponds to the condition side of a production.
good ADRs state “when this architectural question arises (trigger), prefer approach X (rule).”
“when you see a function over N lines, flag it” (trigger-rule pair) vs. “keep functions short” (bare rule).
The Ottawa Ankle Rules give a clinician an explicit condition under which an ankle X-ray is warranted. An ankle radiographic series is indicated only if there is pain in the malleolar zone and any one of: bone tenderness at the posterior edge or tip of the lateral malleolus, bone tenderness at the posterior edge or tip of the medial malleolus, or an inability to bear weight both immediately after the injury and in the emergency department. The rule’s value is that it converts a vague clinical instinct (“order imaging when a fracture seems plausible”) into a checkable triggering condition, which is what makes it reliably applicable across clinicians and what lets it safely reduce unnecessary radiographs.This is a trigger-rule pair in clinical medicine. The_trigger is the articulated decision criterion — the specific, recognizable findings (malleolar tenderness at named sites, or failure to bear weight) whose presence is what fires the rule. The_rule is the action the trigger authorizes: obtain the radiographic series. A bare clinical maxim like “image when in doubt” is a rule without an addressable trigger — it never tells the clinician precisely when doubt should convert to action, so it cannot be applied consistently or audited. The Ottawa Rules earn their keep precisely by supplying the missing invocation condition.Inference: a clinical decision rule is the medical form of the trigger-rule pair, and its diagnostic and economic power comes from the trigger half being operationalized — stated as observable findings rather than as an aspiration. The discipline of replacing “use judgment” with “when these specific signs are present, take this specific action” is what turns expert intuition into a transmissible, evaluable rule.
Pattern-language tradition (Alexander et al.): each pattern has a “forces” section describing the situation that calls for the pattern — equivalent to the trigger.
The Wells clinical model for deep-vein thrombosis assigns points for findings such as active cancer, recent immobilization, localized tenderness along the deep venous system, and asymmetric calf swelling, subtracting points when an alternative diagnosis is at least as likely. The cumulative score then triggers a branch in the diagnostic pathway: a score of one or less classifies DVT as “unlikely,” sending the patient to a D-dimer test that, if negative, rules out DVT without imaging; a score of two or more classifies DVT as “likely,” sending the patient directly to compression ultrasonography. The score is not the diagnosis — it is the condition that determines which downstream rule applies.This is the trigger-rule pair embedded in a diagnostic algorithm. The_trigger is the stratified pretest probability — the score crossing its threshold (”≥ 2 → likely,” ”≤ 1 → unlikely”) is the recognizable condition that fires a particular next action. The_rule is the action that the threshold authorizes: in the “unlikely” branch, “obtain a D-dimer and rule out on a negative result”; in the “likely” branch, “proceed to ultrasonography.” The score’s job is to make the rule addressable — without a quantified trigger, a clinician facing a swollen leg has no principled way to decide which test sequence the patient should enter.Inference: a scored decision rule is a trigger-rule pair whose trigger is a threshold on an aggregated signal rather than a single observation. The structural point is identical to the simpler clinical rules — the rule executes only when its invocation condition is articulated and met — but the trigger here is graded, which lets a single algorithm route different patients to different rules by where their score lands. Defining the threshold is defining the trigger.