tv-anarchy/docs
Natalie a86e68c525 feat(apps): add fleet engine mesh core integration
Co-Authored-By: Lilith Autocommit <noreply@atlilith.com>
2026-06-09 21:23:36 -07:00
..
architecture.md feat(apps): add fleet engine mesh core integration 2026-06-09 21:23:36 -07:00
data-model.md feat(apps): add fleet engine mesh core integration 2026-06-09 21:23:36 -07:00
glossary.md docs(@applications/tv-anarchy): 📝 add technical glossary definitions 2026-06-08 22:14:11 -07:00
operations.md feat(apps): add fleet engine mesh core integration 2026-06-09 21:23:36 -07:00
README.md docs(@applications/tv-anarchy): 📝 update app description and architecture details 2026-06-09 20:57:51 -07:00
roadmap.md feat(apps/tv-anarchy): add restart command support 2026-06-09 21:17:10 -07:00

TV Anarchy — Documentation

TV Anarchy is a native macOS (SwiftUI) front end — plus an iOS companion app — for a home media stack centered on plum (the laptop) and black (the media server). It unifies what was previously CLI/MCP-only: pick a playback device, browse a cached library, search and manage torrents, enrich metadata, and manage the device registry — all from one app. A larger, forward-looking layer (the self-healing torrent fleet/mesh) is designed but not yet built.

This directory is the project's living documentation. Component-level READMEs stay next to their code; these documents are the cross-cutting reference.

Living docs

Doc What it covers
architecture.md System shape — the shipped app, its helper subprocesses, and the planned mesh layer
data-model.md Config + state schemas in use today, and the planned fleet/mesh data model
operations.md Build, install, run, configure, and deploy every component
roadmap.md Status (built vs. designed) and the de-risked path to the full vision
glossary.md Domain terms (fleet, custody floor, duty, F2F relay, …)

Component docs (next to the code)

Design source of truth