Overlays are optional context layers you can mix into runs to validate a window, add narrative color, or add a veto signal. Use one or two for signal hygiene, or stack several when you want a richer lens.
Alternate encodings for phrase transforms and resonance checks.
Example: use Atbash or Caesar to see if an intent still resonates after a transform.
Market or price-based context to anchor timing choices to real-world behavior.
Example: avoid a launch window when volatility spikes or a macro indicator drops.
Calendar labels and civic month references for ritual or historical framing.
Example: align a project kickoff to a named Hellenic month for thematic resonance.
Space-weather and solar activity context for geomagnetic or atmospheric correlation.
Example: annotate a window with geomagnetic unrest when testing sensitive equipment.
Coherence and global attention signals as a shared consciousness overlay.
Example: add a narrative layer when a global event may bias a run.
Seismic activity context for risk or anomaly awareness.
Example: add caution tags when local or global quake activity is elevated.
Intent-to-glyph generation for focus and symbolic reinforcement.
Example: generate a sigil for a timing window and compare variants for clarity.
Phase, illumination, and daylight visibility cues to refine timing hygiene.
Example: prefer a waxing Moon for growth actions or avoid dark-Moon starts.
Deterministic draws for symbolic confirmation or warning flags.
Example: pull a draw to sanity-check a proposed go window.
Forecast context to avoid obvious real-world blockers.
Example: skip a field action when the forecast contradicts a great timing score.