Architecture Decision Records

ADR documents capture the rationale behind significant technical decisions.

Catalogue

001 – Configuration revisioning
002 – Setup token lifecycle
003 – Libtorrent session runner
004 – Phase one delivery
005 – FS operations pipeline
006 – API/CLI contract
007 – Security posture
008 – Remaining phase-one tasks
009 – FS ops permission hardening
010 – Agent compliance sweep
011 – Coverage hardening
012 – Agent compliance refresh
013 – Runtime persistence
014 – Data access layer
015 – Agent compliance hardening
016 – Libtorrent restoration
017 – Avoid sqlx-named-bind
018 – Retire testcontainers
019 – Advisory RUSTSEC-2024-0370 temporary ignore
020 – Torrent engine precursor hardening
021 – Torrent precursor enforcement
022 – Torrent settings parity and observability
023 – Tracker config wiring and persistence
024 – Seeding stop criteria and overrides
025 – Seed mode admission with optional hash sampling
026 – Queue auto-managed defaults and PEX threading
027 – Choking strategy and super-seeding configuration
028 – qBittorrent parity and tracker TLS wiring
029 – Torrent authoring, labels, and metadata updates
030 – Migration consolidation for initial setup
031 – UI Nexus asset sync tooling
032 – Torrent FFI audit closeout
033 – UI SSE + auth/setup wiring
034 – UI SSE normalization and ApiClient singleton
035 – Advisory RUSTSEC-2021-0065 temporary ignore
036 – Asset sync test stability under parallel runs

Suggested Workflow

Create a new ADR using the template in docs/adr/template.md.
Give it a sequential identifier (e.g., 001, 002) and a concise title.
Capture context, decision, consequences, and follow-up actions.
Reference ADRs from code comments or docs where the decision applies.