Trust
Trust is built into the operating model.
Most vendor trust pages are written to survive a skim, not a review. This one is written for people paid to distrust it: every claim below sits beside the exact evidence that would upgrade it, and every rail is stated as something Rōvn will never do, not a promise it might keep.
Certification language gets curved by lawyers, audit trails stay behind a demo login, and headline numbers arrive marked estimated with no source attached. A reviewer’s real job becomes untangling marketing from fact before the actual review can start.
Demonstrations, unsigned pipeline, technical readiness, and internal rehearsals are steps toward proof, not proof. Each stage is earned. The company does not market stage six while stage one is unproven.
Bring your own policy. Bring your questions.
01 The governing triad
Three separations hold the operating model up.
Every claim on this site reduces to one of three guarantees below. Break any one of them and the rest stop mattering.
Source truth
Evidence carries its own provenance and freshness: where it came from, and when it was last checked. A claim without a dated source behind it is not evidence, it is an assertion.
Explicit consent
Future disclosure begins closed and follows the record’s owner. Nothing is shared by default, sharing is a choice that can be revoked, and nothing is sold or used to train a model without that basis.
Named authority
Every regulated decision remains with an authorized person. AI never hires, rejects, credentials, privileges, or assigns; a named human handles every exception, visibly, with a receipt behind it.
02 The proof map
Every claim, beside the evidence that would upgrade it.
A deployed surface is not production. A green test suite is not an approval. A demo URL is not evidence. A tool run is not an independent review.
Each row below states what is claimed, what is true about it today, and the exact, dated evidence that would move it forward.
| Claim | Status today | Evidence that upgrades it |
|---|---|---|
| Company status | Pre-launch, until immutable evidence proves otherwise. No paid customer has operated on the network yet. | The first executed, paid contract, entered into this register with a start date. |
| Verification sources | Source adapters exist in differing readiness states: some query a live source today, others are still being built. | A dated, per-source adapter status list, published beside this page. |
| AI and agent workflows | Designed, and partly implemented. Not every workflow described on this site runs unattended today. | A workflow-by-workflow implementation status, dated. |
| Production | A deployed surface is not the same claim as real-data production. What is live today is exactly what these sections describe, nothing more. | The first real-data production deployment, named and dated. |
| CVO and delegation | A strategic path, not a current status. No delegated credentials-verification authority is in effect today. | A signed delegation agreement or CVO designation, referenced by contract ID. |
| Open product demonstrations | Public pages explain product structure without representing customer operations. | Real operation requires the applicable evidence, authority, and date. |
| Customer counts, logos, testimonials | None exist, so none appear anywhere on this site. | A named, consented customer reference, published with a date. |
03 The never register
What Rōvn will never do.
Rails, not promises. Each line is a boundary this site does not cross and the operating model does not permit, stated plainly instead of implied.
Not a staffing agency.
No fee contingent on a hire, from either side.
Not an employer of record.
Not payroll, benefits, tax, or a general HR system.
Not a passive job board.
Stale postings are suppressed; opportunity is one surface of the operating loop, not a listings business.
Not the decision maker.
No autonomous hiring, credentialing, privileging, or scheduling authority, ever. Not your committee.
Not a primary source.
Rōvn queries sources and carries their receipts; it never becomes the source.
No score, no clearance.
No persistent cross-context person score, no facility-facing worker reliability score, no universal clearance.
No selling, no steering, no penalty.
Worker data is never sold. No hidden steering. No per-reuse penalty.
No placement fee.
No commission, success, or finder fee, ever, from anyone, on any side.
No default cross-tenant training.
Raw tenant data never becomes cross-tenant training data by default.
How the never is enforced.
04 What the record can prove later
What the record can prove later.
Authorized people can reconstruct what Rōvn knew at a prior date, without rewriting history. The record is append-only, tamper-evident, tenant-verifiable, and exportable: a correction adds a new row, it never edits the row it corrects.
A hash chain is one control. It is not proof of compliance by itself, and this page does not claim otherwise.
A correction adds a new record. The original remains available.
Original source response and recorded value- Correction linked to the original, with source and authority recorded
Nothing above is deleted. A correction remains linked to the prior record.
05 Security posture and vocabulary
Security posture, and what the words mean.
Security and agreement scope are defined during contracting.
- Default-deny access
- Real, server-verified authentication
- Scope enforced below the UI
- Append-only audit
- Fail-closed source activation
Source confirmed means a primary source returned this fact, on a dated query. Organization verified means an authorized person at one organization accepted it. Neither is a universal clearance.
The evidence is the subject, never the person: “This license is Source Confirmed” is correct. “She is verified” is not, and it does not appear anywhere on this site.
- Check queuedPending looks pending, always.
- Source confirmedA source returned the evidence.
- Organization verifiedWritten out in full: one organization, never universal.
06 For review teams
Bring your policy and questions.
The receipt and audit trail are inspectable in a walkthrough, and the proof map above is the agenda. Come with your own checklist; we would rather answer it against evidence than argue with it against adjectives.
Corrections are owed, as a duty: a wrong fact gets corrected everywhere it went, and a delivered incorrect claim earns a written correction and blocks further claims of its class.
The accessibility floor is constitutional: WCAG AA, 320px reflow, 200 percent resize, 16px body minimum, full keyboard operation, visible focus, status never carried by color alone.