Architecture Decision Records¶
This section contains Architecture Decision Records (ADRs) documenting significant technical decisions.
ADR Index¶
| ADR | Title | Status |
|---|---|---|
| 001 | Connectivity Check Strategy | Accepted |
| 002 | Dry Run Safety Mode | Accepted |
| 003 | Documentation Site Architecture | Accepted |
| 004 | Core Engine in Rust | Accepted |
| 005 | Actor Model with Message Passing | Accepted |
| 006 | Lock-Free Orderbook Cache | Accepted |
| 007 | Execution State Machine (Saga Pattern) | Accepted |
| 008 | Control Interface Architecture | Accepted |
| 009 | Multi-Platform Credential Management | Accepted |
| 010 | Deployment Architecture | Accepted |
| 011 | Multi-Tenancy Model | Accepted |
| 012 | Performance Monitoring Architecture | Accepted |
| 013 | Low-Latency Optimizations | Accepted |
| 014 | Paper Trading and Backtesting | Accepted |
| 015 | Kalshi Demo Environment Support | Accepted |
ADR Format¶
Each ADR follows this structure:
- Status: Proposed, Accepted, Deprecated, Superseded
- Context: Why this decision was needed
- Decision: What was decided
- Consequences: Positive, negative, and neutral outcomes
Creating New ADRs¶
- Copy the template from an existing ADR
- Use the next sequential number (e.g.,
004-*.md) - Submit for council review using reasoning tier
- Update this index after acceptance