02 / Research system
Tau's process connects research and live-market constraints from the start: testable signal logic, portfolio construction, venue-aware execution, and controls that determine whether a strategy advances.
03 / Research loop
A candidate strategy is evaluated as a complete path, not just a backtest. Each stage supplies evidence for the next and exposes assumptions that need to be challenged.
Market data across venues is aligned, checked, and prepared for research.
Systematic candidates are tested against market-neutral strategy objectives.
Position sizing is considered alongside exposure, liquidity, and capacity.
Routing is designed to manage fill quality, slippage, and MEV-aware protections.
Pre-trade checks and automated protections gate progression and deployment.
04 / Connected systems
Signal generation, smart order routing, risk controls, and launch operations are being built as one connected system. Each has to hold up before Tau scales.
Alpha research
The research process examines predictable patterns in liquid digital asset markets. Each candidate signal is tested for persistence, market neutrality, capacity, and sensitivity to implementation costs.
Execution layer
The execution layer is designed to route across venues, manage slippage and latency, and test whether fill quality remains consistent with research assumptions.
Risk architecture
The risk framework is being built into the trading system itself. Pre-trade checks are intended to enforce exposure limits, liquidity thresholds, and concentration bounds before an order executes.
Launch readiness
The roadmap tracks progress from research toward deployment across infrastructure, legal and compliance readiness, operational procedures, disclosures, and launch communications.
05 / Review gates
Evidence at one stage does not guarantee progression. A strategy must remain understandable after costs, constraints, and failure conditions are introduced.
Persistence and regime behavior are examined before implementation.
Capacity, latency, fees, slippage, and venue constraints are accounted for.
Limits and automated responses are defined before deployment is considered.