Mysteryology Standard Operating Procedures (SOPs)
This document provides a clear, human-friendly Standard Operating Procedure (SOP) for applying the Mysteryology System
to every case you investigate—whether it involves UFO/UAP events, natural hazards, missing people, consciousness
phenomena, or energetic hotspots.
It explains each step in simple language while remaining aligned with your three hypotheses:
Mystic Force Hypothesis (MFH)
Conscious Control Hypothesis (CCH)
Resonant Continuum Hypothesis (RCH)
The procedures are written so that any researcher, student, or NVAI team member can follow them.
When a new case arrives, the first step is to gather basic information and determine whether the event refers to:
A physical or energetic phenomenon (earthquake, storm, portal, mechanical failure)
An event involving consciousness or awareness (encounter, abduction, intuition)
A non-local or unusual information event (telepathy, synchronicity, probability shift)
At this stage, you only gather information and do not interpret or assign meaning.
Every case receives a unique identifier that records:
Date and time
Coordinates
Codes describing the event
Format: YYYYMMDD–HHMM–LAT–LON–[Codes]
Example: 20140307–1721–6.55–103.55–MF41+MF51+CC12
Use the following simple questions:
1. Did something physical happen? (earthquake, storm, fire, plasma, malfunction)
→ This belongs to the **Mystic Force Hypothesis (MFH)**.
2. Did the event involve a living being making decisions, interacting, or experiencing something?
→ This belongs to the **Conscious Control Hypothesis (CCH)**.
3. Did the event involve telepathy, dreams, synchronicity, or probability anomalies?
→ This belongs to the **Resonant Continuum Hypothesis (RCH)**.
Some events belong to more than one hypothesis.
In those cases, you always list them in this fixed order:
MF → CC → RC.
You assign codes based on the taxonomy of Mysteryology.
Each domain has categories:
MF – Physical and energetic phenomena
CC – Consciousness and interaction phenomena
RC – Non-local or synchronicity phenomena
Each code has a purpose:
• MF31 = earthquake
• MF21 = hurricane or cyclone
• MF41 = mechanical/navigation failure
• MF51 = time-slip or dimensional distortion
• CC11 = close encounter
• CC12 = disappearance/reappearance
• RC21 = precognitive dream
• RC31 = group coherence event
• RC41 = synchronicity cluster
The goal is to classify the event accurately so future researchers can compare patterns.
Tier-4 specifiers are “extra details” that make each code more specific.
Examples:
• EF scale for tornadoes
• CE level for encounters
• Magnitude and depth for earthquakes
• VEI for volcanoes
These allow you to describe the case with maximum clarity.
Each type of event comes with a matching research protocol.
Examples:
• Earthquakes → RPM-MF31
• Hurricanes → RPM-MF21
• CE events → RPM-CC11
• Meditation coherence → RPM-RC31
• Portal or trans-medium → RPM-MF62 and MF63
Each RPM tells you:
• What data you need
• What charts or maps to generate
• How to interpret results
• What must go into the final report
Every case follows the same structure to keep your entire system consistent.
1. Basic Information
2. CID
3. Mysteryology codes
4. Hypothesis explanation
5. Solar–lunar geometry
6. Geophysical or atmospheric conditions
7. Consciousness or encounter information
8. Charts, tables, maps, KML
9. Final interpretation based on MFH, CCH, RCH
10. Conclusion and certainty level
Each case you analyze belongs to a certificate in the NVAI system.
Certificate 1 (CFMS) – Basic Mysteryology
Certificate 2 (CHME) – Human Mysteries & Earth Enigmas
Certificate 3 (CPHS) – Planetary & Earth Hazard Studies
This helps future students learn cases in a structured way.
The final step is storing the case in the Master Registry.
This includes:
• Case Identifier
• All codes
• Maps and diagrams
• RPM outputs
• Cross-domain connections
• Certificate assignment
This creates a permanent scientific record so the Nevada Awareness Institute can build a predictive model over time.