Home / Today
A non-dashboard daily care canvas with appointments, family pulse and review attention.
Product evidence
The Care House, screen by screen.
This page separates implemented product surfaces from connected services and documented concepts. All product images below are real rendered golden-test screenshots extracted from the supplied archive and converted to WebP for delivery.
Real screenshot: project golden outputInteractive demo: faithful browser reconstructionMarketing diagrams: illustrative only
Home / Today
Daily focus, next appointment and work needing review.
Real project screenshot
Care
Entry points for updates, tasks, appointments and notes.
Real project screenshot
Family
Members, invitations, access and responsibility.
Real project screenshot
Records
Documents, source links and archive organisation.
Real project screenshot
Care Inbox
Extracted suggestions with missing-detail and review states.
Real project screenshot
Task creation
Assignment, timing, priority and controlled save flow.
Real project screenshot
Appointment creation
Visit details, timing and preparation context.
Real project screenshot
Documents and OCR
File intake, document classification and family notes.
Real project screenshot
Nura Desk
Bounded conversation with a suggested room handoff.
Real project screenshot
Source references
Source presence, interpretation limits and proposed care work.
Real project screenshot
Permission boundary
Protected action blocked until the appropriate family role reviews it.
Real project screenshot
Timeline and visit packet
Longitudinal events and family-prepared visit material.
Real project screenshot
Reports
Confirmed care events organised into a reviewable family summary.
Real project screenshot
Memory confirmation
Explicit confirmation before a preference becomes persistent.
Real project screenshot
Private memory
Visible scope, correction and forget controls.
Real project screenshot
Authentication
Sign-in and product-boundary copy at the front door.
Real project screenshotImplemented product areas
Routes, screens and repositories found in the archive.
The implementation contains functional UI and data layers for the central Care House. A route or screen in source does not guarantee that its connected cloud service is deployed; those distinctions are carried into the status table.
Tasks
Lists, creation/edit flows, assignment response and Firestore repository logic.
Appointments
List and form flows with scheduling context and device-calendar adapter.
Notes
Family care notes with Firestore-backed save and review surfaces.
Family
Member views, recipient setup, invitations, roles and administrator boundaries.
Records
Documents, upload, detail view, source cards, links and archive routes.
Documents and OCR
PDF/JPEG/PNG intake with Latin-script on-device text recognition and action extraction support.
Care Inbox
Message/update input, deterministic and Firebase extraction providers, review state and commit adapter.
Review queue
Structured drafts and human review items with source references and trusted commit metadata.
Nura Desk
Conversation/session UI, semantic provider pipeline, source cards, permissions and command handoff.
Reports and timeline
Weekly report, care rituals, longitudinal events and doctor-visit packet views.
Controlled memory
Owner-scoped memory ledger with confirmation, correction and forget flow.
Invitations and roles
Single-use invite functions, approval, revocation and member-management boundaries.
Notifications
Messaging runtime, token storage, preferences and notification triggers.
Voice and sharing
Speech-to-text capture, sharing intent, TTS and family handoff paths.
Product architecture
A layered implementation with explicit authority boundaries.
The stack below is listed only where verified in the archive. No unsupported infrastructure, compliance service or commercial platform is added.
Experience layerFlutter Material 3 screens, responsive shell, Care House navigation, Nura avatar and design tokens.
State and routingRiverpod providers and go_router with nested Home, Care, Family, Records, Settings and Nura routes.
Domain and controllersCare repositories, structured drafts, review items, trusted action handoffs, source references and guardian decisions.
Firebase servicesAuthentication, Firestore, Storage, Cloud Functions, App Check and Messaging references in application code.
Cloud functionsNode 22 functions for semantic processing, Care Inbox extraction, invitations, account deletion, notifications, schedules and external intake.
Device capabilitiesML Kit text recognition, file/image selection, speech-to-text, TTS, sharing intent and device calendar adapters.
VerificationFlutter widget/domain tests, golden screenshots, Node unit tests, Firebase rules tests and CI configuration.
Truth map
What the archive supports.
This table is intentionally conservative. “Implemented” means relevant code exists; it does not mean a production service was deployed or validated with live users.
| Area | Status | Evidence | Open work / caveat |
|---|---|---|---|
| Core navigation and product rooms | Implemented | Routes, screens, responsive shell and golden tests | Runtime still depends on authenticated Firebase bootstrap. |
| Tasks, appointments and notes | Implemented | Forms, repositories, routes and save-flow tests | Production data migration and permissions require validation. |
| Documents and OCR | Partially implemented | Upload/detail screens, Storage repository and ML Kit provider | Device permissions, PDF/image edge cases and production retention need validation. |
| Care Inbox and review queue | Implemented foundation | Extraction providers, UI, structured drafts and review repositories | Live AI provider and cloud deployment require configuration. |
| Nura Desk and guardians | Implemented foundation | Persona, semantic providers, safety/permission guardians and tests | External model endpoint, cost controls and production evaluation remain buyer work. |
| Reports, timeline and memory | Implemented foundation | Domain models, Firestore repositories, rules and golden screens | Schedules, deletion and live production behaviour require verification. |
| Voice, TTS and sharing | Partial / device-gated | Platform adapters and screens are present | Background, lock-screen, call interruption and route behaviour are documented as open. |
| Localisation | Not verified | No ARB files or Flutter localisation framework found | English-only foundation; localisation work remains. |
| Public launch and revenue | Not verified | No store listing, active contracts or revenue evidence found | Buyer must validate market, operations and launch plan. |
| Legal and compliance | Draft / review required | In-app privacy, terms and boundary copy plus security documentation | Final jurisdiction-specific legal and regulatory review is required. |
Try the flow
Use the interactive sample-data demonstration.
The browser demo reconstructs the implemented visual language and lets a buyer navigate rooms, add and complete a task, review a suggestion, inspect a source and open a doctor-visit packet.