Every Retirement Facility Should Be a Library
We spend a fortune maintaining buildings and almost nothing preserving the lives inside them.
Think about any retirement facility you’ve ever walked into. A hundred residents. A hundred careers, marriages, wars survived, businesses built, children raised, mistakes made and learned from. Centuries of lived knowledge under one roof — and when those residents pass, almost all of it goes with them. Not because nobody cared. Because nobody built the shelf.
I’ve been calling the answer the wisdom trust: a captured life, left behind like a 401k. Not money — proof. This was a life that was lived, and here’s what it taught.
Why now
The technology to capture a life story has existed for years. Voice cloning, chatbots, digital twins you can question forever — the demos are dazzling and mostly beside the point.
The real breakthrough is much dumber, and much more important: there’s finally an onboarding pattern simple enough for an 85-year-old.
The pattern that works looks like this: a family member (the “archivist”) sends a question by email. The elder (the “storyteller”) clicks one link and lands in a chat. No app to install. No account to create. They type or they talk — twenty-plus languages — and each story saves to the family’s encrypted vault. That’s it. That’s the whole unlock.
A company called Aeterna recently productized exactly this with their “Send a Question” feature, and whatever you think of their wilder claims (an interactive twin you can talk to forever — company claim only, no independent test yet), the onboarding fix is real and it’s the part that matters. The ceiling just became the floor: the hard part was never the AI, it was getting a grandmother to tap one link.
The facility is the venue
Here’s the part nobody’s saying: the natural home for this isn’t an app store. It’s the retirement facility.
Facilities already have the residents, the trust relationships, the activities programming, and the family touchpoints. What they don’t have is a story worth telling at move-in — something beyond square footage and dining menus. Imagine touring two facilities and one of them says: “Every resident here gets their life captured. Your mother’s stories, in her voice, preserved for your grandchildren. It’s part of living here.”
That’s not an amenity. That’s a reason to choose.
The cost per resident is low — a link, a few prompts, staff time folded into activities programming they already run — and the perceived value to families is enormous. It differentiates the facility, deepens family loyalty, and creates the kind of word-of-mouth no ad budget buys. (I’m not going to put a hard dollar figure on it; the honest version is that the expensive parts are the ones facilities already pay for.)
The machine-readable half
Here’s the part I’m most excited about, and it’s the reason this kit looks the way it does.
We make books and videos so other humans can understand and act. But a wisdom trust isn’t really a book for humans — it’s a book for bots. A machine needs to be able to pick up a resident’s captured life and do work with it: build the timeline, cut the quote cards, draft the family digest, notice what’s missing and ask the next question.
So the kit ships with a second half most open-source starter kits don’t have: a plug-in contract for AI. In the `automation/` folder you’ll find the whole thing — and it reads like a book’s anatomy:
- README = the cover letter. Tells any AI what this collection is, what state it’s in, and where to start.
- Pipeline = the table of contents. Eight stages, from raw audio to a curated collection: ingest, clean, segment, enrich, render, digest, gallery, and gap-scan.
- Schemas = the grammar. JSON schemas for every bucket — stories, timeline events, quote cards, people, places, artifacts — so the machine files things the same way every time.
- Prompts = the instructions. Copy-paste prompts for each stage, written so a different model next year can run the same pipeline.
- Worked example = “see, like this.” One resident’s collection, filled in, showing what “done” looks like.
Human-readable enough to trust. Machine-readable enough to run.
The provenance rule
One rule governs everything the machine makes, and it’s non-negotiable:
Every generated artifact — an illustration, a song, a video, a voice reading — must carry three things: what it is, what it is not, and why it was made. The why is the thinking that connected the source story to that form, and it’s part of the heirloom. A grandchild shouldn’t just see a painting of a drugstore; they should read that it was painted because their great-grandmother’s story mentioned the store but no photograph of it survived — and that it is not a photograph of the actual place.
The machine curates. The family decides. Weekly letters stay drafts until a human approves them — nothing auto-sends, ever.
The kit (open source)
I’m not building a company around this. I’m making the seed and putting it on the shelf.
I’ve published an open-source starter kit — wisdom-trust-in-a-box — with everything a facility or a builder needs to pilot it:
- A question library: forty prompts across a life (childhood, work, love, hard times, wisdom)
- The one-link onboarding flow, with a staff script and a family email template
- A plain-language consent template (the elder owns their stories, period)
- A one-page pilot brief a facility director can read in three minutes
- The economics: why a facility wants this, in one page
Fork it. Pilot it. Improve it. Tell me how it goes.
The ask
I’m good at making seeds. I’m not going to be the gardener on this one — that’s not false modesty, it’s knowing my lane.
So this is the handoff: the kit is on the shelf, the pattern is written down, and the onboarding problem that blocked all of this for a decade finally has a working pattern worth copying. Somebody’s going to be the first facility that does this the way they all have Wi-Fi now.
Might as well be yours.
