How rx flows across 4 doors
A single operator runs four life domains — fitness, nutrition, finance, learning — each backed by its own data pipeline, knowledge corpus, and storage backend. The rx (prescription) layer is the unified recommendation engine that reads each domain's live signals, consults a personal knowledge vault, and proposes one ranked, sourced, counter-thesised action at a time.
This explainer is visual first. Start with the overview, then follow the path that matches your role.
System architecture
Hover any node to see what it's connected to. Drag nodes to rearrange. Use the controls bottom-left to zoom, fit, or lock the view.
Pick a path
Overview
What rx is. What the 4 doors mean. Why the storage routing is split. Read this first.
Ingestion
Every data source that flows in — markets, screenshots, videos, workouts, filings. Cadence and destination for each.
rx pipeline
How a single recommendation is born. The 11-step canonical flow, counter-thesis rule, auto-dedup, snooze + auto-revive.
The 4 doors deep dive
Per-door storage, signals math, UI surface, status. Drift composite weights spelled out.
Feedback loop
What happens when you act, dismiss, or snooze. Phase W reconciler. Action-rate as system-death signal.
Deep tech
Embedding model choice, chunking, the three-layer hybrid retrieval, graph re-ranking math.
Maintenance
Rot vectors. The 6 touch points to add a new door. Hardcoded coupling to find before refactoring.
What this isn't
AGENTS.md for the re-verify workflow when source repos change.