MQLPro — Production Architecture Breakdown · STEP 61MQLPro
STEP 61 — Production Architecture Breakdown
Translate the STEP 60 architecture baseline into concrete production components, service boundaries, interfaces, ownership domains, dependencies, and deployment boundaries.
Architecture: BASELINED
Implementation: NOT STARTED
Environment: DESIGN / PROTOTYPE
Production: NOT AUTHORIZED
Prototype boundary: This HTML page documents the intended production architecture. It does not create backend services, database connections, broker connectivity, authentication infrastructure, or live trading execution.
1. Production Component Registry
Architecture ownership map
UI-01
Web Frontend
Public marketplace, signals, community, account dashboard, administration and operational control interfaces.
API-01
API Gateway
External API boundary, request validation, rate limiting, authentication handoff, routing and API versioning.
IAM-01
Identity & Access
User identity, sessions/tokens, RBAC, privileged access, service identities and access policy enforcement.
STR-01
Strategy Service
Strategy registry, metadata, lifecycle, provider configuration and public strategy protection boundaries.
CPY-01
Copy Engine
Master signal intake, normalization, follower allocation, orchestration and copy-state management.
RSK-01
Risk Engine
Exposure, allocation, drawdown, eligibility, symbol restrictions and execution safety decisions.
ORD-01
Order Orchestrator
Order lifecycle state machine, idempotency, retries, acknowledgement handling and execution reconciliation.
BRK-01
Broker Connector Layer
Broker adapter abstraction, credentials boundary, execution transport and broker-specific normalization.
DAT-01
Data Platform
Transactional database, market data stores, configuration data, reporting data and durable state.
AUD-01
Audit & Evidence
Immutable event records, correlation, evidence packages, retention, legal hold and controlled export.
The production component boundaries are defined at the logical level. The gate remains open until the service contracts, database architecture, identity implementation, execution interfaces, security controls, infrastructure and operational mechanisms are implemented and validated in later production steps.
Protected proprietary logic. Entry rules, parameters and internal decision model are not publicly exposed.
Risk & Allocation
Recommended allocation is determined by the subscriber's own risk profile and account conditions. MQLPro can apply allocation limits, exposure limits and copy controls before execution.
Important Past performance does not guarantee future results.
Recent Trading Activity
Signal-level activity
Time
Symbol
Direction
Result
Duration
Return
Today 14:32
XAUUSD
BUY
Profit
2h 41m
+0.84%
Today 09:15
XAUUSD
SELL
Profit
1h 58m
+0.52%
Yesterday 16:07
XAUUSD
BUY
Loss
3h 12m
−0.31%
Yesterday 10:42
XAUUSD
BUY
Profit
5h 02m
+1.06%
Copy Configuration
Review broker connection and copy settings before execution.
Risk notice. Trading involves risk of loss. Historical performance and statistics are illustrative prototype data.
Home / Ranking
Ranking
Compare monitored trading signals using multiple performance and risk metrics.
SIGNALS TRACKED1,284
ACTIVE SIGNALS936
AVERAGE RETURN+24.8%
MEDIAN MAX DD8.42%
DATA PERIOD12 Months
Top Signals
Illustrative marketplace ranking
#
Signal
Return
Max DD
Profit Factor
Win Rate
Subscribers
Weeks
Risk / Return
1
Gold Strategy Pro
StrategyLab · Gold / XAUUSD
+82.40%
4.81%
2.14
74%
124
68
17.13
View →
2
FX Momentum MT5
AlgoWorks · Forex
+61.18%
6.20%
1.91
69%
96
51
9.87
View →
3
Quantum Gold
QuantForge · Gold / XAUUSD
+47.63%
7.15%
2.03
71%
78
43
6.66
View →
4
Index Flow Pro
DataEdge · Indices
+39.22%
5.17%
1.82
68%
63
47
7.58
View →
5
Atlas Swing System
NorthStar · Forex
+34.75%
6.41%
1.76
66%
51
82
5.42
View →
6
Vector Scalper Prime
VectorLabs · Forex
+31.60%
7.56%
1.69
72%
44
36
4.18
View →
How Ranking works
Ranking is designed as a discovery layer. Users can switch the displayed metric and period rather than treating a single number as a complete measure of a trading system. MQLPro can later calculate these rankings from verified account data.
Risk context
Return alone does not describe risk. Max drawdown, profit factor, consistency, trading history and account-level exposure should be reviewed together before copying a signal.
Ranking notice. The figures in this prototype are simulated. A production ranking engine should use verified performance records, defined calculation windows and anti-manipulation rules.
Home / Articles
Articles
Trading, markets, risk management and algorithmic trading knowledge.
Featured · Copy Trading
Building a Robust Cross-Broker Copy Trading System
What needs to happen between a master strategy and a follower account when brokers, symbols, execution rules and risk limits are not identical.
MQLPro Research · 16 Sep 2026 · 8 min read
MQLPro
Latest Articles
Knowledge Hub
COPY
Copy Trading
Building a Robust Cross-Broker Copy Trading System
Architecture, execution mapping and risk controls for cross-broker replication.
MQLPro Research · 8 min
RISK
Risk Management
Understanding Drawdown Before Copying a Signal
Why return alone is an incomplete description of a trading system.
Risk Desk · 6 min
DATA
Education
Profit Factor vs Win Rate: Reading Signal Statistics
Two commonly displayed metrics can tell very different stories.
MQLPro Education · 5 min
EA
MetaTrader
What an Expert Advisor Actually Does
A practical overview of automated execution, rules and platform constraints.
Platform Desk · 7 min
XAU
Market Analysis
Trading Gold: Understanding Volatility and Exposure
How volatility can affect position sizing and account-level exposure.
Market Desk · 6 min
RANK
Signals
How Signal Rankings Should Be Interpreted
Why rankings should be read together with the underlying performance metrics.
MQLPro Research · 4 min
Editorial note. MQLPro Articles are designed as an educational and research layer. Published analysis should distinguish historical data, methodology and opinion.
Building a Robust Cross-Broker Copy Trading System
MQLPro Research · 16 September 2026 · 8 min read
A cross-broker copy trading platform is not simply a mechanism for duplicating an order. The difficult part is maintaining the intended exposure when the master and follower accounts operate under different trading conditions.
1. Master signal
The master side produces a normalized trading event. The platform should separate the public signal representation from proprietary strategy logic, exposing only the information required by the follower and the risk engine.
2. Normalization layer
Before a follower receives an execution instruction, the platform needs to map symbols, contract specifications, volume rules and execution constraints. A BUY event on one broker is not automatically equivalent to the same raw order parameters on another broker.
3. Risk and allocation
Follower allocation can be proportional, fixed-risk or another defined model. Account equity, exposure limits, minimum volume and other broker constraints should be evaluated before an order is sent for execution.
4. Execution and reconciliation
A connector should report whether an instruction was accepted, rejected or partially executed. Reconciliation then compares the intended follower state with the actual account state so the platform can identify discrepancies.
5. Monitoring
A production platform should retain an auditable event history: signal received, risk checks applied, connector response and resulting account state. This is useful for operational monitoring and user transparency.
Prototype note. This article describes the intended platform architecture. It does not represent live broker connectivity or guarantee execution behavior.
Home / Community
Community
Discuss trading, strategies, platforms, automation and market research with other MQLPro users.
MQLPro Community
Ask questions, share research and discuss trading technology. Community content is separate from verified signal performance and marketplace listings.
AllUnansweredPopularFollowing
AR
How should symbol mapping work across different brokers?
Looking at a cross-broker copy architecture. How should the connector handle differences such as XAUUSD naming, contract size and minimum volume?
Copy TradingExecution
Arif R. · 18 replies · 642 views · 2h ago
DN
Which metrics do you check before following a signal?
I am comparing return, maximum drawdown, profit factor and trading history. Interested in how others organize the comparison.
SignalsRisk
Dimas N. · 27 replies · 1,204 views · 5h ago
FK
MT5 EA on VPS: what should I monitor?
Collecting a checklist for uptime, terminal connection, order execution and log monitoring for automated systems.
MetaTraderExpert Advisor
Fajar K. · 11 replies · 388 views · 1d ago
SA
Proportional allocation vs fixed-risk copying
What are the practical differences between proportional sizing and fixed-risk models when follower account balances vary?
Copy TradingRisk Management
Satria A. · 9 replies · 301 views · 1d ago
NR
How are you handling XAUUSD volatility?
Discussion about exposure limits and execution considerations when gold moves rapidly around major market events.
Market AnalysisGold
Nadia R. · 15 replies · 710 views · 2d ago
Community note. User discussions are community-generated and should not be treated as verified performance data, financial advice or an endorsement by MQLPro.
How should symbol mapping work across different brokers?
Arif R. · 16 September 2026 · 18 replies · 642 views
AR
Arif R.
Original post · 2h ago
Looking at a cross-broker copy architecture. How should the connector handle differences such as symbol naming, contract size, minimum volume and execution constraints? I am interested in the architecture rather than a specific broker.
QF
QuantForge
1h 42m ago
A normalization layer is useful. Keep the master event abstract, then map symbol, volume and execution rules for each follower account before sending the order.
AW
AlgoWorks
1h 18m ago
I would also keep reconciliation separate from execution. The connector should report the actual account state so the platform can detect differences between intended and executed positions.
SL
StrategyLab
54m ago
Risk checks should happen before the connector call. That allows allocation, exposure and broker-specific constraints to be evaluated consistently.
Join the discussion
Home / Documentation
Documentation
Guides and technical references for using the MQLPro platform.
Welcome to MQLPro Documentation
Start with the platform basics, then explore signal discovery, copy trading, market products, performance metrics, risk controls and connector architecture.
Get Started
Recommended path
01
Getting Started
Understand the platform, create an account and learn the basic workflow.
6 guides
02
Signals
Learn how to browse signals, inspect historical metrics and open signal details.
9 guides
03
Copy Trading
Architecture, allocation, execution, reconciliation and follower account concepts.
12 guides
04
Market
Browse products and understand product listings, versions and marketplace information.
7 guides
05
Ranking & Performance
Definitions and methodology for performance metrics displayed by MQLPro.
8 guides
06
Risk Management
Understand exposure, allocation limits, drawdown and account-level controls.
10 guides
07
Broker Connectors
Technical concepts for connecting follower accounts and handling broker differences.
11 guides
08
API & Webhooks
Integration concepts for future external applications and event-driven workflows.
5 guides
Documentation status. This prototype defines the public information architecture. Live broker APIs, authentication, webhooks and production connector behavior are not connected yet.
MQLPro is structured around signal discovery, performance research, marketplace products and copy-trading infrastructure. This documentation explains how those components are intended to work.
Core workflow
Browse the Signals marketplace and select a signal to inspect.
Review historical performance, drawdown and other available metrics.
Check the signal's risk information and subscription/copy settings.
Configure the follower allocation and applicable risk limits.
Connect the follower account through a supported connector.
Monitor execution and reconciliation after copying begins.
Important concepts
Signal
A signal represents a monitored trading strategy or account whose historical and current performance can be presented to users.
Follower
A follower is an account configured to replicate a signal according to its allocation and risk settings.
Connector
A connector is the integration layer responsible for translating platform instructions into broker-specific execution operations.
Prototype scope: examples on this page describe MQLPro's planned information architecture. Actual broker compatibility and execution behavior depend on the eventual connector implementation.
Use the documentation sidebar to explore the relevant module. For implementation questions, the Community section can provide a discussion layer while production integrations are developed.
Create your MQLPro account to follow signals, manage marketplace purchases and configure copy trading.
Already have an account? Login
Prototype. Account creation currently demonstrates the UI flow only. No credentials are stored.
Home / Account
My Account
Manage your profile, signals, purchases and copy-trading configuration.
IH
MQLPro User
user@example.com
Active Signals2
Subscriptions3
Market Purchases4
Copy Accounts1
Recent Activity
Activity
Status
Date
Subscribed to Alpha Trend
Active
16 Sep 2026
Added follower account
Connected
15 Sep 2026
Purchased Quantum Titan MT5
Completed
12 Sep 2026
Account layer. This page is the front-end foundation for the future MQLPro user system. Real authentication, subscriptions, purchases and broker connections will be wired to their respective back-end services later.
Home / Dashboard
Dashboard
Your MQLPro signals, subscriptions and copy-trading activity.
Welcome back, MQLPro User
Monitor your subscriptions and connected copy-trading accounts from one place.
Active Signals2
Monthly Subscriptions3
Copy Accounts1
Market Purchases4
My Signal Subscriptions
Alpha Trend
Forex · 12 Month subscription
+18.42%
DD 5.21%
Active
Gold Momentum
XAUUSD · 6 Month subscription
+12.61%
DD 4.81%
Active
Index Pulse
Indices · 3 Month subscription
+8.77%
DD 3.94%
Paused
Copy Trading Accounts
Account
Broker
Signal
Status
Last Sync
Primary Follower
Demo Broker
Alpha Trend
Connected
2 min ago
Quick Actions
Dashboard status. Subscription, payment, broker connectivity and execution values shown here are prototype data.
Browse Signals
Discover trading signals, compare performance metrics and open Signal Detail pages before subscribing.
My Signal Subscriptions
Alpha Trend
Forex · 12 Month subscription
+18.42%
DD 5.21%
Active
Gold Momentum
XAUUSD · 6 Month subscription
+12.61%
DD 4.81%
Active
Index Pulse
Indices · 3 Month subscription
+8.77%
DD 3.94%
Paused
Copy Trading Accounts
Account
Broker
Signal
Status
Last Sync
Primary Follower
Demo Broker
Alpha Trend
Connected
2 min ago
Connector status. The connected account is prototype data. Real broker authentication and execution will be connected later.
Review the product and complete the purchase setup.
MQLPro MARKET
Quantum Titan MT5
Trading Tool · MT5 · Version 2.4
1. License
Personal License
For use on your own supported trading account.
Commercial License
For eligible commercial or multi-account usage.
2. Account
3. Payment
Prototype. No real payment is processed. Product delivery and licensing will be connected in a later integration stage.
● Order created
Purchase Review
Your market purchase request has been prepared. Review the details below.
ProductQuantum Titan MT5
LicensePersonal
Amount$149
Prototype. Payment is simulated. No funds have been charged and no product has been delivered.
Home / Dashboard / Orders
Orders & Subscriptions
Manage your MQLPro signal subscriptions and Market purchases.
Signal Subscriptions
Market Purchases
3 subscriptions
Alpha Trend
Signal · Forex · 12 Month plan
$399
Active
Started16 Sep 2026
Renewal16 Sep 2027
Performance+18.42%
Max DD5.21%
Gold Momentum
Signal · XAUUSD · 6 Month plan
$249
Active
Started01 Sep 2026
Renewal01 Mar 2027
Performance+12.61%
Max DD4.81%
Index Pulse
Signal · Indices · 3 Month plan
$129
Paused
Started10 Aug 2026
Renewal10 Nov 2026
Performance+8.77%
Max DD3.94%
4 purchases
Quantum Titan MT5
Trading Tool · MT5 · Personal License
$149
Completed
Order IDMQL-24091
Purchased12 Sep 2026
Version2.4
DeliveryAvailable
Risk Manager Pro
Utility · MT5 · Personal License
$79
Completed
Order IDMQL-23872
Purchased08 Sep 2026
Version1.8
DeliveryAvailable
Prototype data. Billing, renewal, cancellation, license delivery and order history will be connected to the production account system in a later backend stage.
Home / Dashboard / Copy Accounts
Copy Trading Accounts
Connect follower accounts and manage their copy-trading configuration.
Connected Accounts1
Active Copies1
Last Sync2 min
Connection StatusConnected
Primary Follower
Follower Account · Alpha Trend
Connected
BrokerDemo Broker
PlatformMT5
Account•••• 4821
Copy StatusActive
Connect another follower account
Choose a supported broker connector and authorize the follower account. MQLPro will use the connector to receive and route eligible copy instructions.
Demo Broker — MT5 Connector
Primary Follower connection
Operational
TransportConnector
PlatformMT5
Last Heartbeat2 min ago
API StatusAvailable
Connector architecture
Broker authentication, signal routing and trade execution are separated into connector services. Credentials should never be exposed in the public Signal or Market interface.
Global Copy Settings
Risk: Copy trading does not guarantee identical execution or results between accounts. Slippage, spreads, latency, rejected orders and broker-specific conditions can affect follower performance.
Activity Log
Time
Event
Account
Status
22:14
Heartbeat received
Primary Follower
OK
22:12
Copy instruction synchronized
Primary Follower
Synced
22:03
Signal subscription checked
Alpha Trend
Active
21:48
Connector authenticated
Primary Follower
Connected
Home / Dashboard / Copy Accounts / Broker Connections
Broker Connector Center
Monitor broker connections, connector health and the copy-trading execution path.
Connector Overview
MQLPro separates the public marketplace from broker authentication and execution. A connector acts as the controlled bridge between a follower account and the MQLPro copy engine.
Active Connectors1
Connected Accounts1
Heartbeat2 min ago
System StatusOperational
Primary Connector
Demo Broker — MT5 Connector
TransportConnector
PlatformMT5
AuthenticationConnected
ExecutionReady
Supported Connections
These are prototype connector types. Production support will depend on broker infrastructure, platform capabilities and the connector implementation.
MT5 Direct Connector
MetaTrader 5 · Expert Advisor / terminal bridge
Available
Trade events · account state · execution routing · heartbeat
Broker API Connector
Broker-provided REST / WebSocket API
Setup Required
Depends on broker API access, permissions, authentication and order endpoints.
Python Execution Bridge
Local / hosted Python integration
Prototype
Can act as an execution bridge where the supported broker/platform interface permits it.
Custom Broker Connector
Broker-specific implementation
Setup Required
Used where a broker requires its own authentication, API or platform integration.
Connection Health
Operational indicators for the prototype connector.
AuthenticationOK
HeartbeatOK
Account ReadOK
Execution ChannelREADY
Recent Checks
Check
Result
Last Checked
Latency
Connector heartbeat
OK
22:14
84 ms
Account synchronization
OK
22:13
126 ms
Signal routing
READY
22:12
91 ms
Execution channel
READY
22:12
118 ms
Production note: A green health indicator in the UI must not be treated as proof that a broker supports every required API or execution operation. Capability verification belongs in the connector onboarding process.
Copy Execution Architecture
Logical flow for cross-broker copy trading. The public Signal page does not directly access follower broker credentials.
Signal Provider
→
MQLPro Signal Engine
→
Risk / Allocation
→
Connector
→
Follower Broker
The connector receives only the information required for the authorized account operation. The implementation may differ between MT5, broker APIs and other supported platforms.
Security boundary: Broker credentials, tokens and execution secrets should be isolated from the public marketplace UI and stored using appropriate server-side security controls.
Onboarding Requirements
Before activating a production connector, MQLPro should verify authentication, account read access, order placement/modification/cancellation, symbol mapping, position state, error handling, rate limits, heartbeat and disconnect recovery.
Home / Dashboard / Signal Engine
Signal Engine
Monitor master signals, normalized trade events and downstream copy routing.
Engine Overview
The Signal Engine converts authorized master activity into normalized events before risk allocation and connector execution. Public users see strategy performance, not broker credentials or execution secrets.
Master Signals12
Active Events3
Followers Routed47
Engine StatusOperational
Core Processing Flow
Master Account
→
Trade Event
→
Normalize
→
Risk / Allocation
→
Follower Queue
→
Connector
Execution boundary: The engine should not assume that a follower broker can execute the same symbol, volume, price or order type as the master. Mapping and validation occur before execution.
Master Signals
Prototype master strategies currently registered with the engine.
Signal
Asset Group
Followers
State
Alpha Trend
Forex
24
LIVE
Gold Momentum
XAUUSD
15
LIVE
Index Pulse
Indices
8
LIVE
Crypto Swing
Crypto
0
TEST
Normalized Trade Events
A normalized event is an internal representation. It is not a public copy instruction and does not expose a master's account credentials.
The routing layer resolves which authorized followers receive an eligible event and passes the result to the appropriate connector.
Signal
Followers
Risk Mode
Queue
Status
Alpha Trend
24
Proportional
Normal
Ready
Gold Momentum
15
Fixed Risk %
Normal
Ready
Index Pulse
8
Proportional
Normal
Ready
Important: Routing eligibility must check subscription status, follower account status, symbol mapping, risk limits and connector health before an execution request is created.
Engine Monitoring
Event Latency91 ms
Queue Depth3
Rejected Events0
Last Heartbeat22:14:02
Operational Checks
Component
Check
Result
Last Check
Event Listener
Master event intake
OK
22:14
Normalizer
Schema validation
OK
22:14
Risk Layer
Follower allocation
OK
22:14
Routing Queue
Dispatch readiness
OK
22:14
Home / Dashboard / Risk & Allocation
Risk & Allocation Engine
Apply follower-specific risk rules before an eligible copy instruction reaches a broker connector.
Risk Engine Overview
A master trade event is not copied blindly. The allocation layer evaluates each follower's subscription, account equity, configured risk mode, limits and instrument constraints.
Followers Evaluated47
Rules Applied142
Blocked Requests2
Engine StatusOperational
Processing Flow
Normalized Event
→
Subscription Check
→
Risk Profile
→
Volume Allocation
→
Safety Guards
→
Execution Request
Risk Rules
Prototype rules used to determine whether and how a signal is allocated to a follower.
Subscription ActiveFollower must have an eligible subscription.
Required
Pass
ENABLED
Account Drawdown GuardBlocks new exposure after the configured threshold.
10%
Current 3.2%
OK
Risk MultiplierScales the normalized master allocation.
1.00x
Follower profile
ACTIVE
Maximum ExposurePrevents exposure above account-level limits.
20%
Current 11.4%
OK
Instrument MappingRequires a valid follower symbol mapping.
Required
1 pending
CHECK
Default Risk Profile
Follower Allocation
Illustrative allocation results for a single normalized event. Values are prototype calculations, not live orders.
Follower
Equity
Risk Mode
Multiplier
Calculated Allocation
Eligibility
Primary Follower
$10,000
Proportional
1.00x
0.27 lot*
Eligible
Follower B
$5,000
Proportional
0.50x
0.07 lot*
Eligible
Follower C
$2,500
Fixed Risk %
1.00x
0.03 lot*
Eligible
Follower D
$1,000
Proportional
1.00x
—
Blocked
*Illustrative only. Final volume depends on the strategy's normalized risk input, instrument contract specifications, broker constraints, account currency, leverage and the follower's configuration. The UI must not imply guaranteed identical sizing across brokers.
Safety Guards
Hard checks that can stop an execution request before it reaches a connector.
Guard
Condition
Current
Action
Status
Max Drawdown
≥ 10%
3.2%
Block new copy
Clear
Max Exposure
≥ 20%
11.4%
Block new exposure
Clear
Connector Health
Not operational
Operational
Pause routing
Clear
Subscription
Inactive / expired
Active
Reject request
Clear
Symbol Mapping
Missing
1 pending
Reject request
Review
Allocation Simulation
Test the allocation logic with example account parameters before connecting a production execution path.
No simulation has been run.
Home / Dashboard / Execution Queue
Execution Queue
Track eligible copy requests from allocation through connector acknowledgement and final execution state.
Execution Overview
The queue is the controlled handoff between risk-approved follower instructions and broker connectors. Each request receives an internal identifier so its lifecycle can be audited.
Queued3
Processing1
Executed Today126
Failed2
Execution Flow
Risk Approved
→
Create Request
→
Queue
→
Connector
→
Broker
→
Acknowledge
→
Reconcile
Order Queue
Prototype requests waiting for or passing through the execution layer.
REQ-77102
Alpha Trend · Primary Follower · Position Open
XAUUSD · BUY · created 22:14:03 · connector MT5
PROCESSING
REQ-77101
Gold Momentum · Primary Follower · Position Update
XAUUSD · MODIFY · created 22:13:42 · connector MT5
22:14:02.251 — ReconciliationFollower position state queued for verification.
Reconciliation
Compare the expected internal state with the follower account state after connector execution.
Request
Expected
Follower State
Result
REQ-77102
Position Open
Pending check
VERIFY
REQ-77101
Position Modified
Modified
MATCH
REQ-77100
Position Closed
Closed
MATCH
REQ-77098
Position Open
Volume mismatch
REVIEW
Reconciliation matters: a successful connector response does not by itself prove that the final follower position matches the intended state. The production system should verify actual account state and handle partial fills, rejected orders and broker-side modifications.
Errors & Recovery
Failed requests should become observable and recoverable rather than silently disappearing.
Request
Failure
Action
Status
REQ-77098
Volume constraint
Recalculate / review
REVIEW
REQ-77091
Connector timeout
Retry with backoff
RECOVERED
REQ-77082
Symbol mapping missing
Block request
BLOCKED
Home / Dashboard / Account Synchronization
Account Synchronization
Maintain a consistent internal view of follower balances, positions and execution state across connected brokers.
Synchronization Overview
The synchronization layer continuously refreshes the platform's internal representation of follower accounts. It is separate from the signal engine: signals create intent, while synchronization verifies actual account state.
Connected Accounts47
Healthy45
Needs Review2
Last Sync22:14:05
State Synchronization Flow
Broker Connector
→
Account Snapshot
→
Normalize
→
Compare
→
Reconcile
→
Internal State
What is synchronized?
State
Purpose
Frequency
Status
Account Balance
Risk and exposure calculations
Periodic
ACTIVE
Open Positions
Copy state and reconciliation
Near real-time
ACTIVE
Pending Orders
Execution tracking
Near real-time
ACTIVE
Margin / Exposure
Safety guard evaluation
Periodic
ACTIVE
Connected Accounts
Illustrative follower account health across connector types.
Primary Follower
ACC-10021 · MT5 Connector
$10,000 equity
Last sync 22:14:05
HEALTHY
Follower B
ACC-10022 · MT5 Connector
$5,000 equity
Last sync 22:14:04
HEALTHY
Follower C
ACC-10023 · API Connector
$2,500 equity
Last sync 22:13:58
HEALTHY
Follower D
ACC-10024 · API Connector
$1,000 equity
Last sync 21:58:12
STALE
Privacy boundary: the dashboard should expose only the minimum account information required by the user. Broker credentials, API secrets and connector tokens should never be rendered in this page.
Follower Positions
Compare platform intent with the current broker-reported position state.
Account
Symbol
Side
Volume
Platform State
Broker State
Primary Follower
XAUUSD
BUY
0.27
Open
MATCH
Follower B
XAUUSD
BUY
0.07
Open
MATCH
Follower C
US500
SELL
0.03
Closed
MATCH
Follower D
XAUUSD
BUY
—
Blocked
NO ORDER
Balance & Exposure Snapshot
Illustrative account snapshots used by the risk layer.
Account
Balance
Equity
Margin Used
Exposure
Snapshot
Primary Follower
$10,120
$10,000
$1,220
11.4%
22:14:05
Follower B
$5,040
$5,000
$620
9.8%
22:14:04
Follower C
$2,520
$2,500
$310
8.1%
22:13:58
Reconciliation Center
Exceptions are retained until the platform state and broker state are aligned or an operator resolves the difference.
Reference
Mismatch
Detected
Suggested Action
Status
ACC-10024
Account snapshot stale
21:58
Refresh connector
OPEN
REQ-77098
Volume differs from intent
21:42
Review execution
OPEN
REQ-77091
Connector timeout
20:11
Verify broker state
RESOLVED
Home / Dashboard / Symbol Mapping
Symbol Mapping
Normalize instruments and broker-specific symbol names before a copy request reaches execution.
Symbol Mapping Overview
Cross-broker copy requires an instrument normalization layer. A strategy may publish one canonical instrument while individual brokers expose different symbol names, suffixes, contract sizes or trading constraints.
Canonical Symbols38
Broker Profiles7
Active Mappings214
Needs Review1
Normalization Flow
Master Symbol
→
Canonical Instrument
→
Broker Profile
→
Follower Symbol
→
Contract Validation
Why this layer exists
Difference
Example
Required Handling
Symbol name
XAUUSD / XAUUSD.a
Explicit mapping
Contract size
100 / broker-specific
Contract metadata
Volume step
0.01 / 0.10
Normalize and validate
Minimum volume
0.01 / 0.10
Broker constraint check
Trading session
Different market hours
Session eligibility
Active Mappings
Illustrative mappings from canonical MQLPro instruments to broker-specific symbols.
XAUUSD
Canonical · Gold Spot
XAUUSD.a
MT5 Profile A
VALID
XAUUSD
Canonical · Gold Spot
GOLD
API Profile B
VALID
EURUSD
Canonical · Euro / US Dollar
EURUSDm
MT5 Profile A
VALID
US500
Canonical · US Equity Index
SPX500.cash
API Profile B
REVIEW
Broker Profiles
A broker profile stores non-secret trading metadata required for safe normalization and execution validation.
Profile
Connector
Symbols
Metadata
Status
MT5 Profile A
MT5
82
Complete
ACTIVE
API Profile B
Broker API
61
Complete
ACTIVE
MT5 Profile C
MT5
43
Complete
ACTIVE
API Profile D
Broker API
28
1 missing
REVIEW
Security boundary: broker credentials, API keys and login secrets are connector secrets. They should be stored in the backend/secret store and never included in the symbol-mapping payload rendered to the browser.
Normalization Rules
Rules define how canonical instruments are translated into broker-specific execution parameters.
Rule
Purpose
Example
Status
Alias Mapping
Translate symbol aliases
XAUUSD → XAUUSD.a
ENABLED
Volume Step
Round to broker step
0.273 → 0.27
ENABLED
Minimum Volume
Reject unsupported size
0.03 below 0.10 → reject
ENABLED
Contract Size
Normalize sizing calculation
100 units
ENABLED
Session Check
Prevent closed-market requests
Outside trading session
ENABLED
Mapping Validation
Every execution request should pass instrument validation before entering the connector.
Check
Result
Details
Canonical symbol exists
PASS
XAUUSD registered
Follower symbol mapped
PASS
XAUUSD.a
Contract metadata
PASS
Available
Volume constraints
PASS
Step 0.01
Trading session
PASS
Open
Home / Dashboard / Copy Policies
Copy Policies
Define how a follower subscription may translate a strategy signal into an eligible copy instruction.
Copy Policy Overview
Policies sit between a published strategy and the execution queue. They determine whether a signal is eligible for a specific follower before sizing and broker execution occur.
Active Policies32
Protected Accounts47
Rules Evaluated Today4,821
Blocked Requests17
Policy Evaluation Flow
Signal
→
Subscription
→
Safety Rules
→
Allocation
→
Exposure Limit
→
Execution
Policy Principles
Principle
Purpose
Example
Explicit opt-in
Only subscribed accounts receive copies
Active subscription required
Risk bounded
Respect account-level limits
Maximum DD / exposure
Broker aware
Respect follower constraints
Volume and session checks
Fail closed
Reject uncertain requests
Missing mapping → block
Safety Rules
Rules that can stop a copy request before it reaches the execution layer.
Maximum Drawdown Guard
Block new exposure when configured account drawdown threshold is reached.
10%
ENABLED
Maximum Exposure
Prevent new positions when total strategy exposure exceeds the account policy.
25%
ENABLED
Daily Loss Guard
Stop eligible new requests after the configured daily loss limit.
3%
ENABLED
Symbol Eligibility
Reject symbols not mapped or explicitly permitted for the follower.
Strict
ENABLED
Trading Session
Reject requests outside the follower broker's supported session.
Broker
ENABLED
Allocation Policy
Choose the sizing model applied after a request passes subscription and safety checks.
Mode
Calculation Basis
Use Case
Status
Proportional Equity
Follower equity / reference equity
Scale strategy exposure
AVAILABLE
Risk Percentage
Target risk per position
Risk-normalized copying
AVAILABLE
Fixed Lot
Configured volume
Simple volume policy
AVAILABLE
Multiplier
Base size × multiplier
Controlled scaling
AVAILABLE
Important: allocation is a calculation policy, not a guarantee of identical broker exposure. Contract size, leverage, minimum volume, volume step and execution conditions must still be validated by the broker profile.
Exposure Limits
Account-level and strategy-level limits provide a second control layer after position sizing.
Limit
Configured
Current
Action
Strategy Exposure
25%
11.4%
ALLOW
Symbol Exposure
15%
8.2%
ALLOW
Daily Loss
3%
0.7%
ALLOW
Open Positions
20
7
ALLOW
Emergency Controls
Operational controls for temporarily stopping new copy instructions. Existing broker positions are not automatically altered by these controls unless a separate close-position policy is explicitly implemented.
Control
Current State
Effect
Global Copy Pause
OFF
Stops new copy requests globally
Strategy Pause
OFF
Stops a selected strategy
Account Pause
OFF
Stops copying to selected follower
New Exposure Lock
OFF
Blocks new positions while allowing state sync
Production requirement: emergency controls should be enforced server-side. A browser-only toggle is not a reliable trading safety mechanism.
Home / Dashboard / Subscription & Billing
Subscription & Billing
Manage signal subscriptions, billing status and copy-trading entitlements.
Subscription & Billing Overview
Billing determines whether a user has an active commercial entitlement to copy a selected signal. Payment state and trading authorization should remain separate backend concepts.
Active Subscriptions84
Monthly Recurring$8,420
Pending Renewal6
Payment Issues2
Entitlement Flow
Signal Selected
→
Checkout
→
Payment
→
Subscription
→
Entitlement
→
Copy Eligible
Billing States
State
Meaning
Copy Access
Active
Paid and within subscription period
ELIGIBLE
Pending
Payment or activation not finalized
HOLD
Past Due
Renewal payment requires attention
POLICY
Cancelled / Expired
Entitlement period ended
NOT ELIGIBLE
Active Subscriptions
Subscriptions connect a user to a signal product and its commercial terms.
Alpha Trend
SUB-10421 · Monthly · Next renewal 01 Oct 2026
$99/mo
Auto renewal
ACTIVE
Gold Momentum
SUB-10418 · Monthly · Next renewal 28 Sep 2026
$129/mo
Auto renewal
ACTIVE
Index Pulse
SUB-10402 · Quarterly · Ends 12 Nov 2026
$249/qtr
Manual renewal
ACTIVE
EUR Scalper
SUB-10387 · Monthly · Payment requires attention
$79/mo
Renewal failed
PAST DUE
Signal Plans
Commercial plans are separate from the strategy's performance and risk metrics.
Plan
Billing
Price
Copy Entitlement
Status
Alpha Trend Standard
Monthly
$99
1 strategy
ACTIVE
Alpha Trend Pro
Monthly
$149
3 strategies
ACTIVE
Portfolio Access
Monthly
$249
10 strategies
ACTIVE
Trial
Limited
$0
Read-only / configured trial
LIMITED
Architecture rule: the frontend should never decide that payment equals trading authorization. A backend entitlement service should validate subscription status, product scope, expiry and any account-specific conditions before copy eligibility is granted.
Invoices & Payments
Illustrative billing records. Payment provider references should be stored securely and only safe display fields exposed here.
Invoice
Subscription
Amount
Date
Status
INV-2026-09121
Alpha Trend
$99
01 Sep 2026
PAID
INV-2026-09118
Gold Momentum
$129
28 Aug 2026
PAID
INV-2026-09103
EUR Scalper
$79
01 Sep 2026
PAST DUE
INV-2026-09088
Index Pulse
$249
12 Aug 2026
PAID
Copy Entitlements
Entitlement is the final authorization state consumed by the copy engine. It should be independently queryable and auditable.
User / Account
Signal
Subscription
Expires
Copy Access
Primary Follower
Alpha Trend
SUB-10421
01 Oct 2026
GRANTED
Follower B
Gold Momentum
SUB-10418
28 Sep 2026
GRANTED
Follower C
Index Pulse
SUB-10402
12 Nov 2026
GRANTED
Follower D
EUR Scalper
SUB-10387
01 Sep 2026
SUSPENDED
Copy eligibility check: entitlement should be evaluated together with risk policy, broker connectivity, symbol mapping and account safety state. An active subscription alone does not override a safety block.
Home / Dashboard / Signal Intake
Signal Intake Gateway
Receive, validate, deduplicate and normalize external strategy events before they enter the MQLPro signal engine.
Signal Intake Overview
The intake gateway is the boundary between external strategy providers and the internal copy-trading pipeline. It should accept only authenticated, schema-valid events and assign a unique event identity before processing.
Production rule: the intake gateway should treat the event ID as an idempotency key. A repeated event must not create a second copy instruction.
Signal Endpoints
Endpoints represent controlled ingestion channels. Secrets and signing keys are never rendered in the browser.
Strategy Alpha Webhook
POST · /v1/signals/alpha · HMAC signature
18,102 events
Last: 14:32 UTC
ACTIVE
Gold Momentum API
POST · /v1/signals/gold · API key + timestamp
6,841 events
Last: 14:31 UTC
ACTIVE
Index Pulse Webhook
POST · /v1/signals/index · HMAC signature
3,214 events
Last: 14:29 UTC
ACTIVE
Legacy Connector
POST · /v1/legacy/signals · migration pending
264 events
Last: 11:02 UTC
REVIEW
Event Log
Operational view of received events and their intake disposition.
Event ID
Source
Instrument
Action
Received
Status
evt_8F21A
Strategy Alpha
XAUUSD
OPEN BUY
14:32:11
ACCEPTED
evt_8F219
Strategy Alpha
EURUSD
CLOSE
14:31:48
ACCEPTED
evt_8F217
Gold Momentum
XAUUSD
OPEN SELL
14:30:02
DUPLICATE
evt_8F211
Legacy Connector
US500
OPEN BUY
14:27:39
REJECTED
Validation Pipeline
Validation should happen before an event becomes an internal signal instruction.
Check
Purpose
Example Result
Authentication
Verify source identity/signature
PASS
Timestamp Window
Reject stale or replayed requests
PASS
Schema
Require valid event structure
PASS
Idempotency
Prevent duplicate processing
PASS
Strategy State
Confirm strategy is allowed to publish
PASS
Instrument
Confirm canonical symbol exists
PASS
Intake Security
The gateway should be treated as a security boundary. Authentication, replay protection and rate controls belong on the server.
Control
Configuration
Status
Request Signing
HMAC / provider signature
ENABLED
Timestamp Validation
± 5 minutes
ENABLED
Idempotency
Event ID required
ENABLED
Rate Limiting
Provider-specific
ENABLED
Secret Storage
Server-side secret store
REQUIRED
Do not expose: API keys, webhook signing secrets, broker credentials, private connector tokens or raw authentication headers in frontend HTML or client-side JavaScript.
Home / Dashboard / Copy Orchestrator
Copy Orchestrator
Coordinate an approved signal from intake through follower order lifecycle, with deterministic state transitions and reconciliation.
Copy Orchestrator Overview
The orchestrator coordinates already-validated instructions. It should not blindly mirror a broker order; it creates an auditable lifecycle for each follower request and preserves idempotency across retries.
Requests Today4,821
Executed4,674
In Flight23
Exceptions7
Copy Lifecycle
Canonical Signal
→
Eligibility
→
Risk / Allocation
→
Symbol Mapping
→
Copy Request
→
Broker Execution
→
Broker Result
→
Reconcile
State Model
State
Meaning
Next Transition
RECEIVED
Canonical signal accepted
ELIGIBILITY_CHECK
ELIGIBLE
Follower passed policy checks
QUEUED
QUEUED
Waiting for connector execution
SUBMITTED
SUBMITTED
Broker request sent
EXECUTED / REJECTED
EXECUTED
Broker acknowledged execution
RECONCILED
EXCEPTION
Unexpected or unresolved state
RECOVERY / REVIEW
Order Lifecycle
A copy request gets its own lifecycle ID so the system can distinguish a signal event, a follower request and the broker's resulting order/deal.
COPY-8F21-001 · Alpha / Follower A
XAUUSD · BUY · target 0.27 lot
14:32:11
Broker: MT5-A
RECONCILED
COPY-8F21-002 · Alpha / Follower B
XAUUSD · BUY · target 0.14 lot
14:32:12
Broker: API-B
EXECUTED
COPY-8F21-003 · Alpha / Follower C
EURUSD · CLOSE
14:31:48
Broker: MT5-C
RETRY
COPY-8F20-991 · Gold / Follower D
XAUUSD · SELL · blocked by policy
14:30:02
Broker: API-D
BLOCKED
Copy Requests
Each request carries the source event, follower account, policy version, mapped instrument and execution intent.
Request ID
Source Event
Follower
Intent
Status
COPY-8F21-001
evt_8F21A
Follower A
OPEN BUY 0.27
RECONCILED
COPY-8F21-002
evt_8F21A
Follower B
OPEN BUY 0.14
EXECUTED
COPY-8F21-003
evt_8F219
Follower C
CLOSE
RETRY
COPY-8F20-991
evt_8F217
Follower D
OPEN SELL
BLOCKED
Idempotency rule: the request ID should remain stable through retries. A timeout after submission must not automatically create a new broker order unless the connector can safely determine the prior request's outcome.
Retries & Recovery
Transient connector failures require controlled retries. Permanent policy or validation failures should not be retried as if they were network failures.
Failure
Classification
Action
Status
Network timeout
Transient
Retry with bounded backoff
RETRYABLE
Rate limit
Transient
Respect retry-after / backoff
RETRYABLE
Invalid volume
Permanent
Recalculate or reject
NO RETRY
Market closed
Conditional
Apply session policy
POLICY
Unknown broker result
Critical
Query broker before retry
RECONCILE
Execution Reconciliation
Reconciliation compares the intended copy state with the broker's observed state. This closes the loop between order submission and actual account state.
Request
Intent
Broker State
Match
Action
COPY-8F21-001
BUY 0.27
BUY 0.27
YES
Close lifecycle
COPY-8F21-002
BUY 0.14
BUY 0.14
YES
Close lifecycle
COPY-8F21-003
CLOSE
Position still open
NO
Investigate
14:32:12 · Broker acknowledgementCOPY-8F21-002 accepted by connector.
14:32:13 · Account syncFollower B position observed at broker.
14:32:13 · ReconciliationRequested volume and observed volume match.
Home / Dashboard / Broker Connector
Broker Connector Runtime
Manage the runtime layer that translates approved copy requests into broker-specific execution commands and returns normalized results.
Broker Connector Overview
The connector is the broker-facing execution boundary. MQLPro should send a normalized execution intent and receive a normalized result regardless of whether the underlying adapter uses MT5, a broker API, FIX or another supported transport.
Design rule: broker-specific credentials and transport details stay inside the connector service. The orchestrator should not need to know how an individual broker executes the request.
Connector Registry
Each adapter has its own capability profile, transport and health state.
REST API · 12 accounts · authentication renewal required
Latency —
Last heartbeat 13:57
ATTENTION
Runtime Workers
Workers consume execution jobs, communicate with broker adapters and publish normalized outcomes.
Worker
Queue
Throughput
Last Heartbeat
Status
worker-eu-01
execution.eu
142/min
14:32:12
RUNNING
worker-ap-02
execution.ap
118/min
14:32:11
RUNNING
worker-us-01
execution.us
96/min
14:32:10
RUNNING
worker-recovery-01
recovery
7/min
14:32:08
STANDBY
Connector Health
Health monitoring should cover transport availability, authentication, latency, execution acknowledgements and account synchronization.
Check
Expected
Observed
Status
Transport
Reachable
Reachable
PASS
Authentication
Valid
Valid
PASS
Heartbeat
< 30 sec
4 sec
PASS
Execution ACK
Received
Received
PASS
Account Sync
Current
Current
PASS
API credential renewal
Valid
Pending
ATTENTION
Connector Credentials
Credentials are represented only by safe metadata in this UI. Secret values must be managed by the backend or a dedicated secret-management system.
Connector
Credential Type
Last Rotated
Expiry
Status
MT5 Connector A
Terminal / bridge credential
01 Sep 2026
Not applicable
HEALTHY
Broker API B
OAuth / API token
15 Aug 2026
15 Nov 2026
HEALTHY
Broker API D
API token
01 Jun 2026
20 Sep 2026
RENEW
Security boundary: never place broker passwords, API secrets, private keys or access tokens in frontend source, localStorage or URL parameters.
Home / Dashboard / Account Sync & Reconciliation
Account Sync & Reconciliation
Compare intended copy state with broker-observed account state and resolve differences before they become persistent drift.
Account Sync Overview
Synchronization closes the loop between MQLPro's internal ledger and the real state reported by connected broker accounts.
Accounts Monitored247
Positions Synced1,284
Matched1,276
Exceptions8
Synchronization Flow
Copy Intent
→
Broker Execution
→
Broker State
→
Account Snapshot
→
Compare
→
Reconcile
→
Audit
Reconciliation Principles
Principle
Purpose
Result
Source of truth
Broker state is observed independently
Current account snapshot
Idempotency
Repeated sync must not duplicate actions
Stable state
Drift detection
Find intent/state differences
Exception generated
Safe recovery
Do not blindly force an order
Policy-based action
Connected Accounts
Account health and last observed snapshot for connected follower accounts.
Follower A · MT5-A
acct_1024 · Equity $10,842 · 4 open positions
14:32:14
Snapshot age 2 sec
SYNCED
Follower B · API-B
acct_1138 · Equity $7,214 · 2 open positions
14:32:13
Snapshot age 3 sec
SYNCED
Follower C · MT5-C
acct_1202 · Equity $15,901 · 7 open positions
14:32:12
Snapshot age 4 sec
SYNCED
Follower D · API-D
acct_1320 · Last broker snapshot incomplete
14:28:57
Snapshot age 3m 17s
STALE
Position Reconciliation
Compare expected follower positions with broker-observed positions after execution.
Account
Symbol
Expected
Observed
Match
Follower A
XAUUSD
BUY 0.27
BUY 0.27
MATCH
Follower B
XAUUSD
BUY 0.14
BUY 0.14
MATCH
Follower C
EURUSD
FLAT
BUY 0.10
DRIFT
Follower D
US500
BUY 0.05
UNKNOWN
STALE
Drift handling: a mismatch should first create an exception and trigger a fresh broker query. Automatic corrective trading should require an explicit, policy-approved recovery path.
Order Reconciliation
Order-level checks link MQLPro request IDs to broker order/deal identifiers.
Copy Request
Broker Ref
Requested
Observed
Status
COPY-8F21-001
MT5 #7812401
BUY 0.27
BUY 0.27
MATCH
COPY-8F21-002
API-B #99218
BUY 0.14
BUY 0.14
MATCH
COPY-8F21-003
Pending lookup
CLOSE
Position open
DRIFT
COPY-8F20-991
None
BUY 0.05
Blocked
EXPECTED
Sync Exceptions
Exceptions require deterministic handling rather than silent correction.
Exception
Account
Cause
Recommended State
Status
EXC-2031
Follower C
Unexpected EURUSD position
Investigate
OPEN
EXC-2029
Follower D
Stale account snapshot
Refresh
OPEN
EXC-2024
Follower A
Delayed broker acknowledgement
Re-query
REVIEW
Home / Dashboard / Observability & Audit
Observability & Audit Center
Monitor the copytrade pipeline, investigate incidents, and maintain an immutable operational trail from signal intake to broker reconciliation.
Observability Overview
A cross-layer operational view of MQLPro. Metrics here describe system state and processing health, not trading performance.
Pipeline Events / min486
Successful Actions99.72%
Open Incidents3
Audit Events Today18,742
End-to-End Health
Signal Intake
Webhook validation, authentication and deduplication
82 events/min
Latency 21 ms
HEALTHY
Copy Orchestrator
Eligibility, allocation and request lifecycle
164 req/min
Latency 38 ms
HEALTHY
Broker Connectors
18 adapters / 247 connected accounts
217 req/min
Latency 91 ms
ATTENTION
Account Reconciliation
Position and order state comparison
1,284 positions
8 exceptions
ATTENTION
Pipeline Health
Monitor processing stages independently so a failure in one layer does not become an invisible failure across the whole system.
Stage
Throughput
Latency
Error Rate
Status
Signal Intake
82/min
21 ms
0.08%
HEALTHY
Signal Engine
82/min
14 ms
0.02%
HEALTHY
Risk Engine
79/min
18 ms
0.11%
HEALTHY
Execution Queue
164/min
7 ms
0.03%
HEALTHY
Broker Connector
157/min
91 ms
0.42%
WATCH
Reconciliation
1,284 snapshots
4 sec
0.62%
WATCH
Event Log
Operational events are correlated by event ID, request ID, account ID and connector ID.
2026-09-16 14:32:14 INFO evt_8F21A COPY-8F21-001 reconciliation.match
2026-09-16 14:32:13 INFO evt_8F21A COPY-8F21-002 broker.execution_ack
2026-09-16 14:32:12 INFO evt_8F21A COPY-8F21-002 connector.submit
2026-09-16 14:32:11 INFO evt_8F21A COPY-8F21-001 execution.queued
2026-09-16 14:32:10 INFO evt_8F21A — risk.approved
2026-09-16 14:32:09 INFO evt_8F21A — signal.normalized
2026-09-16 14:32:08 INFO evt_8F21A — intake.accepted
2026-09-16 14:31:49 WARN evt_8F219 COPY-8F21-003 broker.result.timeout
2026-09-16 14:31:48 INFO evt_8F219 COPY-8F21-003 retry.scheduled
Incident Center
Incidents group related failures so operators investigate the root cause rather than treating every retry as a separate problem.
INC-1042 · API-D authentication renewal
Connector: Broker API D · first detected 13:57
17 min
3 accounts
OPEN
INC-1041 · Position drift
Follower C · EURUSD unexpected open position
18 min
1 account
OPEN
INC-1040 · Broker timeout burst
Connector C · 7 requests affected
22 min
7 requests
INVESTIGATING
Audit Trail
Audit records should answer who or what performed an action, what changed, when it happened, and which object was affected.
Time
Actor
Object
Action
Result
14:32:14
system/reconciler
COPY-8F21-001
RECONCILE
MATCH
14:32:12
connector/mt5-a
COPY-8F21-001
EXECUTE
ACK
14:32:10
risk-engine
evt_8F21A
APPROVE
PASS
14:32:08
intake-gateway
evt_8F21A
ACCEPT
VALID
14:28:57
system/sync
acct_1320
SNAPSHOT
STALE
14:32:08 · Signal acceptedGateway assigned correlation ID evt_8F21A.
14:32:10 · Risk approvedPolicy evaluation produced an approved copy intent.
14:32:12 · Broker acknowledgedConnector returned a broker reference.
14:32:14 · ReconciledObserved broker state matched intended state.
Audit rule: audit history should be append-only in production. Administrative corrections should create a new audit event instead of silently modifying the historical record.
Home / Dashboard / Security & Access Control
Security & Access Control
Control identities, permissions, sessions and sensitive operational actions across the MQLPro platform.
Security Overview
Security boundaries are separated from trading logic. Authentication establishes identity; authorization determines which operations that identity may perform.
Active Users1,284
Active Sessions417
API Credentials63
Open Security Alerts2
Security Layers
Identity & Authentication
Login, session validation and multi-factor authentication policy
1,284 users
0.12% failures
HEALTHY
Authorization
Role and permission checks for dashboard and API actions
42 policies
100% enforced
ACTIVE
Credential Security
Broker secrets and API credentials kept outside frontend state
63 credentials
2 renewals
REVIEW
Privileged Actions
Reset, disable, rotate, reconnect and recovery operations
18 today
100% audited
AUDITED
Production rule: the frontend is not a security boundary. Every privileged operation must be authorized again by the backend, even if the UI hides the corresponding button.
Roles & Permissions
Use least privilege: an identity receives only the permissions required for its operational responsibilities.
Sessions should be short-lived where appropriate, revocable server-side and bound to an authenticated identity.
Session
Role
Last Activity
Device
Status
sess_7A91
Platform Admin
14:32:18
Chrome / Windows
ACTIVE
sess_8B22
Risk Operator
14:31:49
Chrome / macOS
ACTIVE
sess_19F2
Support
12:08:21
Firefox / Linux
IDLE
sess_0A17
Unknown
09:17:02
Unrecognized device
REVOKED
API Access
API credentials should be scoped, rotated and revocable. Secret material is intentionally never rendered here.
connector-api-prod
Broker connector service · execution scope
Last used 14:32
Expires 2026-11-15
VALID
reconciler-prod
Account snapshots · read + reconciliation scope
Last used 14:32
Expires 2027-01-10
VALID
legacy-import
Historical migration · no live execution scope
Last used 2026-08-12
Expired
DISABLE
Sensitive Actions
High-impact actions should require explicit authorization, server-side policy checks and an audit record.
Action
Required Permission
Extra Control
Audit
Status
Rotate broker credential
security.credential.rotate
Re-authentication
Required
ENFORCED
Reconnect connector
platform.connector.manage
Confirmation
Required
ENFORCED
Manual reconciliation recovery
account.reconcile.recover
Reason + confirmation
Required
ENFORCED
Change risk policy
risk.policy.manage
Admin approval
Required
ENFORCED
Revoke session
security.session.revoke
None
Required
ENFORCED
Defense in depth: hiding a control in the UI does not protect the API. Authorization must be enforced at the service boundary for every request.
Home / Dashboard / Production Readiness
Production Readiness & Deployment
Validate the platform before production deployment with explicit release gates, dependency checks, rollback readiness and operational sign-off.
Production Readiness Overview
This control layer separates “the UI works” from “the system is safe to operate in production.” Every critical dependency must have an explicit state.
Readiness Checks28 / 30
Critical Blockers0
Warnings2
Rollback ReadyYES
Release Gates
Application & Routing
All dashboard routes resolve and protected pages remain access-controlled.
100%
0 blockers
PASS
Trading Pipeline
Signal → risk → queue → connector → reconciliation path is defined.
100%
0 blockers
PASS
Security Controls
Authentication, authorization, credential and audit boundaries documented.
93%
2 warnings
REVIEW
Operational Recovery
Incident, reconciliation and rollback procedures are represented.
92%
2 warnings
REVIEW
Important: a passing frontend prototype is not evidence that live trading is production-safe. Real broker credentials, backend authorization, durable storage, monitoring and tested recovery procedures must exist outside this HTML prototype.
Readiness Checks
A production release should fail closed when a critical dependency is unavailable or an essential safety control has not been verified.
Check
Area
Evidence
Gate
Status
Frontend route integrity
Application
Dashboard navigation
Required
PASS
Authentication & session policy
Security
Security control definition
Required
PASS
Server-side authorization
Security
Permission model
Critical
VERIFY BACKEND
Credential secret storage
Broker
Secret manager integration
Critical
VERIFY
Idempotent execution
Execution
Request ID / deduplication
Critical
DEFINED
Broker reconciliation
Operations
Expected vs observed state
Critical
DEFINED
Backup & restore test
Infrastructure
Restore evidence
Required
PENDING
Incident response test
Operations
Game-day record
Required
PENDING
Release Control
Production deployment should be versioned, traceable and reversible. No direct “deploy now” action is implied by this prototype.
Current Release · mqlpro-web 0.29.0
Baseline: STEP 29 · Security & Access Control
2026-09-16
Build verified
CURRENT
Candidate Release · mqlpro-web 0.30.0
Includes Production Readiness & Deployment control layer
Pending
Pre-production
CANDIDATE
Release Freeze
Freeze live execution changes during an active incident unless emergency procedure is invoked.
Policy
Incident linked
ENABLED
Rollback Readiness
Rollback is a controlled restoration to a known-good application version. It must not be confused with reversing a financial trade.
Control
Current State
Required Evidence
Status
Previous known-good build
0.29.0
Immutable artifact
READY
Database migration compatibility
Backward compatible
Migration test
VERIFY
Configuration snapshot
Versioned
Restore test
READY
Connector compatibility
Tracked
Adapter version matrix
READY
Operator procedure
Documented
Game-day rehearsal
PENDING
Separation of concerns: application rollback restores software state. It does not automatically undo broker-side executions or close positions. Those are separate operational workflows requiring reconciliation.
Production Sign-off
Final release approval should be explicit and attributable. The prototype records the structure of the sign-off, not a real production authorization.
Owner
Area
Evidence
Decision
Status
Engineering
Application
Build & route checks
Approve
RECORDED
Security
Access & secrets
Backend verification
Pending
PENDING
Operations
Recovery
Incident rehearsal
Pending
PENDING
Trading Operations
Execution
Connector & reconciliation test
Pending
PENDING
Release gate: all critical backend, credential, recovery and broker-integration checks must be independently verified before any real-money deployment.
Home / Dashboard / Infrastructure & Service Health
Infrastructure & Service Health
Monitor the runtime dependencies that keep the MQLPro trading pipeline available, responsive and recoverable.
Infrastructure Overview
Infrastructure health is separate from trading logic. A healthy service does not imply a successful trade; it means the dependency is available to perform its defined role.
Services Healthy14 / 15
API Availability99.98%
Queue Depth12
Recovery Readiness94%
Critical Dependencies
API Gateway
Authentication, routing and inbound service boundary
12 ms
99.99%
HEALTHY
Application Services
Signal, risk, orchestration and account services
28 ms
99.98%
HEALTHY
Message Queue
Durable execution and event processing
12 pending
0 stuck
HEALTHY
Database
Users, subscriptions, ledger, configuration and audit metadata
18 ms
99.99%
HEALTHY
Secrets / Configuration
Runtime credentials and environment configuration
Rotation due
2 items
REVIEW
Operational boundary: infrastructure monitoring detects dependency failures. It should not silently retry financial actions without the execution policy and idempotency controls defined by the trading pipeline.
Service Health
Each service has an independent health state and dependency relationship.
Service
Instance
Latency
Error Rate
Status
Signal Intake
3 / 3
21 ms
0.08%
HEALTHY
Signal Engine
3 / 3
14 ms
0.02%
HEALTHY
Risk Engine
3 / 3
18 ms
0.11%
HEALTHY
Copy Orchestrator
4 / 4
38 ms
0.03%
HEALTHY
Connector Runtime
12 / 13
91 ms
0.42%
DEGRADED
Reconciliation
3 / 3
4 sec
0.62%
WATCH
Database Health
Database state supports operational records, configuration, subscriptions and audit metadata. Financial execution state should remain consistent with the broker reconciliation model.
Primary Database
Read/write workload · application state
18 ms
Healthy
ONLINE
Read Replica
Read workload · reporting and dashboard queries
24 ms
Lag 0.4 sec
ONLINE
Backup Snapshot
Latest verified snapshot
02:00 UTC
Age 12h
AVAILABLE
Restore Test
Last complete recovery rehearsal
2026-09-02
14 min
RETEST
Queue Health
Queues isolate asynchronous work and provide durable request state. Every financial execution message should have an idempotency key or equivalent deduplication mechanism.
Queue
Depth
Oldest
Retry
Status
signal-events
0
—
0
HEALTHY
execution-requests
7
1.8 sec
1
HEALTHY
broker-results
3
0.9 sec
0
HEALTHY
reconciliation
2
2.1 sec
1
HEALTHY
dead-letter
0
—
0
EMPTY
Recovery Readiness
Recovery controls restore service availability while preserving the integrity of execution and reconciliation records.
Control
Last Test
Target
Evidence
Status
Service restart
2026-09-15
< 2 min
Runbook #SR-12
PASS
Database restore
2026-09-02
< 30 min
Restore #DB-44
RETEST
Queue replay
2026-09-10
No duplicates
Replay #Q-19
PASS
Connector failover
2026-09-11
Controlled
Failover #CX-07
PASS
Audit continuity
2026-09-12
No gaps
Audit #AU-31
PASS
Recovery distinction: restoring infrastructure does not authorize new trades, cancel broker orders, or close positions. After recovery, reconciliation must establish the actual broker state before normal execution resumes.
Home / Dashboard / Disaster Recovery & Business Continuity
Disaster Recovery & Business Continuity
Define how MQLPro continues operating, contains failures and restores service without losing execution or audit integrity.
Recovery Overview
Disaster recovery is broader than restarting servers. The objective is to restore critical services while preserving durable execution state, account reconciliation and audit continuity.
Critical Services15
Recovery Plans12 / 12
Last Full Drill2026-09-02
Continuity Readiness94%
Recovery Domains
Application Services
Restore application instances, routing and configuration.
Target < 10 min
Last 6 min
READY
Data Layer
Restore durable data and validate consistency before reopening writes.
Target < 30 min
Last 14 min
READY
Trading Pipeline
Rebuild queues and processing state without duplicating execution requests.
Target < 15 min
Last 11 min
READY
Broker Connectivity
Restore connectors, then compare broker state with internal state.
Target < 20 min
Last 17 min
REVIEW
Core rule: after a disaster, MQLPro should recover into a controlled state. New execution should remain paused until identity, queues, connector health and broker reconciliation have been verified.
RTO / RPO
Recovery Time Objective (RTO) describes the target time to restore a service. Recovery Point Objective (RPO) describes the maximum acceptable amount of data loss for the defined workload.
Component
RTO Target
RPO Target
Current Evidence
Status
API / Dashboard
< 10 min
< 5 min
Restore test 6 min
PASS
Operational Database
< 30 min
< 15 min
Restore test 14 min
PASS
Execution Queue
< 15 min
0 lost requests
Replay test
PASS
Audit Records
< 30 min
0 gaps
Continuity test
PASS
Broker State
< 20 min
Reconcile before resume
Connector test
REVIEW
Do not equate RPO with “number of trades lost.” For financial execution, the system must reconcile actual broker state rather than assume an internal event log is the authoritative source of open positions.
Failure Scenarios
Each scenario has a containment action, recovery path and explicit condition for resuming normal execution.
Scenario
Immediate Response
Recovery
Resume Condition
Status
Application outage
Fail traffic / preserve state
Restore instances
Health checks pass
DEFINED
Database failure
Stop writes
Restore snapshot / replica
Consistency verified
DEFINED
Queue failure
Pause execution consumers
Recover durable queue
Deduplication verified
DEFINED
Connector outage
Pause affected execution path
Reconnect / fail over
Broker state reconciled
DEFINED
Credential compromise
Revoke credential
Rotate and re-authenticate
Access audit complete
DEFINED
Regional infrastructure loss
Activate recovery environment
Restore critical services
Full readiness gate
REHEARSE
Business Continuity
Continuity defines which functions remain available during degraded operation and which functions are deliberately suspended.
Read-only Dashboard
Users can inspect known internal state while writes are restricted.
Priority P1
Degraded mode
AVAILABLE
Signal Intake
Can accept events only when durable storage and downstream controls are healthy.
Priority P1
Conditional
GATED
New Trade Execution
Must remain paused when broker state or execution idempotency cannot be verified.
Priority P0
Fail-closed
CONTROLLED
Reconciliation
Used to establish actual broker state after a connectivity or data incident.
Priority P0
Recovery path
REQUIRED
Audit Trail
Must remain durable across recovery and preserve operational traceability.
Priority P0
Continuous
REQUIRED
Recovery Drills
Recovery procedures are only meaningful when rehearsed. Drill results should capture duration, evidence, failures and corrective actions.
Drill
Date
Duration
Result
Follow-up
Database Restore
2026-09-02
14 min
Successful
Retest quarterly
Queue Replay
2026-09-10
11 min
Successful
Keep dedupe test
Connector Failover
2026-09-11
17 min
Successful
Test regional failover
Audit Continuity
2026-09-12
8 min
Successful
Verify retention
Regional Recovery
Pending
—
Not tested
Schedule rehearsal
STEP 51 • OPERATIONAL GOVERNANCE
Operational Risk & Control Effectiveness
Governance layer untuk mengidentifikasi risiko operasional, menguji efektivitas kontrol, memantau residual risk, dan memastikan control owner menutup kelemahan secara terukur.
Effectiveness Review
Risk Register
OR-REG-001
Operational risk inventory
Controls Assessed
42
Periodic effectiveness cycle
Open Exceptions
5
Requires owner action
Effectiveness Gate
REVIEW
Residual risk reconciliation pending
Operational Risk Register
Active Review
Risk ID
Risk Domain
Scenario
Inherent
Residual
Owner
Status
OR-001
Execution
Copy execution mismatch
High
Medium
Execution Ops
Controlled
OR-002
Broker Connectivity
Connector interruption
High
Medium
Connectivity
Monitored
OR-003
Access
Excessive privileged access
High
Low
Security
Controlled
OR-004
Data
Privacy control failure
High
Medium
Data Governance
Review
OR-005
Resilience
Recovery validation gap
High
Medium
Platform Ops
Open
Control Effectiveness Assessment
Periodic Test
Preventive controlsReviewed
Detective controlsReviewed
Corrective controlsValidation
Manual control evidenceRequired
Automated control evidenceVerified
Control owner attestationPending
Control Health Indicators
5 Exceptions
Design Adequacy94%Control design review
Operating Effectiveness91%Evidence-based testing
Evidence Completeness88%Open evidence gaps
Remediation SLA84%Within target window
Control Testing & Exception Registry
Action Required
Control ID
Control
Test Method
Result
Exception
Action
CTL-014
Execution Reconciliation
Sample + system evidence
PASS
None
Maintain
CTL-021
Privileged Access Review
Access recertification
PASS
None
Maintain
CTL-028
Privacy Disclosure Control
Evidence sampling
PARTIAL
2 evidence gaps
CAPA-OR-004
CTL-035
DR Restore Validation
Controlled exercise
OPEN
Restore test pending
CAPA-OR-005
CTL-041
Security Detection Review
Rule + alert validation
PASS
None
Maintain
Residual Risk & Treatment Governance
Risk Response
Identify
Map operational scenarios to affected assets, processes, controls, and dependencies.
Assess
Record inherent risk, control coverage, evidence quality, and residual exposure.
Treat
Assign mitigation, acceptance, transfer, or avoidance action to an accountable owner.
Verify
Re-test remediation and confirm that residual risk reflects the current control state.
Re-certify
Control owners and governance functions attest to the reviewed risk and control position.
CAPA & Control Improvement Queue
Open
Action ID
Finding
Owner
Due
Verification
Status
CAPA-OR-004
Privacy evidence gaps
Data Governance
2026-09-24
Evidence re-test
OPEN
CAPA-OR-005
DR restore test
Platform Ops
2026-09-26
Exercise evidence
OPEN
CAPA-OR-006
Manual control documentation
Operations
2026-09-28
Owner attestation
OPEN
Operational Control Effectiveness Gate
REVIEW
Control effectiveness belum dinyatakan final sampai exception material, evidence gap, residual risk, dan CAPA diverifikasi oleh control owner serta governance function terkait.
Governance layer untuk menilai dependency pihak ketiga, broker, vendor teknologi, service provider, SLA, konsentrasi risiko, kontrol akses, dan kesiapan exit atau contingency.
Third-Party Review
Third-Party Registry
TPR-REG-001
Vendor & dependency inventory
Active Dependencies
18
Broker / vendor / provider
Open Assessments
4
Periodic due diligence
Governance Gate
REVIEW
Contract & risk evidence pending
Third-Party Risk Registry
Active Review
Entity
Type
Criticality
Service
Dependency
Risk
Status
Broker Connector A
Broker
Critical
Trade Execution
High
Medium
Monitored
Market Data Provider
Vendor
High
Pricing Feed
High
Medium
Monitored
Cloud Infrastructure
Provider
Critical
Compute / Network
High
Medium
Review
Identity Service
Provider
High
Authentication
Medium
Low
Controlled
Notification Service
Vendor
Medium
Operational Alerts
Medium
Low
Controlled
Broker / Vendor Due Diligence
Assessment
Legal entity & ownershipVerified
Service scope & dependencyVerified
Security control assessmentReview
Business continuity capabilityReview
SLA / incident obligationsVerified
Exit / portability readinessPending
Third-Party Control Health
4 Open
Due Diligence92%Assessment completeness
SLA Compliance96%Service-level evidence
BCP Coverage83%Continuity evidence
Exit Readiness71%Portability / contingency
Contract, SLA & Service-Level Governance
Exceptions
Dependency
Contract
SLA
Incident Notice
Data / Access
Exit Clause
Status
Broker Connector A
Active
99.9%
Defined
Restricted
Defined
Compliant
Market Data Provider
Active
99.5%
Defined
Restricted
Defined
Compliant
Cloud Infrastructure
Active
99.9%
Defined
Privileged
Review
Review
Identity Service
Active
99.9%
Defined
Restricted
Defined
Compliant
Dependency Concentration & Failure Impact
Risk Mapping
Critical Dependency Mapping
Hubungkan vendor atau broker dengan execution, pricing, identity, data, infrastructure, dan monitoring.
Single-Dependency Detection
Identifikasi service yang tidak memiliki alternatif, failover, atau acceptable workaround.
Failure Impact Assessment
Ukur dampak terhadap trading state, customer access, reconciliation, privacy, dan operational continuity.
Contingency Validation
Pastikan fallback, backup provider, manual procedure, atau recovery path telah diuji.
Third-Party Incident & Remediation Queue
Open Actions
Action ID
Finding
Dependency
Owner
Due
Status
TP-CAPA-001
Exit readiness evidence gap
Cloud Infrastructure
Vendor Risk
2026-09-25
OPEN
TP-CAPA-002
BCP evidence refresh
Market Data Provider
Operations
2026-09-27
OPEN
TP-CAPA-003
Connector contingency exercise
Broker Connector A
Connectivity
2026-09-29
PLANNED
Third-Party Governance Gate
REVIEW
Dependency kritis tidak dianggap fully governed sampai due diligence, contract/SLA, access boundary, resilience, concentration risk, incident obligations, exit readiness, dan remediation evidence tervalidasi.
Coordinate detection, containment, investigation, recovery and post-incident review without confusing service recovery with trading-state recovery.
Operational Incident Overview
An incident is an operational event that can affect availability, data integrity, security or trading execution. Severity determines the response path, not the blame assigned to an individual.
Open Incidents1
Critical0
Last Major Incident18 days ago
Runbooks Ready18 / 18
Operational Domains
Application Availability
Routing, frontend and backend service availability.
Severity S2
On-call
MONITORED
Data Integrity
Unexpected divergence, missing records or inconsistent state.
Severity S1
Immediate
MONITORED
Trading Execution
Unexpected order state, connector outage or execution mismatch.
Severity S0
Immediate
HIGH PRIORITY
Security
Credential compromise, unauthorized access or suspicious activity.
Severity S0
Immediate
HIGH PRIORITY
Fail-safe principle: if an incident can make the system's internal execution state unreliable, affected trading actions should be paused until the broker state and internal state can be reconciled.
Active Incidents
Current operational events and their containment state.
INC-2026-014 · Connector latency degradation
Affected scope: one connector runtime · Detection: automated latency alert · No confirmed duplicate execution.
SEV-2
Investigating
OPEN
No other active critical incidents
Security, database and queue health currently within defined thresholds.
—
—
CLEAR
Operational Runbooks
Runbooks provide repeatable response steps. Production procedures should live in version-controlled operational documentation and require appropriate authorization.
Runbook
Trigger
Primary Action
Resume Gate
Status
RB-01 Application Outage
5xx / availability
Failover / restart
Health checks
READY
RB-02 Database Recovery
DB unavailable
Protect writes / restore
Consistency check
READY
RB-03 Queue Recovery
Queue stalled
Pause consumers / recover
Deduplication check
READY
RB-04 Connector Failure
Broker link loss
Pause affected path
Broker reconciliation
READY
RB-05 Security Incident
Credential anomaly
Revoke / contain
Access review
READY
RB-06 Data Divergence
State mismatch
Freeze affected actions
Reconciliation complete
REVIEW
Incident Timeline
Timeline entries establish what happened and when. They should be append-only and attributable in a production audit system.
Time
Event
Actor
Evidence
State
22:14:02
Latency threshold exceeded
Monitoring
ALERT-9182
DETECTED
22:14:18
Connector path marked degraded
Automation
HEALTH-447
CONTAINED
22:15:01
Affected execution path paused
Policy
POL-EXEC-04
SAFE
22:17:42
Connector diagnostics started
Operator
RUN-2231
INVESTIGATING
Pending
Broker reconciliation
Operations
—
PENDING
Post-Incident Review
The review focuses on system conditions, detection quality, recovery time and preventive controls. The objective is learning and risk reduction.
Review Item
Evidence
Owner
State
Root cause / contributing factors
Logs + metrics + change history
Engineering
REQUIRED
Customer / account impact
Scope and affected accounts
Operations
REQUIRED
Trading-state impact
Broker vs internal reconciliation
Trading Ops
REQUIRED
Detection / response quality
Alert and incident timeline
SRE
REQUIRED
Corrective actions
Tracked remediation tasks
Owner assigned
REQUIRED
Important: an incident review should not declare an incident “resolved” merely because the application is online. Resolution includes confirming that affected financial execution state is understood and reconciled.
Home / Dashboard / Monitoring & SLO
Monitoring, Alerting & SLO
Turn system telemetry into operational signals with defined thresholds, service objectives and actionable alerts.
Monitoring Overview
Monitoring provides evidence about system behavior. It does not replace authorization, execution controls or broker reconciliation.
Services Monitored15 / 15
Active Alerts2
SLOs Within Target7 / 8
Telemetry Ingest99.97%
Key Signals
API Availability
Successful requests across public and authenticated endpoints.
99.99%
Target 99.90%
HEALTHY
Execution Queue Age
Age of the oldest pending execution request.
1.8 sec
Alert > 10 sec
NORMAL
Connector Latency
Round-trip latency for broker connector operations.
91 ms
Alert > 75 ms
ALERT
Reconciliation Lag
Time between broker observation and internal reconciliation.
4 sec
Target < 10 sec
NORMAL
Alerting principle: an alert should correspond to an actionable condition. High-volume informational events should not be treated as incidents merely because they are visible.
System Metrics
Core metrics used to detect degradation across the application and trading pipeline.
Metric
Current
Target
Window
Status
HTTP 5xx rate
0.08%
< 0.50%
5 min
NORMAL
API p95 latency
142 ms
< 300 ms
5 min
NORMAL
Queue depth
12
< 100
1 min
NORMAL
Connector latency
91 ms
< 75 ms
5 min
DEGRADED
Database connections
42 / 200
< 160
1 min
NORMAL
Reconciliation lag
4 sec
< 10 sec
5 min
NORMAL
Audit ingest delay
0.7 sec
< 5 sec
5 min
NORMAL
Alert Rules
Alerts are evaluated against thresholds and routed to the appropriate operational owner.
AL-001 · Connector latency
Trigger when p95 connector latency exceeds 75 ms for 5 minutes.
SEV-2
Trading Ops
ACTIVE
AL-002 · Queue backlog
Trigger when execution queue exceeds 100 pending requests for 2 minutes.
SEV-1
Engineering
ARMED
AL-003 · Reconciliation divergence
Trigger when broker and internal state remain inconsistent beyond defined tolerance.
SEV-0
Trading Ops
ARMED
AL-004 · Authentication anomaly
Trigger on unusual login or credential activity according to security policy.
SEV-0
Security
ARMED
SLO / Error Budget
Service Level Objectives define reliability targets over a measurement period. Error budget represents the allowed unreliability before reliability work takes priority.
API Availability
Monthly objective: 99.90%
99.99%
Budget 92%
WITHIN SLO
Execution Queue Processing
Requests processed within defined latency objective.
99.96%
Budget 88%
WITHIN SLO
Reconciliation Freshness
Broker state observed and reconciled within target window.
99.71%
Budget 74%
WATCH
Connector Availability
Connector service available for its defined operational window.
99.42%
Budget 61%
WATCH
Governance: an exhausted error budget should trigger reliability review. It should not be used as an automatic instruction to increase trading activity or take financial risk.
Telemetry Pipeline
Telemetry should preserve enough context to investigate failures while respecting access controls and sensitive-data policies.
Source
Type
Retention
Ingest
Status
Application Services
Logs / Metrics
30 days
99.99%
HEALTHY
Execution Pipeline
Events / Metrics
90 days
99.98%
HEALTHY
Broker Connectors
Logs / State
90 days
99.95%
WATCH
Security Events
Audit / Alerts
365 days
99.99%
HEALTHY
Infrastructure
Metrics
30 days
99.97%
HEALTHY
Privacy boundary: telemetry should avoid unnecessary secrets or credentials. Production logs must use redaction and access controls appropriate to the data they contain.
Home / Dashboard / Audit, Compliance & Governance
Audit, Compliance & Governance
Establish traceability, controlled access, change accountability and operational evidence across the MQLPro platform.
Governance Overview
Governance connects operational controls with evidence. Every sensitive action should have an accountable actor, a defined authorization path and an auditable record.
Audit Coverage99.98%
Privileged Users8
Policy Controls24 / 24
Open Findings2
Governance Domains
Audit Trail Integrity
Append-only operational evidence for authentication, configuration and execution events.
Coverage 99.98%
Continuous
HEALTHY
Access Governance
Role-based access, privileged actions and periodic access review.
8 privileged
Monthly review
CONTROLLED
Change Management
Production changes require traceability, approval and rollback evidence.
18 changes
30-day window
CONTROLLED
Compliance Findings
Open findings require owner, due date, evidence and closure verification.
2 open
Review weekly
REVIEW
Governance principle: a dashboard indicator is not evidence by itself. Production controls should retain durable records that can be independently reviewed.
Audit Trail
Audit records should answer who acted, what changed, when it happened, what authorization applied and what outcome resulted.
Event
Actor
Authorization
Timestamp
Result
Production configuration change
admin-02
CHG-2041
2026-09-16 18:42
SUCCESS
Connector credential rotation
ops-01
SEC-882
2026-09-16 17:11
SUCCESS
Execution policy update
trading-ops
POL-119
2026-09-16 15:33
SUCCESS
Privileged login
admin-04
MFA + role
2026-09-16 13:08
RECORDED
Failed authorization
user-173
Denied by policy
2026-09-16 11:49
DENIED
Access Governance
Access should follow least privilege, separation of duties and periodic review. High-impact operations should require explicit authorization.
Role
Users
Privileged Actions
Review
Status
Platform Admin
2
Configuration / user access
Monthly
REVIEWED
Trading Operations
3
Execution controls / reconciliation
Monthly
REVIEWED
Security
2
Credentials / security controls
Monthly
REVIEWED
Read-only Analyst
11
None
Quarterly
REVIEWED
Separation of duties: where practical, the person requesting a high-impact production change should not be the sole person approving and validating that same change.
Change Control
Changes affecting execution, risk, connectivity or security should be attributable and reversible. Emergency changes require retrospective review.
Change
Owner
Approval
Rollback
Status
API release v2.8.4
Engineering
CHG-2044
Verified
COMPLETE
Connector runtime patch
Platform
CHG-2043
Verified
COMPLETE
Risk policy threshold update
Trading Ops
CHG-2042
Pending test
REVIEW
Database maintenance
SRE
CHG-2040
Verified
COMPLETE
Emergency connector mitigation
Operations
Emergency
Post-review pending
FOLLOW-UP
Policy Controls
Policies define the boundaries within which the platform may operate. Technical enforcement should be paired with periodic review.
Authentication & Session Policy
MFA, session expiry and privileged login controls.
POL-AUTH-01
Monthly
ACTIVE
Execution Authorization Policy
Defines which actors and services may submit or control execution actions.
POL-EXEC-04
Monthly
ACTIVE
Data Retention Policy
Defines retention and access requirements for audit and operational records.
POL-DATA-02
Quarterly
ACTIVE
Incident Response Policy
Defines severity, escalation, containment and post-incident review requirements.
POL-INC-03
Quarterly
ACTIVE
Change Management Policy
Defines approval, testing, deployment and rollback requirements.
POL-CHG-05
Quarterly
ACTIVE
Home / Dashboard / Data Governance
Data Governance & Retention
Define how MQLPro classifies, stores, protects, retains, exports and disposes of platform data across its lifecycle.
Data Governance Overview
Data governance establishes ownership, classification, retention and access rules so operational data remains useful, traceable and appropriately protected throughout its lifecycle.
Data Domains9
Retention Policies9 / 9
Classified Assets100%
Open Data Findings1
Primary Data Domains
Identity & Account Data
User identity, authentication and account-management records.
Restricted
Owner: IAM
CONTROLLED
Signal & Strategy Data
Signal metadata, strategy configuration and marketplace information.
Confidential
Owner: Product
CONTROLLED
Trading & Execution Data
Execution events, order state, reconciliation records and connector state.
Restricted
Owner: Trading Ops
CONTROLLED
Audit & Security Data
Authentication, authorization, configuration and security-event records.
Restricted
Owner: Security
CONTROLLED
Data governance principle: retention is not the same as indefinite storage. Each data class should have a documented purpose, owner, retention period and disposal or archival rule.
Data Classification
Classification determines the controls required for storage, access, export and disposal. Labels should be applied consistently across databases, files, logs and backups.
Class
Examples
Access
Export
Control
Public
Public marketplace descriptions
Open
Allowed
STANDARD
Internal
Operational documentation
Authenticated
Controlled
CONTROLLED
Confidential
Strategy metadata / commercial data
Role-based
Restricted
RESTRICTED
Restricted
Credentials / account / execution records
Least privilege
Approval required
HIGH CONTROL
Secret handling: credentials, API keys and similar authentication material should not be exposed through ordinary application views, exports or logs. Store secrets using an appropriate secret-management mechanism.
Data Lifecycle
Every major data domain should have a predictable lifecycle from collection through active use, archival and final disposal.
1. Collection
Capture only data required for a defined product, operational or compliance purpose.
Purpose-bound
Validation
CONTROLLED
2. Active Processing
Use data through authorized services and role-based access controls.
Role-based
Audit
CONTROLLED
3. Archival
Move records that are no longer operationally active but must be retained.
Encrypted
Retention
CONTROLLED
4. Disposal
Delete or securely dispose of data after its approved retention period and legal holds.
Verified
Evidence
GOVERNED
Lifecycle exception: a legal, regulatory or incident-related hold can suspend ordinary disposal. The hold itself should be recorded and have an accountable owner.
Retention Schedule
Illustrative retention controls for the MQLPro architecture. Final production periods must be aligned with applicable legal, contractual and business requirements.
Data Domain
Active Retention
Archive
Disposal Rule
Status
Authentication Events
90 days
365 days
Scheduled deletion
DEFINED
Audit Events
180 days
365 days
Policy-controlled
DEFINED
Execution Events
90 days
7 years*
Controlled archival
VERIFY
Application Logs
30 days
90 days
Automated deletion
DEFINED
Market Content
Active
As required
Owner decision
REVIEW
Backup Snapshots
30 days
180 days
Rotation policy
DEFINED
*Illustrative only: retention periods for trading, financial, tax or regulated records must be determined from the requirements applicable to the actual MQLPro operating entity and jurisdictions. The UI does not establish a legal retention requirement.
Data Access Governance
Access to sensitive data should be purpose-limited, role-based, logged and periodically reviewed.
Data
Primary Role
Secondary Role
Export
Review
User Identity
IAM
Support
Restricted
MONTHLY
Trading Execution
Trading Ops
Audit
Controlled
MONTHLY
Broker Credentials
Connector Service
Security
Prohibited
HIGH CONTROL
Strategy Protection Data
Strategy Owner
Platform Admin
Restricted
MONTHLY
Audit Records
Security / Audit
Compliance
Evidence workflow
QUARTERLY
BlackBox boundary: strategy-protection data may be required internally to execute or monitor a strategy, but public marketplace views should expose only the information intentionally designated for public consumption.
Home / Dashboard / Release & Deployment
Release & Deployment Control
Control how application, connector, risk and infrastructure changes move from development into production with validation, approval and rollback evidence.
Release & Deployment Overview
Production changes should be traceable to a version, owner, approval path, validation result and recovery plan. High-impact trading changes require additional controls.
Production Versionv2.8.4
Deployments Today6
Release Gates12 / 12
Rollback Ready100%
Current Release State
Application API v2.8.4
Production release containing API and dashboard changes.
Approved
CHG-2044
LIVE
Connector Runtime v1.14.2
Broker connector runtime patch with verified rollback package.
Approved
CHG-2043
LIVE
Risk Policy v3.7
Threshold configuration pending final production validation.
Validation
CHG-2042
STAGED
Database Maintenance
Schema maintenance completed with backup verification.
Completed
CHG-2040
CLOSED
Deployment principle: deployment success means the software was delivered. It does not automatically mean the trading system is safe to resume. Post-deployment health checks and reconciliation remain separate gates.
Release Registry
A release record connects source version, change request, test evidence, approver and deployment result.
Release
Component
Owner
Approval
Status
v2.8.4
Application API
Engineering
CHG-2044
PRODUCTION
v1.14.2
Connector Runtime
Platform
CHG-2043
PRODUCTION
v3.7
Risk Policy
Trading Ops
CHG-2042
STAGED
v5.2.1
Dashboard UI
Frontend
CHG-2039
COMPLETE
v1.6.0
Audit Service
Security
CHG-2038
COMPLETE
Deployment Pipeline
Changes progress through controlled environments before production. Each stage produces evidence for the next gate.
1. Build & Package
Compile, dependency validation, artifact creation and integrity checks.
Automated
Artifact signed
PASSED
2. Automated Tests
Unit, integration, regression and security checks appropriate to the change.
Automated
1,842 checks
PASSED
3. Staging
Deploy candidate to staging and verify functional and operational behavior.
Controlled
Health checks
PASSED
4. Production Approval
Confirm change scope, risk, owner, rollback plan and authorization.
Human gate
CHG-2044
APPROVED
5. Production Deployment
Deploy using controlled rollout and monitor service health.
Controlled
Canary + rollout
COMPLETE
6. Post-Deploy Verification
Validate telemetry, execution pipeline and reconciliation state.
Operational
Resume gate
REQUIRED
Release Gates
Gates prevent a release from progressing when required evidence or controls are missing.
Gate
Requirement
Evidence
Owner
Status
Code Integrity
Artifact matches approved build
Hash / signature
Engineering
PASS
Automated Testing
Required test suite passes
CI report
Engineering
PASS
Security Review
No blocking security findings
Scan report
Security
PASS
Change Approval
Authorized production change
CHG record
Change Owner
PASS
Rollback Plan
Recovery artifact verified
Rollback test
Platform
PASS
Post-Deploy Health
Telemetry remains within thresholds
Monitoring
Operations
PENDING
Trading Resume
Reconciliation and risk checks pass
Resume record
Trading Ops
PENDING
Critical distinction: a successful software deployment should not bypass trading-specific controls. Connector health, account synchronization, risk state and broker reconciliation must be independently validated before automated execution is resumed.
Rollback Control
Rollback restores a previously validated software state when a release causes unacceptable degradation. It is not a substitute for incident investigation.
Application API v2.8.3
Previous production version retained as validated fallback.
Ready
Artifact verified
AVAILABLE
Connector Runtime v1.14.1
Previous connector runtime available for controlled restoration.
Ready
Artifact verified
AVAILABLE
Risk Policy v3.6
Previous policy snapshot available for authorized restoration.
Ready
Snapshot verified
AVAILABLE
Database Schema
Rollback depends on migration compatibility and verified backup restoration.
Conditional
Backup test
REVIEW
Rollback safety: before restoring a trading-related component, confirm the resulting state will not create duplicate execution, stale orders, mismatched account state or other reconciliation problems.
Home / Dashboard / Backup, Restore & Business Continuity
Backup, Restore & Business Continuity
Protect critical platform state, prove that backups can be restored, coordinate recovery, and prevent trading from resuming until the recovered system passes explicit control gates.
Backup & Recovery Control Overview
STEP 38 closes the operational chain after release and deployment. A deployment can be technically successful while the platform remains unrecoverable. This layer therefore treats backup evidence, restore evidence, continuity capacity and trading resumption as separate controls.
Protected Data Sets14 / 14
Latest Backup12 min
Restore Tests5 / 5
BCP Readiness92%
Resume GateLOCKED
Operational Chain
The recovery path deliberately separates technical recovery from the decision to resume live trading.
1. ReleaseKnown version
2. BackupProtected state
3. RestoreKnown-good state
4. ContinuityService capacity
5. ReconcileBroker truth
6. Resume GateExplicit unlock
Current Protection State
Database: healthy · encrypted snapshot available Object storage: replicated · integrity check passed Configuration: versioned · recovery package available Audit data: append-oriented archive available Connector state: credentials excluded from ordinary backup payloads and handled through controlled recovery procedures.
Recovery Constraint
A restored application is not automatically a restored trading state. Before live execution resumes, the system must compare intended state with observed broker state, resolve material exceptions, validate risk controls and obtain the required operational approval.
Control principle: backup success proves that data was captured. Restore success proves that the captured state can be used. Business continuity proves that critical services can continue or recover within defined objectives. None of these alone authorizes trading resumption.
Backup Inventory
Inventory of critical recovery artifacts. Production implementation should record immutable identifiers, timestamps, integrity results, retention policy and storage location for each backup.
Core users, subscriptions, copy configuration, execution metadata and platform state.
12 min ago
Encrypted · SHA verified
AVAILABLE
Configuration Bundle · cfg-v2.8.4
Application configuration, feature flags and non-secret deployment settings.
18 min ago
Versioned artifact
AVAILABLE
Audit Archive · audit-2026-W38
Operational and administrative audit records required for investigation and recovery evidence.
42 min ago
Replicated storage
AVAILABLE
Connector Recovery Package · conn-runtime-1.14.2
Connector runtime and compatibility metadata; secrets remain under controlled credential management.
1h ago
Signed package
AVAILABLE
Disaster Recovery Snapshot · dr-region-b
Secondary recovery environment snapshot for regional or infrastructure-level disruption.
3h ago
Cross-region copy
VERIFY
Backup Policy Matrix
Artifact
Frequency
Retention
Recovery Priority
Status
Primary Database
15 min
30 days
Critical
COMPLIANT
Configuration
On release / change
180 days
Critical
COMPLIANT
Audit Archive
Daily
Policy-defined
High
COMPLIANT
Connector Runtime
On release
180 days
High
COMPLIANT
DR Snapshot
Daily
30 days
Critical
VERIFY
Important: retention values shown here are architectural examples, not legal or regulatory advice. Final retention must be defined for the actual operating entity and jurisdictions.
Restore Center
A restore operation must identify the target environment, source snapshot, restore scope, owner, expected side effects and post-restore validation plan. The UI intentionally provides a controlled workflow rather than a one-click production restore.
Restore Evidence
REC-037 · Database point-in-time restore
Recovered to isolated environment; schema, row counts and application checks completed.
16 Sep 2026
RTO 19 min
PASSED
REC-036 · Configuration recovery
Versioned configuration restored and compared against release manifest.
15 Sep 2026
Drift 0
PASSED
REC-035 · DR region simulation
Secondary environment activated for service-health validation.
12 Sep 2026
RTO 31 min
REVIEW
Post-Restore Validation
Database integrity PASS
Schema / migration state PASS
Application health PASS
Authentication / authorization PASS
Connector configuration VERIFY
Account reconciliation PENDING
Business Continuity Control
Business continuity focuses on keeping critical functions available or restoring them within agreed objectives during disruption. It is broader than backup: people, dependencies, communication, capacity and decision rights all matter.
Critical Services9 / 9
RTO Coverage100%
RPO Coverage100%
Dependency Tests17 / 19
Open Gaps2
Critical Service Continuity
Signal Intake Gateway
Accept and validate incoming signal events without creating duplicate events.
RTO < 5 min
RPO near-zero
READY
Risk & Eligibility Engine
Preserve risk policy evaluation and prevent uncontrolled execution when dependencies are unavailable.
RTO < 10 min
RPO < 5 min
READY
Execution Queue
Retain pending intents safely and support idempotent recovery after interruption.
RTO < 10 min
RPO near-zero
READY
Broker Connector Layer
Restore connectivity without blindly replaying orders whose execution status is unknown.
RTO < 20 min
RPO < 5 min
TEST DUE
Reconciliation Service
Compare intended state, internal state and broker-observed state after recovery.
RTO < 15 min
RPO near-zero
READY
Continuity Modes
Normal: full execution and monitoring. Degraded: non-critical features restricted; new execution may be held depending on policy. Recovery: restore services, validate state and reconcile accounts. Safe Hold: trading execution remains blocked while operational evidence is incomplete.
This is the final control between recovery and live trading. The default state is locked. A recovery event must never infer permission to resume merely because the application is online.
Gate Status · LOCKED
Live execution remains blocked until all mandatory checks are complete and the designated operator records the resume decision.
4 of 7 checks complete
Application healthPASS
Backup / restore evidencePASS
Connector healthVERIFY
Risk policyPASS
Queue integrityPASS
Broker reconciliationPENDING
Operational approvalNOT GRANTED
Mandatory Resume Conditions
Recovery snapshot verified PASS
Application and dependencies healthy PASS
No unresolved critical incidents VERIFY
Execution queue classified PASS
Broker state reconciled PENDING
Risk limits revalidated PASS
Authorized operator approval REQUIRED
Resume decision audited REQUIRED
Safety rule: if broker execution status is unknown, positions differ materially, duplicate execution cannot be ruled out, or critical risk controls are unavailable, the system should remain in a safe hold state until the exception is resolved or an explicitly approved recovery procedure determines the next action.
Home / Market
Market
Trading robots, indicators and tools for MetaTrader and algorithmic trading.
FeaturedTop RatedFreeUnder $50MT5MT4
Popular products
24,812 products
QT
Quantum Titan MT5
QuantForge
Expert Advisor · MT5
Automated multi-session system designed for systematic market execution.
RATING★★★★★ 4.8
SALES1,284
UPDATED2d ago
$99View product →
GM
Gold Momentum Pro
AlgoWorks
Expert Advisor · MT5
Momentum-oriented trading robot with configurable risk and execution settings.
RATING★★★★☆ 4.4
SALES927
UPDATED5d ago
$79View product →
MS
Market Structure X
ChartLab
Indicator · MT5 / MT4
Charting toolkit for market structure, levels and configurable alerts.
RATING★★★★★ 4.9
SALES2,410
UPDATED1d ago
$49View product →
TM
Trade Manager Pro
RiskTools
Utility · MT5
Position management utility with risk sizing and trade control tools.
RATING★★★★★ 4.7
SALES746
UPDATED8d ago
$35View product →
VF
Volume Flow Analyzer
DataEdge
Indicator · MT5
Volume and flow visualization with configurable market filters.
RATING★★★★☆ 4.5
SALES512
UPDATED12d ago
$29View product →
EC
Execution Core
DevStack
Library · MT5
Reusable execution and order-management components for developers.
RATING★★★★★ 4.8
SALES338
UPDATED3d ago
$59View product →
Become a developer on MQLPro
Publish trading applications, manage versions, documentation, licensing and sales from one developer account.
Verify recovered state, prove execution integrity and keep trading blocked until every mandatory post-recovery control is evidenced.
Post-Recovery Control Overview
Recovery proves that services can be restored. This control layer proves that the restored system is internally consistent, externally reconciled and safe to transition through a controlled trading resumption.
Verification Checks9 / 12
Execution Exceptions2
Accounts Reconciled8 / 10
Resume ReadinessBLOCKED
Monitoring Window30 min
Control Chain
01Recovery complete
02State verify
03Dependency verify
04Reconcile
05Readiness gate
06Controlled resume
07Monitor
Current Recovery Transition
REC-038 · Production recovery event
Recovery package restored; service layer is online and validation is in progress.
INC-1042
Baseline v2.8.4
VERIFYING
Trading execution
New copy instructions remain held while account and broker state are reconciled.
Safe Hold
Queue protected
BLOCKED
Resume authorization
No operator approval may be recorded until mandatory evidence reaches the required state.
Trading Ops
Gate pending
NOT GRANTED
Control principle: application availability is not equivalent to trading readiness. A system can be technically online while execution remains intentionally blocked.
Post-Recovery Verification
Validate the recovered runtime against the approved release, configuration, data and dependency state before evaluating trading readiness.
Release artifact integrity PASS
Database integrity & schema PASS
Configuration checksum PASS
Authentication / authorization PASS
Signal intake health PASS
Execution queue integrity PASS
Risk policy loaded PASS
Broker connector session VERIFY
Clock / timestamp consistency PASS
Duplicate-event protection PASS
Monitoring telemetry VERIFY
Incident evidence completeness PENDING
Verification Rules
Checks must reference the recovered version and current environment. A stale health check is not sufficient evidence. Failed or unverifiable checks keep the transition in Safe Hold.
Evidence Requirements
Record timestamp, operator, environment, check result and source evidence. Preserve the evidence with the recovery record so the decision can be audited later.
Execution Reconciliation
Compare intended execution, internal state and broker-observed state. Unknown execution outcomes must be resolved before a new instruction can safely proceed.
Account
Expected
Broker Observed
Exceptions
Status
Primary Follower
4 positions · 2 pending
4 positions · 2 pending
0
MATCHED
Secondary Follower
3 positions
2 positions
1 position
REVIEW
Reserve Follower
2 positions
2 positions
0
MATCHED
Recovery Test Account
0 positions
0 positions
0
MATCHED
Exception Handling
EX-021 · Secondary Follower
Expected position is not present in broker-observed state; execution history requires operator investigation.
Material
Trading Hold
OPEN
EX-022 · Connector acknowledgement
One acknowledgement sequence requires confirmation after reconnect.
Operational
Connector Ops
OPEN
Idempotency rule: do not replay an instruction merely because the internal system lacks a confirmation. First determine whether the broker already executed it.
Resume Readiness
Readiness aggregates evidence from recovery, infrastructure, connector, risk, queue and reconciliation controls. The result is a control state, not a prediction.
Readiness Gate · BLOCKED
Mandatory evidence remains incomplete. Trading cannot transition to controlled resumption while material reconciliation exceptions are open.
9 of 12 verified
Recovery evidencePASS
Runtime healthPASS
Connector healthVERIFY
Risk policyPASS
Queue integrityPASS
Account reconciliationPENDING
Exception reviewPENDING
Operator approvalNOT GRANTED
Mandatory blockers
Connector acknowledgement, unresolved material account exception and incomplete incident evidence remain blockers in this prototype state.
What does not unlock the gate
Application uptime, successful login, restored database state or a completed deployment alone do not authorize live trading.
Controlled Trading Resumption
Once readiness requirements are satisfied, resumption should occur in controlled phases with explicit authorization and a defined rollback-to-hold path.
Phase 1 · Observe only
Keep execution blocked; verify telemetry, broker sessions and state stability.
0 orders
Monitoring
REQUIRED
Phase 2 · Limited resume
Permit only policy-approved low-risk execution after operator authorization and reconciliation closure.
Limited scope
Risk gate
CONTROLLED
Phase 3 · Normal operation
Return to normal execution only after the limited-resume observation window completes without blocking anomalies.
Full scope
Ops approval
CONTROLLED
Resume Decision
Current state: LOCKED. The prototype does not permit a resume action while mandatory blockers remain unresolved.
LIVE TRADING LOCKED
Post-Resume Monitoring
The observation window detects regressions that may appear only after execution resumes. Any defined stop condition should return the system to Safe Hold.
Control
Window
Threshold / Signal
Action
Status
Connector latency
Continuous
Within service threshold
Alert / Hold if breached
READY
Execution rejects
30 min
No unexplained spike
Investigate / Hold
READY
Position drift
Continuous
Zero unexplained material drift
Reconcile / Hold
ARMED
Queue age
Continuous
No abnormal backlog
Throttle / Hold
READY
Risk exposure
Continuous
Within policy
Block new execution
READY
Automatic Return-to-Hold Conditions
Material position drift HOLD
Unknown execution outcome HOLD
Connector session loss HOLD
Risk policy unavailable HOLD
Auditability: every transition should produce an immutable event containing the previous state, new state, operator or service identity, timestamp, reason and supporting evidence reference.
Home / Dashboard / Operational Closure & Incident Learning
Operational Closure & Incident Learning
Close the recovery event with evidence, reconstruct what happened, track corrective actions and prevent recurrence.
Operational Closure Overview
A recovery event is not complete when services return online. Closure requires evidence that the incident was understood, impact was recorded, corrective actions assigned and the resulting changes verified.
IncidentINC-1042
SeveritySEV-1
RCA StatusIN REVIEW
Open Actions4
ClosureBLOCKED
Closure Chain
01 · Recovery evidence
Recovery and post-recovery evidence linked to the incident.
Recovery
Evidence linked
COMPLETE
02 · Incident reconstruction
Timeline and system events reconstructed from immutable records.
Incident Ops
Timeline
COMPLETE
03 · Root cause analysis
Primary and contributing causes require reviewer confirmation.
Engineering
RCA
IN REVIEW
04 · Corrective actions
Four actions remain open across engineering and operations.
CAPA
4 open
OPEN
Closure Gate · BLOCKED
Incident closure cannot be recorded until RCA approval, mandatory corrective actions, change verification and final evidence review are complete.
AUDIT CLOSURE LOCKED
Incident Timeline & Evidence Reconstruction
Use event IDs, timestamps and evidence references to reconstruct the incident without relying on memory or informal notes.
14:08:11 · INC-1042 opened
Production anomaly detected; automated alert linked to incident record EVT-55101.
14:11:37 · Trading Safe Hold activated
New execution instructions blocked while system state was assessed.
14:26:04 · Recovery initiated
Approved recovery runbook REC-038 started by Trading Ops.
14:41:19 · Services restored
Runtime returned online; post-recovery verification remained mandatory.
14:53:42 · Reconciliation review opened
Two execution exceptions identified for operator investigation.
15:22:10 · Controlled monitoring started
Post-recovery evidence collection continued; closure remained blocked.
Every closure artifact should reference an immutable event or controlled document version. Screenshots without provenance are supporting material, not authoritative state.
Root Cause Analysis & Impact Assessment
Separate observed facts from hypotheses. The RCA record should identify primary cause, contributing factors, detection gaps and evidence supporting each conclusion.
Primary cause identified REVIEW
Contributing factors documented REVIEW
Detection gap assessed DONE
Recovery trigger documented DONE
Customer/account impact quantified PENDING
Trading impact reconciled PENDING
Working RCA
Observed: execution services entered an inconsistent state after deployment. Hypothesis: a configuration/state transition mismatch contributed to the failure. Final cause remains subject to evidence review.
Impact Scope
Impacted window: 14:08–14:53. Accounts requiring reconciliation: 2. Execution exceptions: 2. Trading remained in Safe Hold during the recovery control window.
Actions must have an owner, due date, verification criterion and evidence reference. Closing an action means proving the control changed, not merely changing its status.
ActionOwnerDueStatus
Validate deployment-state transition guard
Add pre-resume consistency check for deployment metadata.
Engineering
19 Sep
OPEN
Expand connector acknowledgement evidence
Persist broker acknowledgement sequence in recovery evidence.
Connector Ops
20 Sep
OPEN
Add automated reconciliation blocker
Prevent resume gate evaluation when material drift exists.
Trading Ops
21 Sep
PLANNED
Run controlled recovery drill
Verify the updated runbook and evidence chain in a non-production exercise.
SRE
25 Sep
PLANNED
Change Control
Incident-derived changes enter normal change control. Emergency remediation does not bypass testing, approval or rollback evidence.
CHG-442 · Deployment state guard
Code/config change derived from RCA-1042.
Normal
Test required
DRAFT
CHG-443 · Reconciliation blocker
Gate logic change to prevent resume with material drift.
Normal
Review required
DRAFT
CHG-444 · Evidence retention extension
Preserve recovery and closure evidence for the defined retention period.
Low
Policy review
PLANNED
Verification Standard
Each change needs an approved version, test evidence, deployment reference, rollback plan and post-change validation before it can be marked effective.
Rollback Principle
If a corrective change introduces a new material anomaly, the system returns to the applicable Safe Hold control rather than bypassing the gate.
Incident Closure Gate
Final closure is a controlled state transition. The incident remains open until all mandatory evidence and actions are verified.
Closure Status · BLOCKED
Timeline approved PASS
Impact assessment approved PENDING
RCA approved PENDING
Mandatory CAPA verified PENDING
Change verification complete PENDING
Evidence package complete PENDING
Final reviewer approval NOT GRANTED
Audit record sealed LOCKED
INCIDENT CLOSURE LOCKED
Closure Record Preview
INCIDENT: INC-1042
RCA: RCA-1042 [IN_REVIEW]
CAPA: 4 actions [OPEN]
CHANGES: 3 [NOT_VERIFIED]
FINAL STATE: OPEN / BLOCKED
AUDIT SEAL: NOT AVAILABLE
Quantum Titan MT5 is a prototype marketplace listing for an automated trading application. The real MQLPro implementation will expose product documentation, supported platforms, release history, licensing information and developer details.
Product specifications
PLATFORMMetaTrader 5
TYPEExpert Advisor
VERSION3.8.2
LAST UPDATE2 days ago
LICENSEPersonal
INSTALLATIONAutomatic / Manual
What's included
EA package, user documentation, update access and product support. Actual files and licensing will be implemented with the marketplace backend.
Home / Dashboard / Privileged Access & Identity Governance
Control production identities, privileges and attributed actions so every sensitive operational change can be traced to an authorized identity.
Identity Governance Overview
STEP 42 identifies production drift. This layer establishes whether the identity that could cause a change is authorized, appropriately privileged, attributable and still valid. Privileged access remains subject to approval, expiry and review.
Identities42
Privileged7
Temporary Access2
Review Due4
CertificationBLOCKED
Identity Control Lifecycle
01Identify
02Assign Role
03Approve
04Grant
05Observe
06Attribute
07Reconcile
08Certify
Control State
Production privileged identities
Seven identities currently hold elevated production capability; two are temporary and require expiry review.
IAM-REG-2026
7 privileged
REVIEW
Emergency access
Break-glass access is time-bound and must generate an attributable audit event plus retrospective review.
BG-002
Expires 30 min
ARMED
Access certification
Certification is blocked while stale privilege and unresolved ownership findings remain.
GATE-043
Evidence required
BLOCKED
Control principle: possession of a credential is not proof of authorization. Every privileged action should resolve to an identity, granted privilege, approved purpose, resource scope and valid time window.
Identity & Service Account Registry
Production identities include human operators, service accounts and emergency identities. Each must have an owner, purpose, scope and lifecycle state.
Identity
Type
Owner
Privilege
Expiry
Status
ops-admin-01
Human
Platform
Production Admin
30 Sep 2026
ACTIVE
svc-copy-engine
Service
Execution
Execution Service
30 Dec 2026
ACTIVE
svc-reconcile
Service
Operations
Reconciliation
30 Dec 2026
ACTIVE
breakglass-prod
Emergency
Security
Privileged Admin
30 min window
CONTROLLED
Roles & Privilege Matrix
Privileges are scoped to the minimum capability required for the operational function. Production write access is separated from observation and approval duties.
Role
Resources
Read
Write
Approve
SoD
Observer
Telemetry / Audit
Yes
No
No
—
Release Operator
Deployment
Yes
Scoped
No
Required
Risk Operator
Risk Policy
Yes
Scoped
Yes
Separate
Production Admin
Platform
Yes
Privileged
No
Required
Break-Glass Admin
Emergency
Yes
Temporary
No
Mandatory review
Least-Privilege Checks
Unused privileged permission REVIEW
Wildcard production scope FINDING
Separate approval identity PASS
Service account owner PASS
Access Request & Approval
Elevated production access requires an explicit business or operational purpose, scope, approver and expiration.
Every sensitive action should be attributable to an identity and linked to the related change, incident, resource and result.
Event
Identity
Resource
Reference
Result
ACT-7712 · config update
ops-admin-01
connector-mt5-a
CR-1048
APPROVED
ACT-7711 · policy read
svc-copy-engine
risk-policy-v4
SVC
AUTHORIZED
ACT-7710 · emergency login
breakglass-prod
prod-platform
INC-1042
REVIEW
ACT-7709 · config update
unknown
connector-mt5-b
DRIFT-004
UNATTRIBUTED
Attribution Rule
An unrecognized identity, expired privilege or action outside the approved resource scope must create an exception. It must not be silently mapped to a generic operator account.
Access Reconciliation
Compare the approved identity state against actual production permissions and recent privileged activity.
Control
Expected
Observed
Action
Status
Privileged identities
7
7
None
MATCH
Temporary grants
2
2
Expiry review
REVIEW
Wildcard scope
0
1
Reduce scope
DRIFT
Unattributed actions
0
1
Investigate
OPEN
Revocation Triggers
Access expired REVOKE
Owner removed REVOKE
Privilege no longer required REVOKE
Unauthorized action detected HOLD + REVIEW
Periodic Access Certification
Access owners certify that each privileged identity remains necessary, correctly scoped and assigned to the right owner. Certification does not approve unresolved exceptions.
Owner
Scope
Identities
Due
Status
Platform
Production Admin
2
20 Sep 2026
DUE
Execution
Execution Service
2
25 Sep 2026
CURRENT
Security
Emergency Access
1
Every use
EVENT-BASED
Certification Gate
All privileged identities have owners PASS
No unresolved excessive privilege FAIL
No unattributed privileged actions FAIL
Temporary grants reviewed PENDING
Access Governance Closure Gate
Certification remains blocked until material privilege findings, unattributed actions and required access reviews are dispositioned with evidence.
Privilege scope findings
Wildcard production permission requires remediation or formally approved exception.
IAM-F-017
Remediation
OPEN
Unattributed privileged action
ACT-7709 must be investigated and linked to an authorized identity or exception record.
IAM-F-018
Investigation
OPEN
Certification decision
Do not certify the privileged-access baseline while material findings remain unresolved.
GATE-043
Evidence required
BLOCKED
Auditability: identity lifecycle events, grants, approvals, privileged actions, revocations and certification decisions should be retained as immutable records with actor, timestamp, reason, scope and evidence references.
Home / Dashboard / Immutable Audit Trail & Evidence
Immutable Audit Trail & Evidence Correlation
Correlate identity, privileged actions, configuration, incidents and execution into a traceable evidence chain.
Events Today
1,284
Prototype event registry
Critical Events
07
Require review
Correlated Chains
42
Cross-system links
Integrity Exceptions
01
Closure currently blocked
Control Objective
WHO → DID WHAT → TO WHICH RESOURCE → WHEN → UNDER WHICH AUTHORIZATION → WHAT CHANGED → WHAT SYSTEM RESULTED → WHAT EVIDENCE PROVES IT
Audit State
REVIEW REQUIRED One integrity exception remains unresolved in the prototype evidence chain.
Evidence Model
Append-only / tamper-evident Production implementation must calculate and verify hashes/signatures server-side.
Control Chain
IdentityActor / service account
→
Privileged ActionAuthorized operation
→
Audit EventTimestamp + correlation ID
→
IntegrityHash / signature check
→
EvidenceLinked source records
→
ReviewClosure decision
Audit Event Registry
Event ID
Timestamp
Actor / Service
Action
Resource
Correlation
Integrity
AUD-104982
2026-09-17 08:04:11
svc-copy-orchestrator
POSITION_UPDATE
Follower-ACCT-17
CORR-8F21
VERIFIED
AUD-104981
2026-09-17 08:03:58
USR-017
CONFIG_CHANGE
connector.mt5
CORR-8F21
VERIFIED
AUD-104980
2026-09-17 08:03:41
USR-017
PRIVILEGE_GRANT
svc-copy-orchestrator
CORR-8F21
REVIEW
AUD-104979
2026-09-17 08:02:19
system
DRIFT_DETECTED
connector.mt5
CORR-8F21
EXCEPTION
Chain Integrity
99.92%
Prototype verification state
Hash Chain
Previous hash → event payload → current hash. Production verification must occur outside the browser.
Exception
AUD-104979 Evidence continuity requires investigation before closure.
Integrity Verification Record
Event
Previous Hash
Current Hash
Signature
Verification
AUD-104982
sha256:7f…a21
sha256:91…c02
ed25519:…
VERIFIED
AUD-104981
sha256:3c…8d4
sha256:7f…a21
ed25519:…
VERIFIED
AUD-104979
sha256:??…
sha256:3c…8d4
missing
EXCEPTION
Integrity is a control model only. The production backend must own the append-only log, cryptographic verification, key custody, retention and access controls.
Actor / service attributionIdentity and service-account reference attached.
✓
Authorization evidenceAccess approval and role context attached.
✓
Before / after stateConfiguration and operational state references attached.
✓
Execution outcomeExecution/reconciliation record linked to the event chain.
✓
Correlation timelineShared correlation ID connects related records.
!
Integrity exception resolutionMissing signature/hash evidence prevents final closure.
Closure Gate
BLOCKED
Mandatory integrity evidence unresolved.
Reviewer
Pending
No final compliance review recorded.
Audit Package
Draft
Package can be prepared but not closed.
Evidence Closure Gate
PASS
All required actors attributedIdentity-to-event mapping is present.
PASS
Authorization references presentAccess and approval context is linked.
PASS
Cross-system correlation completeIncident, change, configuration and execution records are linked.
BLOCK
Integrity verification completeOne event still has an unresolved integrity exception.
BLOCK
Compliance reviewer approvalFinal approval is unavailable while mandatory evidence is blocked.
Gate result: BLOCKED. Resolve the integrity exception, attach authoritative evidence, rerun verification, then obtain reviewer approval before audit closure.
Home / Dashboard / Configuration & Production Drift
Configuration Management & Production Drift Control
Maintain a known-good production baseline, detect unauthorized or unexpected changes, reconcile drift and require evidence before re-certification.
Configuration Control Overview
STEP 41 controls planned changes. This layer controls the state that actually exists in production, including changes made outside the approved change path. A drift finding remains open until the observed state is reconciled, remediated or explicitly accepted under policy.
Managed Assets38
Baseline Coverage94.7%
Open Drift4
Critical Drift1
Baseline StatusDEGRADED
Configuration Control Lifecycle
01Register
02Baseline
03Observe
04Detect Drift
05Assess
06Reconcile
07Remediate
08Certify
Control State
Production baseline
Last certified baseline CFG-2026-09-16. Current production contains four observed deviations.
CFG-2026-09-16
94.7% coverage
DEGRADED
Unauthorized configuration change
One connector configuration differs from the approved release record.
DRIFT-004
High impact
OPEN
Baseline re-certification
Blocked until material drift is resolved or formally dispositioned.
GATE-042
Evidence required
BLOCKED
Control principle: “Observed in production” is not equivalent to “approved.” Every production state must be traceable to an approved configuration, release, emergency record or explicitly accepted exception.
Asset & Configuration Registry
Inventory of production-affecting configuration objects and the evidence needed to identify their owner, source of truth and current state.
Asset
Type
Owner
Source of Truth
Observed
Status
mqlpro-api-prod
Application
Platform
Release CFG
v4.8.2
MATCH
execution-queue
Service
Execution Ops
Config Store
q-v17
MATCH
mt5-connector-a
Connector
Broker Ops
Approved Change
cfg-91b7
DRIFT
risk-policy-prod
Policy
Risk Control
Policy Registry
RP-3.6
MATCH
postgres-primary
Database
Data Ops
Schema Registry
2026.09.16
MATCH
signal-router
Service
Signal Ops
Release CFG
v2.14.0
REVIEW
Production Configuration Baseline
The baseline is the reference state against which production configuration is evaluated. A baseline should be versioned, immutable after certification and linked to the release or approved change that created it.
Current Certified Baseline
BASELINE: CFG-2026-09-16
Release: REL-2026.09.16-04
Environment: production
Assets: 38
Coverage: 94.7%
Certification: CONDITIONAL
Hash: 9c7a...e18d
Owner: Platform Control
Integrity Coverage
Application binaries MATCH
Environment variables MATCH
Database schema MATCH
Risk policies MATCH
Connector settings DRIFT
Routing rules REVIEW
Baseline rule: re-certification must create a new baseline version. Existing certified baselines remain immutable so historical production state can be reconstructed.
Drift Detection
Detected differences are classified by materiality, provenance and operational impact. Unknown or high-impact drift should trigger investigation and may require Safe Hold for affected execution paths.
DRIFT-004 · MT5 connector configuration
Observed value differs from approved configuration CFG-91A2. No matching change or emergency record found.
Threshold differs from baseline but maps to CHG-2088 awaiting closure evidence.
Monitoring
Medium impact
PENDING LINK
DRIFT-007 · Runtime flag
Flag changed during approved release window and matches deployment evidence.
Application
Low impact
EXPLAINED
Detection requirement: drift records should capture expected value, observed value, detection time, detection source, provenance reference and impact classification. Do not silently overwrite a drifted state.
Configuration Reconciliation
Each drift finding must be reconciled to one of four controlled outcomes: restore baseline, approve a new state through change control, link a valid emergency record, or open an exception requiring explicit authorization.
Drift
Expected
Observed
Disposition
Evidence
Gate
DRIFT-004
cfg-91a2
cfg-91b7
Investigate
None
BLOCK
DRIFT-005
10s
8s
Link emergency record
EMG-144
REVIEW
DRIFT-006
threshold=5
threshold=4
Link CHG-2088
CHG-2088
PENDING
DRIFT-007
false
true
Approved release
REL-04
MATCHED
Remediation & Exception Handling
Remediation must preserve evidence. Restoring the baseline may be appropriate, but the system should retain the observed state and the reason for remediation before it is changed.
Exception rule: an exception does not convert drift into an approved baseline. It records an authorized deviation with an owner, expiry, compensating controls and review date.
Baseline Re-Certification Gate
A new production baseline may be certified only after material drift is dispositioned, evidence is complete and the resulting configuration is reconciled to an approved source.
All critical drift resolved NO
All observed changes have provenance 8 / 10
Configuration hashes captured YES
Exceptions reviewed YES
Production verification completed PENDING
Certification owner assigned YES
Gate Decision
Current DecisionBLOCKED
Certification remains blocked while DRIFT-004 is unauthorized and material. Re-certification should not erase the prior baseline or conceal the deviation.
Audit Timeline
09:14:22 · Drift detectedCFG scanner observed connector state cfg-91b7 against baseline cfg-91a2.
09:16:04 · Finding classifiedImpact raised to High because the asset participates in execution connectivity.
09:21:48 · Reconciliation openedNo approved change reference found in the current registry.
09:25:11 · Certification blockedBaseline re-certification gate retained in BLOCKED state.
STEP 53 • COMPLIANCE GOVERNANCE
Regulatory / Compliance Control Framework
Governance layer untuk memetakan kewajiban regulasi, applicability, kontrol, evidence, pengujian, exception, remediation, attestation, dan kesiapan compliance. Status di halaman ini adalah status governance/prototype, bukan pernyataan sertifikasi atau kepatuhan hukum aktual.
Compliance Review
Regulatory Obligation Registry
REG-OBL-001
Obligation inventory & ownership
Applicability Matrix
APP-042
Jurisdiction / product scope
Control Mapping
CTL-MAP-118
Obligation → control traceability
Compliance Gate
REVIEW
Evidence & exceptions require validation
Regulatory Obligation Registry
Obligation
Scope
Owner
Review
Status
REG-OBL-001
Platform Governance
Compliance Owner
Periodic
Review
REG-OBL-002
Data / Privacy
Data Governance
Change-driven
Mapping Required
REG-OBL-003
Broker / Third Party
Risk Owner
Periodic
Pending
Jurisdiction / Applicability Matrix
Jurisdiction
Service
Applicability
Basis
JUR-01
Copy Trading
Review
Regulatory analysis required
JUR-02
Broker Connectivity
Pending
Service / entity scope
JUR-03
Data Processing
Review
Data-flow assessment
Compliance Control Mapping
REG-OBL-001Obligation mapped to CTL-SEC-014 / CTL-AUD-009Evidence owner assigned
REG-OBL-002Mapped to data classification, access and retention controlsControl test pending
REG-OBL-003Mapped to third-party due diligence and SLA controlsApplicability review pending
Policy & Procedure Registry
POL-001 — Compliance PolicyReview
POL-002 — Regulatory Change ProcedureActive
POL-003 — Exception & Remediation ProcedureReview
POL-004 — Evidence / Attestation ProcedurePending
Regulatory Change Monitoring
Change IntakeMonitored
Applicability Re-assessmentRequired
Control Impact AnalysisPending
Policy UpdatePending
Compliance Evidence & Attestation
Evidence
Control
Integrity
Attestation
EVD-CMP-001
CTL-AUD-009
Recorded
Pending
EVD-CMP-002
CTL-DAT-012
Recorded
Not Due
EVD-CMP-003
CTL-TPR-006
Review
Pending
Breach / Non-Compliance Exception Registry
CMP-EX-001Open
CMP-EX-002Under Review
CMP-EX-003Remediation Planned
Evidence Gap2 Items
Remediation / CAPA
CAPA-CMP-001Close evidence gap for mapped obligationOwner assigned • verification required
CAPA-CMP-002Revalidate applicability after regulatory changeImpact analysis pending
Gate tidak menyatakan status legal compliance. Produksi harus memvalidasi kewajiban berdasarkan yurisdiksi dan entitas yang relevan, melibatkan counsel/compliance officer bila diperlukan, serta menyimpan evidence dan keputusan applicability yang dapat diaudit.
STEP 54 • CONTROL ORCHESTRATION
End-to-End Control Orchestration
Control-plane untuk menghubungkan identity, configuration, audit, security, fraud, privacy, resilience, operational risk, third-party, dan compliance menjadi satu alur traceability dan decision gate. Ini adalah governance/prototype layer; keputusan produksi tetap membutuhkan backend, policy engine, evidence store, dan authorization enforcement.
EvaluateIdentity, policy, risk, configuration and dependency controls evaluatedDecision inputs collected
CorrelateAudit events, evidence, alerts, incidents and exceptions linked by correlation IDEvidence graph constructed
GateApplicable blocking and review rules determine the control statePolicy-driven decision
Execute / HoldAuthorized action proceeds or remains held pending remediation / approvalOutcome recorded
CloseEvidence, attestation, remediation and final decision are retainedAudit-ready closure
Control Orchestration Health
Cross-domain event correlationOperational
Decision provenanceRecorded
Policy evaluation coverageReview
Exception propagationOperational
Evidence completenessReview
Human approval checkpointsEnforced by policy
End-to-End Control Gate
Identity → Change → Configuration → Execution → Audit → Security → Fraud → Data → Recovery → Risk → Third Party → Compliance → DecisionREVIEW REQUIRED
Orchestrator harus menjadi decision layer yang dapat ditelusuri, bukan sumber kebenaran tunggal yang menggantikan enforcement backend. Produksi harus memastikan setiap gate memiliki policy ID, input evidence, decision reason, actor/service identity, timestamp, correlation ID, dan mekanisme override yang terotorisasi.
STEP 55 • EXECUTIVE GOVERNANCE
Platform Governance & Executive Control Center
Executive control layer untuk melihat health, risk, compliance, security, resilience, third-party dependency, control effectiveness, dan decision gates secara teragregasi. Tampilan ini merangkum evidence dari domain governance sebelumnya dan tidak menggantikan source-of-truth backend atau otorisasi operasional.
Executive Review
Platform Control Health
REVIEW
Cross-domain governance state
Critical Open Items
09
Require owner / disposition
Active Decision Gates
14
Policy-driven checkpoints
Executive Gate
REVIEW
Evidence and exceptions under review
Executive Control Summary
Domain
Control State
Open Issues
Evidence
Gate
Identity & Privilege
Operational
01
Complete
PASS
Change & Configuration
Operational
01
Complete
PASS
Audit & Evidence
Review
02
Partial
REVIEW
Security / Fraud
Review
02
Partial
REVIEW
Data / Privacy
Operational
01
Complete
PASS
Resilience / Recovery
Operational
00
Complete
PASS
Operational Risk
Review
01
Partial
REVIEW
Third Party / Broker
Review
01
Partial
REVIEW
Regulatory / Compliance
Review
02
Partial
REVIEW
Executive Risk Register
Critical operational exposureReview
Security incident exposureReview
Third-party concentrationMonitor
Compliance evidence gapOpen
Resilience readinessValidated
Control effectivenessReview
Key Control Indicators
Preventive controlsOperational
Detective controlsOperational
Corrective controlsReview
Evidence integrityReview
Exception agingMonitor
Gate coverageMapped
Executive Decision Queue
Decision
Context
Owner
Required Evidence
Status
EXE-DEC-001
Security / audit evidence exception
Security Governance
Integrity verification
Pending
EXE-DEC-002
Compliance applicability review
Compliance Owner
Applicability analysis
Pending
EXE-DEC-003
Third-party dependency exception
Risk Owner
Contingency evidence
Monitoring
EXE-DEC-004
Control effectiveness remediation
Control Owner
Retest result
Open
Governance Escalation Matrix
Level 1 • Control OwnerResolve routine exceptions and maintain evidenceOperational remediation
Level 2 • Risk / ComplianceReview material exceptions and policy impactsGovernance escalation
Level 3 • ExecutiveReview cross-domain exposure and unresolved gatesDecision authority
Level 4 • Formal Incident / Legal ReviewTriggered only where policy, contractual or legal criteria require itDocumented escalation path
Executive Reporting Pack
Control health summaryAvailable
Risk & exception registerAvailable
Security / incident summaryAvailable
Resilience readinessAvailable
Compliance evidence indexPartial
Decision audit trailRecorded
Governance Accountability
AccountabilityEvery material decision maps to an accountable owner and policy basisOwner + authority + timestamp
TransparencyExecutive summaries retain links to underlying controls and evidenceSummary → evidence reconstruction
Exception DisciplineOverrides require documented rationale, authorization and expiry where applicableNo silent bypass
Platform State → Risk → Control Health → Evidence → Exceptions → Decisions → Accountability → Executive GateREVIEW REQUIRED
Executive control center menyajikan ringkasan governance, bukan approval otomatis. Setiap keputusan material harus tetap mengikuti delegation of authority, segregation of duties, policy yang berlaku, evidence yang dapat diaudit, dan mekanisme eskalasi yang terdokumentasi.
STEP 56 • SYSTEM INTEGRATION
Final System Integration & Cross-Control Validation
Integration layer untuk memvalidasi hubungan antar-domain governance dari identity sampai executive decision. Fokusnya adalah traceability, dependency coverage, gate consistency, evidence continuity, exception propagation, dan cross-control validation sebelum masuk ke production-readiness gate.
Integration Review
Integration Coverage
96%
Cross-control mappings validated
Validation Checks
48 / 50
Two checks require review
Traceability
98%
Identity → decision evidence chain
Integration Gate
REVIEW
Open validation findings remain
System Control Domains
Domain
Source
Downstream Dependency
Validation
Gate
Identity & Privilege
Access / Session
Audit / Execution
Passed
PASS
Change & Configuration
Change / Baseline
Release / Drift
Passed
PASS
Audit & Evidence
Events / Integrity
Incident / Compliance
Passed
PASS
Security / Fraud
Telemetry / Detection
Incident / Response
Review
REVIEW
Data / Privacy
Data Assets / Access
Retention / Compliance
Passed
PASS
Resilience
Backup / DR Test
Recovery / Resume
Passed
PASS
Risk / Third Party
Risk / Vendor
CAPA / Governance
Passed
PASS
Regulatory / Compliance
Obligation / Applicability
Evidence / Attestation
Review
REVIEW
Executive Governance
Aggregated Gates
Decision / Escalation
Passed
PASS
Cross-Control Validation Matrix
Validation
Expected Relationship
Observed
Status
VAL-001
Identity → Privileged Action → Audit
Correlation preserved
PASS
VAL-002
Change → Configuration Baseline → Drift
Trace preserved
PASS
VAL-003
Security Alert → Incident → Evidence
Evidence link requires review
REVIEW
VAL-004
Data Event → Privacy → Compliance
Trace preserved
PASS
VAL-005
Third Party Incident → Risk → CAPA
Trace preserved
PASS
VAL-006
Compliance Exception → Executive Gate
Escalation preserved
PASS
Validation Coverage
Identity traceability100%
Configuration lineage100%
Audit correlation98%
Security incident linkage92%
Data / privacy lineage100%
Compliance evidence lineage94%
Executive decision provenance100%
Integration Test Queue
IT-056-001Validate correlation ID propagation across security incident and audit evidenceOwner: Security Governance • Status: Review
ActorIdentity and privilege state identifiedUSR-017
ActionPrivileged / operational action correlated to resourceCORR-8F21
System StateConfiguration, release and dependency state reconstructedBaseline + drift evidence
DetectionSecurity / anomaly signals linked where applicableAlert → incident chain
EvidenceAudit, integrity, retention and compliance evidence assembledEvidence package
DecisionApplicable risk, policy and governance gates reconstructedDecision provenance
OutcomeExecution, hold, remediation or closure outcome recordedFinal state
Open Integration Findings
Finding
Impact
Owner
Required Action
Status
INT-FND-001
Evidence lineage
Security Governance
Complete cross-system evidence link
OPEN
INT-FND-002
Compliance escalation
Compliance Owner
Validate applicability → gate mapping
OPEN
Final Integration Gate
Identity → Change → Configuration → Execution → Audit → Security → Fraud → Data → Recovery → Risk → Third Party → Compliance → Executive GovernanceREVIEW REQUIRED
Gate hanya dapat dinyatakan siap setelah seluruh cross-control validation yang material selesai, evidence lineage lengkap, open findings memiliki disposition yang sah, dan setiap domain menghasilkan decision state yang konsisten dengan policy. Angka pada prototype ini adalah contoh UI, bukan hasil audit produksi.
STEP 57 • PRODUCTION READINESS
Production Readiness / Go-Live Gate
Final pre-production control layer untuk menilai kesiapan platform sebelum deployment. Gate menggabungkan technical readiness, security, identity, configuration, audit/evidence, resilience, operational controls, third-party, compliance, support, rollback, dan executive authorization. Status prototype tidak merupakan approval produksi aktual.
Go-Live Review
Readiness Coverage
94%
Pre-production checks mapped
Mandatory Gates
18 / 20
Two gates require closure
Open Blockers
02
Must be dispositioned before go-live
Go-Live Decision
HOLD
Pending final evidence / authorization
Production Readiness Checklist
Domain
Readiness Requirement
Evidence
Owner
Status
Application
Build / dependency validation
Release evidence
Engineering
PASS
Security
Threat / vulnerability controls
Security test evidence
Security
REVIEW
Identity
RBAC / privileged access certification
Access certification
IAM Owner
PASS
Configuration
Production baseline / drift controls
Baseline hash / registry
Platform Ops
PASS
Audit
Event / evidence integrity
Audit verification
Audit Owner
REVIEW
Resilience
Backup / restore / recovery validation
DR test evidence
Resilience
PASS
Operations
Monitoring / alerting / support coverage
Runbook + monitoring
Operations
PASS
Third Party
Broker / vendor readiness
Due diligence / SLA
Risk Owner
REVIEW
Compliance
Applicability / obligation / evidence
Compliance package
Compliance
REVIEW
Technical & Infrastructure Gate
Build artifact integrityPASS
Environment parityPASS
Database migration validationPASS
Secrets / credential readinessREVIEW
Observability coveragePASS
Capacity / dependency readinessPASS
Security & Access Gate
Least privilegePASS
Privileged access certificationPASS
Security monitoringPASS
Incident response readinessPASS
Evidence integrityREVIEW
Break-glass procedurePASS
Operational & Recovery Readiness
RunbookDeployment, rollback, incident, recovery and escalation procedures validatedOperational documentation
BackupBackup integrity and restore procedures tested against defined recovery objectivesRecovery evidence
FailoverFailover / failback dependencies and controlled resume conditions validatedContinuity readiness
SupportOwnership, escalation contacts, on-call coverage and incident workflow establishedSupport readiness
Release & Rollback Gate
Control
Required State
Observed
Status
Release artifact
Approved / immutable
Recorded
PASS
Deployment plan
Reviewed
Validated
PASS
Rollback artifact
Available / tested
Validated
PASS
Rollback decision authority
Assigned
Assigned
PASS
Post-deploy verification
Defined
Defined
PASS
Go-Live Dependencies
Critical open incidentNone
Critical configuration driftNone
Unresolved evidence integrity01
Compliance evidence gap01
Third-party critical blockerNone
Executive authorizationPending
Go-Live Blocker Registry
Blocker
Domain
Impact
Required Closure
Status
GLB-001
Audit / Evidence
High
Complete integrity verification and evidence linkage
OPEN
GLB-002
Compliance
High
Finalize applicability and evidence review
OPEN
Final Authorization Chain
Control OwnersConfirm domain-specific readiness and evidence completenessOwner certification
Risk / Security / ComplianceReview material exceptions, residual risk and applicable obligationsIndependent governance review
OperationsConfirm deployment, monitoring, support and rollback readinessOperational sign-off
Executive AuthorityApprove or hold go-live according to documented delegation of authorityFinal authorization
Post-Go-Live GateValidate production behavior and retain deployment evidenceControlled transition
Production Go-Live Gate
Build → Security → Identity → Configuration → Audit → Data → Resilience → Operations → Third Party → Compliance → Risk → Executive AuthorizationHOLD
Go-live hanya dapat dibuka setelah seluruh mandatory blocker ditutup atau memiliki exception yang sah sesuai governance. Prototype ini tidak memberikan authorization produksi; production gate harus dieksekusi oleh sistem backend dan pejabat/owner yang berwenang dengan evidence yang dapat diaudit.
STEP 45 · Evidence Lifecycle Governance
Audit Evidence Retention, Legal Hold & Controlled Export
Memastikan evidence audit tidak hanya immutable dan dapat dikorelasikan, tetapi juga
memiliki lifecycle yang terkontrol: classification → retention → hold → access →
export → verification → disposition.
05 · DisposeControlled disposition only after all blockers clear.
Prinsip utama: retention tidak boleh mengalahkan legal hold, dan export tidak boleh
menjadi jalan untuk melewati access control atau evidence integrity.
Lifecycle State
RETENTIONNormal evidence preservation
LEGAL HOLDDisposition blocked
EXPORT REVIEWApproval required
VERIFIEDIntegrity confirmed
EXCEPTIONManual review required
DISPOSE READYAll gates clear
Retention Registry
Evidence Set
Class
Owner
Retention
Expiry
State
AUD-2026-09-17-104xxx
OPS-AUDIT-07Y
Audit Ops
7 years
2033-09-17
ACTIVE
INC-1042-EVIDENCE
INCIDENT-07Y
Incident Owner
7 years
2033-09-17
HOLD LINKED
CHG-2048-PACK
CHANGE-03Y
Release Owner
3 years
2029-09-17
ACTIVE
EXPORT-0091
CONTROLLED-01Y
Compliance
1 year
2027-09-17
REVIEW
Nilai retention di atas adalah contoh policy class untuk prototype. Implementasi produksi harus mengambil policy dari policy engine yang disetujui.
Active Legal / Investigation Holds
Hold ID
Scope
Reason
Owner
Disposition
HOLD-003
INC-1042
Investigation evidence preservation
Compliance
BLOCKED
HOLD-002
USR-017 / CHG-2048
Access & change review
Security
BLOCKED
HOLD-001
CORR-8F21
Evidence correlation package
Audit Ops
BLOCKED
Hold Enforcement
HOLD ACTIVE
→ freeze disposition
→ preserve original evidence
→ preserve integrity metadata
→ preserve access/export history
→ allow only authorized review
→ release hold requires recorded approval
→ recalculate disposition eligibility
Evidence hanya boleh masuk disposition setelah retention selesai, tidak ada active hold, tidak ada open investigation, integrity state verified, dan seluruh required approvals terpenuhi.
Exception tidak boleh dihapus hanya karena retention clock telah habis.
Evidence Lifecycle Gate
Retention PolicyPASS
Legal Hold CheckPASS · no unsafe release
Integrity CheckPASS for eligible set
Access ReviewPASS
Export Review12 requests pending
DispositionBLOCKED by 1 exception
GATE STATUS: REVIEW REQUIRED
Tidak ada evidence yang boleh di-dispose ketika legal hold aktif atau integrity exception belum diselesaikan.
Mengubah audit trail menjadi security detection layer: mengumpulkan security telemetry,
mendeteksi pola anomali, menghubungkan event lintas sistem, menetapkan severity,
melakukan triage, dan menyediakan controlled escalation tanpa mengubah evidence sumber.
8,421Security Events / 24h
17Active Detections
04High-Severity Alerts
99.2%Telemetry Coverage
Security Detection Control Objective
01 · ObserveCollect identity, access, configuration, execution and platform telemetry.
02 · NormalizeNormalize timestamp, actor, resource, source and correlation context.
03 · DetectEvaluate rules, thresholds and behavioral anomalies.
04 · CorrelateConnect alerts to audit, change, identity and execution evidence.
05 · TriageClassify severity, confidence, impact and required response.
06 · EscalateCreate controlled security incident when escalation criteria are met.
Detection adalah signal, bukan bukti final. Evidence asli tetap berada pada audit/evidence
layer dan tidak boleh dimodifikasi oleh detection engine.
Current Security State
Telemetry99.2% coverage
Detection17 active rules
Critical0 uncontained
High4 pending triage
Correlation96.4% enriched
GateREVIEW REQUIRED
Security Telemetry Registry
Source
Telemetry
Coverage
Integrity
Latency
State
Identity Provider
Login / MFA / privilege events
100%
Verified
2.1s
HEALTHY
Copy Orchestrator
Execution / session / service events
99.8%
Verified
1.4s
HEALTHY
Configuration Store
Baseline / drift / change events
98.7%
Verified
4.8s
MONITOR
Broker Connector
Connection / order / response telemetry
97.9%
Verified
3.7s
MONITOR
Detection Rule Registry
Rule
Pattern
Severity
Confidence
Response
State
DET-PRIV-001
Privileged access outside approved window
HIGH
High
Escalate + correlate
ACTIVE
DET-CFG-004
Production config mutation after baseline
HIGH
High
Freeze + investigate
ACTIVE
DET-AUTH-002
Repeated authentication anomaly
MEDIUM
Medium
Challenge + review
ACTIVE
DET-COPY-007
Execution pattern inconsistent with policy
CRITICAL
Medium
Trading hold gate
REVIEW
Rule examples di atas adalah prototype logic. Production detection engine harus versioned, tested, approved, monitored for false positives, dan memiliki rollback/change governance.
Mengubah security detection menjadi response lifecycle yang terkontrol: incident intake,
classification, containment, evidence preservation, response actions, recovery coordination,
validation, communication, dan closure. Semua tindakan response tetap attributable dan masuk audit trail.
02 · IntakeCreate incident with unique ID and source alerts.
03 · ClassifySeverity, scope, confidence and affected assets.
04 · ContainLimit impact while preserving evidence.
05 · RespondExecute authorized response actions.
06 · RecoverRestore controlled operation and validate.
07 · CloseEvidence, RCA/CAPA, approvals and lessons learned.
Response action bukan sekadar “fix”. Setiap action harus memiliki actor, authorization,
timestamp, scope, expected result, actual result, dan evidence.
Current Response State
Open06 incidents
High02 incidents
Contained04 incidents
Evidence100% preserved
Recovery02 active
GateREVIEW REQUIRED
Incident Intake Registry
Incident
Source Alert
Detected
Scope
Owner
State
SEC-1042
ALT-7720
08:02:21
connector.mt5
Security Ops
INVESTIGATING
SEC-1041
ALT-7716
07:41:13
Identity Provider
IAM Ops
CONTAINED
SEC-1040
ALT-7709
06:55:49
Evidence Export
Compliance
RESOLVED
Incident intake harus mempertahankan source alert dan tidak mengganti evidence asli dengan ringkasan incident.
Governance layer untuk mendeteksi pola tidak wajar, penyalahgunaan privilege, manipulasi operasional, dan anomali trading tanpa langsung menganggap setiap anomaly sebagai fraud.
Detection Governance Active
Detection Rules186 high-risk
Open Signals072 require triage
High-Risk Cases02under investigation
Control GateGUARDEDno auto-verdict
Detection Signal Registry
Setiap sinyal memiliki rule, source, severity, confidence, dan correlation reference.
7 OPEN
Signal
Source
Pattern
Severity
Confidence
Status
FRA-2041
Execution
Order burst anomaly
HIGH
94%
OPEN
FRA-2039
Identity
Privilege use outside baseline
HIGH
91%
TRIAGE
FRA-2037
API
Repeated failed authentication
MEDIUM
87%
OPEN
FRA-2034
Copy Engine
Allocation deviation
MEDIUM
82%
REVIEW
Abuse Pattern Registry
Pattern library untuk penyalahgunaan layanan, account, privilege, dan execution path.
Execution Manipulation PatternSignal → Order → Broker ResponseHIGH
Account Abuse PatternLogin → Session → API ActivityMEDIUM
Resource Exhaustion PatternAPI → Rate → Queue → Service HealthMEDIUM
Anomaly Baseline & Behavioral Deviation
Baseline dipisahkan dari verdict. Deviation hanya menghasilkan signal untuk triage.
BASELINE VALID
Execution Rate+31%vs rolling baseline
Login Pattern+18%new device variance
API Failure+44%5-min window
Allocation Drift+7.2%policy threshold 5%
Important: anomaly ≠ fraud. Sistem hanya menentukan bahwa aktivitas menyimpang dari baseline atau rule. Penetapan abuse/fraud memerlukan evidence correlation dan human/control review.
Risk Scoring & Triage
Risk score digunakan untuk prioritas investigasi, bukan sebagai keputusan final.
REVIEW REQUIRED
Identity anomaly78 / 100
Execution anomaly91 / 100
API abuse indicators64 / 100
Evidence confidence86 / 100
Investigation GateGUARDEDEscalate high-confidence/high-impact signals to Security Incident Response.
Governance layer untuk memastikan data memiliki owner, classification, purpose, lifecycle, access boundary, retention policy, dan evidence trail yang dapat diaudit.
Privacy Governance Active
Data Domains12registered
Classified Assets98.7%coverage
Open Privacy Cases03under review
Privacy GateGUARDEDpolicy enforcement active
Data Asset Registry
Inventarisasi data berdasarkan domain, classification, owner, purpose, dan lifecycle.
REGISTERED
Asset
Domain
Classification
Owner
Purpose
Lifecycle
USR-PROFILE
Identity
CONFIDENTIAL
IAM
Account operation
ACTIVE
TRD-EXECUTION
Trading
RESTRICTED
Execution Ops
Order processing
ACTIVE
AUD-EVIDENCE
Audit
RESTRICTED
Compliance
Auditability
RETAINED
ANL-METRICS
Analytics
INTERNAL
Risk Ops
Monitoring
ACTIVE
Data Classification
Classification menentukan minimum handling, access, export, dan retention control.
POLICY CONTROLLED
PUBLICInformasi yang memang ditujukan untuk publikLOW
INTERNALOperational information dengan akses internalMEDIUM
CONFIDENTIALData account dan operational context terbatasHIGH
RESTRICTEDData berisiko tinggi dengan access & export control ketatCRITICAL
Purpose & Processing Governance
Setiap penggunaan data harus memiliki tujuan yang terdaftar dan scope yang sesuai.
PURPOSE MAPPED
Purpose Mapped96%registered processing
Unmapped Processing02requires remediation
Excess Collection01review required
Policy Exceptions03time-bound
Control principle: data yang tersedia tidak otomatis berarti boleh digunakan untuk semua tujuan. Processing harus terikat pada purpose, authorization, dan policy yang berlaku.
Privacy Risk & Triage
Risk scoring digunakan untuk memprioritaskan review dan remediation.
Anomaly CorrelationFRA-2044 linked to access deviation
05
Response GateBlocked and preserved for authorized investigation
Data Governance Controls
Minimum controls sebelum data dapat diproses, dibagikan, atau dihapus.
Asset ownershipPASS
ClassificationPASS
Purpose registrationPASS
Access authorizationPASS
Retention mappingPASS
Export/disclosure controlGUARDED
Privacy Governance Gate
Final gate untuk menjaga agar data governance terhubung ke control chain MQLPro.
Overall Data GovernanceGUARDEDOpen exceptions must be resolved, accepted under policy, or explicitly escalated before sensitive processing paths are released.
Control Chain
STEP 49 menambahkan data lifecycle dan privacy governance ke rangkaian kontrol MQLPro.
STEP 49 ACTIVE
Data Asset→Classification→Purpose→Identity & Access→Processing→Audit Evidence→Retention→Privacy Gate
STEP 58 · RELEASE CANDIDATE
Final Hardening & Release Candidate
Final hardening, artifact integrity, dependency validation, production baseline freeze, resilience rehearsal, and release-candidate acceptance.
PROTOTYPE · GOVERNANCE VIEW
RC StatusCONDITIONALPrototype acceptance state
Hardening Controls13Release candidate domains
Open Known Issues4Requires disposition
Production FreezeREADYPending final authorization
Release Candidate Registry
RC REGISTRY
RC ID
Version
Build
Environment
Status
Owner
RC-2026-058
8.0.0-rc1
BUILD-58041
PRE-PROD
CONDITIONAL
Release Engineering
RC-2026-057
7.9.4
BUILD-57984
STAGING
VALIDATED
Platform Engineering
Build Artifact Integrity / Hash & Provenance
INTEGRITY
Source CommitRELEASE-58041
Artifact Digestsha256:prototype-artifact-digest
Build ProvenanceTRACEABLE
Artifact SignatureVERIFY SERVER-SIDE
Promotion RecordRC-2026-058 → PRE-PROD
Dependency / Supply-Chain Validation
DEPENDENCIES
Dependency InventoryREGISTERED
Version PinningREVIEWED
Vulnerability ReviewPENDING FINAL SCAN
License / Provenance ReviewTRACEABLE
Unapproved Package0 detected in prototype registry
Security Hardening Checklist
SECURITY
Control
State
Evidence
Owner
Gate Impact
Least-Privilege Enforcement
READY
IAM-CERT-058
Security
PASS
Session / Token Controls
READY
SEC-SESSION-058
Security
PASS
Input / API Boundary Hardening
READY
API-HARD-058
Platform
PASS
Security Headers / Browser Policy
VERIFY
SEC-HEAD-058
Platform
REVIEW
Production Security Scan
PENDING
SCAN-058
Security
BLOCKER
Secrets / Credential / Key Rotation Readiness
SECRETS
Production Secrets StoreDEFINED
Credential Rotation PlanREADY
Signing / Encryption KeysROTATION TEST PENDING
Secret Exposure ScanNO PROTOTYPE FINDING
Break-Glass Credential ReviewREGISTERED
Configuration Lock / Production Baseline Freeze
FREEZE
Approved BaselineBASELINE-58041
Configuration FreezeREADY
Drift DetectionENABLED
Unauthorized Change WindowCLOSED
Exception RegisterCFG-EX-058-01
API / Connector / Broker Hardening
CONNECTIVITY
Boundary
Authentication
Authorization
Failure Handling
Status
Client API
Token / mTLS*
Scoped
Rate-limit + retry policy
READY
Copy Engine ↔ Connector
Service identity*
Least privilege
Fail-safe hold
READY
Broker Adapter
Broker-specific*
Account-scoped
Disconnect → HOLD
INTEGRATION TEST
Webhook / Event Boundary
Signed event*
Allow-list
Replay protection*
VERIFY
* Illustrative production control pattern. Actual mechanisms must be implemented and verified server-side for each integration.
PROTOTYPE GATE RESULTCONDITIONAL — NOT AUTHORIZED FOR PRODUCTION
The example state intentionally contains unresolved controls. Production authorization requires verified evidence, server-side enforcement, approved risk disposition, and accountable human approval.
Prototype disclaimer: This page is a governance/control-center prototype. Hashes, signatures, scans, approvals, SLOs, broker controls, key rotation, and security findings shown here are illustrative records and are not evidence of real implementation, penetration testing, certification, compliance, or production authorization.
STEP 59 · AUDIT READINESS
Final Audit / Certification Readiness
Evidence completeness, control traceability, audit-request management, certification scope, remediation status, and final audit closure readiness.
PROTOTYPE · AUDIT READINESS
Audit ReadinessCONDITIONALIllustrative governance state
Controls in Scope59Integrated control domains
Evidence Completeness92%Prototype evidence index
Open Findings4Disposition required
Audit Readiness Registry
READINESS
Audit ID
Scope
Period
Evidence State
Findings
Gate
AUD-2026-059
MQLPro Control Framework
Release 8.0
CONDITIONAL
4
REVIEW
AUD-2026-058
Security / Operations
Release 7.9.4
COMPLETE
0
CLOSED
Control Evidence Completeness
EVIDENCE
Governance / Policy Evidence100%
Identity / Privilege Evidence98%
Audit / Integrity Evidence96%
Security / Incident Evidence91%
Resilience / Recovery Evidence89%
Release / RC Evidence87%
Policy / Control Traceability
TRACEABILITY
Policy → ControlMAPPED
Control → TestMAPPED
Test → EvidenceMAPPED
Evidence → FindingMAPPED
Finding → Remediation4 OPEN
Remediation → ClosurePENDING
Audit Request Tracker
PBC / REQUESTS
Request
Requested Evidence
Owner
Due
Status
PBC-059-001
Production access certification
Security
2026-09-21
READY
PBC-059-002
Release artifact provenance
Release Engineering
2026-09-21
READY
PBC-059-003
Broker connector test evidence
Integration
2026-09-22
PENDING
PBC-059-004
Security scan / remediation proof
Security
2026-09-22
PENDING
Evidence Package Index
PACKAGE
Package IDEVID-PKG-2026-059
Control Evidence Items486 indexed
Integrity VerificationPASS
Retention / Legal HoldLINKED
Export ManifestGENERATED
Missing / Pending Items4
Management Representation / Attestation Readiness
ATTESTATION
Management Representation DraftPREPARED
Control Owner Attestations56 / 59
Exception DisclosuresINDEXED
Known Issues DisclosurePENDING FINALIZATION
Final Sign-OffNOT EXECUTED
Finding / Remediation Register
FINDINGS
Finding
Domain
Severity
Remediation
Owner
State
FND-059-01
Security
HIGH
Complete final security scan + evidence
Security
OPEN
FND-059-02
Integration
HIGH
Complete broker adapter validation
Integration
OPEN
FND-059-03
Secrets
MEDIUM
Rehearse key rotation
Security
OPEN
FND-059-04
Performance
MEDIUM
Complete load/failure evidence
Platform
OPEN
Certification Scope / Boundary
SCOPE
In ScopeApplication, API, copy-control plane, governance controls
Infrastructure ScopeProduction hosting and data services
Out of ScopeThird-party environments not contractually assessed
Boundary ApprovalPENDING
Audit Closure Gate
CLOSURE
Evidence CompletenessREVIEW
TraceabilityPASS
Audit Requests4 PENDING
Findings4 OPEN
AttestationPENDING
Scope ApprovalPENDING
Final Audit Readiness Gate
AUDIT GATE
PROTOTYPE GATE RESULTCONDITIONAL — AUDIT / CERTIFICATION NOT YET CLOSED
The displayed records are illustrative. Certification requires an appropriately scoped independent assessment or applicable assurance process, verified evidence, documented findings, remediation, and authorized sign-off. This interface does not itself constitute certification.
Prototype disclaimer: This page is an audit-readiness governance prototype. It does not issue, imply, or replace a real audit opinion, certification, regulatory approval, penetration-test result, compliance attestation, or independent assurance conclusion.
STEP 60 · FINAL ARCHITECTURE
MQLPro Final Architecture / Production Baseline
Final reference architecture, component ownership, interfaces, security boundaries, data flows, copy-engine boundaries, observability, governance planes, deployment topology, and production baseline.
PROTOTYPE · FINAL BASELINE
Architecture StateBASELINEDReference architecture defined
* Adapter choice depends on the broker and approved integration method. The architecture must not assume that every broker exposes the same API or execution interface.
User / Strategy→Signal→Eligibility→Risk Gate→Copy Decision→Normalized Order→Broker Connector→Execution→Reconciliation→Audit Evidence
CorrelationOne correlation identifier follows the transaction across control domains.
Failure PrincipleUncertain execution state routes to reconciliation / HOLD rather than silently assuming success.
Audit PrincipleMaterial decisions and privileged actions generate attributable evidence.
Copy Engine / Broker Connector Boundary
TRADING CORE
Layer
Responsibility
Must Not Own
Control
Signal Intake
Receive normalized strategy events
Direct broker credentials
Schema + authenticity validation
Copy Engine
Determine follower execution instruction
Unbounded broker access
Risk / policy gate
Risk Engine
Evaluate limits and eligibility
UI presentation logic
Deterministic decision record
Order Orchestrator
Coordinate order lifecycle
Strategy secrets
Idempotency + state machine
Broker Connector
Translate command to broker interface
Global platform policy
Account scope + connector health
Reconciliation
Compare intended vs broker-confirmed state
Blind auto-assumption
Exception / HOLD gate
The exact connector mechanism—broker API, FIX, MT5/EA bridge, or another approved adapter—must be selected from the broker's documented capabilities and operational constraints. A Python process alone is not inherently a broker connector; it is an implementation runtime that still requires a valid execution interface.
Observability Architecture
TELEMETRY
MetricsLatency, throughput, error rate, exposure, connector health
* Infrastructure components are architectural examples, not claims that they are already deployed.
Production Baseline
BASELINE
Baseline Domain
Required State
Current Prototype
Production Evidence
Source / Build
Reproducible, signed, traceable
REFERENCE
CI/CD evidence required
Identity / Access
Least privilege + certification
MODELED
Live IAM evidence required
Execution / Risk
Deterministic gates + fail-safe states
MODELED
Integration / test evidence required
Broker Connectivity
Approved, authenticated, monitored adapter
REFERENCE
Broker-specific validation required
Data / Backup
Recovery-tested and reconciled
MODELED
Infrastructure evidence required
Audit / Evidence
Integrity, retention, reconstruction
MODELED
Backend implementation required
Observability
Alerting + SLO + incident response
REFERENCE
Live telemetry evidence required
Final Release Gate
ARCHITECTURE GATE
Architecture DefinitionPASS
Component OwnershipPASS
Interface BoundariesPASS
Security BoundariesPASS
Copy / Connector BoundaryPASS
Data / Evidence PlanePASS
ObservabilityIMPLEMENTATION
Production InfrastructureIMPLEMENTATION
Independent ValidationREQUIRED
PROTOTYPE GATE RESULTARCHITECTURE BASELINED — PRODUCTION IMPLEMENTATION REQUIRED
This STEP establishes the reference architecture and governance baseline. The current one-file HTML remains a prototype control-center presentation layer; it is not the backend, trading engine, broker connector, database, security system, or production deployment architecture.
Final prototype disclaimer: STEP 60 is the final reference-architecture/control-center baseline for this prototype series. It does not certify that MQLPro has been implemented, security-tested, independently audited, approved by a broker, approved by a regulator, or authorized for production. Real production readiness requires separate backend services, execution infrastructure, broker-specific integrations, security controls, data stores, operational procedures, testing, evidence, and accountable approvals.