What it exposes
State, with provenance.
Evidence state with class labels, readiness projections, activation and consent state, receipts, and human decisions where authorized. Incomplete stays visibly incomplete, never a boolean.
Integrations
Read what you have. Operate alongside it. Earn the replacement.
No customer is required to accept a big-bang replacement. Rōvn reads the systems you run, coordinates the work between them, and writes back only with explicit authority and receipts.
The governed read surface
§ 01 / the governed read surface
consent resolves per call, per purpose, per recipient
What it refuses
The lines that never cross.
No PHI, no restricted identifiers, no raw documents. Source-confirmed truth can never be minted over this path, and revocation fails closed on the next call.
What it writes
Receipts first, write-back second.
Outbound status and receipt write-back to the systems you already trust, version-bound and receipted, after shadow mode proves the mapping.
The build order, pulled by customers
§ 02 / the build order, pulled by customers
workflow systems report state; primary sources prove facts
Roster and applicant capture first. Then the credentialing system your first facility already runs. Then outbound status write-back, workforce and provider-directory integration, schedule demand exchange, and the deeper enterprise connectors that contracted customers pull.
Keep your systems. Gain the loop.
A demonstration reads a roster export and returns readiness without touching production.