
Service 08 · AI Audits & Compliance
Agents in regulated work, evidence on file
Your controls assume a person wrote the commit. An agent-written one breaks that.
- Agents stay in your regulated work
- Produce the evidence your standard already asks for
- Captured as the work runs, alongside delivery
- Named gaps, each with an owner
Example record
A control, and the record behind it
So your assessor reads evidence pulled from the work as it ran. A gap is named, with an owner.
The assessor reads the record as it was written.
- Evidence
Change approved by a named person
sign-off record, linked
- Evidence
Review by a session that did not write the code
review attached to the change
- Evidence
Secret paths refused
refusals logged with reasons
- Gap
Action log retention
owner: your platform team

What an assessor asks for
Your trail, built while the work ran
Rebuild it afterwards and you pay several times as much, for a trail with the gaps an assessor is trained to find.
The question that arrives late
Most teams bring agents into delivery first and meet the regulator second. The meeting goes badly for a reason you can avoid.

- A
Change control assumes an identified, authorised person
- B
PCI DSS 4.0.1 wants traceability over in-scope changes
- C
SOC 2 wants an approval trail. DORA wants control over ICT changes
- D
ISO 27001 A.8.32 wants controlled change. HIPAA wants an audit trail on health data
- E
Each asks who authorised the change
- F
An agent-written change with no named approver is the gap they find first
Where the EU AI Act comes in
So your record-keeping and oversight evidence is on file when counsel asks. 4 sign-offs with named owners support it, and on their own do not make a system compliant.
Articles 12 and 14 ask high-risk AI systems for logs and human oversight
A signed delivery trail counts as evidence toward that
A named person who can override, on the record
Your counsel decides which obligations apply to your system
Capabilities
How we close the gap
Model
What we fix, and what you decide
What we fix
- F1Each control mapped to evidence, or to a gap with an owner
- F2Evidence is pulled from the log and the pipeline
- F3Gaps close as committed checks
- F4Model, version, provider, region and data flow are inventoried
- F5Controls are verified on a schedule
What you decide
- C1Which frameworks are in scope, and which assessor
- C2Remediation by us, or findings handed to your team
- C3Retention policy on the action log
We do not issue certifications. We produce the evidence and close the gap, so your answers are ready before the assessor asks.
Next step
Assessments have dates.
Send us the date and the scope. What you get back is what closes before it, and a named owner for each gap left open.


