Files
timmy-config/infra/matrix/docs/adr/ADR-001-conduit-selection.md
Ezra (Archivist) 3e25474e56 [ezra] ADRs + Execution KT for Matrix/Conduit (#183, #166)
- Add 5 standalone ADRs in infra/matrix/docs/adr/
- Add EXECUTION_ARCHITECTURE_KT.md: exact path from DNS decision to fleet ops
- Architecture proof and continuity preserved
2026-04-05 18:20:46 +00:00

40 lines
1.2 KiB
Markdown

# ADR-001: Homeserver Selection — Conduit
**Status**: Accepted
**Date**: 2026-04-05
**Deciders**: Ezra (architect), Timmy Foundation
**Scope**: Matrix homeserver for human-to-fleet encrypted communication (#166, #183)
---
## Context
We need a Matrix homeserver to serve as the sovereign operator surface. Options:
- **Synapse** (Python, mature, resource-heavy)
- **Dendrite** (Go, lighter, beta federation)
- **Conduit** (Rust, lightweight, SQLite support)
## Decision
Use **Conduit** as the Matrix homeserver.
## Consequences
| Positive | Negative |
|----------|----------|
| Low RAM/CPU footprint (~200 MB) | Smaller ecosystem than Synapse |
| SQLite option eliminates Postgres ops | Some edge-case federation bugs |
| Single binary, simple systemd service | Admin tooling less mature |
| Full federation support | |
## Alternatives Considered
- **Synapse**: Rejected due to Python overhead and mandatory Postgres complexity.
- **Dendrite**: Rejected due to beta federation status; we need reliable federation from day one.
## References
- Issue: [#166](http://143.198.27.163:3000/Timmy_Foundation/timmy-config/issues/166)
- Issue: [#183](http://143.198.27.163:3000/Timmy_Foundation/timmy-config/issues/183)
- Conduit docs: https://conduit.rs/