Work with us
AI Evidence & Release Audit
Check what your AI release actually does. Follow its claims back to the tests and source records, keep the failures visible and decide what to release, fix or hold back.
Your starting point
Would this help?
This is a fit when
- A model or AI feature approaching an internal release decision
- A team that cannot currently connect a claim to exact data, model, config, and evaluation identities
- A failed or disputed release that needs technical reconstruction
- A repeated evidence process that may later justify Evidence Control co-development
When another approach is a better fit
- A request for legal, clinical, privacy, safety, or regulatory certification
- A request to hide failures, rewrite thresholds after results, or endorse an unsupported claim
- A release whose model, data, or software rights cannot be reviewed
- An organisation unwilling to name owners or preserve material evidence
The useful output
What you take away.
- 01An account of what the release used, changed and tested.
- 02Findings you can trace back to the source records.
- 03A recommendation on what to release, fix or hold back.
Full project checklist
- 01Technical decision record and bounded claim register
- 02Model, data, configuration, dependency, and artifact inventory
- 03Evaluation, failure, change, and release reconstruction
- 04Technical security/data-evidence review and finding register
- 05Release, remediate, or hold pack plus a reusable minimum evidence schema
Working together / 2–4 weeks
How we’ll work together.
Pick the release and the claims behind it. Follow the source records and test history, inspect the failures and decide what needs fixing before release.
The project steps in detail
- 01Freeze the release, audit boundary, claims, owners, and decision question.
- 02Inventory identities, artifacts, tests, changes, failures, and approvals.
- 03Test traceability, comparability, integrity, and missing-evidence behavior.
- 04Review findings with owners and record remediation or objection.
- 05Issue the technical release, remediate, or hold decision pack.
What we need before work starts
Before starting
- One named release, candidate, or release decision
- Access to relevant claims, configurations, evaluations, failures, and change records
- Named technical and release owners
- A protected review environment and agreed retention/destruction rules
- Acceptance that hold can be the correct technical recommendation
The release must be identifiable and the customer must lawfully provide enough artifacts, decision history, and reviewer access to reconstruct it.
Scope and handover
What we agree before starting.
We agree the work in a signed statement of work before starting. This page explains the offer; the signed agreement sets the commitment.
How you accept the handover
- The agreed release boundary, claims, identities, and evidence inventory are complete or explicitly missing.
- Every material finding has an owner, severity, evidence link, and disposition.
- The release, remediate, or hold recommendation is reconstructable from the audit record.
- The customer accepts the technical decision or records unresolved objections.
What this work covers
Bounded founder-led technical service; inquiry and qualification open.
Technical evidence and release reconstruction only. No legal opinion or privacy, clinical, safety, cyber, engineering, or regulatory certification.
An available founder-led audit is not an accreditation product or automated governance platform.
Offer source and review record
Questions
Before you enquire.
Does the audit certify compliance?
No. This is a technical evidence audit and release recommendation, not legal, privacy, safety, cyber, or regulatory assurance.
Must the customer use ERAIS?
No. The audit can reconstruct a release built with any sufficiently inspectable model and toolchain.
What if evidence is incomplete?
The result is hold, with the missing evidence and remediation path made explicit.
Talk to us
What’s getting in the way?
Tell us what keeps going wrong and what you need to do once it’s sorted. We’ll come back with what we think could help.