Praxis In One Page
Praxis is Vaquum's execution system. It turns trading decisions into venue actions, durable execution state, and auditable outcomes through an event-sourced runtime centered on the Event Spine.
The current repository is a partial implementation of RFC-4001. Where the RFC and the code diverge, the code is authoritative. Today the implemented center of gravity is the Trading sub-system: Binance Spot testnet execution, per-account isolation, event-backed state replay, and integration wiring with the rest of the Vaquum stack.
Start Here
If You Are New To Praxis
- Read the product home page
- Read the architecture and intended scope in RFC-4001
- Run Setup And Verification
- Read Trading and Trade Lifecycle
- Run Binsim Walkthrough for a local paper buy and restart, or use Binance Spot Testnet to verify testnet access
- Review the current known implementation gaps in TechnicalDebt.md
If You Want To Understand The Current Runtime
- Start with the product home page
- Read RFC-4001 for the target model
- Read Launcher, Trading, and Trade Lifecycle
- Continue to Execution Manager, Event Spine, Trading State, and Venue Adapter
- Continue to Recovery And Reconciliation, Trade Outcomes, and Slippage And Order Book
- Review TechnicalDebt.md for known constraints and shortcuts in the shipped implementation
If You Want To Contribute Or Maintain
- Start with Developer/README.md
- Read RFC-4001
- Read Documentation System
- Review TechnicalDebt.md
- Use the repository code as the final source of truth for behavior
How Praxis Flows
- A manager or integration layer submits trade decisions into Praxis.
- Praxis validates and routes those decisions through per-account runtimes.
- State-changing facts are persisted to the Event Spine before or alongside execution lifecycle changes.
- Venue adapters submit, cancel, query, and reconcile against Binance Spot testnet.
- Trading state is rebuilt through replay, and outcomes are routed back downstream to callers.
Docs Map
Overview: Product Home, this docs hubGuides: Setup And Verification, Launcher, Trading, Trade Lifecycle, Binsim, Binsim Walkthrough, Binance Spot TestnetReference: Command And Event Reference, Execution Manager, Event Spine, Trading State, Venue Adapter, Recovery And Reconciliation, Trade Outcomes, Metric Snapshots, Slippage And Order BookDeveloper: Developer Home, Documentation SystemOperations: Technical DebtArchitecture: RFC-4001
Product Boundary
Praxis Owns
- execution intake and routing
- venue communication
- order lifecycle tracking
- durable execution state through the Event Spine
- replay and recovery of trading state
- outcome routing back to manager integrations
Praxis Does Not Yet Fully Own
- the completed Account sub-system described in the RFC
- the full RFC execution-mode surface beyond current shipped behavior
- strategy generation or trade decisioning
- a fully generalized multi-venue execution layer
Read Next
- For a first real local path, continue to Setup And Verification
- For runtime flow, continue to Launcher, Trading, and Trade Lifecycle
- For core state and execution surfaces, continue to Execution Manager, Event Spine, Trading State, Venue Adapter, Recovery And Reconciliation, Trade Outcomes, and Slippage And Order Book
- For contributor-facing docs rules, continue to Developer/README.md