Mine Alpha
Find research opportunities across evidence sources and market behaviour.
Mine opportunities, turn evidence into testable strategies, run controlled experiments, challenge promising results, and preserve what the research learns.
Alpha OS is designed as a connected research process rather than a collection of disconnected AI features.
Find research opportunities across evidence sources and market behaviour.
Express the economic idea as an explicit, testable claim.
Translate the hypothesis into a transparent strategy specification.
Evaluate the strategy with controlled assumptions and realistic costs.
Stress the result for leakage, fragility, overfitting and bad assumptions.
Use holdouts, replication and robustness tests before trust.
Store evidence and failures as reusable institutional memory.
Alpha OS is intended to combine financial research, market and event data, price and volume behaviour, prior experiments, and portfolio needs into a structured opportunity pipeline. The objective is not to produce endless random strategies, but to identify hypotheses worth spending research budget on.
Research ideas are translated into auditable definitions covering universe, signals, entry and exit logic, position sizing, risk constraints, data requirements, execution assumptions, and the validation protocol. This creates a common language between researchers, agents, and the backtesting engine.
Alpha Command is the experimentation layer: repeatable backtests, parameter studies, cross-security analysis, regime breakdowns, realistic cost assumptions, and versioned results. Every meaningful run can be tied back to the research object and assumptions that produced it.
The research-integrity layer is designed to check data timing, parameter sensitivity, execution assumptions, holdout discipline, statistical fragility, and independent replication. Its job is to make autonomous research harder to fool—even when an initial backtest looks attractive.
Finding an attractive backtest is not the end of research. Alpha OS is designed to challenge promising results, test their assumptions, and reject strategies that do not survive scrutiny.
Alpha OS doesn't just search for reasons a strategy works. It actively searches for reasons it doesn't.
Illustrative example only. Values shown above are not historical Predvix investment performance.
These principles describe how we want autonomous quantitative research to behave. They are methodology goals for a product still in development, not claims that every capability is already production-ready.
Separate the economic idea from the code. Define what should happen, why it should happen, the required data, and what would count as evidence against it.
Record strategy definitions, data assumptions, parameters, costs, execution assumptions and the environment needed to understand a result later.
Promising backtests deserve more scrutiny. Test nearby parameters, timing shifts, cost shocks, regimes, leakage risks and alternative explanations.
Development, validation and holdout periods should be treated differently. Once a holdout influences strategy choices, the research record should say so.
Where practical, a separate implementation should receive the hypothesis—not the original code—and attempt to reproduce the result.
Rejected hypotheses, broken assumptions and failed replications are useful information. Research memory should compound from negative results as well as successes.
The same research loop, whether you run a desk or run your own book. Discipline shouldn't depend on headcount.
Give a team one auditable path from question to evidence, with every experiment versioned and every rejection retained.
The same challenge-first workflow a desk would run, so a strategy you build alone still has to survive the tests that matter.
Alpha Forge is the knowledge layer behind Alpha OS: sources, claims, hypotheses, experiments, outcomes and contradictions can remain connected rather than disappearing into old notebooks and chat threads. Each serious investigation is kept as a versioned research object: question, mechanism, universe, datasets, strategy definition, experiment protocol, results, robustness checks, contradictory evidence, replication outcome and status.
Connect findings back to research, datasets, assumptions and the experiment that produced them.
Retain strategy definitions, parameters, environment information, results and subsequent challenges.
Record why an idea failed so future research can avoid repeating the same mistakes.
Use accumulated evidence to improve future hypothesis prioritization and research design.
We are speaking with serious quantitative researchers and design partners while the product is in development.