Public product story, Passport Studio, case study, pilot room, share controls, and demo-safe workflows.
Launch readiness
Professional enough to show. Conservative enough to trust.
Movement Identity is demo-ready and pilot-shaped. It should not accept real PHI or live patients until consent, notification copy, production Supabase/RLS, legal, security, and clinical review are complete.
5-10 opt-in participant workflows can be discussed and run with demo-safe or de-identified data.
Requires consent, legal, security, clinical review, production RLS verification, and notification copy approval.
Decision support only. Outputs must show confidence, source data, uncertainty, and disclaimer.
Trust controls
What makes this feel like infrastructure instead of a demo.
The product should make consent, source labels, access scope, audit history, and clinical boundaries visible before anyone interprets recovery or performance context.
Athlete or patient controls the Passport and approved data categories.
Surgeon, PT, team, trainer, agent, family, school, or employer views stay purpose-limited.
Every major recovery event should show source, date, confidence, and review state.
Access, grants, expirations, revocations, and review actions should be recorded where schema supports it.
MI organizes context for review and routes uncertainty back to clinicians.
Real PHI starts only after legal, security, consent, and RLS preflight are complete.
Human review before real users
Required before live PHI or real patient deployment.
Best next move
Capture pilot interest Run demo-safe pilots while the compliance track catches up.
Keep the first partner conversations around opt-in pilots, de-identified examples, aggregate source data, and workflow value. Move to real PHI only after the review packet is complete.