Skip to content

Safety and Consent Screening Protocol

Screening protocol — instantiates Retrieval-Cued Revision

Screens the target, the person, and the setting before any reactivation, gating the intervention behind confirmed consent, safety, and a stopping plan so a malleable pattern is never opened where it could harm.

Version
v1 · 2026-08-24 · History
Mechanism #
7888
Type
Screening Protocol
Form family
Assessment, Review & Assurance
Solution family
Knowledge, Memory & Provenance
Problem family
Learning, Knowledge & Capability Gaps
Problem subfamily
Memory Encoding, Retrieval & Consolidation
Origin domain
Medicine & Healthcare
Also from
Law & Governance, Psychology
Instantiates
Retrieval-Cued Revision

Safety and Consent Screening Protocol is the gate that runs before anything is reactivated and decides whether opening the pattern is permissible at all. Its defining feature is that it never activates the pattern — it does not cue, and it does not correct. It evaluates three things: whether this target is appropriate to open (or whether it is beyond the depth this setting and these people can safely hold), whether the person has genuinely consented and retains the agency to stop, and whether the setting has the safeguards and a defined stopping condition to contain a window once it is opened. If any of those fails, the gate holds and no reactivation proceeds. The whole archetype's power — that a reactivated pattern is unusually malleable — is also its danger, and this protocol exists because the same window that lets a correction land also lets harm, coercion, or a suggested falsehood land just as durably.

Example

A therapist is considering memory-focused work with a client whose panic is tied to a car accident. Before any session brings that memory into active, malleable focus, a screening protocol runs. It first bounds the target: is the appropriate object of revision the client's present over-generalized fear response, and is the deeper traumatic memory out of scope for this setting and this level of support? It confirms consent as an ongoing, revocable thing — the client understands what reactivation involves, agrees to it, and knows they can halt at any point without penalty. It checks the setting: is there a stabilization plan if arousal spikes, a stopping condition, and follow-up support, so an opened window can be safely closed? Suppose the screen surfaces that the client is in acute crisis with no support system in place. The protocol's output is a hold: not now, not here. Nothing has been reactivated, no memory has been touched — the gate has simply prevented a malleable window from being opened where it could not be safely contained.

How it works

  • Scope the target against the setting's depth. Decide whether the specific pattern proposed for revision is appropriate to open here, or whether it exceeds the safety and expertise available — and should be referred or deferred.
  • Confirm consent and agency. Establish that the person understands what reactivation entails, agrees to it freely, and holds a real, unpenalized ability to stop.
  • Verify containment. Check that the setting has safeguards, a stabilization fallback, and an explicit stopping condition before any window is opened.
  • Guard against coercion and pressure. Screen out status pressure, dependency, and any dynamic that would make "consent" nominal rather than real.
  • Gate, don't proceed. Emit a go / hold / refer decision. On anything short of a clear go, hold — and hand a cleared case, never an opened one, to the reactivation mechanism.

Tuning parameters

  • Screening depth — how thoroughly target, person, and setting are assessed; deeper screening catches more risk but adds friction and can gate out cases that were actually safe.
  • Consent standard — how strong and how explicit the required agreement is; a high bar protects agency but slows access and may feel bureaucratic for low-stakes patterns.
  • Referral threshold — how readily a target is judged out of scope and referred to greater expertise; a conservative threshold is safer but sends more cases elsewhere.
  • Setting-safeguard bar — how much containment (stabilization plan, stopping condition, support) must be in place before a go; a high bar prevents unsafe openings but restricts where the archetype can be applied at all.

When it helps, and when it misleads

Its strength is that it is the one mechanism positioned to prevent harm rather than remedy it — by refusing to open patterns whose reactivation the setting cannot safely hold, it protects against the archetype's worst outcomes before they can occur. It is grounded in the principle of informed, revocable consent and in trauma-informed practice, where reactivating a sensitive memory without safeguards is treated as a serious risk, not a casual technique.[n1]

Its failure mode is the theater of a checklist: a consent form signed under pressure, or a rushed screen that clears a case the setting cannot actually contain, gives false permission that is worse than none because it launders the risk as due diligence. The classic misuse is treating the gate as a formality to get past on the way to the "real" work. The guarding discipline is to make holds and referrals genuinely acceptable outcomes — a screen that can never say no is not a gate — and to keep consent live and revocable throughout rather than captured once at the start.

How it implements the components

  • target_pattern_boundary — deciding whether the specific pattern is appropriate to open here, or is out of scope and must be referred, sets the boundary before any cue exists.
  • interference_and_distortion_guard — screening out coercion, status pressure, and unsafe conditions guards the (not-yet-opened) pattern against harm and contamination.
  • provenance_and_consent_boundary — establishing informed, revocable consent and preserved agency is the gate's core, ensuring revision is authorized rather than imposed.

It does not build a retrieval_cue, open a malleability_window_boundary, or deliver a corrective_difference_payload — those belong to Controlled Reactivation Prompt and Corrective Experience Pairing. Where Controlled Reactivation Prompt actually cues the pattern into an open state, this protocol only decides whether cueing may proceed, and activates nothing.

Editorial Notes

Form Classification

Form family: Assessment, Review & Assurance

Rationale: Safety And Consent Screening Protocol operates by evaluates appropriateness, available expertise, consent, and risk and issues a proceed, defer, or refer finding. That concrete deployed or enacted form is Assessment, Review & Assurance under the frozen taxonomy.

Nearest alternative: Decision, Gate & Allocation — Although Decision, Gate & Allocation can support this mechanism, the frozen evidence makes its operative form the act that evaluates appropriateness, available expertise, consent, and risk and issues a proceed, defer, or refer finding; the alternative is therefore secondary rather than defining.

Review outcome: Adjudicated after independent review; high confidence.

Origin Attribution

Primary origin: Medicine & Healthcare

Origin pattern: Cross-disciplinary synthesis

Present-day reach: Multi-domain

Rationale: Preintervention screening of person, target, setting, consent, and stopping plan is clinical safety practice.

Related originating lineages:

  • Law & Governance — Legal doctrine, regulatory governance, and procedural accountability supplies a parallel or contributing lineage for the mechanism's defining operation: screens the target, the person, and the setting before any reactivation, gating the intervention behind confirmed consent, safety, and a stopping plan so a malleable pattern is….
  • Psychology — Experimental, clinical, and behavioral psychology supplies a parallel or contributing lineage for the mechanism's defining operation: screens the target, the person, and the setting before any reactivation, gating the intervention behind confirmed consent, safety, and a stopping plan so a malleable pattern is….

Review resolution: Both blind reviewers agree that medicine_healthcare is the primary historical origin. Explicit reconciliation of domain_reach_disagreement starts from reviewer_a's mechanism-specific evidence: Preintervention screening of person, target, setting, consent, and stopping plan is clinical safety practice. Reviewer A proposed alternates=law_governance, psychology, origin_mode=cross_disciplinary_synthesis, domain_reach=specialized, and encyclopedia_synthesis=true; reviewer B proposed alternates=law_governance, psychology, origin_mode=cross_disciplinary_synthesis, domain_reach=multi_domain, and encyclopedia_synthesis=true. The final record retains every independently supported alternate from either review (law_governance, psychology) without an arbitrary cap, selects origin_mode=cross_disciplinary_synthesis to represent the combined lineage evidence, and records domain_reach=multi_domain and encyclopedia_synthesis=true. Present-day transfer is recorded as reach and is not treated as proof of historical origin.

Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.

Review outcome: Reconciled after independent review; high confidence.

Notes

This protocol is a gate, not a step in a sequence that always advances — its most important output is often "hold" or "refer." Downstream mechanisms consume a cleared case from it, never an opened one; the moment it hands off, the pattern is still dormant, and reactivation is the next mechanism's act, not this one's.