Selection & Symmetry Protocol

This page publishes the current Empire Codes scanner method in full, including the symmetry requirement and rejection discipline.

The objective is mechanism tracking across power centres. The objective is not selective pattern emphasis on Western actions.

Scanner Guardrails (Current)

  • Selection symmetry rule: For every mechanism logged, actively search for and note counter-examples where the same instrument has been applied by non-Western or non-US-aligned actors (e.g. China, Russia, Iran, or other state actors using corridor control, sanctions-style pressure, recognition doctrine, or permission structures). If no counter-example is found, explicitly note that absence as part of the signal strength assessment. The goal is pattern recognition across power centres, not selective pattern emphasis on Western actions.
  • Mechanism over incident: items only survive if they expose a reusable procedural, legal, corridor, or permission instrument.
  • Primary evidence discipline: preference for primary or tier-1 records, with explicit carve-out handling where access restrictions are themselves part of the mechanism.
  • Duplicate rejection: no duplicate timeline or signal entries across Tier-1 and Tier 2/3 layers.
  • Two-layer writing rule: Reporting states source-grounded fact; Interpretation states one mechanism sentence.

Rejected-Log Practice

Each scanner run records rejected items with a one-line reason, including:

  • duplicate of an existing entry
  • no reusable mechanism
  • insufficient source material
  • pure commentary without evidential anchor
  • failed symmetry check where no counter-example search note is provided

Rejected logs remain part of the editorial audit trail and are reviewed during dossier refreshes.

Symmetry Tracker

Running tracker of whether each instrument currently has cross-application evidence across power centres in the scan window.

Instrument Primary context logged Cross-application status Latest note date
Corridor control plus selective transit permissions Hormuz and maritime access governance Counter-example required on next scan pass 2026-05-05
Recognition doctrine and asset-custody leverage Venezuela routing and seizure architecture No counter-example located in scan window 2026-05-05
Sanctions-style pressure through services and finance Tariff and compliance-chain coercion Counter-example required on next scan pass 2026-05-05
Permission structures via bases, ZEDE, and legal carve-outs Tier 2/3 Hondurasgate-linked mechanism claims No counter-example located in scan window 2026-05-05

Operational Scope

This protocol governs scanner selection for:

πŸœ‚ Explore the Next Episode

Support The Gnostic Key

If this work helps you, a small contribution keeps the archive alive.