Diligence Notice
TL;DR: This is the confidential diligence room for Rōvn, Inc. (Delaware C corporation), pre-launch by design. Governing truth source: Rōvn master canon generation 8, promoted 2026-07-21 through a hash-pinned registry. What is real today: deployed demo and staging surfaces running synthetic data, a canon-governed claims discipline, and this room with its canon-grounded AI agent on Google Cloud. What is not yet real: verified paying customers, verified signed pilots, certifications, or real-data production operation. Every current-state claim in this room is held to the canon claim formula: what exists, where it exists, synthetic or real data, who has used it, which gates are complete, and the evidence date. AI compresses the work. Source systems prove the facts. Humans make every credentialing, privileging, hiring, and clinical decision.
1. Posture statement
Rōvn is a pre-seed company at a pre-launch posture by design.
- Zero verified paying customers and zero verified signed pilots. Reported founding-pilot letters of intent are recorded in the canon amendment queue and remain unverified pending the signed documents. They are not presented as traction anywhere in this room.
- Demo surfaces are synthetic. The Readiness, Operator, and Worker demos run governed synthetic data. Alder Crest Health Network, Maya Patel, and Maria Alvarez are synthetic personas, not customers or users. No real facility has completed a governed workflow on Rōvn.
- Compliance posture is designed, not certified. HIPAA-aligned, BAA available. Not SOC 2 certified yet. Not NCQA-certified yet. No CVO certification and no signed delegation agreement yet.
- Timelines are design targets. Any 14, 7, 21, or 30 day figure in company material is a design target, never a logged result.
This posture is intentional: architecture, governance, and honesty discipline come first; paid operation follows the applicable gates.
2. Truth layers
Every statement in Rōvn material belongs to one of four truth layers, defined in the canon:
| Layer | Meaning | External use |
|---|---|---|
| APPROVED | Present in the registry-resolved current canon generation | May be used subject to current fact verification and the rails |
| PROPOSED | Founder-requested or research-backed change awaiting its gate | Internal review only unless separately approved |
| DESIGNED | Deliberately specified but not necessarily built or activated | Described as designed, planned, or being built |
| PROVEN | Verified through current code, deployment, signed agreement, receipt, or observed workflow | Stated only with the supporting evidence and date |
3. The claim formula
Every current-state claim must identify:
- what exists;
- where it exists;
- whether it uses synthetic or real data;
- who has used it;
- which provider or source is live;
- which legal and operational gates are complete;
- the evidence date.
Pages in this room that predate the current canon generation carry a dated banner and are historical snapshots, not current proof. The current-state ledger lives at Current Investor Room Status.
4. What we explicitly do not claim
| Topic | Honest position |
|---|---|
| HIPAA | HIPAA-aligned, BAA available. No HIPAA certification language: no authority issues a HIPAA certification. |
| SOC 2 | Not SOC 2 certified yet. |
| NCQA and CVO | Not NCQA-certified yet. CVO certification and delegation are a strategic path, not a current status. |
| Joint Commission | No survey has been performed against Rōvn. Customers carry their own accreditation. |
| Customers and pilots | Zero verified. Reported letters of intent remain unverified pending signed documents. |
| Production operation | A deployed demo or staging surface is not real-data production readiness. |
| Network effect | A thesis. It is proven only by measured second Work Activation time and cost, and no such measurement exists yet. |
| AI authority | AI never approves, hires, rejects, credentials, privileges, or assigns anyone. Humans make every regulated decision. |
5. How to verify
- Open the demos linked in the footer. All run synthetic data and are labeled as such.
- Ask the canon-grounded agent. It is constrained to the hash-pinned generation 8 canon and fails closed if the deployed canon does not match the registry.
- Request engineering diligence access to repositories, receipts, and deploy proofs under signed NDA and IP-protective terms.
- Founder Q&A: Giles-Evan Mboumi is available for deep-dive sessions through the diligence window.
6. Confidentiality
This room is confidential. Access is granted under signed NDA or the implicit confidentiality of a serious investor engagement.
- Do not forward any document in this room without explicit founder consent.
- Do not share screenshots outside your firm or advisor network.
- Names of advisors and prospective partners disclosed in diligence are subject to mutual confidentiality.
7. Update cadence
Material changes publish as dated entries in the Investor Update series and in Current Investor Room Status. Dated pages keep their dates; a newer entry supersedes an older one, it does not overwrite it.
Last updated: 2026-07-22. To schedule a diligence session, contact founder Giles-Evan Mboumi.