Docs / Getting started
ReferenceRoadmap and status
The single place that says what is built.
Milestones
| Milestone | Scope | Status |
|---|---|---|
| M1 | Value types, clock, events, message bus, cache | Real |
| M2 | Orders, risk checks, portfolio, simulated venue, backtest engine | Simulation |
| M3 | Bars, stops, brackets, mark-to-market, tear sheets | Real |
| M4 | Parquet data catalog, SHA-256 manifest, fth-catalog | Real |
| M5 part 1 | Engine generic over a venue, incremental run API, startup reconciliation | Real |
| M5 part 2 | A demo-only adapter for an event-contract venue (request signing designed, not built) | Planned |
| M6 | XRPL testnet venue, fth-xrpl tool, two testnet transactions | Testnet |
| Task 7 | XRPL token tools for testnet; this docs site and the trader site | Testnet |
| Hardening | Live-session recorder, performance budgets, a cancel-rejected event | Planned |
| Brokers | Stocks, commodities and energy through a regulated broker or futures commission merchant | Planned |
| Python layer | Bindings for research and strategy code | Proposed |
| Mainnet | Any real-asset path on the XRP Ledger | Planned (not built; founder sign-off) |
Rule
A milestone is done only when its code runs, its tests pass including failure paths, and the result is recorded. A document or an unrun script is not done.
Merged
M1 to M4 and M5 part 1 with M6 have each been reviewed independently, fixed, and merged to the main branch. Nothing has been released.