Field note
21 April 2026
What 'attended to' means when no one is watching.
A short reflection on the difference between a camera that sees and a system that notices – and why the second is the one elderly care should be building.
6 minutes
Read →Insights
Reading from the team.
Field notes, architecture decisions, working descriptions of the product as it takes shape. We write because the things we are working out — privacy by architecture, quality of care as a measurable quantity, voice that includes — are worth working out in public.
The collection is small, intentionally. Slow writing for a slow product.
Filter by
Architecture
07 April 2026
Why we don't write video to disk, ever.
An engineering note on the consequences of treating image data as ephemeral by construction. The constraint is the feature.
11 minutes
Read →Practice
12 March 2026
Confirming the 02:00 round.
Night rounds carry the highest variance and the lowest documentation quality. A working description of what changes when presence is the source of truth.
8 minutes
Read →Position
28 February 2026
Confidential care – two words, and why.
On the choice of tagline, the doctor-patient connotation, and what we are deliberately not saying about the product.
5 minutes
Read →Field note
14 February 2026
The Sunday afternoon problem.
What managers actually need from a quality-of-care dashboard – and why the answer is shorter than the existing tools assume.
7 minutes
Read →Architecture
30 January 2026
The line that activity events do not cross.
A diagram and a defence: why the architectural separation between camera unit and central server is the only commitment that matters.
9 minutes
Read →Practice
16 January 2026
Six languages, one cadence.
Designing the voice copilot for residents whose first language is not the language of the facility's administration.
12 minutes
Read →Field note
08 December 2025
What the night shift wants the morning shift to know.
A handover is a story, not a checklist. The system's job is to make the story easier to tell – not to replace it.
6 minutes
Read →Next step
A conversation, not a demo.
The right way to evaluate SeniorVision is to talk to us. Write with a question, a constraint, a deployment context. We will reply within two working days.