RLS proof
Exercise multi-organization Supabase row-level security before any lab sees a tenant.
Current Status
This page exists so a clinic, lab, university, or diligence reader can evaluate Foveo without guessing. It is intentionally direct.
Readiness Table
| Component | Status | Plain state |
|---|---|---|
| Synthetic design demo | Built | Generates synthetic eye surfaces, review artifacts, STL files, warnings, hashes, and replayable records for software demonstration. |
| ESR v0.1 spec | Built | Public scanner-neutral Eye Surface Record spec, adapter interface, validation helpers, and conformance tests exist. |
| Public website | Live | Public pages describe workflow, scope, limitations, legal boundaries, partner integration, and the spec. |
| Guarded public intake | Built, gated | The request path is designed to fail closed unless production verification, rate limiting, and delivery settings are configured. |
| Private Supabase console | Built, unwired | Private console code and migrations exist, but there is no live production tenant connected to external users. |
| Real scanner ingest | Not built | No real scanner export adapter is claimed. Foveo needs one written-permission, non-PHI export before building a real adapter. |
| External users | Zero | No clinic, lab, university, OEM, or patient user is represented as active, paid, live, or referenced. |
| Clinical readiness | Not ready | Foveo is not for diagnosis, treatment, fitting, dispensing, manufacturing release, regulatory submission, or wearable lens fabrication. |
| Uptime guarantee | None | No service-level agreement, uptime promise, support guarantee, or production operating commitment exists. |
Next Proof
Exercise multi-organization Supabase row-level security before any lab sees a tenant.
Generate a one-page packet from a synthetic record that prints frame, provenance, warnings, sign-off, and record-only boundaries.
Obtain one written-permission, non-PHI export and find out what the ESR adapter gets wrong.