Rowan omi.projectz.xyz
Connected services

What two other platforms would add to Rowan

Rowan keeps its own records and does nothing outside the routine. That was a deliberate first decision, and it mostly still holds: the only things Rowan writes to MeCentral today are the patient's nearby settings and their journey (see Nearby), and there is no HandleMy.World connection at all. The Roadmap lists things Rowan could learn to do on its own. This page is the other list: what Rowan would gain from two platforms that already exist, what it would hand each of them, and what it would keep to itself.

Nothing here is built or decided. The same rules apply as everywhere else: only the button finishes a step, and a report never changes after the fact.

MeCentralHandleMy.WorldBoth
MeCentral

The record would belong to the person it is about

MeCentral is a vault platform. Every person owns one vault for life, and the organisations that produce documents about them file copies into it instead of keeping the only copy. The organisation can still vouch for what it filed, but the person holds it. Access is granted with a MeCode: a scoped, time-limited key, never a shared password. Nothing is deleted; a correction is a new document that replaces the old one. Today every run, step and report Rowan produces lives only in Rowan's own database. On MeCentral it would live with Eli.

Eli owns the report, not RowanMeCentral
What the family would see
Nothing changes during the morning. Afterwards, each completed run is filed in Eli's own vault: the steps, the times, how each one was finished. If the family stops using Rowan, changes schools, or Eli grows up and moves out, the record goes with him. Rowan would hold the only copy of nothing.
What Rowan would share
Rowan files the report and stays its custodian, the way a CPR instructor keeps custody of the card in a student's vault. Filing is queued, so a MeCentral outage never delays the caregiver's summary. The report is already frozen when the run ends; the vault copy is that same document with a checksum, filed under "Routines".
To build it
A client for filing on the patient's behalf (three sister projects already have one), a consent sentence at signup, and a vault for Eli that he can claim later. Nothing in the run engine changes.
A care-team seat becomes a grantMeCentral
What the family would see
Grandma still sees Eli's bedtime on her phone. What changes is where the permission lives. It becomes a grant on Eli's record that names her, says what she may see and when it ends, and the family can see it as such. When her coverage window ends, so does the grant.
What Rowan would share
Each seat carries a grant id. Removing the seat cancels the grant; the seat's end date is the grant's expiry. Rowan still checks its own care-team table on every request, so nothing gets slower or depends on MeCentral being up.
To build it
Issue a grant when a seat is created and end it when the seat ends. The roadmap's one-night babysitter seat becomes a one-night grant.
A clinician gets a MeCode, not a loginMeCentral
What the family would see
The IEP team, the occupational therapist, the paediatrician. The primary picks eight weeks and three routines and sends a MeCode. The clinician opens exactly those reports, with the family's notes and nothing else, until the code expires. No Rowan account, no PDF in an email.
What Rowan would share
The roadmap lists "A report for a clinician" as a print layout plus an expiring seat. On MeCentral the expiring seat already exists: a share of specific documents, to a specific person, for a limited time.
To build it
Sharing built on the filed reports. Rowan chooses the set; MeCentral issues the code and keeps the record of who opened what, which the family can read.
A record the family can checkMeCentral
What the family would see
A report says "cleared by caregiver push, Dad, 7:41", and the family can confirm it has said that since the morning it happened. An edit that changed a step's timing is a new version; the old one is still there. Nobody, Rowan included, can quietly rewrite a Tuesday.
What Rowan would share
Rowan already never rewrites a report. Filing it on MeCentral makes that checkable from outside Rowan: every document carries its checksum, and a replacement points at what it replaced.
To build it
Nothing new in the engine. It is a second copy of a promise Rowan already keeps, held by someone the family does not have to take Rowan's word about.
Routines follow whoever wrote themMeCentral
What the family would see
Ms. Rivera moves to a new classroom next year. The Circle-time routine she wrote, with its timings and reasoning, is in her vault as something she authored; the family's copy stays with Eli. A mother with two children keeps one library across both. Clinician-written templates carry a real byline.
What Rowan would share
Routines are filed to their author as well as to the patient. The roadmap's "Change history on a routine" becomes a chain of versions.
To build it
An export format that round-trips, and a filing on every save. Cheap once report filing exists.
Growing up is a claim, not a migrationMeCentral
What the family would see
The roadmap describes a teenager becoming their own primary and keeping their history. On MeCentral the history was theirs from the first morning. They claim their vault, their parent's access narrows to what they allow, and Rowan only changes who holds the primary seat.
What Rowan would share
No data moves. Self mode is a role change in Rowan plus a vault claim the patient completes on their own phone.
To build it
A claim flow on the patient's phone (MeCentral issues the claim code) and a role handover in Rowan. This is the strongest single reason to use the platform; the alternative is Rowan building custody transfer itself.
HandleMy.World

The chores a routine reveals would get handled

HandleMy.World notices what is coming up, suggests what to do about it (yes, tell me more, not now), and once you say yes a real person, or with your approval an AI, gets it done and reports back in one thread. It is organised into twelve areas of life (health, house, family, money and so on), each with cards that describe a task, its steps and when it is finished. Rowan already produces exactly the kind of signal HandleMy.World acts on: a step that keeps needing three repeats, a medication that is running low, a Thursday with nobody on duty. Today that signal stops at the report.

The medication step counts down to a refillHandleMy.World
What the family would see
The "Take medication" step has been done 24 times since the bottle held 30. HandleMy.World suggests the refill a week early, with the pharmacy already known, and the caregiver taps yes. The prescription is ready before the step ever fails. Eli notices nothing.
What Rowan would share
Rowan hands over a count and a routine name, not the transcript: "medication step done 24 times since this date". HandleMy.World matches that to its refill task. Rowan never learns what the medication is unless the caregiver wrote it into the step.
To build it
A per-step setting that says "this uses up a supply", a counter in Reports, and a call to HandleMy.World carrying the count. Consent is the caregiver's tap on the suggestion; nothing is booked from a report.
Three repeats on Brush teeth becomes an errandHandleMy.World
What the family would see
The report already suggests moving Brush teeth earlier. Some mornings the real answer is a dentist appointment, a toothbrush that plays music, or a step stool. HandleMy.World turns the suggestion into a task with the family's own dentist on it and someone to book it.
What Rowan would share
Report suggestions gain a "handle it" option next to "change the routine". Rowan stays the record of what happened; HandleMy.World is the record of what was done about it, and its thread links back to the report week that started it.
To build it
A suggestion type that maps to a task card (health, house or family) and a one-way handoff of the suggestion text. The task never writes back into the run.
A gap in coverage becomes a task, not just a notificationHandleMy.World
What the family would see
Thursday bedtime has nobody on duty, so it falls to the primary, who is at work. HandleMy.World spots the gap two days out and suggests the family's usual sitter. Yes books her, and her phone gets the roadmap's one-night seat for exactly that window.
What Rowan would share
Coverage windows are the trigger. Rowan already works out who is on duty and where the gaps are; that calendar, not the run data, is what HandleMy.World sees. Rowan issues the sitter's seat with the role and end time from the booking.
To build it
A coverage feed (the roadmap's calendar export) that HandleMy.World reads, and a callback that creates the seat when the task is accepted.
Let the platform that already notices do the noticingHandleMy.World
What the family would see
The roadmap's first section (weather, the school calendar, transit, snow days) is all about outside information. HandleMy.World already follows calendars, seasons and renewal dates for the household. Rowan would ask it "is there anything about tomorrow morning?" instead of building five feeds of its own.
What Rowan would share
The answer is a short list of facts saved with the run when it starts, as the roadmap requires for any outside information: "no school tomorrow", "dentist 8:15", "rain". Rowan still only ever says words the caregiver approved.
To build it
A read-only question at run start, and one each night for the scheduler. If HandleMy.World cannot be reached, the clock works as it does today.
One login for the caregiverHandleMy.World
What the family would see
Mom signs in to Rowan with the account she already uses for the house, the car and the kids' school forms. Dad and Grandma are already people in her household there, so inviting them to the care team means picking a name, not typing an email.
What Rowan would share
HandleMy.World's hub is a sign-in provider: one member, one credential, an account in each service. Rowan would be one more service. The care team stays Rowan's own list; only "who is this person" comes from the hub.
To build it
Single sign-on against the hub and an optional people picker when inviting. Patient and pendant tokens are untouched. The patient still never has a login anywhere.
The handoff note has somewhere to goHandleMy.World
What the family would see
When a run finishes, Rowan already sends a handoff note to the next caregiver on duty. If that caregiver is a HandleMy.World handler (the sitter, a respite carer), the note lands in the thread they are already reading, with the open step and a link to the run, and their reply comes back to the family the same way.
What Rowan would share
Rowan sends the same note it sends today, to one more place. Replies become notes on the run, which the roadmap already proposes.
To build it
A thread id on a coverage window that was booked through HandleMy.World, and a two-way message hook. Nothing in the engine.
What Rowan wrote, filed where the family keeps everythingBoth
What the family would see
The eight-week clinician report, the IEP letter a handler drafted from it, and the receipt for the step stool sit on the same shelf in Eli's vault, next to whatever else the household has filed there. HandleMy.World already files proof of finished tasks into the member's vault with their consent; Rowan's reports would arrive the same way.
What Rowan would share
One consent sentence, shown once and kept: "Rowan may file completed routine reports about Eli in Eli's vault." HandleMy.World's task proof carries its own sentence. Neither service sees the other's documents unless a grant says so.
To build it
Both of the above, plus agreeing the shelf name and tags. HandleMy.World already has the tag vocabulary.

What stays inside Rowan, whatever is connected

The engine
Every change to a run still goes through Rowan, whichever app caused it. Neither platform can finish a step, add time, or start a routine. MeCentral receives a run after it is over; HandleMy.World receives a summary or a count, never a live run.
The patient's voice
What Eli says while Rowan is listening, the phrases he taught it, and the replies Rowan did not count all stay in Rowan. None of it is filed or shared. A transcript is a hint for the caregiver, not a document about a child.
Who gets in
A seat on the care team remains the one and only check. A grant on MeCentral or a household on HandleMy.World can create a seat or end one; it never replaces one. The patient still has no password, on any platform.
The API
Every filing or handoff described above would also be a documented call under /api/v1, so a native app could drive it. Nothing in the browser talks to either platform.
If it were built, the order
Report filing first, because everything else on the MeCentral side builds on it and the connection already exists. Then the clinician MeCode, which replaces a roadmap item outright. On the HandleMy.World side, the coverage-gap task first, because it needs nothing but the calendar Rowan already has. Each is a decision still to be made.