docs: add data-flow refactor dev plan & spec

Incremental, phased plan (P0-P6) to put every subsystem on a shared
SubscriptionManager + RelayHealth foundation with unidirectional data flow,
fixing the O(videos x relays) REQ storms and emit-loop feedback identified
from real-environment logs. No feature removed; each phase shippable.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
This commit is contained in:
thePR0M3TH3ANandClaude Opus 4.8 committed 2026-06-14 09:55:03 -04:00
1 parent 35c4e68cde
commit 57902e5cb5
2 files changed
+264

No files matched your search

+1
View File
@@ -5,6 +5,7 @@ Welcome to the bitvid documentation. This directory contains detailed architectu
## Core Systems
- **[Application Coordinators](./app-coordinators.md)**: Overview of the coordinator pattern used to manage app-wide state and services.
- **[Data-Flow Refactor — Dev Plan & Spec](./architecture-refactor.md)**: The incremental plan to put all subsystems on a shared, governed relay/data foundation (SubscriptionManager, stores, unidirectional flow).
- **[Authentication Architecture](./auth-architecture.md)**: How session management, login flows, and signer integration work.
- **[Feed Engine](./feed-engine.md)**: The pipeline for fetching, filtering, scoring, and sorting video feeds.
- **[Playback & Fallback](./playback-fallback.md)**: The URL-first playback strategy with WebTorrent fallback orchestration.