▌VERTIMAX<GO>
FEED:LINK AUTH:OK MODE:READ-ONLY SESSION:ANON 2026-08-31 · 04:12:07 UTC

Module// QUANT ENGINE· ONE ENVIRONMENT FOR THE FULL RESEARCH LIFECYCLE· AUDITABILITY BUILT IN FROM INGESTION

Research scope: cryptocurrency markets.

RESEARCH LIFECYCLE · ONE ENVIRONMENT DATApoint-in-time SIGNALconstruction BACKTESTcost-aware RISKbudget same versioned data end-to-end · every run is a commit (replayable)
The full research lifecycle in one environment — same versioned data from ingestion to risk
vertimax@desk:~$ ./quant_engine --status // module: quant engine · read-only view

▚01 · Data Layer — Point-in-Time Ingestion● AUTHORIZED

Every dataset is stored as it was first observed, not as it was later corrected. The platform retains revision history so a signal can be evaluated against the information actually available on any given date.

Survivorship-bias-free universes are constructed from point-in-time membership. Delisted, renamed, and suspended securities remain in the panel; corporate actions, identifier mappings, and vendor normalisation are versioned and replayed on their effective dates. There is no lookahead, and no future information can leak into the as-of view.

▚02 · Backtesting Engine● PAPER

02.1 · Simulation

Cost-aware & event-driven

  • Event-driven matching against point-in-time order books and reference prices.
  • Transaction costs modeled explicitly — impact, spread, and slippage — rather than deducted after the fact.
  • Turnover is a measured output of the simulation, not an input assumption.
02.2 · Discipline

No lookahead, no hindsight

  • Signals are evaluated only against information available at the decision timestamp.
  • Corporate actions and restatements are applied on their effective as-of date.
  • Universe membership is re-evaluated each rebalance, not inherited from the current snapshot.
02.3 · Reproducibility

Every run is a commit

  • Data version, code revision, and parameters are captured with each result.
  • Any backtest can be replayed to the exact same state, for audit or for review.
  • Results are diffable, so a changed assumption is visible, not silent.
02.4 · Guardrails

Against overfitting

  • Walk-forward and holdout windows are first-class objects, not conventions.
  • Multiplicity in factor selection is tracked, so in-sample Sharpe cannot pose as a forecast.
  • Degradation between in-sample and out-of-sample is measured and surfaced, not hidden.
COST-AWARE · EVENT-DRIVEN order event-driven matchvs point-in-time book fill enters objective transaction costimpact · spread · slippage modeled explicitly · ⛔ deducted after the fact
Cost-aware, event-driven backtest — transaction costs enter the objective, not deducted afterward

▚03 · Risk Analytics● WITHIN BOUNDS

Risk is reported the way a systematic manager needs it: factor exposure, drawdown analytics, and regime conditioning — all recomputed from the same data as the backtest.

Drawdown is decomposed into contributions by factor, sector, and regime rather than reported as a single number. Exposures are computed from the same point-in-time holdings as the backtest, and regime shifts feed the risk budget directly rather than being noticed after a loss.

RISK BUDGET · DECOMPOSED drawdown by contribution — not one number: factor sector regime risk budgetregime-conditioned regime shift feeds the budget directly · ⛔ noticed after a loss
Risk-budget decomposition — drawdown split by factor, sector and regime; regime shifts feed the budget directly

▚04 · Execution Research● PAPER

Execution is where the simulation meets the book. The platform models schedule, impact, and the price of urgency so an implementation shortfall can be studied before it is paid.

Timing studies compare urgency against patience in the same book, and capacity estimates are derived from measured market impact rather than assumed from a turnover rule.

▚05 · Strategy MetricsVALUES WITHHELD

MetricDefinitionValue
Sharpe ratioExcess return per unit of volatility, annualized.—
Sortino ratioExcess return per unit of downside deviation.—
Max drawdownLargest peak-to-trough decline over the window.—
Calmar ratioAnnualized return divided by max drawdown.—
Win rateShare of periods with positive contribution.—
Annual turnoverGross notional traded as a share of capital.—
Capacity estimateCapital at which measured impact erodes the edge.—
Correlation to benchmarkReturn correlation to the stated reference.—
VertiMax does not publish strategy performance on this site. The schema is shown to illustrate the reporting standard; values are disclosed to authorized parties only, subject to the limitations in Compliance.

▚06 · SystemSCHEMATIC

Ingest
point-in-time data, versioned revisions, universe construction
→
Research
factor definition, cost-aware simulation, walk-forward
→
Risk
exposure, drawdown decomposition, regime conditioning
→
Execution
schedule, impact, capacity, implementation shortfall
vertimax@desk:~$ ./quant_engine --help▮