Every sheet, every column, every action — explained plainly. Keep this open the first week. After that, you won't need it.
This isn't a task archive. It's a decision-compression layer. Under pressure you need one answer instantly: does this move the number — or not?
The cockpit answers that without making you stop and think. Filter to today's lens, do the amber tasks first, and ignore the rest until it's their turn.The number is real history uploaded by people who'd be upset to lose it. Sign-ups aren't the test. Trust enough to populate is. Every sheet bends toward that one signal.
Operating principle: every quarter retires one major uncertainty. The gate isn't "did we ship?" — it's "do we now know?" And each quarter pre-commits the result that would kill the thesis.
If a row can't answer these, it isn't ready to be worked. The columns that answer them are named beside each.
Each does one job. The ⚡ line under each is the rule that keeps it honest.
The control room. Drive three fields: Current Quarter, Focus Mode, Current Bottleneck. Counts auto-update from the Master Plan.
The engine. 88 tasks across all 12 quarters, 17 columns each. Filter on Stage + Strategic State to shrink it to today.
The 12-quarter arc: Activate → Monetize → Scale → Ecosystem. One major achievement per quarter, each with its gate.
The binary checklist that must be green before you pour money into distribution.
The real KPI sheet. Activation, the 2nd-family-member north star, event-triggered return, conversion.
Every clinic, lab and channel scored independently on Reliability, Data-Readiness, and Trust.
Triggered users tracked one by one through the funnel — now also by Trigger Tier (hallway strength) and whether they carry their own records or someone else's.
Operational intelligence, pre-loaded with Recavora-specific risks. Add incidents as they happen.
The one uncertainty to retire, the ~10 triggered users to recruit by doorway, the experiment, and the kill-criterion.
The slow-erosion register. False-confidence AI extraction sits at the top — the error the user believes.
The master clock. Cash, burn, and one verdict: does cash reach the next piece of evidence?
Pre-written protocols for the moments trust is tested: export, dispute, offboard, correction, wind-down, breach.
Seventeen columns. The two amber rows are what make this Recavora's system and not a generic tracker.
| Column | What it means · how to use it |
|---|---|
| ID | Reference code (RC-001…). Use it in comms: "RC-024 is blocked on the provider." Never change an existing ID — it breaks dependencies. |
| Quarter | Which of the 12 quarters the task belongs to. This is how the 3-year plan lives inside the engine. |
| Stage | Activate · Monetize · Scale · Ecosystem. The mode of that quarter. Filter with Strategic State for your Focus Mode. |
| Strategic State | Whether you're pursuing it now. The attention-management column. Full guide below. |
| Workstream | Product · Trust · Company · Billing · Compliance · Distribution · Partnerships · Metrics. Colour-coded. |
| Task | The deliverable. Glows amber when Strategic State = Critical and Trust Impact = High. |
| Details | The definition of done. A task with no detail has no done. |
| Owner | One person — CEO, CTO, or Imu. Blank means it belongs to no one, which means it won't happen. |
| Priority | Critical = blocked without it · High · Medium · Low. Different from Trust Impact. |
| Effort | How heavy the task is. Avoid stacking three High-effort tasks on one day. |
| Trust Impact | Does it move the one number — real records uploaded? High = directly (trust page, export, smart-upload prompt). This is Recavora's signature column. |
| Status | Work progress: Not Started · In Progress · Done · Blocked. Different from Strategic State. Dashboard reads this. |
| Dependency | What must be done first. Don't start a task before its dependency clears. |
| Target | The quarter window. Month-level precision is enough at this stage. |
| Est. Cost | Budget flag. Reveals where money goes before it goes. |
| Reality Risk | How likely it goes sideways — vendor delays, regulators, single points of failure. Different from Priority. |
| Notes | Operational truth that fits nowhere else. Institutional memory. Write it down. |
The single most important column. It answers one question: are we pursuing this right now?
Trust, activation, money, or reputation blocked without it. Resolve before anything else.
Current working tasks. Normal operational flow.
Good idea, wrong timing. Strategically alive — scheduled, not forgotten.
Needs clarity before committing either way.
Consciously set aside. Seen, considered, shelved on purpose. Reinstatable.
Explicitly killed, so dead ideas stop resurrecting every few months.
Year-3 ecosystem only. Saved for when it becomes a real concern.
Deleting a task destroys memory. Use Ignored or Cancelled instead. You'll want to search it later.
When a task is both Critical and High Trust Impact, its Task and Details cells turn amber. These are the tasks most tied to whether someone trusts Recavora enough to hand over real history. When time is short, they come before every other Critical task.
Continuity is a founder word, not yet a customer word. People don't search for "continuity" — they search for pregnancy records, a visa medical, a pilot Class 1, a new diagnosis. Those are the doorways: the moment a trigger makes continuity suddenly urgent. Enter through them, reveal the building later.
But the doorway has a trap. A single-trigger user came for one thing — the pregnancy ends, the visa clears — and the urgency that brought them evaporates. If nothing converts them while the trigger is hot, they leave. So the doorway only works with a hallway: a nudge, fired mid-trigger, that pulls them from "tracking one thing" to "this is where my family's history lives." The pregnant user adding the baby's records is the doorway becoming the building — and it's the same move as your 2nd-family-member north star.
Tier the doorways by hallway strength. Pregnancy, a chronic condition, an elderly parent, a pilot's recurring medical — these carry a hallway built in. Visa and insurance triggers resolve, and need one engineered. And watch a quieter signal: the person populating may be a steward — a spouse, an adult child, a carer — not the patient. If so, the steward is the customer, and your family-profile and Guardian roles already fit them. Record it from user #1.
Each quarter names the one belief it retires, the evidence that settles it, and the result that would kill the thesis. The full kill-criteria live in the Roadmap sheet.
Five steps, every day. It takes two minutes and decides what the day is actually about.
Check counts. Note what's blocked. Confirm the current quarter.
The one thing blocking forward movement right now. Be specific.
Activation Sprint? First Revenue? Tells everyone which lens to use.
Stage + Strategic State to match the mode. Work only that view.
Inside the filtered view, the amber tasks come before everything.
It's intentionally detailed, and that's correct for the founder stage. When the operation runs on two people's memory, depth is protection — every "why" written here is a decision you don't have to re-argue at 11pm.
Later, when new people need onboarding in hours, build the one-page daily version alongside this. Not yet. Simplifying too early strips the philosophy before the culture has absorbed it. The culture comes first. Then the shorthand.