Book / Trade execution

Praxis Docs

This page is the routing hub for the Praxis docs. Use it to choose the right path based on what you are trying to do.

Contents

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

  1. Read the product home page
  2. Read the architecture and intended scope in RFC-4001
  3. Run Setup And Verification
  4. Read Trading and Trade Lifecycle
  5. Run Binsim Walkthrough for a local paper buy and restart, or use Binance Spot Testnet to verify testnet access
  6. Review the current known implementation gaps in TechnicalDebt.md

If You Want To Understand The Current Runtime

  1. Start with the product home page
  2. Read RFC-4001 for the target model
  3. Read Launcher, Trading, and Trade Lifecycle
  4. Continue to Execution Manager, Event Spine, Trading State, and Venue Adapter
  5. Continue to Recovery And Reconciliation, Trade Outcomes, and Slippage And Order Book
  6. Review TechnicalDebt.md for known constraints and shortcuts in the shipped implementation

If You Want To Contribute Or Maintain

  1. Start with Developer/README.md
  2. Read RFC-4001
  3. Read Documentation System
  4. Review TechnicalDebt.md
  5. Use the repository code as the final source of truth for behavior

How Praxis Flows

  1. A manager or integration layer submits trade decisions into Praxis.
  2. Praxis validates and routes those decisions through per-account runtimes.
  3. State-changing facts are persisted to the Event Spine before or alongside execution lifecycle changes.
  4. Venue adapters submit, cancel, query, and reconcile against Binance Spot testnet.
  5. Trading state is rebuilt through replay, and outcomes are routed back downstream to callers.

Docs Map

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

Edit this sourceCheckout revision · 7381aa49
Reference / keep your place
Find a passage