Platform Guide
Prime Market AI Docs
Quick reference for every key option and attribute shown in the UI.
Technology & Deployment
- Data Infrastructure: integrated market data services and MetaTrader-compatible data workflows.
- Deployment: supported for cloud deployment and operations.
- Strategy Privacy: internal signal-generation methodology is intentionally not disclosed on the platform.
Landing Page
- Sign In with Google: starts secure account login.
- Open Dashboard: opens live signal workspace (when logged in).
- Support / Billing / Careers: contact and subscription links.
Dashboard Filters
- Model Family: choose active family (`prime7`, `prime21`, etc.); locked families are disabled.
- Asset Class: filter by `fx`, `commodities`, or `crypto`.
- Symbol: choose instrument within selected family/asset.
- Trial Alert: shows trial status and access limitations.
Status Board
- Session: active market session in your timezone context.
- Market: market open/closed state.
- Your Time: local viewer time.
- Engine: inference cadence and latest execution time.
Signal Board Columns
- Symbol: instrument code.
- Asset: instrument class.
- Action: `BUY`, `SELL`, or `HOLD` signal state.
- 5m Target: target close estimate for the forward window.
- ETA: time remaining until target evaluation point.
- Expected Move: projected relative move from current base.
- Status: `Live` or `Market Closed` for that instrument context.
- Session: mapped session label for quick regional context.
Insights Panel
- Historical Signal Confidence: gauge summarizing prior directional reliability.
- Real vs Predicted: chart comparing resolved predictions, actual outcomes, and upcoming targets.
- Tracker Confidence: composite quality score using hit-rate and error behavior.
- Predicted / Actual / Upcoming toggles: show or hide traces on chart.
- Historical Tracker table: row-level audit of target time, predicted value, actual value, error %, direction result, and status.
- Within Band (Historical Tracker): prediction and actual were close enough to be treated as acceptable inside the tolerance range, even if exact direction was not perfect.
How to Read Confidence Scores (Guidance Only)
- Historical Signal Confidence: this reflects how often recent resolved signals were directionally aligned (with tolerance handling for small deviations).
- If confidence is high but many signals are HOLD: this usually indicates low-move or range-bound conditions where expected price change is below action threshold; it is not a contradiction.
- If the score is around 80: it suggests stronger recent alignment than average, but it is still not a guarantee of next-signal outcome.
- Tracker Confidence: combines direction quality and error quality to indicate recent model stability in practical terms.
- Within Band / Correct / Outside Band: these labels help you judge closeness vs direction in context, not certainty.
- Use as guidance: treat both confidence metrics as decision support signals, and always apply your own risk controls.
Tutorial Scenarios (With Examples)
- Scenario 1 - What is Base Price (`from ...`): if Signal Board shows `5m Target 67870.65 from 67920.00`, then `67920.00` is the base used for direction and error context.
- Scenario 2 - Why a row can be `Correct` with non-zero error: if base is `67920.00`, predicted is `67870.65`, and actual is `67956.00`, direction may still be marked `Correct` when evaluated under platform direction logic even though error is `0.126%`.
- Scenario 3 - What `Within Band` means: if predicted and actual are not identical but remain close inside tolerance, row is marked `Within Band` (accepted closeness, not exact point match).
- Scenario 4 - What `Outside Band` means: prediction and actual diverged beyond tolerance, so row is not treated as acceptable proximity.
- Scenario 5 - What `Resolved` status means: target time has passed, actual market value is available, and tracker has completed evaluation.
- Scenario 6 - What `Upcoming` status means: target time has not passed yet, so final outcome is pending and will update after reconciliation.
- Scenario 7 - Why many `HOLD` signals can appear: expected move may be below actionable threshold in range-bound conditions; this indicates low-move environment, not necessarily model failure.
Terms & Risk Modal
- Full Name Signature: required acknowledgment before data access.
- Version: active legal/risk document version being accepted.
- I Accept: stores timestamped acceptance record.
Billing Page
- Premium Price: `$20/month` for full family access.
- Contact Billing: direct billing support mail action.