Coordinated Opportunity Detection & Yield | Unknown Author | ResearchPod

Transcript: Coordinated Opportunity Detection & Yield

Sam: A risk check inside your model's own process is a suggestion, not a control. That line sits at the heart of a design document for an automated trading system called CODY. Its argument is simple. Forecasting, sizing, sending orders, and the emergency stop run on different clocks, so they belong in separate programs that fail separately.

Alex: Before we get into the parts, place it for me. Whose document is this, and what kind?

Sam: It's an internal, confidential architecture specification from a quantitative trading team. It covers equities, futures, and crypto. It's version two, dated October 2026, and it replaces an earlier spec written for interns. No authors are named. So it's a design document with rules and reasons, not a study with results.

Alex: Most of our listeners don't trade. Why should someone building, say, machine learning pipelines or lab automation care?

Sam: Because the problem travels. Any system where a model's output becomes an action has to decide where the slow, experimental work ends and where the off switch lives. This spec draws those lines very concretely. We'll cover what broke in version one, the idea behind the redesign, one worked example, and how far to trust a document that has no performance numbers in it.

Alex: Start with version one. What was the original sin?

Sam: Version one was a single pipeline, from raw price tick to order. Research, portfolio construction, and execution all shared one clock, one message bus, and one failure domain. So one component stalling could stall everything. It also snapped every tick onto a fixed millisecond grid and converted all prices to US dollars on the way in.

Alex: Snapping data to a regular grid sounds like ordinary preprocessing. Why does the spec treat it as a mistake?

Sam: Because filling a grid means interpolating, and the spec says that invents trades the exchange never sent. The dollar conversion has a similar problem. A bitcoin trade priced in another currency, converted at the door, can't be replayed against an exchange that never saw that dollar price. So version two's ingest is described as an archivist. It keeps native currency, exchange time, local receive time, and sequence numbers. Each consumer translates for itself.

Alex: So what's the core idea of version two, in a sentence or two?

Sam: Four planes, where a plane is a separate failure domain with its own clock. Research runs on minutes to overnight and produces forecasts. Portfolio takes snapshots every second to every few minutes and turns forecasts into target holdings. Execution runs at the speed of a round trip to the exchange and only tries to reach those targets cheaply. Control is always on, in its own binary, and can flatten the book.

Coordinated Opportunity Detection & Yield

Unknown Author

Oct 11, 2026·8:41·user_upload

Opportunity DetectionYield OptimizationInstance ArbitrationQuantitative Trading ArchitectureAutomated Quantitative TradingSystem Decoupling

Listen

9 min

Summary

Overview of CODY v2 Architecture

CODY v2 is an automated quantitative trading system designed to manage the full lifecycle of alpha-generating trades across equities, futures, and crypto. Moving away from the v1 model of a single event-driven pipeline, v2 introduces a four-plane architecture where Research, Portfolio, Execution, and Control each possess independent clocks, state management, and failure domains. By decoupling these functions, the system prevents alpha-side bottlenecks from jeopardizing execution or risk management.

The Four-Plane Model

Research Plane: Handles data ingestion, feature storage, and signal generation. It operates on event time with watermarks, allowing research processes to be computationally intensive without impacting real-time execution.
Portfolio Plane: Converts signals into target holdings using a cost-aware optimizer that accounts for covariance and risk constraints. It operates on snapshot intervals (1s to 5m) rather than tick-by-tick, ensuring stable portfolio construction.
Execution Plane: Manages parent order slicing and routing to venues. It resides on dedicated hardware with PTP synchronization to minimize implementation shortfall, strictly forbidding high-level alpha opinion within its logic.
Control Plane: Acts as the final authority on risk, maintaining an independent binary that can execute a hard flatten or halt regardless of the state of the other planes. It utilizes dedicated venue sessions to ensure that risk-off commands are never queued behind stalled alpha or portfolio tasks.

Implementation Standards

Unlike its predecessor, v2 enforces strict contracts. Signals must be emitted as 'View' objects containing expected returns and uncertainty, rather than dimensionless scores. The architecture mandates as-of-correct point-in-time feature storage to prevent look-ahead bias and requires a rigorous, two-door promotion gate (Shadow and Live) that accounts for cost-aware PnL and trial counts (DSR). By mandating native tick ingestion and prohibiting global grids or interpolated pricing, the system maintains high fidelity for both backtesting and live operations.

Key Terms and Definitions

View — The core signal contract consisting of an expected return (mu), uncertainty (sigma), and horizon, replacing dimensionless z-score votes.
Promotion Gate — A mandatory testing framework including purged walk-forward validation and shadow-mode burn-in that a node must pass before it can influence live target weights.
Dead-man — A control-plane safety mechanism that triggers a hard flatten if heartbeat signals from other planes are missed, ensuring automatic risk mitigation during system failure.
Implementation Shortfall — The difference between the arrival price and the actual fill price, which the execution plane aims to minimize without injecting alpha opinions.
As-of Correctness — A data integrity standard ensuring that features are only built using information that was knowable at the specific historical timestamp, preventing data leakage.

Coordinated Opportunity Detection & Yield: Research Paper Podcast