Hopiplaka Goldbach System with Signals

This study builds a PO3 (Power-of-3) price range, projects Goldbach-derived levels inside that range, and issues contextual buy/sell signals only when multiple, explicitly defined filters align (Tesla-Vortex state, ICT AMD phase, time confluence, volume bias, level quality, and momentum). It is a rules-based confluence tool—not an auto-trader.

What it plots
- PO3 Range: Upper/lower dashed boundaries for a selectable PO3 size (3…2187). Optional auto-expansion (×3) occurs when price nears range edges by a user-set sensitivity.
- Goldbach Levels (Premium / Standard / Discount): Lines computed from Goldbach partitions mapped into the active PO3 range.
- OB / LV flags: A level can be flagged as Order-Block zone (OB) or Liquidity-Void zone (LV) when spacing/quality rules (below) are met.
- Tesla Vortex nodes: Levels marked when they align with the Vortex criteria.
- Hit markers: A small dot when price touches a level within tolerance.
- Arrows: Buy/Sell arrows only when confluence and confidence thresholds are satisfied.
- Info panel: Live readout of PO3 stats, current signal + confidence, Tesla state/strength, AMD phase, time bias, volume bias, and liquidity status.
- Data-window series: Vortex strength, time bias value, volume bias flag, and signed signal strength.

How it works (high-level but specific)
1) PO3 engine
- Let S be the chosen PO3 size. The script computes [Lower, Upper] = [floor(Price/S)·S, Lower + S] as the active range.
- Auto-expansion: If price moves within a user-defined percentage of Lower/Upper, the range may expand to 3S (once per trigger), so higher-order structure is captured without re-anchoring.

2) Goldbach mapping
- For even numbers E ∈ {4,6,…,Precision}, generate prime partitions E = p₁ + p₂.
- Each partition defines a ratio r = p₁/(p₁+p₂). The level is L = Lower + r·(Upper−Lower).

Classification:
- Premium: partitions with “small-prime” characteristics (higher weight).
- Discount: partitions with “larger-prime” characteristics (lower weight).

Standard: otherwise.
- Spacing rules (to avoid clutter and force structure):
- Enforce “true” spacing near ~6% of the PO3 height between adjacent lines.
- If a level is flagged OB, use the OB spacing threshold (e.g., ~8%).
- If a level is flagged LV, use the LV spacing threshold (e.g., ~9%).
- Levels violating spacing vs. existing levels are discarded.
- Reliability score starts from the partition weight and is later adjusted by time/volume/vortex factors.

3) Tesla-Vortex filter
- Uses a fixed lookback to compute average range vs. directional change and produces a Vortex strength; from this it derives a state (mean-reverting “MMxM” vs. trend).
- Some levels qualify as Tesla nodes; those receive priority/weighting in signals and thicker styling on chart.

4) ICT context (AMD/IPDA bias proxy)
- Over a user lookback, compute recent high/low and price position inside that range to classify Accumulation / Manipulation / Distribution and a simple structure bias.

5) Time analysis (Goldbach-time confluence)
- For the last N bars, detect swing highs/lows; check whether (hour + minute) is an even number with a valid prime partition.
- Build a time bias from the relative frequency of Goldbach-valid times at swings and a confluence score used in signals.

6) Volume weighting
- Compare current volume to a lookback average. If relative volume is elevated, reliability of nearby levels is scaled up.

7) Signal engine
- Candidate only forms near a qualified level and must pass these checks (user can require 1–6 of them):
1- Tesla state alignment (e.g., MMxM favors buys; trend favors sells when applicable)
2- AMD phase alignment (Accumulation→buys, Distribution→sells)
3- Time bias alignment (bullish vs. bearish)
4- Volume bias (high relative)
5- Level quality (Tesla node / Premium)
6- Momentum (simple 2-bar direction check)

- If Confluence Count ≥ Required and scaled Confidence ≥ 0.5, a Buy (below level) or Sell (above level) arrow is printed. Cooldown prevents immediate repeats.

Inputs you’ll care about
- PO3: range size, auto-expansion toggle & sensitivity, liquidity zone width.
- Goldbach: precision cap (computation depth), enforce ~6% spacing, OB/LV spacing.
- Signals: sensitivity, min reliability, confluence required, cooldown, min distance to level, show arrows/hit markers.
- Filters (toggles): Tesla-Vortex, AMD, Time, Volume, Liquidity.
- Display: show historical/future projections, labels, paths, phase transitions; per-feature colors.

Alerts included
- Buy / Sell signal (with confluence)
- Goldbach level hit
- PO3 upper/lower break and PO3 expansion
- Near Goldbach / Tesla node / Premium level
- Vortex phase change
- Liquidity sweep risk
- Strong time confluence
- High-volume level approach

Confirmation / repainting
- Calculations are live; arrows can change until the bar closes. For stricter behavior, use alerts on bar close or require close-based confirmations in your rules.

How to use (quick workflow)
1- Pick a PO3 size that matches your timeframe/instrument (e.g., 81–243 for intraday; larger for swing).
2- Prioritize Tesla nodes, Premium OB, and time-confluent, volume-weighted levels.
3- Start with Confluence Required = 3–4 and Cooldown = 10–20; then tune Sensitivity to control frequency.
4- Execute with your entry model (e.g., pullback or micro-MS break) and fixed risk.

Why these components are combined (originality rationale)
- Goldbach partitions provide a deterministic way to project repeatable intra-range proportions.
- PO3 stabilizes the reference frame so Goldbach levels are comparable across moves.
- Tesla-Vortex / AMD / Time / Volume each target a different failure mode (wrong regime, wrong phase, wrong time, weak participation). Requiring confluence reduces false positives versus any single method. This is not a cosmetic mashup; each component gates signals.

This publication consolidates prior small variations; future improvements will be issued using Update rather than separate scripts.