Deception Blowback Register¶
Governance register — instantiates Deception Blowback Containment
A standing ledger that records every authorized planted signal — its purpose, owner, audience, truth-anchor location, expiry, and cleanup duty — so nothing is deployed unrecorded and nothing is later mistaken for genuine.
Every other containment mechanism assumes you know what you planted. Deception Blowback Register is the standing ledger that makes that true: a single authoritative record in which every authorized planted signal is entered before deployment — its authorizing purpose and the constraints it must stay within, its owner, who is read in, where the protected truth baseline lives, when it expires, and the obligation to clean it up. It takes no action on the signal itself; its role is to be the index that ties every other containment move to a specific, sanctioned artifact — and the lookup that lets any authorized person ask "did we plant this?" and get a definitive answer.
Example¶
A bank's leak-investigation unit is trying to find which insider is passing client lists to a competitor. It plants uniquely-worded "canary" records — a barium meal[n1] — seeding a slightly different fabricated client into each suspect's distribution list, so that whichever version surfaces outside identifies the leaker. The blowback risk is acute: months later a fraud analyst or an external auditor could stumble on a canary record and report it as a real anomaly, and the bait boomerangs into the bank's own investigations.
The Deception Blowback Register forecloses that. At authorization, every canary is entered — its exact fingerprint, the manager who authorized it and why, who is read in, where the true client baseline is recorded, an expiry date, and the duty to purge afterward. When an analyst later asks whether a suspicious record is real, the register answers in one lookup. No canary is deployed unrecorded, and the bank can always tell its own bait from a genuine signal.
How it works¶
- Register before deployment. No artifact is planted until it has an entry — the register is a gate, not an afterthought.
- Bind each artifact to its authorization. The entry states the authorized purpose and the constraints the deception must not exceed, and names an accountable owner.
- Link, don't duplicate. Each entry points to the artifact's truth anchor, expiry rule, audience map, and cleanup obligation — the register is the connective index that ties those other mechanisms to this specific artifact.
Tuning parameters¶
- Mandatory fields — a minimal entry vs an exhaustive one; richer entries contain better but slow registration and tempt people to skip it.
- Access control on the register — it is a catalogue of all your deceptions, so its own confidentiality is a high-value target; tighter access is safer but makes the lookup less available to those who need it.
- Fingerprinting — how precisely artifacts are described so a later encounter can be matched back to an entry.
- Workflow linkage — whether expiry and review fire automatically off the entry or are left to manual follow-up.
- Closed-entry retention — how long expired entries are kept for audit before purge.
When it helps, and when it misleads¶
Its strength is that it turns "did we plant this?" from institutional memory into a lookup, and it is the backbone that makes sunset, correction, and reconciliation enforceable — each of those needs a definitive list of what was deployed, and the register is that list. Without it, containment depends on whoever happens to remember.
Its failure modes are incompleteness and concentration. An unlogged deception is invisible to every other mechanism and therefore uncontained — so the register's value collapses the moment registration becomes optional. And because it aggregates every operation in one place, the register is itself a high-value leak: compromised, it is a map of all your deceptions. Its classic misuse is being run backwards — used to retroactively "authorize" a deception that was never sanctioned, laundering an unapproved operation into the record. The discipline is registration-before-deployment as a hard gate, strict access with independent oversight of the register itself, and a standing rule that no entry means no deployment.
How it implements the components¶
Deception Blowback Register fills the single authorization component; the rest of its fields only point outward:
authorized_purpose_and_constraint_statement— each entry records the purpose the deception is authorized for and the constraints it must stay within; the register is where that authorization formally lives.
Every other field in an entry is a pointer, not an implementation: the register links to but does not itself provide the truth anchor (Truth Anchor Memo), the expiry rule (Sunset and Debrief Trigger), the audience map (Audience-Channel Matrix), or the cost tally (After-Action Truth Reconciliation). It is the ledger that connects them.
Related¶
- Instantiates: Deception Blowback Containment — the register is the connective record the rest of the containment is built on.
- Sibling mechanisms: Truth Anchor Memo · After-Action Truth Reconciliation · Sunset and Debrief Trigger · Audience-Channel Matrix · Contaminated Record Quarantine
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Deception Blowback Register operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it a standing ledger that records every authorized planted signal — its purpose, owner, audience, truth-anchor location, expiry, and cleanup duty — so nothing is deployed unrecorded and nothing is later mistaken for genuine.
Independent corroboration: The frozen evidence defines Deception Blowback Register as 'A standing ledger that records every authorized planted signal — its purpose, owner, audience, truth-anchor location, expiry, and cleanup duty — so nothing is deployed unrecorded and nothing is later mistaken for genuine', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Security Studies & Intelligence Analysis
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Specialized
Rationale: Intelligence tradecraft cohered controlled deception records that distinguish authorized planted signals from genuine reporting and preserve purpose, ownership, read-in, expiry, and cleanup obligations.
Related originating lineages:
- Military & Strategic Studies — Military deception supplied sanctioned cover stories, protected truth baselines, and blowback risk when friendly analysts encounter planted material.
Review resolution: Intelligence tradecraft cohered controlled deception records that distinguish authorized planted signals from genuine reporting and preserve purpose, ownership, read-in, expiry, and cleanup obligations.
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¶
The register is a passive record, not a control — its entire value is in being complete and consulted. Registration-before-deployment is the gate that makes every other containment mechanism possible: a deception that never gets an entry cannot be sunset, corrected, or reconciled, because nothing else knows it exists.
[n1] A canary trap (or barium meal test) plants uniquely-varied information with each suspected leaker so that the version which surfaces identifies the source — a sanctioned use of planted falsehood. Because the bait is realistic, the planter's own analysts can later mistake it for a genuine signal; the register exists so every piece of bait can be looked up and recognized as one's own. ↩