Architecture Decision Records (ADRs)¶
This directory contains Architecture Decision Records (ADRs) for the Signal Fish Server project.
What are ADRs?¶
Architecture Decision Records document important architectural decisions made during the development of the project. Each ADR captures:
- Context: The problem or situation requiring a decision
- Decision: The architectural choice that was made
- Consequences: The impacts (both positive and negative) of the decision
- Alternatives: Other options that were considered and why they were rejected
ADRs are immutable once accepted. If a decision needs to be changed, a new ADR should supersede the old one.
ADR Index¶
| ADR | Title | Status |
|---|---|---|
| ADR-001 | Reconnection Protocol | Accepted |
| ADR-0001 | Protocol v3: Two-Axis (Topology + Transport) Capability-Gated Signaling | Accepted |
| ADR-0002 | Matchbox-Compatible Signal Payloads | Accepted |
| ADR-0003 | Formal Verification and Fuzzing for the Protocol v3 Session Core | Accepted |
| ADR-0004 | Native Reference Client with a Real WebRTC Stack | Accepted |
| ADR-0005 | Browser Reference Client on Real Headless Chromium | Accepted |
| ADR-0006 | Protocol v3 Delivery Reliability and Lifecycle Boundaries | Accepted |
Numbering note: the legacy
ADR-001(3-digit) predates the currentADR-00014-digit scheme. New ADRs use the 4-digitADR-NNNNform; the legacy ID is preserved as-is to keep existing links stable.
Related Resources¶
- Architecture - Overall system architecture
- Protocol - WebSocket protocol documentation
- Development - Building and testing