Systematic · Diversifying alpha · U.S. equities

A multi-manager research floor, run by agent teams.

A multi-agent quantitative investment platform: independent research pods under principal-investigator orchestration, feeding one long-only U.S. equity book. 45 signals in production, 250+ hypotheses documented, and nothing reaches the book on any agent's word alone.

Thesis

Multi-strategy, horizontally scaled.

Every large multi-manager converged on the same design: independent research pods hunting alpha in parallel, with a shared data, risk, and execution platform underneath. The design's limit has always been people. There are only so many world-class pods you can field.

Polyvaria removes that limit. Its research pods are agent teams directed by centralized principal-investigator orchestration: priorities and risk budgets flow down, results and attribution flow up. A pod develops its hypotheses from idea through implementation against the shared backtester and submits the survivors for validation. The PI layer moves compute toward the families earning it and retires lines of research that stall. It also keeps the shared record of what has already failed, and a dead hypothesis doesn't get run twice. Adding a pod is a deployment rather than a hire. Research breadth grows with compute, and the gates still decide what earns weight in one book.

The platform underneath is staffed the same way. The data service, the backtester, risk, optimization, and execution are separate systems, each owned by its own agent team with its own quality rules. The separation is deliberate. A research pod cannot touch the referee that scores it or the data room it reads from, so there is no way to cheat, only to pass. Every result is recomputed from pinned inputs, and the verdict is cryptographically signed with keys no agent holds. That is what makes the breadth safe to scale. The gates don't care whether the work came from an agent or a human.

  • Research pods scale horizontally; orchestration stays centralized.
  • Multi-manager breadth, single-book risk discipline.
  • No result earns weight until the platform has recomputed it.

Research

The research loop.

It starts when the platform notices a weakness in the book: a decaying signal, a corner of the market with no coverage. An agentic principal investigator turns the gap into funded research, pods build candidate signals, and a statistical validation gate judges what they produce. Survivors are deployed and watched, the watching surfaces the next weakness, and humans govern the whole loop without sitting inside it.

The Polyvaria research loop A closed research loop that runs continuously. The platform senses decay, crowding, and coverage gaps in the live book and drafts its own research mandates. A human governor sits outside the loop, ratifying mandates, setting risk budgets, and holding the halt. The PI agent treats compute as capital and funds research themes by the evidence they produce. A hypothesis swarm generates diverse candidate ideas, checking dead ideas first. Research pods build signals with data on demand while a standing red team attacks every candidate before trial. The validation gate judges: combinatorial purged cross-validation, a deflated Sharpe bar, a ceiling on the probability of backtest overfitting, leakage tripwires, and marginal value to the book, with machine-signed verdicts. Survivors start small and earn weight, and day-one monitoring of every new signal feeds the sensing that starts the next turn. Rejects hibernate in institutional memory with revisit tripwires. A second-order loop runs alongside: playbooks and protocols are themselves experiments. runs continuously upgrades request serve verdicts · rejects consulted first HUMAN GOVERNANCE Ratifies mandates · sets risk budgets · holds the halt THE PLATFORM 01 Sense Decay, crowding, coverage gaps become draft mandates. PI AGENT 02 Allocate Compute is capital; themes earn it by evidence produced. HYPOTHESIS SWARM 03 Generate Diverse pods recombine ideas; dead ideas checked first. 251 hypotheses documented PODS + RED TEAM 04 Build & Duel Signals built data-on-demand, then attacked before trial. VALIDATION GATE 05 Verify CPCV · deflated Sharpe · PBO tripwires · marginal value. PRODUCTION 06 Deploy & Watch Starts small, earns weight; watching restarts the loop. 45 signals live · one book SECOND-ORDER LOOP The loop improves the loop: playbooks and protocols are themselves experiments. SELF-EXPANDING DATA LAYER Missing data? Agents probe the vendor, prove PIT correctness, backfilled to 2010, mid-run. INSTITUTIONAL MEMORY Every hypothesis ever tried, kept and queryable. Rejects hibernate with revisit tripwires and wake when the world changes.

Approach

The pipeline.

The same code runs the live daily rebalance and the multi-year historical backtest. The backtest pins the as-of date and simulates its fills; everything else is the same path. Each stage is owned by one of the platform's independent agent teams.

  1. 01

    Universe

    Point-in-time by construction.

    The investable universe is rebuilt for every historical date, delisted names included, so the backtest never sees a company the live book couldn't have traded. About 2,500 tradable names on a typical day, sixteen years deep.

    point-in-time universe

  2. 02

    Alpha Research

    45 signals in production.

    Research pods work price, fundamental, event, analyst, and news data into cross-sectional rankings of the universe. Fundamentals enter as first filed and news as it arrived, never as later revised. The newest layer is interaction alpha: momentum confirmed by an earnings surprise, surprise confirmed by cash profitability, reversal that skips announcement windows. In testing, these conditioned signals held up where naive combinations failed. Candidates clear durability gates across three market regimes before they earn a weight.

    cross-sectional alpha ranks

  3. 03

    Machine-Learning Overlay

    Two horizon models, one unified score.

    Gradient-boosted models blend the signal panel into a unified alpha score at two- and three-week horizons. Every model is trained under a pre-registered protocol: features, folds, and acceptance gates are frozen before training starts, and every trial lands in a permanent ledger. The overfitting math never gets to forget an experiment. Refits are walk-forward with purge and embargo against leakage. In live serving, the overlay abstains rather than guesses when its inputs drift.

    unified alpha score

  4. 04

    Factor Risk Model

    Barra-grade, estimated daily.

    A cross-sectional factor model in the USE4 tradition: market, seven styles (size, value, momentum, leverage, residual volatility, beta, quality), and industries, re-estimated every trading day. The covariance corrects for the ways risk models actually fail: serial correlation in factor returns, the optimizer's habit of betting hardest on the least-well-estimated directions, and volatility regimes that move faster than a trailing window. Signals are winsorized, z-scored within sector, and residualized against this structure. What survives is return the factor model can't explain, and that residual is what the book bets on.

    residual alpha · factor covariance

  5. 05

    Portfolio Optimizer

    Constrained conic QP.

    A conic solver maximizes expected return net of risk and transaction cost, subject to long-only, sector, market-cap, single-name, and turnover constraints. Cost and turnover are charged against current holdings, which keeps the trade list stable from one rebalance to the next, and a turnover circuit-breaker sits behind the solve as a second, independent line. Each plan carries a deterministic, content-addressed identifier. Any day's solve replays exactly.

    target weights · rebalance plan

  6. 06

    Execution

    Every order knows its urgency.

    Each trade in the plan carries an urgency score built from alpha decay, risk reduction, and drift, then damped by liquidity. The score maps to a schedule: patient limit orders where the edge is slow, immediate marketable orders where it is dying. Target price bands and participation caps come from a spread-and-impact cost model, and post-trade TCA feeds realized costs back into the optimizer, and the cost curve the book trades against ends up reflecting what it actually pays.

    fills · realized cost

Research Library

Thirteen signal families.

Each family is owned by a research pod that works it for new signals against the platform's backtester and sixteen years of point-in-time history. Published anomalies are assumed to be decaying from the day they were published, and get haircut accordingly. More candidates means more accidental discoveries, which is exactly why validation sits outside the pod. A candidate stays on the bench until the referee says it clears, and the referee is never its author.

The zero is deliberate. A family that keeps testing dead stays on the board, where nobody can quietly retry it.

Data

Grown, not bought.

When research asks for data that doesn't exist, the platform builds it mid-investigation, and every new dataset proves it can't see the future before it lands. Most asks are answered from the catalog in seconds. What follows is the morning when the answer is no:

One dataset onboarding, request to serving A swimlane diagram of one autonomous data onboarding, crossing four subsystems. The research pod asks in plain English at 9:04 and keeps working. The MCP front door, which holds only read-only credentials, searches the catalog at 9:05 and probes the vendor for a sample and schema at 9:07. The onboarding worker, a privileged and isolated subsystem, writes the onboarding code at 9:12 and runs the gate at 9:31: a point-in-time proof that the data is visible the day it became knowable and invisible the day before, plus an adversarial skeptic panel. The lake backfills history to 2010 at 11:46, and at 13:58 the dataset is served point-in-time from the catalog and the pod's backtest resumes. One morning, gate-governed, no human in the path. 09:04 09:05 09:07 09:12 09:31 11:46 13:58 RESEARCH POD asks; keeps working. MCP FRONT DOOR read-only credentials. ONBOARDING WORKER privileged · isolated. LAKE + HDS point-in-time serving. the backtest resumes. Ask in plain English. Search the catalog usually has it. Probe vendor sample + schema. Generate onboarding code written. Gate PIT proof · skeptic panel. Backfill history to 2010. Serve live in the catalog. one morning · gate-governed · no human in the path
The lake holds 74 datasets backfilled to 2010: vendor feeds, reference tables, risk factors, and the 45 derived signals the book trades on. Scout agents keep it growing against the book's coverage gaps, and datasets that stop earning are retired.

Verification

How results earn trust.

The platform assumes every result might be wrong until machinery says otherwise. A standing red team attacks each candidate before trial, and the verdict comes from checks its authors cannot touch.

Untrusted code, trusted verdicts.

Agent-written signal code runs in a fail-closed sandbox: no network, no filesystem, no credentials. Only numbers cross the boundary. The platform recomputes every statistic itself and signs the verdict with a key the agents don't hold, so no agent can mint its own acceptance.

Negative results are archival.

Each investigation ends in a findings memo whose verdict is set by the scorer, never the author, and a row in a research log where rejects are first-class. When deeper history exposed a shipped signal as a small-sample artifact, it was deleted from production the same week. The no's are written down so they stay dead.

Execution calibrates on its own fills.

The linear and square-root impact coefficients in the cost model are fitted to the platform's own broker fills and refitted as trade history accumulates. Slippage assumptions track what the book actually pays to trade, and the same fills drive the post-trade TCA that order scheduling is tuned against.

The operators write the platform.

Pipelines, monitors, data ingest, the backtesting harness, and the platform code itself are built and improved by the same agent pods that operate the system day to day; validation stays with gates the builders don't own. There is no separate engineering organization for research to wait on.

EXHIBIT A · FROM THE RESEARCH LOG
signal
insider_grade_consensus
family
Analyst & Sentiment
lifecycle
shipped June 2026 · retired July 2026
research read
IC t-stat 3.04, on a 77-name subset
full history
IC t-stat 0.12 · durable in 0 of 3 regimes
disposition
small-sample artifact · rejected
action
deleted from production · 1,647 partitions dropped
verdict
recomputed from pinned inputs · machine-signed

Controls

Where the autonomy stops.

The agents operate the platform; people set its boundaries. The mandate, the constraint stack, and the gate thresholds belong to the platform's human principals, and nothing reaches the live book without clearing them.

Mandate
One long-only, unlevered U.S. equity book. No shorts, no derivatives. The mandate is deliberately narrow: every layer of the platform gets to specialize.
Hard constraints
Single names are capped at 5% of the book; one-way turnover is capped at 30% per rebalance, a ceiling the cost penalty keeps the book well under. Sector and market-cap bounds sit beside them, and all of these are constraints inside the solve itself, so a book that violates them can never come out of it. The same limits bound the book's liquidity footprint to what the cost model says can trade without moving prices.
Validation gates
A signal gets live weight only after clearing combinatorial purged cross-validation (folds cut so nothing bleeds back from the future), a deflated Sharpe bar (which rises with every experiment run against the data), a ceiling on the probability of backtest overfitting, and tripwires that plant bait to catch look-ahead. The numbers are net of costs, with commission and impact charged before anything is judged. Results are recomputed from pinned inputs in a sandbox the author can't touch, and the gates are the same for agents and humans.
Fail-safe
Holdings are reconciled against the broker before every rebalance, and any day's decisions replay exactly from pinned inputs. A rebalance that can't reconcile, validate, or solve doesn't trade; the book holds its last valid positions. The human principals can halt the book at any time.

Stack

Boring on purpose.

The interesting risks belong in the research. The parts that touch money are chosen for determinism and auditability first, speed second, and the heavy intelligence stays upstream in the research layer.

Polyvaria subsystem architecture Four bands. On top, human governance: mandate, risk budgets, gate thresholds, and the halt. Below it, the research floor of agents: the PI agent funding mandates by evidence, research pods turning hypotheses into signals with data on demand, and subsystem teams owning risk, data, and execution end to end. Between the floor and production runs the validation gate: CPCV, deflated Sharpe, PBO, leakage tripwires, machine-signed verdicts — the only door from the floor to the book. Below it, the deterministic production line: the signal library feeds the ML alpha blend, then the portfolio optimizer, then execution, ending in one book. The optimizer also takes the factor covariance from the risk service and the cost curve from the trade cost model, and the signal library publishes into the data service. Human governance touches only the PI agent, which directs the research pods. At the base, the shared foundation both worlds run on: the point-in-time historical data service with its MCP front door, the backtesting service acting as referee with signed verdicts, the factor risk service publishing its risk model daily, the trade cost model fitted to the platform's own fills, and the orchestrator — agents decide, it schedules. HUMAN GOVERNANCE Mandate · risk budgets · gate thresholds · the halt RESEARCH FLOOR PI Agent Funds mandates by evidence; retires stalled lines. Research Pods Hypotheses become signals, data on demand. Subsystem Teams Risk, data, execution: agent-owned end to end. THE VALIDATION GATE CPCV · deflated Sharpe · PBO · leakage tripwires · machine-signed verdicts. The only door from the floor to the book. PRODUCTION LINE Signal Library 45 signals, published daily. ML Alpha Blend Two horizons, one score. Portfolio Optimizer Conic QP, hard constraints. Execution Urgency-tiered, cost-aware. one book publishes covariance cost curve SHARED FOUNDATION HDS Data Service As-of reads · MCP front door. Backtesting Service The referee. Signed verdicts. Factor Risk Service Risk model published daily. Trade Cost Model Spread & impact, from fills. Orchestrator Agents decide; it schedules.
Agent layer
Research pods and subsystem teams, sandboxed with scoped data and compute, under principal-investigator direction. Output reaches production only through the gates.
Optimization
CVXPY with the Clarabel interior-point solver. Conic QP, re-solved daily.
Data lake
Apache Parquet, DuckDB, Polars. Arrow-native end-to-end.
Orchestration
Dagster asset graph. Daily partitions, retry policy, idempotent stages.
Risk
Barra-grade multi-factor model in the USE4 tradition: market, seven styles, and industry factors, with Newey-West, eigenfactor, and volatility-regime adjustments. The differentiated work is what gets residualized against it.
Machine learning
XGBoost over an evidence-curated feature panel; two horizon models, walk-forward refit under purged combinatorial cross-validation.
Verification
Fail-closed kernel sandboxing for agent code; every verdict recomputed from pinned inputs and signed.
Execution
Urgency-tiered order scheduling against a spread-and-impact model; deterministic plan identifiers; broker reconciliation before every rebalance.
Methods appendix: the actual thresholds
cross-validation
combinatorial purged CV, C(6,2) = 15 splits · purge ≥ 21 bars · embargo 10 bars
acceptance
deflated Sharpe probability ≥ 0.95 · probability of backtest overfitting ≤ 0.5
scoring costs
1 bp commission · next-open fills, one-bar lag · impact charged before judgment
leakage tripwires
future-invariance · planted canary · measured lookback
durability screen
same-sign IC, |t| > 1 in each regime: 2012–16 · 2017–21 · 2022–26
sandbox
no network, read-only root, cleared environment, capabilities dropped · 4 GB / 1,200 CPU-second caps
verdicts
ECDSA P-256 signatures binding signal code, config, and data snapshot hashes
numeric oracle
agreement within rtol 1e-9 against an independent implementation
skeptic panel
three adversarial verifiers, five on dissent · uncertainty defaults to reject
onboarding dry run
512 MB memory ceiling proven before any backfill
ml overlay
pre-registered protocol · purge 11–16 days, embargo 10–15 by horizon · walk-forward refit
risk model
daily cross-sectional WLS · Newey-West · eigenfactor adjustment · volatility-regime scaling

Polyvaria is in active development and trades proprietary capital only. It is not open to outside investment or inquiries.