This directory contains Architecture Decision Records (ADRs) for the GTM MiroFish Demo project.
ADRs capture the key architectural decisions made during the project, along with their context and consequences. They follow the format proposed by Michael Nygard.
| ADR | Title | Status | Date |
|---|---|---|---|
| 001 | Multi-LLM Provider Abstraction via OpenAI SDK | Accepted | 2026-03-25 |
| 002 | Vue 3 Composition API with Pinia State Management | Accepted | 2026-03-25 |
| 003 | Intercom Design Token System via CSS Variables | Accepted | 2026-03-25 |
| 004 | Async Task-Based Simulation with Polling | Accepted | 2026-03-25 |
| 005 | Lightweight Demo Mode Docker Deployment | Accepted | 2026-03-25 |
| 006 | Optional OAuth with Domain Enforcement | Accepted | 2026-03-25 |
| 007 | Vue 3 + Vite for Frontend Framework | Accepted | 2026-03-25 |
| 008 | Flask for Backend Framework | Accepted | 2026-03-25 |
| 009 | D3.js v7 for Data Visualizations | Accepted | 2026-03-25 |
| 010 | Zep Cloud for Knowledge Graph Storage | Accepted | 2026-03-25 |
| 011 | Railway Per-Service Docker Deployment | Accepted | 2026-03-25 |
- Copy the template below into a new file named
NNN-short-title.md - Fill in each section
- Add an entry to the index table above
- Submit via pull request
# ADR-NNN: Title
## Status
Proposed | Accepted | Deprecated | Superseded by [ADR-NNN](NNN-title.md)
## Date
YYYY-MM-DD
## Context
What is the issue that we're seeing that is motivating this decision or change?
## Decision
What is the change that we're proposing and/or doing?
## Consequences
What becomes easier or more difficult to do because of this change?