SwisperStudio - Architecture Decision Records¶
Last Updated: 2026-06-03
Total ADRs: 11
Quick Reference¶
| # | Decision | Impact | Phase |
|---|---|---|---|
| 001 | Use MUI Instead of Tailwind | 🟢 Frontend | Phase 1 |
| 002 | Database Separation Strategy | 🔴 Architecture | Overall |
| 003 | Two-Mode Configuration System | 🟡 Backend | Phase 4 |
| 004 | Data-Driven Admin UI via SAP | 🟡 Full Stack | Phase 4 |
| 005 | Graph-Level Auto-Instrumentation | 🟢 SDK | Phase 1 |
| 006 | Build from Scratch vs Fork | 🔴 Strategy | Overall |
| 007 | Pragmatic Async Testing Strategy | 🟢 Testing | Overall |
| 008 | Phase 2 Architecture | 🟡 Backend | Phase 2 |
| 009 | Prompt Architecture Simplification | 🔴 Architecture | Prompt Studio |
| 010 | MCP Trace Tools Reuse Route Handlers In-Process | 🟡 Backend | MCP Server |
| 011 | MCP OAuth RS — RFC 9728 Host-Root Bridge + Fail-Closed Dev Auth | 🔴 Security | MCP Server |
Legend: - 🔴 Critical (affects entire system) - 🟡 Significant (affects major feature) - 🟢 Tactical (affects specific component)
By Category¶
Infrastructure & Data¶
Frontend¶
Backend¶
SDK & Integration¶
- ADR-005: Graph-Level Auto-Instrumentation
- ADR-009: Prompt Architecture Simplification
- ADR-010: MCP Trace Tools Reuse Route Handlers In-Process
- ADR-011: MCP OAuth Resource Server (RFC 9728 bridge + fail-closed dev auth)
Strategy¶
Testing & Quality¶
Architecture & Design¶
Timeline¶
Nov 1, 2025
├── ADR-001: MUI vs Tailwind
├── ADR-002: Database Separation
├── ADR-003: Two-Mode Config
├── ADR-004: Data-Driven UI
├── ADR-005: Auto-Instrumentation
└── ADR-006: Build vs Fork
Nov 7, 2025
├── ADR-007: Async Testing Strategy
└── ADR-008: Phase 2 Architecture
Nov 12, 2025
└── ADR-009: Prompt Architecture Simplification ⭐
Jun 3, 2026
├── ADR-010: MCP Trace Tools Reuse Route Handlers In-Process ⭐
└── ADR-011: MCP OAuth Resource Server (security) ⭐
Future ADRs (Planned)¶
Decisions we'll make later: - Phase 2: State diff algorithm choice - Phase 2: LLM telemetry capture method - Phase 3: Graph layout algorithm - Phase 4: SAP versioning strategy - Phase 5: ClickHouse migration approach
How to Use ADRs¶
Before Starting a Phase¶
- Read relevant ADRs
- Understand context and rationale
- Follow implementation notes
- Validate decision is still correct
When Making New Decisions¶
- Check if ADR exists
- If yes, follow it
- If no, create new ADR
- Get approval before implementation
When Revisiting Decisions¶
- Review ADR
- Check validation metrics
- Update status if superseded
- Create new ADR if changing approach
Created By: Development Team
Maintained By: Lead Architect