A note from Jason Pekovitch
Why Livonne has to exist.
Livonne is connected to my grandmother, LaVonne. She experienced dementia, and watching that stage of her life was heartbreaking.
I expect my family—and eventually me—to face some version of the same aging journey. I want that chapter to have better continuity, dignity, support, and family coordination than families are asked to carry today.
And I do not believe fixing it should require turning private family life into someone else’s data asset.
Why local hardware
The promise needs a boundary inside the home.
Dedicated hardware lets assistance exist where life is happening, supports durable memory and patient ambient interaction, and makes privacy concrete. Livonne is harder to build than another cloud chat window because the household deserves more than another account holding its most private context.
The long view
Earn trust in Care. Let continuity widen responsibly.
Care is where Livonne must first prove that local memory, visible assistance, safeguards, and family coordination genuinely help. That same governed continuity can later serve Maya’s household through Family, route real-world support through Network, and move with Ron into Community.
The expansion has to come from earned usefulness—not extraction from a vulnerable person.
More moonshots
Livonne is part of a broader body of work.
See Jason’s wider portfolio and the other systems he is exploring.
View Jason’s Moonshots portfolio (opens in a new tab)