local-first residential records
Research / Prototype
A resident's records, kept by the resident.
Lazi explores how the people living in a Romanian apartment block can keep their invoices, water readings, payment notes, and evidence on their own phone, share selected records with a household or community on purpose, and still have a usable history when the administrator, the delivery provider, or the app changes.
I am defining the product, the local-first record model, the trust and recovery rules, and the Android and shared Kotlin foundation.
Project images
What we are building
Invoices and readings, kept locally
Invoice capture from email or PDF, manual water readings with a meter photo as an aid, payment status, reminders, and history live on the phone and keep working while every remote service is unreachable.
Three spaces, one set of records
A private vault, a household shared under explicit and revocable grants, and a community for notices, requests, and polls. Joining a community never publishes the vault.
Signed, portable records
A reading or a poll answer becomes a signed record the resident keeps. Delivery is shown as queued, delivered, or included in a result, and the app never claims more than it can verify.
Evidence and recovery
Encrypted local export exists today. The target adds linked-device recovery and optional archives encrypted with a key only the resident holds, so no operator can reset into them.
How it works
Authority is not ownership
An administrator confirms who lives where and runs particular workflows. They do not own a resident's history, and changing administrator does not cost the resident their records.
Useful with every model deleted
OCR and local AI remain optional experiments. An assistant may prepare or explain a record; the resident confirms anything financial or visible to others. Nothing decides on their behalf whether a financial fact is true.