Bounded Correction Protocol¶
Response protocol — instantiates Deception Blowback Containment
When a planted signal reaches friendly decision-makers, corrects or re-contextualizes it just enough to stop it steering their decisions — without disclosing more of the deception than necessary.
Compartmenting works only until a signal slips past the compartment. Bounded Correction Protocol is the reactive move for when a planted signal has already reached a friendly decision-maker who was never read in and is about to act on it as though it were genuine. It delivers the smallest correction that stops that reliance — a targeted "re-contextualize this" or "treat this as non-genuine," to just the authorized audience at risk — while preserving as much of the deception and its confidentiality as containment allows. Its defining move is that it corrects the decision dependency, not the record and not the world: surgical, need-to-know, and calibrated to immunize the friendly choice without announcing the trick to everyone.
Example¶
A map publisher salts its database with a fictitious "trap street"[n1] — a short road that does not exist — so that any competitor who copies it can be caught. Years later the publisher's own logistics team, building a delivery-routing layer on the same data, plans routes down that phantom street. Left alone, dispatch will send drivers toward a road that isn't there.
A bounded correction fixes exactly that: the routing team (and a navigation partner under NDA) is quietly told to treat that specific segment as non-navigable — enough to keep their routing decisions off it — without publishing a public erratum that would reveal to copyists which street is the trap. The friendly decision is immunized; the trap keeps working. The correction is scoped to the decision at risk and no wider.
How it works¶
- Scope to the reliant audience. Identify exactly who is about to act on the signal — usually from a Friendly Reliance Probe or the exposure map — and correct only them.
- Correct the dependency, not the deception. Deliver the minimum re-contextualization that breaks reliance ("disregard X"), rather than a full disclosure of the operation.
- Preserve confidentiality. Choose a channel and wording that reach the friendly decision-maker without leaking to the intended target or the wider audience.
Tuning parameters¶
- Correction scope — how many people are told; wider correction reduces residual friendly harm but raises the chance of blowing the operation.
- Correction depth — a bare "disregard this" flag vs the underlying truth; more detail is more convincing but more exposing.
- Timing — how fast the correction goes out; a late correction lands after the decision is already made.
- Channel — the same channel as the signal vs a protected side channel out of the target's view.
- Traceability — whether the correction is itself logged and recallable, so it does not become an uncontained new signal.
When it helps, and when it misleads¶
Its strength is that it stops friendly reliance without unwinding the whole operation — the difference between a decision quietly steered back on course and a blown deception. It is the repair that makes an aggressive containment posture survivable, because a signal that escapes the compartment need not become a friendly-side error.
Its failure modes cluster around scope and timing. Correct too late and the decision is already made; too narrow and someone downstream is still relying on the signal; too broad and the correction blows the trap. The sharpest misuse is a correction that is itself deceptive — a "clarification" issued to push a second false picture rather than to break reliance, so the repair becomes a new lie. The discipline is to base scope and timing on evidence of actual reliance rather than guesswork, to log every correction so it can be tracked and recalled, and to prefer plain "disregard this" flags over elaborate counter-narratives that can take on a life of their own.
How it implements the components¶
Bounded Correction Protocol fills the friendly-decision side of the correction machinery:
friendly_decision_immunity_guard— the protocol's whole output is a friendly decision that no longer depends on the planted signal.correction_and_quarantine_path— it operates the correction branch of this path: re-contextualizing the live signal for the authorized audience at risk.
The quarantine branch of that path — isolating the contaminated records themselves — belongs to Contaminated Record Quarantine. It does not size the compartment ahead of time (Compartmented Briefing) or detect where friendly reliance exists in the first place (Friendly Reliance Probe).
Related¶
- Instantiates: Deception Blowback Containment — this protocol is the reactive repair that keeps an escaped signal from steering a friendly decision.
- Consumes: Friendly Reliance Probe locates the reliance this protocol corrects; the Audience-Channel Matrix bounds who may need it.
- Sibling mechanisms: Contaminated Record Quarantine · Compartmented Briefing · Friendly Reliance Probe · Deception Blowback Register · Truth Anchor Memo
Editorial Notes¶
Form Classification¶
Form family: Intervention, Treatment & Transformation
Rationale: When a planted signal reaches friendly decision-makers, corrects or re-contextualizes it just enough to stop it steering their decisions — without disclosing more of the deception than necessary, making its operative form a direct operation whose success is a changed target state or capacity.
Independent corroboration: The frozen evidence defines Bounded Correction Protocol as 'When a planted signal reaches friendly decision-makers, corrects or re-contextualizes it just enough to stop it steering their decisions — without disclosing more of the deception than necessary', so its operative form is Intervention, Treatment & Transformation.
Nearest alternative: Protocol, Workflow & Routine — It directly changes the misleading signal for affected decision-makers, while its protocol constrains scope and disclosure.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Security Studies & Intelligence Analysis
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Specialized
Rationale: Deception and compartmentation practice uses a need-to-know correction when a friendly actor begins relying on planted information, disclosing only enough to stop the harmful dependency.
Related originating lineages:
- Law & Governance — Law and governance contribute the charter, contract, adjudication, rights, disclosure, or procedural-accountability form used here.
- Military & Strategic Studies — Military practice contributes briefing, after-action learning, deception, command, or operational planning discipline used here.
Review resolution: Security and intelligence is the agreed primary lineage because the protocol permits a constrained corrective intervention under explicit authorization and escalation rules. Law supplies due-process limits and military doctrine supplies disciplined response under threat; the tailored combination is an Encyclopedia synthesis.
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¶
Correction targets live decisions; its record-side counterpart, Contaminated Record Quarantine, targets stored artifacts. A signal that has both reached a decision-maker and entered the records needs both: correct the decision, quarantine the record.
[n1] A trap street (in cartography) or mountweazel (in reference works) is a fictitious entry planted to catch copyists — a genuine, sanctioned use of deliberate falsehood. Its blowback risk is precisely the one this mechanism addresses: the fabricator's own downstream users can later mistake the planted fiction for fact. ↩