What is rx, and what are the 4 doors?
rx stands for prescription. The system watches your life across four domains, notices when something is drifting away from your stated goal, and writes you a single concrete recommendation backed by evidence — and a counter-argument. One at a time. Sourced. Ranked.
The metaphor
Imagine your life as a house with four doors, each leading into a different room. Each room has its own books, its own instruments, and its own log. They share nothing structurally — what happens in one room does not bleed into another.
What does an rx look like?
Every recommendation is a markdown file. The frontmatter is machine-readable (id, drift score, signals, confidence, status). The body is human-readable. Always exactly one driving signal. Always at least one counter-thesis (the strongest case against taking the recommendation). Always 3–5 source citations from the knowledge vault.
Why split storage like this?
The split was made deliberately. It is the load-bearing decision of the whole architecture, locked into the decisions log as D-045 (storage routing) and D-047 (Lovable scope).
The locked rules
Hover a row to see its mapping highlight.
| Door | Where the rec lives | Who shows it to you |
|---|---|---|
| Zeus fitness | Supabase cloud, shared with phone | Lovable verocity app |
| Athena nutrition | Supabase cloud (zombie — no consumer) | none D-047 removed it |
| Lakshmi finance | TradingV postgres laptop-only, no cloud | TradingV FastAPI panel |
| Ganesh learning | markdown file system only | none editor reads the file |
Three things every rx contains
The drift score
A 0–1 number summarising how far reality has drifted from the goal. It is a weighted average of per-signal sub-scores. The math is copied verbatim from a SQL view or local helper — Claude does not do the arithmetic.
The driving signal
Exactly one of the contributing sub-scores has the highest weighted value. That signal is named, and the recommendation addresses it specifically — not the entire drift surface.
The counter-thesis
The strongest argument against acting on this rec, plus the conditions under which the counter-thesis wins. Mandatory by decision D-008. If a rec doesn't have one, it is malformed.
How the knowledge vault enters the picture
Drift signals tell you that something is off. They don't tell you what to do about it. For that, every rx command consults a personal knowledge vault — a folder of curated reading: books, newsletters, video transcripts, SEC filings, smart-money snapshots.
The vault is partitioned by domain (finance / fitness / nutrition / learning). Four small server processes (one per domain) hold an embedding index of the vault and answer ranked-evidence queries. The technical layer is fully explained on the Deep tech page.
Lifecycle in one sentence
/rx-<door>, a single
artifact is composed, dispositioned by you in the UI surface (or by
editing the markdown), and the next invocation reconciles your
disposition back into the file. If <30% of recs get acted on in a
rolling window, the system declares itself broken.