The Armor · risk architecture · independent supervision

Risk is an operating discipline, not a footer.

Controls start before an order exists, run inside every isolated bot, and extend to account and operational supervision. One system.

Position capsBot circuit breakersAccount-level drawdown controlsWeekend flat-guard
TPC / RIndependent risk supervision
Controls active
  • 01PositionExposure capsActive
  • 02BotCircuit breakersActive
  • 03AccountDrawdown refereeActive
  • 04OperationsCalendar + monitoringActive
PORTFOLIO BOUNDARYSupervision activeIndependent above every bot
FOUR CONTROL LAYERSONE PORTFOLIO BOUNDARY

Layered risk architecture

Four control layers. One portfolio boundary.

Position, bot, account, and operations. No single safeguard carries the full burden.

01

Position layer · per-position sizing caps

Exposure begins capped.

Every position is capped before it can touch portfolio risk.

02

Bot layer · catastrophic circuit breakers

Each bot has its own boundary.

Unique identifiers, isolated state, per-bot circuit breakers. No bot can interfere with another.

03

Account layer · drawdown referee

A referee sits above every bot.

Account-level drawdown controls govern total exposure as roster bots are promoted, reduced, or retired.

04

Operations layer · weekend flat-guard

The market week has a hard edge.

A weekend flat-guard and independent dashboards supervise the 24/5 operating window.

Bot isolation

Every active bot operates within its own risk envelope.

The roster is a governed set of specialized bots and flexes with market fit. The isolation model never changes: every bot manages only its own orders under its own identifier and limits, while account-level controls watch total exposure.

  • Unique bot identifier
  • Independent order and position state
  • Per-bot circuit breaker
  • Portfolio-level exposure coordination
  • EURUSD×—
  • GBPUSD×—
  • USDJPY×—
  • USDCHF×—
  • USDCAD×—
  • AUDUSD×—
  • NZDUSD×—
Account-level referee A governed roster of active algo bots Total exposure view

Operational diligence

The environment is governed as carefully as the bots.

Separation, release discipline, monitoring, and response protect the live system's integrity.

01

Separation

Research workloads never run inside the dedicated live MetaTrader VPS.

02

Release control

Only reviewed, versioned, compiled EX5 artifacts cross the live boundary.

03

Monitoring

Independent dashboards supervise execution, bot state, and account-level risk.

04

Calendar guard

The weekend flat-guard puts a hard edge on the 24/5 FX cycle.

05

Response

Bots are reduced, quarantined, or retired without touching another bot's controls.

06

Rotation

Capital concentration remains subject to the same portfolio risk constraints.

Results in context

Results belong inside a complete risk view.

Performance is reported as historical observations from real broker fills on a model stack — never as forecasts, guarantees, or audited track-record claims. The complete figures live inside the client dashboard, where every number sits beside the ledger that produced it.

Broker-directEvery figure derives from broker deal history
Ledger-scopedResults are always shown against their full month-by-month record

Published in the client dashboard · read-only

Dashboard figures are historical observations on a model-stack presentation basis (not actual AUM or broker equity). Not annualized, projected, targeted, audited, or guaranteed. Trading involves risk of loss. Full disclosures

Live reporting

Review live results with timing and risk context.

Open the dashboard