| owner | docs@geosync |
|---|---|
| review_cadence | quarterly |
| last_reviewed | 2026-01-01 |
Owner: Principal System Architect Last Updated: 2025-12-08
Architecture Decision Records document significant architectural decisions made during the development of GeoSync. Each ADR captures:
- The context and problem being addressed
- The decision made and its rationale
- Consequences (positive, negative, and neutral)
- Alternatives considered and rejected
- Implementation guidance
All new ADRs should follow the template: template.md
| ADR | Title | Date | Status | Requirement |
|---|---|---|---|---|
| 0001 | Fractal Indicator Composition Architecture | 2025-11-18 | ✅ Accepted | REQ-001 |
| 0002 | Versioned Market Data Storage | 2025-11-18 | ✅ Accepted | SEC-001 |
| 0003 | Automated Data Quality Framework | 2025-11-18 | ✅ Accepted | REQ-002 |
| 0004 | Contract-First Modular Architecture | 2025-12-08 | ✅ Accepted | N/A |
| 0005 | Multi-Exchange Adapter Framework | 2025-12-08 | ✅ Accepted | N/A |
| 0006 | TACL / Thermodynamic Control Layer | 2025-12-08 | ✅ Accepted | N/A |
These ADRs existed before the formalization effort:
| ADR | Title | Date | Status |
|---|---|---|---|
| 0001 | Security Compliance Automation | Earlier | Active |
| 0002 | Serotonin Controller Architecture | Earlier | Active |
| 0003 | Principal Architect Security Framework | Earlier | Active |
| ADR | Title | Requirement | Target Date |
|---|---|---|---|
| 0007 | Time Series Synchronization and Resampling | REQ-003 | Q4 2025 |
| 0008 | Incremental Backtest Execution | REQ-004 | Q4 2025 |
| 0009 | Fault-Tolerant Order Execution | REQ-005 | Q4 2025 |
| 0010 | Deterministic Backtesting Framework | SEC-002 | Q1 2026 |
| 0011 | Pre-Trade Risk Management | SEC-003 | Q1 2026 |
| 0012 | Secrets Management and Encryption | SEC-004 | Q1 2026 |
| 0013 | Compliance and Audit Logging | SEC-005 | Q1 2026 |
- Copy Template:
cp template.md 00XX-title-of-decision.md - Fill Content: Document context, decision, consequences, alternatives
- Review: Submit for Architecture Review Board approval
- Merge: Once approved, merge to main branch
- Update Index: Add to this README and Formalization Index
- Minor Changes: Direct edit with explanation in commit message
- Major Changes: Create new ADR that supersedes the old one
- Deprecation: Mark status as "Superseded by ADR-XXXX"
- Proposed: Under discussion, not yet implemented
- Accepted: Approved and being/to be implemented
- Deprecated: No longer applicable, replaced by new approach
- Superseded: Replaced by another ADR (link provided)
- Formalization Index: ../FORMALIZATION_INDEX.md
- Requirements: ../requirements/requirements-specification.md
- Contracts: ../contracts/interface-contracts.md
- Architecture: ../ARCHITECTURE.md
Questions about ADRs?
- Open an issue with label
architecture - Contact: Principal System Architect
ADRs are living documents. Keep them current as the architecture evolves.