Competence Condition Activation¶

When a situation calls for action, make the qualified actor know that the condition is met, that they are competent to act, and that inaction or handoff is accountable.

Gap-Fill Rationale¶

This draft fills the accepted-prime gap for bystander_effect and cognitive_appraisal. The candidate is not merely about assigning authority or calibrating confidence. It addresses a recurring structural failure: people see a situation that may require intervention, but they do not know whether the situation is theirs to handle, whether they are competent enough to act, or whether acting would be legitimate.

The archetype turns that ambiguity into a competence-conditioned activation rule. Qualified actors are expected to act when the condition is met. Unqualified or uncertain actors are still responsible for safe alerting, stabilization, documentation, or handoff.

Essence¶

Competence-Condition Activation links three judgments that are often left separate: “Does this situation require intervention?”, “Am I competent and authorized to act?”, and “What must I do if I am not?” The solution is a gate-and-route structure: act within verified competence, escalate outside it, and make both choices observable.

The pattern is especially useful where the cost of inaction and the cost of unqualified action are both high. It does not say that only experts matter; it says that everyone needs a competence-matched role.

Compression statement¶

Competence-Condition Activation prevents bystander paralysis and unsafe overreach by binding intervention to explicit competence verification. It defines the triggering situation, the minimum competence and authority requirements, observable cues, permissible actions, escalation paths, and review feedback. Qualified actors are activated; unqualified actors are not left passive, but are routed to alert, stabilize, document, or hand off to someone competent.

Canonical formula: activation = situation_threshold_met AND competence_verified AND scope_authorized; else safe_escalation_or_handoff

When to Use This Archetype¶

Use this archetype when a problem is visible to multiple people, intervention requires skill or authority, and the current system leaves people guessing about who should act. It is appropriate for first response, on-call engineering, safeguarding, moderation, peer support, workplace safety, clinical triage, and other domains where “someone should do something” is not an adequate rule.

It is not the right archetype when anyone can safely act, when the only missing piece is motivation, or when a fully automatic control system can intervene without human appraisal.

Structural Problem¶

Bystander ambiguity and competence uncertainty reinforce each other. The more people who can see a problem, the easier it is for each person to assume another person is responsible. At the same time, the more specialized the action, the more reasonable hesitation becomes. Without an explicit competence condition, hesitation can be mistaken for prudence and overreach can be mistaken for initiative.

The structural problem is therefore not only “people fail to act.” It is that the system lacks a legitimate mapping from observed condition to qualified actor to safe action or handoff.

Intervention Logic¶

First, define the situational threshold: what observable cue means the event is no longer background. Second, define the competence condition: what skill, authority, recency, credential, or context knowledge is required for direct action. Third, map actor states so that observers know whether to act, stabilize, alert, hand off, support, or stand down. Fourth, make responsibility claiming visible. Fifth, review outcomes to recalibrate the gate.

A compact rule is: if the situation threshold is met and the actor satisfies the competence condition, act within scope. If the threshold is met and competence is absent or uncertain, escalate or hand off. If a competent actor has claimed the case, coordinate support rather than collide.

Key Components¶

Competence-Condition Activation links three judgments that are usually left separate — whether a situation requires intervention, whether an observer is competent and authorized to act, and what to do when they are not — into a gate-and-route structure that activates qualified actors while keeping everyone else constructively responsible. The Situational Activation Threshold identifies the observable cue that lifts an event out of the background and into something requiring attention. The Competence Condition Specification then states who may act directly, naming the skill, recency, credential, or context knowledge that direct action demands, and the Authority and Legitimacy Mapping explains why that action would be accepted rather than merely well-intentioned. Because the realistic choice is rarely between full intervention and doing nothing, the Actor State Matrix sorts observers into act, stabilize, alert, hand off, support, or stand-down roles, and the Safe Handoff Path makes the non-expert duty practical so routing a problem to competence is easier than passive waiting.

The remaining components make activation visible, bounded, and self-correcting. The Activation Cue and Claim Protocol lets a qualified actor visibly take the case, so coordination replaces collision when several capable people are present. The Scope Boundary and Stop Rule prevents competence activation from sliding into unlimited discretion, holding the activated actor inside the scope that justified acting in the first place. The Activation Review Loop examines activations, non-activations, over-activations, and handoffs to recalibrate the thresholds without turning every false alarm into blame. Together these components guard against the pattern's twin failures — gate-as-passivity, where people hear "only the qualified should act" and fail to escalate, and overconfident self-activation, where confidence or status is mistaken for verified competence.

Component	Description
Situational Activation Threshold ↗	identifies when the event requires attention.
Competence Condition Specification ↗	states who may act directly.
Authority and Legitimacy Mapping ↗	explains why that action is accepted.
Actor State Matrix ↗	prevents the false choice between full intervention and doing nothing.
Safe Handoff Path ↗	makes non-expert responsibility practical.
Activation Cue and Claim Protocol ↗	lets the qualified actor visibly take the role.
Scope Boundary and Stop Rule ↗	prevents competence activation from turning into unlimited discretion.
Activation Review Loop ↗	keeps the rule calibrated.

Common Mechanisms¶

Common mechanisms include qualification gate activation, diffusion-to-duty conversion, secondary appraisal prompting, qualified actor claiming, safe escalation defaulting, scope-limited unlocking, outcome calibration, and minimum safe stabilization. These mechanisms can be implemented through checklists, rosters, credentials, access controls, incident channels, physical badges, training scripts, dispatch workflows, or interface prompts.

Activation Outcome Calibration
Diffusion-to-Duty Conversion
Minimum Safe Stabilization
Qualification Gate Activation
Qualified Actor Claiming
Safe Escalation Defaulting
Scope-Limited Unlocking
Secondary Appraisal Prompting

Parameter / Tuning Dimensions¶

Tune the archetype along several dimensions: how severe the situational threshold must be, how strict competence verification is, how much uncertainty triggers escalation, how much minimum stabilization is allowed before handoff, how visible the responsibility claim must be, how quickly competence evidence expires, and how much false alarm the system can tolerate.

The most important tuning tension is between response speed and overreach prevention. If the gate is too loose, unqualified action increases. If it is too strict, people wait while harm grows.

Invariants to Preserve¶

Competence must be verified rather than inferred from confidence, rank, proximity, or enthusiasm. Unqualified observers must still have a constructive duty. Qualified actors must know when the case is theirs. Scope boundaries must be explicit. Handoffs must be easier than passive waiting. Good-faith escalation must be protected. Reviews must update thresholds without turning every false alarm into blame.

Target Outcomes¶

The archetype aims for faster qualified intervention, less bystander delay, fewer out-of-scope actions, clearer handoffs, more legitimate action, and better after-action learning. A successful implementation makes the right actor more likely to act and everyone else more likely to support, escalate, or stand down appropriately.

Tradeoffs¶

Competence gating improves safety but can slow response. Formal credentials improve enforceability but can ignore tacit or recently decayed competence. Clear rules reduce ambiguity but can become rigid. Alert protections improve reporting but can create noise. Visible responsibility claiming improves coordination but can cause premature disengagement by others.

Failure Modes¶

A common failure mode is gate-as-passivity: people hear “only qualified actors should act” and do not escalate. Another is credential theater, where formal qualification substitutes for actual competence. Overconfident self-activation occurs when people treat confidence as capability. Activation collision occurs when several qualified actors act without a lead. False negative hesitation occurs when thresholds are too strict or psychologically unsafe. Scope creep occurs when an activated actor exceeds the boundary that justified activation.

Neighbor Distinctions¶

This archetype is distinct from competence_calibration_feedback, which aligns confidence with ability but does not itself create a duty-to-act trigger. It is distinct from threshold_based_activation, which triggers action after a cutoff but does not centrally gate by actor competence. It is distinct from decision_rights_clarification, which assigns authority but does not necessarily resolve the cognitive-appraisal moment of “is this mine to handle now?” It is also distinct from local_autonomy_tiered_escalation, which routes work by level but does not necessarily define competence-conditioned direct action.

Cross-Domain Examples¶

In emergency response, a trained responder begins first aid while bystanders call for help and clear space. In software reliability, the on-call engineer claims a severity-one incident while others preserve evidence and avoid unsafe fixes. In workplace safety, any worker may stop work for defined hazards, while specialized repair remains with certified personnel. In peer support, a volunteer can de-escalate within scope but must escalate risk cues to a clinician. In content moderation, frontline reviewers handle clear cases and route ambiguous safety cases to specialized reviewers.

Non-Examples¶

A motivational poster saying “do something” is not this archetype because it lacks competence verification. A credential registry with no activation cue is not this archetype because it does not say when qualified actors should act. A restrictive license rule that prevents ordinary reporting is not this archetype because it removes the handoff duty. A generic escalation ladder with no competence condition is not this archetype because it does not distinguish direct action from safe routing.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (2)

Bystander Effect: A coordination failure in which each potential responder's chance of acting falls as the group grows, so more available helpers can paradoxically mean less help.
Cognitive Appraisal: The interpretive step that evaluates a situation's significance and one's coping resources, determining the emotional and behavioral response rather than the raw stimulus doing so.

Also references 21 related abstractions

Access Control: Restrict system access.
Accountability: Responsibility for actions.
Authority: The recognized, legitimate right to issue binding decisions within a defined scope, distinct from raw coercive force or mere persuasive influence.
Bounded Rationality: Limited decision capacity.
Calibration: Aligning a system's output to a trusted reference by measuring deviation, adjusting to reduce it, and monitoring for drift.
Coordination: Aligning independently controlled actors so their separate actions combine into a coherent collective outcome despite distributed decision-making and incomplete shared information.
Decision: Committing to one alternative from a set under uncertainty and trade-off, collapsing open deliberation into a chosen path and foreclosing the others.
Delegation of Authority: Assign responsibility.
Error Proofing (Poka-Yoke): Error prevention.
Feedback: Outputs influence inputs.

▸ Show 11 more

Variants¶

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Trained Bystander Activation · governance variant · recognized

Activates people with specific bystander-intervention training when they observe a defined risk or harm cue.

Distinct from parent: This variant emphasizes group-observer ambiguity and diffusion of responsibility.
Use when: The population includes many observers but only some have relevant training; Delay is likely because the event is socially ambiguous; Untrained observers need a safe alert or support role.
Typical domains: anti-harassment intervention, community safety, classroom safeguarding
Common mechanisms: diffusion to duty conversion, secondary appraisal prompting, safe escalation defaulting

Credential-Gated Intervention · implementation variant · recognized

Permits direct action only for actors with a recognized license, credential, access right, or demonstrated qualification.

Distinct from parent: This variant emphasizes formal authorization more than social or cognitive ambiguity.
Use when: Unauthorized action can cause material harm; Credentials are meaningful proxies for competence; An access or permission system can enforce the gate.
Typical domains: medical scope of practice, industrial maintenance, secure systems administration
Common mechanisms: qualification gate activation, scope limited unlocking

On-Call Competence Trigger · temporal variant · recognized

Activates the currently assigned qualified responder when a monitored condition crosses a severity or responsibility threshold.

Distinct from parent: This variant emphasizes temporal assignment and acknowledgement workflows.
Use when: Responsibility rotates over time; Incidents require rapid acknowledgment by the competent owner; Observers need to know who has claimed the incident.
Typical domains: SRE incident response, security operations, clinical call coverage
Common mechanisms: qualified actor claiming, safe escalation defaulting, activation outcome calibration

Scope-Limited Stabilization · risk or failure variant · candidate

Allows minimally trained actors to take bounded low-risk stabilizing actions while escalating to a fully competent actor.

Distinct from parent: This variant relaxes the direct-action gate only for predefined minimum safe actions.
Use when: Waiting is dangerous; Full intervention requires competence that the observer lacks; A small safe action can reduce harm without overreach.
Typical domains: first aid, cyber incident containment, workplace hazard isolation
Common mechanisms: minimum safe stabilization, safe escalation defaulting

Near names: Competence-Gated Intervention, Qualified Action Trigger, Licensed Intervention Gate, Trained Responder Activation, Duty to Act When Qualified.