Product · Prototype
Lantern.
Care coordination for the family around an aging parent. One shared log, one list of what needs doing, and plain rules for who sees what.
From my own family.
With an aging parent, I found out how hard the coordination is, even for someone technical and good at troubleshooting.
Who it’s for
I built it for the adult children of an aging parent and the circle around that parent: the child doing most of the organizing, family who live farther away, a paid caregiver, and the parent, who reads what is shared with them, sees a count of what is not, and always sees who is in the circle.
No family has used it yet, and the interviews that would test it have not started.
What I built
AI writes most of the code; I decide what it builds and review what comes back.
On its first day, 11 August 2026, the web app already ran a family circle’s shared log, its task list and a Circle page on demo data, and 33 tests covered the permission rules. The real database, with tests that keep one family from seeing another’s, landed 2 days after the first commit. A readiness assessment 17 days in rated it ready for a guided demo on seeded data, and not ready for real families until real sign-in exists.
What it does now, on demo data:
- Four roles and three tiers of who sees what. Parent, organizer, family and caregiver, each with its permissions in one table I can audit. Each log entry and task is for everyone in the circle, family only, or family private, and a paid caregiver never sees the family tiers.
- Tasks start unclaimed. Anyone allowed can claim, release or complete one, and a task can be flagged as something family far away can do.
- Replies and edits keep their privacy. A reply is exactly as hidden as the entry it sits under. An edit is marked as one and cannot change who sees the entry.
- Invitations by link. An organizer can invite family or a paid caregiver. The link expires after 14 days and can be revoked, and accepting it makes a membership.
- Made for older readers and for phones: a 17px base type size, generous focus rings, dark mode, zoom support and a skip link.
- A labeled “Viewing as” switcher. A demo viewer can see the same screens as each role. It is fake sign-in, kept on purpose for demos, and it must never reach real people’s data.
Two calls on the stack went against my own precedent. For the mobile build, which is specified but not built, I chose Expo and React Native over the native SwiftUI I use for DeHoardMe: the permission rules live in one shared package a mobile app can use unchanged, and I expect this audience to use Android far more. And Lantern is one repository, not a frontend and a backend like 50RH, so there is one copy of the permission model.
Designed on paper and not built: a spec for the mobile build, locality and local providers, and voice. The voice research stopped at props for the interviews, with no code and no vendor account.
A walkthrough of a seeded demo family, made up for the demo, was recorded on 30 August 2026. This frame is its Circle page: each person’s role, and what they can see.

How fast
- 11 AugA shared log, a task list and a who-sees-what page ran on demo data, with 33 permission tests.
- 13 AugEntries saved in a real database, with tests that one family never sees another’s.
- 28 AugOrganizers invite family and a caregiver by link, and replies keep their entry’s privacy.
- 28 AugThe full tests and a production build run on every pull request.
- 28 AugInterview plan written. Until the interviews happen, build nothing new.
- 30 AugA second AI model reviews a change on request. It advises and never blocks a merge.
- 30 SepVoice researched and kept to props for the interviews. No code, no vendor account.
- 30 SepThe everyone-sees-it default is pinned by tests, not by the order of a list.
How it stays right
The family-private tier is the part that has to be defended. Five handling rules make it defensible: everyone in the circle is the default; the picker names the parent; each feed shows a count of the entries its reader cannot see; every member can read the who-sees-what table; and filtering happens in the data layer, so nothing a viewer may not see is sent to their browser. The count is there on purpose. It is the difference between a private tier and a secret one.
The checks behind it:
- Filtering was checked for each role against the raw HTML the server sends, not only against the page as drawn.
- Integration tests run against a real database that also holds a fully populated second family, so a query that forgets the family boundary fails instead of passing by luck.
- A private item that is hidden and one that does not exist return the same error, so a caregiver cannot learn that a private task exists. A test pins the two messages equal.
- In September, the everyone-sees-it default turned out to rest on the order of a list rather than on the documented setting. It now reads the setting, two tests pin it for every role, and the server output checked afterward was unchanged.
And the way the work is run:
- Type checks, lint, the full test suite on a scratch database and the production build run on every pull request and on main: 95 tests across three workspaces as of 5 October 2026, all passing on the last merged change.
- Some lines are written down so the product does not drift over them: no marketplace, lead generation or referral fees; no public ratings written by families; no automatic booking. Nothing in it is a medical record, and it should not become one.
- I have kept my own rule. Since the interview plan merged, the only work merged has been automated checks, documents and one fix to an existing rule. No new feature.
Some security decisions for real data are still open.
The call
The other options written down for the first slice: medications and appointments, a vault for documents and accounts, and wellbeing check-ins.
I decided: the shared log and tasks first. The log is the spine that family far away hangs off. The other three are products of their own, left unscheduled rather than built badly in parallel.