PRIVATE TERMINAL

Evatrix Control Center

Strategy Intelligence Layer

Strategy Intel

Strategy families, regime fit, contribution visibility, and intelligence-layer transparency without exposing proprietary execution logic.

Disclosure Mode
Surface-Level
Core Logic
Protected
Optimization State
Active
Strategy Scope
Crypto Perps
Active Families
4
Core setup groups currently driving signal production
Best Performing Family
Liquidity Reclaim
Most consistent contribution in current market regime
Regime Fit
Trend-Biased
Current strategy stack favors directional continuation
Logic Visibility
Controlled
High-level transparency without exposing core IP
Strategy Families
High-level view of the engine’s active intelligence groups
Liquidity Reclaim
Continuation / Re-entry · Trend markets
Performs best when higher-timeframe alignment and reclaim confirmation stay intact.
High ContributionPrimary
EMA Pullback
Trend continuation · Structured directional markets
Most stable when momentum cools without damaging bullish or bearish structure.
High ContributionCore
Pressure Reversal
Counter impulse reaction · Mixed / local exhaustion
Needs stronger confluence than continuation families to remain premium-grade.
Medium ContributionSelective
HTF Reclaim
Higher-timeframe confirmation · Swing-quality environments
Used when broader structure validates cleaner continuation or recovery scenarios.
High ContributionPrimary
Intelligence Logic
Strategy families should be shown as capability groups, not exposed code logic
Users need to understand how the engine behaves, not how to clone it
Performance contribution matters more than indicator name-dropping
Regime Notes
Continuation families dominate when Market Pulse stays constructive
Reversal logic should remain more selective under strong major-led trends
Weak or fragmented breadth should reduce confidence in lower-quality families
Operator Principles
This page builds trust through structure, not through full disclosure
Good strategy intel explains edge categories while protecting proprietary execution logic
Best UX outcome: users understand why signals appear without reverse-engineering the engine
Strategy Snapshot
Current Dominant FamilyLiquidity Reclaim
Trend SensitivityHigh
Reversal UsageSelective
IP ExposureRestricted
Contribution Mix
Continuation Families52%
Reclaim / Recovery31%
Reversal Logic17%
Disclosure Policy

Strategy identity can be visible without exposing decision code.

Trust is built through structured transparency, not source-level disclosure.

Users should understand edge families, not replicate them.

Forward Integration
Bot Family AttributionPlanned
Setup Performance FeedPlanned
Regime-Strategy MappingPlanned
Internal Logic LayerProtected