Architecture decision records
| ADR | Decision | Status | Owner |
|---|---|---|---|
| 001 | Centralized messaging timing | Accepted | Eng lead |
| 002 | v1 product → Lynkoria authentication | Accepted | Eng lead |
| 003 | Console admin authentication | Superseded in part | Eng lead |
| 004 | Room creation | Accepted | Eng lead |
| 005 | Message ordering | Accepted | Eng lead |
| 006 | Multi-device call behavior per product | Open | Product owners |
| 007 | One database across products | Proposed | Security reviewer |
| 008 | Fidescript SFU | Proposed | Security reviewer |
| 009 | Recording | Proposed | Product + legal |
| 010 | E2EE for calls and chat | Open | Product + security |
| 011 | Livestream publish rights | Proposed | VibeLynk owner |
| 012 | Message retention | Open | Product + legal |
| 013 | npm registry | Open | Eng lead |
| 014 | WebSocket fallback | Proposed | Eng lead |
| 015 | Redundancy and SLA | Proposed | Ops owner |
| 016 | Multi-region | Accepted | Eng lead |
| 017 | AR SDK | Proposed | VibeLynk owner |
| 018 | Tailwind CSS as the styling layer | Accepted | Eng lead |
| 019 | Documentation structure | Accepted | Eng lead |
| 020 | Attachment quarantine keys | Accepted | Eng lead |
| 021 | Multi-instance API (Redis Streams) | Accepted | Eng lead |
| 022 | JavaScript SDK package architecture | Accepted | Eng lead |
| 023 | TLS between the API and the scanner (private CA) | Accepted | Eng lead |
| 024 | Console charts stay on in-house SVG components | Accepted | Eng lead |
| 025 | Where console analytics come from | Accepted | Eng lead |
| 026 | Console audience, authorization and audit log | Accepted | Eng lead, security owner |