Current truth·Rōvn master canon generation 8 · effective 2026-07-21. Earlier dated diligence documents are historical snapshots, not current deployment proof.Ask the canon-grounded agent →
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 source-adapter wiring as of the snapshot date below, captured in the earlier AWS-era deployment and retained as a dated capability snapshot. This maps source-adapter coverage capability on Rōvn's synthetic corpus; no real roster has yet run through it (pre-launch by design).
api
manual_review
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 canon generation 8, with on-page source citations.
Investor questions run through Google Cloud Vertex AI and are constrained to the hash-pinned Rōvn generation 8 canon. No PHI belongs in this room or its prompts.