The parent problem
A closed loop produces thousands of signals every week. The hard part is no longer collecting data; it is knowing which tiny slice deserves attention.
Speaker kit
A parent cannot digest 6,000+ diabetes data points every week.
LoopCoach turns the week into what changed, why it matters, what evidence supports it, and what a parent should watch next.
The LoopCoach answer
Turn CGM, AAPS, Nightscout, settings changes and family notes into a readable weekly review with explicit evidence and cautious next steps.
The product boundary
LoopCoach does not apply therapy changes. It helps parents ask better questions, challenge recommendations and keep an audit trail.
Review spine
Five screens, one coherent story.
Keep the story focused on trust: evidence first, recommendation second, parent choice always visible.
- 1Open the weekly review and show the week summary.
- 2Open a recommendation and inspect its evidence window.
- 3Ask why the coach chose that setting change.
- 4Show the Apply / Reject audit path and parent note.
- 5Open replay for a day with a note, meal or pod/site issue.
Architecture story
From fragile sync to a parent-grade data bridge.
Now
Nightscout plus AAPS exports, synced into LoopCoach and reviewed weekly.
Next
Android companion uploads AAPS exports directly, replacing fragile Syncthing folder choreography.
Then
One isolated LoopCoach instance per family, with a separate management plane only when hosted operations need it.
Use UK mmol/L language in every parent-facing example.
Show notes such as pod failures, porridge guesses and exercise as first-class evidence.
Say decision support clearly. Do not let the talk sound like auto-prescribing.