Operator Portal
Tools + rules for reading regimes.
This portal explains how to interpret REZIME Engine, Sync, and Battle Lines. It does not tell you to buy/sell. The goal is to reduce decision-noise and keep exposure aligned with the dominant Empire.
System architecture
The Stack
Three indicators, minimal redundancy. Each answers a different question.
REZIME Engine
What regime are we in?
- Bull Empire / Bear Empire dominance
- Rebellion / transition visibility
- Revolution = confirmed regime flip
REZIME Sync
Are timeframes aligned?
- HTF–MTF–LTF alignment at a glance
- Rebellion = LTF challenges HTF
- Revolution = confirmed HTF flip
REZIME Battle Lines
Where is the battlefield?
- Territory walls (rolling bounds)
- Wide walls = safer holds / cleaner move
- Tight walls = compression / endgame
How to read it
Interpretation Rules (no signals)
REZIME is a context layer. You still decide entries, sizing, and tactics.
1) Identify the Empire. If Engine shows Empire dominance, default posture is: hold with the trend, reduce churn.
2) Respect Rebellion. Rebellion is not “reverse now.” It’s warning: volatility and counterpressure have increased. Reduce leverage, tighten rules.
3) Uprising = transition. When disagreement intensifies, aim for survival, not optimization. “Do less, not more.”
4) Revolution = reset. A confirmed flip changes the operating environment. Old assumptions are invalid. Rebuild positioning under the new Empire.
How you use it
Operator Doctrine
Your philosophy: make trades riskless ASAP, then let upside be unlimited.
Entry posture
Prefer a single clean entry at smallest meaningful confluence: LTF + MTF alignment, often near an MTF transition (SMA100 break) with early EMA respect.
You’re not trying to “add 7 times.” You’re trying to enter clean, neutralize risk, and hold.
Exit posture
Exit is not “took profit.” Exit is “structure broke.” You stay until a real reversal challenges MTF/HTF and confirms a regime flip.
REZIME is designed to avoid catastrophic drawdowns — not to capture every turning point.
Proof library
Case Study Slots (placeholders)
These sections are where you’ll later paste screenshots of the regime strip only (MA hidden), to prove behavior without leaking construction.
COVID Crash
Empire → Rebellion → Uprising → Revolution mapping during panic.
Screenshot slot
Luna Collapse
Transition behavior under structural failure and cascade.
Screenshot slot
BTC Cycles
Longer empires, fewer rebellions — why HTF works best.
Screenshot slot
IP protection
What’s Shown vs Hidden
You can demonstrate outcomes without disclosing construction.
Public proofs will show the regime strip and state labels only (Empire/Rebellion/Uprising/Revolution).
The moving average construction and territory/border logic remain internal until subscriber access is released.
This keeps the message clear: REZIME is a map — the details are for operators.
Want the institutional framing?
Allocator portal = factsheet archive + mandate + governance + risk.