ANTHERA01 / The system thesisDesign edition 0.1 · fe342eePDF
01

route

The system thesis

Nautilus owns the trading kernel; Anthera extends one canonical trace into durable history and multi-user delivery.

Question
What must remain true from ticker selection to chart paint?
Binding decision
The browser reaches data only through an authenticated application gateway; every queue is bounded and recoverable.
Owner input
Production SLOs, provider budgets, and data-rights limits remain owner decisions.
End-to-end market-data traceDBN passes through DataEngine, Nautilus, a bounded projection, QuestDB, the gateway, and the chart. The highlight marks the chapter focus.DBNData Eng.NautilusProjectQuestDBGatewayStreamChart
Fig. A — The stable reading trace. Runtime topology and narrative order are related, not identical.
Reading focusThe browser reaches data only through an authenticated application gateway; every queue is bounded and recoverable.

The trace is the product boundary

The target begins with Databento decoded directly into canonical Nautilus values. LiveNode routes those values through DataEngine, Cache, MessageBus, strategies, portfolio, risk, and execution. Anthera extends that proven kernel into QuestDB history, rebuildable Redis projections, and an authenticated browser gateway without inventing a second market model.

  • Live updates use append-or-replace semantics instead of rebuilding the visible window.
  • Historical reads use opaque cursors against a stable committed watermark.
  • Cold symbols attach live ownership while bounded history work begins in parallel.
  • A reconnect either replays a complete suffix or emits an explicit resync instruction.

EvidenceOfficial Nautilus architecture and Databento integration docs; frozen Rust source; accepted Nautilus-first ADR.

Authority is explicit

Nautilus owns in-process market and trading semantics. Its event store owns state-affecting run history. QuestDB owns bulk hot Quote, Trade, and Bar history. Redis accelerates service reads and coordination but remains rebuildable. The Cache database is an engine-state projection, not the browser's infinite-history authority.

  • Durable acknowledgement follows the declared QuestDB commit boundary.
  • Provisional delivery is labeled and always has a committed recovery path.
  • Provider, dataset, schema, Nautilus identity, generation, and provenance cross every service boundary.

EvidenceOfficial Cache and Event Sourcing docs plus the frozen persistence and infrastructure source audit.

Verify the design packagemise x -- task verify

Prompt structure, Rust harness, lint, tests, and state checks pass.