$ cat /forge/markets.md —— a decade on the tape, from MetaTrader to real-time crypto feeds

Algorithmic Trading & Real-Time Market Data

Dragos Postelnicescu|AI Systems Engineer · 25+ years infrastructure · ~10 years algorithmic trading

This is the market-facing line of my work, in one place. It starts with ten years of MetaTrader/MQL engineering — Expert Advisors, custom indicators, tick-level backtesting and risk frameworks — and runs through to real-time market-data pipelines that stream live ticks off broker terminals and monitor live crypto venues, score them with disciplined multi-model decision systems, and gate every action behind honest measurement. Built, run, and repaired end-to-end on my own multi-node platform, the Forge. The through-line maps directly onto real-time market-data architecture: ingest, normalize, distribute low-latency, validate rigorously, manage risk, and own it from wire to decision.

~10 yrsMQL / algorithmic trading
~600 MBpersonal MQL corpus
live ticks2 broker feeds · 8 FX pairs · ~5 ms IPC
multi-venuecrypto real-time monitors
L1–L3verification before promotion

Read this first. This is the work of a solo research-and-production lab (NexCore AI), not a record of enterprise client deployments. Every performance figure below is a measured evaluation metric from my own test harness — research instrumentation, not a returns claim and not financial advice. Live trading capital is small and deliberately not overstated; most systems here are read-only market-data monitoring and offline research, with any execution gated behind manual approval. What I am showing is capability, engineering discipline, and depth — a decade of it.

Real-time market-data architecture, mapped to what I've actually built.

The role is multi-channel real-time market-data infrastructure: low-latency, high-throughput distribution, fail-over and DR, wired into trading systems and market-data flows. Here is the honest mapping — each requirement against concrete, running work on the Forge, followed by the systems themselves.

RequirementMulti-channel, multi-venue real-time market data
Live tick feeds streamed off two MetaTrader broker terminals (Admiral, RoboForex) across 8 FX symbols via a file-bridge harvester, plus live crypto venue feeds from Bybit v5 and MEXC over their REST APIs, each behind a per-venue normalizing monitor. Adding a venue means adding an adapter, not rewriting the core.
RequirementLow-latency, high-throughput distribution
MetaTrader↔Python inter-process comms over a RAM-drive file channel at ~5 ms to spare SSD wear and keep round-trips tight; per-bar-close scoring; streaming deltas rather than re-polls; a standing idle-timeout keep-alive rule so long-running model calls are never killed mid-stream by a wall-clock; GPU-local model pools next to the data.
RequirementFail-over, DR & resilience
Node-liveness watchdogs poll the whole fleet on a 60-second cycle and diagnose flaps; exchange clients carry retry/backoff, server-time re-sync and reconnect; automated cross-node backups; and hard kill-switches at the trading layer — daily-loss stops and liquidation-distance cut-outs that trip before capital is at risk.
RequirementBacktesting & validation rigor
A walk-forward backtest engine (Sharpe, profit factor, drawdown), tick-level MetaTrader Strategy-Tester validation with slippage and spread modelling, a vectorized OHLCV replay oracle that grades every signal against what price actually did, and a calibration layer scored by Brier skill against a persistence baseline. Sample-size honesty is enforced — a 70% win-rate at n=20 that reverted to 47% at n=43 is recorded as a gotcha, not a headline.
RequirementRisk management
A 7-gate pre-trade filter (drawdown, correlation, position size, spread, session, signal score, market regime); factor-neutral portfolio research with an idiosyncratic-risk buffer and a liquidation-surface kill-switch; adaptive position sizing; and session/spread/regime gates that simply refuse to trade dead or chaotic markets.
RequirementEnd-to-end ownership: architecture → build → handover
Every system here was designed, built, deployed and operated by one person — self-hosted under systemd, exposed through Cloudflare tunnels, observable via Grafana/Prometheus/Loki, and documented in a queryable institutional memory so nothing is lost between sessions. This is Digiterre's stated DNA — owning delivery from wire to decision — done solo, at depth.

Six systems, one lineage.

From the MetaTrader foundation to the real-time crypto era. Expand any card for architecture, data flow, and what's actually measured. Badges say what each one is — a foundation, a live market-data pipeline, or active research.

01 MetaTrader / MQL — a decade of algorithmic tradingFoundation · ~10 yrs The oldest and most on-point credential: Expert Advisors, custom indicators, and a mathematical, non-indicator trading approach — built over roughly ten years.

My market work begins on MetaTrader. Across roughly a decade I wrote Expert Advisors and custom indicators in MQL4 and MQL5, tested and compiled in the terminal, and pursued a deliberately mathematical, non-indicator approach to trading — price structure and geometry rather than lagging oscillators. That philosophy became the “9-point” method: a structured multi-factor score rather than a single crossover signal. I validated in the Strategy Tester on historical data pulled straight from the terminal, down to tick level, with slippage and spread modelled and risk-per-trade and reward-to-risk fixed in code. The result is a large personal body of work — a ~600 MB corpus of MQL (roughly half original, half studied third-party EAs and indicators; one archive alone holds 156 source files, including a 6,000-line multi-type grid EA and polynomial-regression indicators). Two research threads grew out of it: MetaTrader↔Python↔LLM bridges to drive strategies from modern code, and an exploratory LLM-consensus approach to reconstructing compiled .ex4/.ex5 EA logic where conventional decompilers fail.

> The honest gap I found reviewing a decade of my own EAs: strong entry ideas, thin risk and money management. Fixing that discipline is what the newer systems are about.

MQL4 / MQL5 EA + indicator→ Strategy Tester · tick + slippage→ optimization→ risk framework→ live MetaTrader
What's in the record
  • Since 2013 — ~10 years of MQL4/MQL5 Expert Advisors and indicators
  • ~600 MB corpus; a single archive = 156 source files (grid EAs, polynomial-regression indicators)
  • Mathematical, non-indicator “9-point” approach; tick-level Strategy-Tester validation
  • MetaTrader↔Python↔LLM bridge (research) · .ex4/.ex5 LLM-consensus decompilation (research)
MQL4 / MQL5Expert AdvisorsStrategy Testerbacktestingrisk managementMetaTrader
02 NinePointTrendScorer — live market-data pipelineLive market data The decade's method, made into running code: live ticks off two broker terminals, a 9-point scorer, regime detection, GA optimization and a 7-gate risk filter.

This is the MetaTrader work turned into a real-time system, and it is my strongest live market-data credential. A bridge Expert Advisor streams live tick and bar data off two real MetaTrader terminals — Admiral (1:30, EU-regulated) and RoboForex — across eight FX symbols, writing through a RAM-drive file channel at roughly 5 ms so the Python side reads a live feed without touching the SSD. On each bar close the 9-point scorer grades the market on three pillars — Structure, Momentum, Exhaustion, three checks each — while a regime detector classifies trending / ranging / volatile / exhausting and a nested genetic-algorithm daemon optimizes parameters on 4-hour and 24-hour cycles. Nothing reaches an order until it clears a 7-gate risk filter, and every strategy is measured on a walk-forward engine reporting Sharpe, profit factor and drawdown. Roughly 17,000 lines across 43 files hold it together.

MetaTrader ×2→ bridge EA→ RAM-drive ~5 ms→ harvester→ 9-point + regime→ 7-gate risk→ executor
Measured / built
  • Live tick feeds on 2 broker terminals × 8 FX pairs, ~5 ms file IPC
  • 9-point Structure / Momentum / Exhaustion scorer + 4-state regime detector
  • Nested GA optimizer daemon (4 h / 24 h) · walk-forward backtest (Sharpe / PF / DD)
  • 7-gate pre-trade risk filter · ~17k LOC / 43 files
real-time datamarket-data pipelinelow-latency IPCgenetic algorithmsregime detectionrisk gating
03 TradeArchitect — multi-model market decisioningResearch / live monitoring Model championships for markets: per-timeframe champions chosen by measured win rate, then a live consensus of three models before any call.

TradeArchitect adds a decision layer on top of the market-data pipeline. It reasons about a specific cluster of recent M15 candles and makes a binary call — long / short / skip — which a vectorized OHLCV replay oracle validates immediately against what price actually did; each episode is stored as few-shot memory so later calls learn from similar past setups, and an adaptive layer tunes the confidence threshold over time. Models earn their seat the hard way: per-timeframe champions are selected by measured evaluation win rate (the M15 champion measured at 75.8%, a reasoning model at 58.1%), and the top timeframe runs a live three-model consensus — local champion, an API reasoning model, and a frontier judge — that fires only on a 2-of-3 majority. Risk is explicit: fixed reward-to-risk, a break-even move, a mandatory higher-timeframe trend gate, friction budgeting, session filtering, a daily-loss kill and demo-first safety with a manual approval gate. To be precise: these are measured harness metrics, this is research instrumentation, not a returns claim, and the discipline of measuring honestly is the actual product.

> Honesty gate, built in: a 70% win-rate at n=20 was flagged as noise and reverted to 47% at n=43. The backtester — never a model — is the sole judge of strategy quality.

live market feed→ champion selection→ 3-model consensus (2/3)→ OHLCV oracle check→ risk controller
Measured results
  • M15 champion measured at 75.8% eval win rate; consensus architecture in validation
  • Immediate OHLCV replay oracle + few-shot episodic memory
  • Adaptive confidence threshold · explicit multi-gate risk model
quantitative researchensemble modelsconsensusbacktesting oraclerisk management
04 Bybit real-time monitor + factor-neutral riskReal-time · research A live positions-and-risk monitor on the Bybit v5 API, plus factor-neutral liquidation research with a hard kill-switch.

The crypto side starts with real-time monitoring. A monitor on the Bybit v5 API continuously mirrors open USDT-perpetual positions exactly as the exchange web panel shows them, with an account-level risk pulse and per-position distance-to-liquidation alerts. On top of it sits factor-neutral liquidation research: a book that neutralizes correlated systematic risk still carries idiosyncratic risk, so the model adds an explicit idiosyncratic buffer and a liquidation-surface control — k_total = (equity − maintenance-margin) / total-PnL-sigma — with a hard kill-switch when the safety distance collapses, and per-leg tail/CVaR guards on the roadmap. The engineering was peer-reviewed by a multi-model panel and passes tiered verification. The track record is kept deliberately honest and small: about +$180 realized on ~$1,000 staked over a year — real, measured, and explicitly not dressed up as anything larger. A separate, exploratory research thread on the same venue applies autoregressive linear-prediction (Burg) signal methods with a multi-source fusion layer to real-time multi-instrument futures; a 16.5-hour instrumented live run surfaced an overtrading failure mode that a stability-focused revision then addressed. This is early-stage signal research — a work in progress, not a validated strategy.

> Standing caveat kept loud: factor-neutrality removes correlated risk only; a single-pair tail blow-up and crash-correlation are modelled but not yet fully captured. High leverage stays dangerous; real capital waits behind the full risk gate.

Bybit v5 API→ live positions + risk pulse→ liquidation-distance guard→ kill-switch / alerts
Measured / built
  • Live USDT-perp monitor matching the exchange panel + account risk pulse
  • Factor-neutral idiosyncratic-risk buffer + liquidation-surface kill-switch
  • Multi-model peer-reviewed · tiered verification green · honest +$180 / $1,000 record
real-time dataexchange APIliquidation riskfactor modelshonest measurement
05 MEXC agent — multi-venue sibling + exchange-AI reconReal-time · research The same monitoring discipline on a second venue, with governance-ratified risk guardrails and a gated execution path.

MEXC is the multi-venue proof: the Bybit monitoring discipline, adapted to a second exchange rather than rebuilt. A real-time agent polls positions, unrealized PnL, margin headroom and funding, runs a dead-capital detector for no-stop lottery-ticket positions, and pushes alerts to my messaging channel. I also ran a structured recon of the exchange's own in-app AI, benchmarking it as a zero-weight sentiment feed (it turned out to be an engagement funnel, not an analyst) and verified live-vs-cached data freshness on the tape. Risk guardrails were ratified by my multi-agent deliberation body — account-level liquidation-distance thresholds (warn / escalate) and a dead-capital rule — and any write capability is gated behind a manual Tier-3 approval, reduce-only first, after a paper-replay gate. An API-parity check against Bybit keeps a single normalized model across both venues.

MEXC API→ monitor + dead-capital detector→ ratified guardrails→ Tier-3 approval gate
Built / governed
  • Second-venue real-time monitor (positions / uPnL / margin / funding) + dead-capital detector
  • Exchange-AI recon as a weight-zero sentiment benchmark; live-data freshness verified
  • Governance-ratified risk thresholds · execution gated behind manual approval
real-time datamulti-venueexchange APIrisk guardrailshuman-in-the-loop
06 SpeculativeOracle — conditional futures & calibrationResearch Conditional outcomes computed faster than wall-clock, with a calibration immune system that distrusts its own forecasts until they prove out.

SpeculativeOracle is the forecasting-and-calibration research behind the market work. Given a set of premises it computes conditional outcomes faster than wall-clock — a deterministic simulation lane plus an ensemble-spread lane — and streams them before the operator has to commit; on a chaotic reference system it ran ~805–837× ahead of real time. What makes it useful for markets is the honesty machinery: a calibration immune system scores every prediction by Brier skill against a persistence baseline and retires anything that stops beating it, a basin classifier labels each forecast robust / marginal / knife-edge with an empirical predictability horizon, and a bitemporal decision register keeps full provenance. It was reviewed through three layers — deliberation body, design critique, and peer review — and uses my trading systems strictly as read-only walk-forward calibration test beds. No retrocausality is claimed or implied; for a deterministic system, prediction is just fast retrieval.

premises→ deterministic + ensemble lanes→ Brier-skill calibration→ basin verdict→ provenance register
Measured / built
  • Conditional futures ~805–837× ahead of wall-clock on a chaotic reference system
  • Calibration immune system (Brier skill vs persistence) + robust/marginal/knife-edge basins
  • Triple-reviewed · markets used only as read-only calibration test beds
forecastingcalibrationpredictability horizonprovenancehonest evaluation

What every one of these stands on.

The market systems are not islands. They reuse the same foundations I built once and apply everywhere — a consensus engine, an adaptive optimizer, a verification ladder, a disagreement institution, and a shared memory.

CloudMind
The multi-model consensus engine underneath every place two or more models are asked to agree — including the trading consensus calls.
DTSE+GA
A proprietary adaptive-optimization layer, so runtime parameters, confidence thresholds and timeouts tune themselves from measured feedback instead of brittle hand-set constants.
TVA · L1–L3
A tiered verification ladder — compile, static analysis, then behavioural assertions against ground truth — that every change clears before it counts as done.
Council + Trinity
A multi-model deliberation body and a bidirectional peer-review panel that ratified the risk guardrails and reviewed the trading engines before they shipped.
ForgeDossier
A vector-backed institutional memory every system reads and writes, so each gotcha — like a noisy small-sample win-rate — is remembered, not relearned.
Keep-alive discipline
A standing rule that long-running model and data calls time out on idleness, never a wall-clock — reset while bytes flow — so nothing is killed mid-stream.

Run like production infrastructure — because that's where I come from.

The market systems run on a self-hosted, multi-node GPU platform I designed and administer end-to-end. Services run under systemd; public edges go through Cloudflare tunnels (this page among them); a Kubernetes (k3s) cluster carries the observability stack — Grafana, Prometheus and Alertmanager for metrics, Loki + promtail for logs — alongside GPU model pools and vector stores.

Resilience is built in rather than bolted on: node-liveness watchdogs, automated cross-node backups, retry/back-off and reconnect logic in the data clients, and tiered verification gates before anything is promoted. The point is that a real-time data platform is only as good as its fail-over, its observability, and the honesty of its measurements — and those are the parts I care about most.

> 25+ years in enterprise infrastructure and telecom. I run AI and market-data systems the way production is run, because that is where I come from.

6+
nodes in the fleet
k3s
Grafana · Prometheus · Loki
~5ms
market-data IPC latency
24/7
monitored operation

Who built this.

AI Systems Engineer — 25+ years across enterprise infrastructure and telecom, most recently as a Principal Technical Support Engineer, and roughly ten years of algorithmic trading in parallel — beginning in 2013 with formal, hands-on trading courses at a licensed forex brokerage in Bucharest, then years of MetaTrader/MQL Expert-Advisor development, and now real-time market-data systems. MSc Open Systems Architecture and BSc Electronics & Computer Science, Politehnica University of Bucharest. Oracle Cloud Infrastructure 2025 Generative AI Professional and AI Foundations Associate.

Everything on this page is real software I designed, built, and operate solo — a decade of demonstrated capability and depth in trading systems and real-time market-data flows, offered honestly as exactly that. Open to a Real-Time Market Data / Solutions Architect engagement — B2B contract or full-time.

>Bucharest, EU · remote-ready >~10 yrs algorithmic trading >25+ yrs infrastructure >real-time market data · low-latency · risk

Talk to me.

Email is the front door — or use the form on the main site. Prefer voice? Request a call by email and I'll confirm a slot.

./email me ./contact form ./linkedin ./full portfolio
Calls
By appointment — request via email
Base
Bucharest, EU · remote-ready