Verification & Sign-off
A model is only as trustworthy as its review. Here is how behaviours are verified, who signs them off, and how you can verify with your own engineers.
Why verification matters
Reading control code and proposing behaviours is the first step; confirming them against the evidence is what makes the model trustworthy. Every model is reviewed by a qualified engineer who checks each behaviour against its cited source, resolves ambiguities, and signs it off. The reviewer is identified and accountable — this is the difference between a reviewed, evidence-backed model and an unaccountable AI summary.
Coverage: verified, flagged, unverified
Every behaviour sits in one of three states for coverage purposes:
| Status | Meaning |
|---|---|
| Verified | A qualified reviewer signed it off (confirmed or corrected against the evidence). |
| Flagged | A reviewer raised a discrepancy or open question to resolve. |
| Unverified | Grounded in source, but not yet authoritatively signed off. |
Safety-relevant behaviours are tracked separately, so the safety-critical part of the system is never lost in the total. A model tells you honestly how much of it has been signed off — coverage is never inflated.
Sign-off tiers
Review is two-tier so volume and authority are separated. A junior reviewer’s confirm is a proposed review; it does not by itself mark a behaviour verified. An authoritative sign-off comes from a senior reviewer (or a Daritas reviewer). Only a signed-off behaviour counts as verified in coverage, the audit pack, and everything downstream.
Bring your own reviewers
For critical systems, you can verify the model with your own engineers instead of Daritas’s reviewers — so a sensitive system is reviewed with no external eyes. Your reviewers work on the same rails: every claim is checked against its cited source, safety-first, with the same sign-off discipline.
A reviewer is one of:
- Employee — your own staff.
- Trusted contractor — an external engineer you trust, who may review across several of your sites.
- Daritas reviewer — our qualified reviewer, when you use our workforce.
The reviewer roster
The org owner manages reviewers under Reviewer roster: invite an engineer by email, set them junior or senior, and mark them employee or contractor. They get review access on their next login. A reviewer who works across several of your organizations can switch between them. Reviewers who are already part of the Daritas network are recognised, so a trusted contractor keeps a single identity.
Attribution: who stands behind a claim
Every sign-off records not just that a behaviour was verified but who stands behind it — a Daritas reviewer, one of your employees, or a trusted contractor — and at what tier (junior/senior). The audit pack carries this attribution, so “who verified this” stays honest and auditable.
The audit pack
The audit pack is the evidence-first verification report for an assessment. It shows overall coverage, the safety-critical picture, and for each behaviour: its status, the source line it rests on, and — where signed off — who verified it and when. It downloads as a clean document and can be white-labelled as your own team’s work.