Diligence notice·Working state of Rōvn as of 2026-06-24 · Pre-launch by designSee 09 for receipts →
AI Diligence Console
43 healthcare roles × 51 jurisdictionsJurisdictional coverage50 US states + DC = 51 jurisdictions · 11.3 coverage grid · 07.7 Source Authority Rail = 2,193 coverage cellsCoverage cells43 roles × 51 jurisdictions = 2,193 coverage cells · 07.7 + 11.3. Every cell is supported. Each is either api (live source-authority API check with receipt) or manual_review (human primary-source verification path). Zero unsupported cells. No fake coverage.
Honest labels.
We do not paint a cell green by routing it to a vendor that doesn't return a primary-source receipt. If the live API isn't available for a role/jurisdiction yet, the cell is manual_review, a human PSV path with a receipt at the end. Status reflects production source-adapter wiring as of the snapshot date below. This maps source-adapter coverage capability on Rōvn's synthetic corpus; no real roster has yet run through it (pre-launchStage03.1 Company Overview · pre-launch by design, zero paying customers, zero signed pilots or design partners by design).
api
manual_review
43 rolesRole coverage43 healthcare roles in the Rōvn workforce catalog · 07.7 + 11.3 coverage grid by 51 jurisdictionsJurisdictional coverage50 US states + DC = 51 jurisdictions · 11.3 coverage grid · 07.7 Source Authority Rail coverage map">
Loading coverage matrix…
What this proves
Breadth: every role × jurisdiction the platform claims to support is mapped, not just a "50-state-ready" marketing line.
Honesty: every cell labels its method. A reader can audit what's API vs human-PSV at the role × state level.
Roadmap clarity: as Verifiable, FSMB PDC, and additional BON adapters go live, manual cells flip to api with a receipt trail, visible to investors and customers as deltas.
Ask the AI agent about this section, the raise, compliance posture, or any cross-document question. Grounded in Rōvn's deep context, with on-page source citations.
AI queries route through AWS BedrockAI provider chain07.3 AI Architecture · AWS Bedrock under BAA → Anthropic Claude Haiku 4.5 under BAA → Rōvn ECS under BAA · Anthropic Claude (Haiku 4.5)Model identity07.3 AI Architecture · Haiku 4.5 chosen for cost + latency + BAA chain under BAA · zero-data-retention posture · no PHI in prompts.