01
Engineering problem
A Hybrid score alone does not answer whether a trade should be opened now, which pair has priority, how portfolio exposure affects eligibility, or what should happen after the position is already open.
02
System response
The application evaluates the seven major FX pairs plus XAUUSD, builds ranked Top Picks, checks signal freshness and quality, market regime, confluence, cost, portfolio exposure, and safety rules, then produces traceable entry decisions. After entry, it keeps supervising positions and can issue HOLD, ADD, REDUCE, or EXIT commands as conditions change.
03
Engineering scope
- Multi-timeframe ATR strength loading and normalization across D1, H4, H1, M15, M5, and M1-style feeds.
- Pair- and currency-level directional analysis using Hybrid outputs, explicit probabilities, confidence fields, and fallback directional logic.
- Trade Picker / Top Picks ranking with configurable strength-gap, confidence, ATR, readiness, regime, and directional-streak filters.
- Stable UID-based position identity built from symbol, magic, side, open time, and open price rather than ticket continuity alone.
- Rule-based HOLD, EXIT, ADD, and REDUCE decisions with reason, confidence, export eligibility, cooldown, and blocking state.
- CSV command routing with SENT, ACKED, and DONE lifecycle visibility.
- Operator panels for ATR grid, directional strength, Top Picks, PM settings, live position snapshots, grouped logs, bridge state, and manual path testing.
- Selected Telegram notifications for signals, PM actions, and runtime visibility.
04
Architecture and responsibility layers
Market and model inputs
Reads Strong files by timeframe, pair/consolidated Hybrid output, Top Picks/debug data, position snapshots, and bridge feedback.
Python control layer
Calculates ATR/currency strength, directional context, candidate ranking, position-management decisions, runtime state, settings, and alert messages.
Execution bridge
Writes structured command rows and reads acknowledgement/completion files without placing broker orders directly from Python.
Operator interface
Provides monitoring, configuration, preview, diagnostics, command-lifecycle review, and manual execution-path testing.
05
Operating workflow
- Load multi-timeframe Strong files, Hybrid output, Top Picks-related inputs, position snapshots, and bridge feedback.
- Compute ATR-based currency strength and pair/currency directional context.
- Rank candidates and apply readiness, confidence, regime, directional, and strength filters.
- Read PM_Positions.csv, build stable position UIDs, and map open trades to the current signal environment.
- Assign HOLD, EXIT, ADD, or REDUCE with reason and safety state.
- Separate decision preview from send eligibility and actual command export.
- Write eligible commands to TradePicker_Commands.csv when auto mode and policy gates allow.
- Read TradePicker_Acks.csv and TradePicker_Done.csv to display command progress and outcome.
- Publish selected Telegram alerts and persist runtime/settings state for monitoring and diagnostics.
06
Data and command interfaces
| Interface | Direction | Purpose |
|---|---|---|
| D1/H4/H1/M15/M5/M1 Strong CSV files | Analysis feeds → dashboard | Supply multi-timeframe ATR and strength values for currency-level normalization and ranking. |
| Per-pair or consolidated Hybrid CSV | Hybrid engine → dashboard | Supplies Hybrid_Final, probabilities, confidence, scores, and directional context. |
| PM_Positions.csv | MetaTrader execution side → dashboard | Provides current open-position snapshots for UID mapping and management review. |
| TradePicker_Commands.csv | Dashboard → execution agent | Carries eligible entry or position-management command rows. |
| TradePicker_Acks.csv / TradePicker_Done.csv | Execution agent → dashboard | Reports acknowledgement and completion states for the command lifecycle. |
| Runtime/debug files and Telegram | Dashboard → operator/diagnostics | Publishes PM state, Top Picks diagnostics, grouped logs, and selected external alerts. |
07A
System outputs
- ATR and directional-strength grids
- Ranked Trade Picker and Top Picks candidates
- HOLD, EXIT, ADD, and REDUCE decisions with reasons
- Entry and management command CSV rows
- Acknowledgement/completion lifecycle state
- PM runtime JSON and Top Picks debug exports
- Telegram monitoring messages
07B
Safety and control layers
- Stale position snapshots can block management exports.
- Decision preview, send eligibility, and actual export are separate states for operator review and debugging.
- Per-action cooldowns, command throttling, maximum command rate, readiness/picks requirements, and ADD/REDUCE count limits constrain exports.
- Dry-run and disabled-export modes allow the decision engine to be inspected without sending commands.
08
Validation evidence
- The supplied public-demo validation report records Python syntax compilation, a Tkinter smoke test under a virtual display, five expected tabs, eight synthetic symbols, and package-manifest/SHA-256 generation.
- The public demo was checked for absence of network, subprocess, broker, CSV-bridge, and secret-loading imports.
- The demo is interface-only; those checks do not establish analytical accuracy, execution correctness, or trading suitability.
09
Public and private boundaries
Published evidence
Hybrid ingestion, currency-strength confirmation, candidate ranking, entry filtering, decision traces, position-management actions, command states, monitoring, and documented application captures.
Protected implementation
Full source, account and broker data, private signal values, exact filter thresholds, routing configuration, Telegram credentials, live positions, private datasets, and production state.
10
Interpretation and limitations
- The dashboard documents decision and position-management software; displayed states are not public trade recommendations.
- Execution is performed by the separate SignalFileTrader application, even when both programs are distributed or operated together.
- Real account data, broker settings, private thresholds, credentials, routing details, and live positions are excluded from public material.
11
Additional interface evidence
Repository-backup evidence
These captures come directly from the supplied GitHub backup and are displayed openly on this page.
Source details
Source: Currency-Strength-Position-Management-Dashboard/docs/screenshots/directional-strength.pngSource details
Source: Currency-Strength-Position-Management-Dashboard/docs/screenshots/fusion-table.pngSource details
Source: Currency-Strength-Position-Management-Dashboard/docs/screenshots/trade-picker-panel.pngSource details
Source: Currency-Strength-Position-Management-Dashboard/docs/screenshots/ppm-monitor.pngSource details
Source: Currency-Strength-Position-Management-Dashboard/docs/screenshots/pm-logs.pngSource details
Source: Currency-Strength-Position-Management-Dashboard/docs/screenshots/pm-settings.pngSource details
Source: Currency-Strength-Position-Management-Dashboard/docs/screenshots/execution-bridge-reduce.pngSource details
Source: Currency-Strength-Position-Management-Dashboard/docs/screenshots/telegram-alerts.pngSource details
Source: Currency-Strength-Position-Management-Dashboard/images/public-demo.pngPreviously documented portfolio evidence
