engagements

Deployment Audit

£500

Up to 5 working days

Credited in full against the next stage.

How it runs

A report of counts against a battery fixed, hashed and dated before it runs.

No call included. The credit applies to a Remediation Specification or Build commissioned within 60 days.

Environment: Yours.
What reaches me: The responses file and the handover record.

Remediation Specification

£2,500–4,000

1–2 weeks

The architecture that fixes what the audit found, written so your engineers can implement it. Each failure mode named with its cause and its mitigation.

The screen-share reads your architecture. Code is written in the Build.

Environment: Yours. Screen-share.
What reaches me: The audit report, your corpus schema, and a short session with one of your lawyers.

In development

A fact-sheet constructor. It reads your configuration on your side and replaces the screen-share.

Compliance Architecture Build

£15,000–25,000

2–5 weeks

Built into your infrastructure. I write the Infrastructure-as-Code and hand it over; your engineers or your CI/CD deploy it.

Documentation ships with the work: architecture, data flow, deployment procedure, runbook. Your engineers are taken through it.

Environment: Mine for development. Yours for the system.
What reaches me: The masked corpus and the schema.

Monitoring Retainer

£5,000–8,000/month

Rolling monthly

Continuous evaluation and drift monitoring against public statutory corpora, with the evidence your buyers' risk assessments ask for.

No document content or matter identifiers are logged. A proprietary masking engine runs over the fields emitted. Updates are built against public data and GPG-signed.

Environment: Yours.
What reaches me: Telemetry carrying no personal data.

Across every stage

No production credentials are held.
Production debugging runs through break-glass access under your named approval with session recording, or a screen-share with your engineer at the keyboard.
Development runs in an isolated environment against a structure-preserving masked corpus.
Where a specialist is engaged for a narrow task, they work only in that environment against synthetic or masked data, hold no production access, commit under a GPG-signed named identity, and are under NDA and written agreement before starting.
Your system is built into your cloud tenancy and runs there.

Jurisdiction, insurance, the sub-processor position and the transfer instrument are set out on Trust, with the artefact that verifies each one.

How the £500 audit runs

Where your system has a public demo or trial, I produce the responses myself and the authorisation is the only thing you supply.

Otherwise I write the corpus and the probes, you run them against your system with your own tooling or with mine, and I score the responses and write the report.

What the report contains

Which checks failed, on how many eligible probes, and whether each failure reproduced across passes.
Which checks did not run.
The complete answer key, hashing to the digest you held before the run.
The date, and the configuration it ran against.

Cause and remedy are the Remediation Specification.

What I need

Nothing is required. Each input below widens coverage. Where there is a public demo or trial, the authorisation is the only one you supply.

Input	Without it
An endpoint	You produce the responses your own way and send the file
Your response shape	You map the responses to the published schema yourself
Upload access	The public-law half of the battery runs standalone
Written authorisation	Injection, cross-tenant canary and index-freshness checks fall out of scope

No document, no codebase, no credential, no call, at any point.

Written authorisation is a signature, not engineering time.

You receive the corpus, the probes and a digest of the answer key before any response exists.

If the battery comes back clean there is nothing here to remediate, and the report says so. Your own buyer can re-run it.

How you commission it

The card step places an authorisation. Nothing is charged at that point. Within one business day I confirm scope in writing: what will be run, what it will and will not establish, the delivery date. On your yes, the payment is captured and the run is scheduled. If the scope is not right, or the work is not something I can take, the authorisation is released.

Commission the audit — £500 →

Personal data

Input	Personal data?
An endpoint, or your own output	No
Your response shape	No
Upload access	No. The planted documents are mine
Written authorisation	Not data
Statutory corpus	No. Public
Corpus schema, from Remediation onward	No. Schema only
Domain knowledge	Not data
Real production documents	Yes. Not needed

At every stage the inputs are my own material, your schema, or a corpus masked before it moves. The one route by which your content can reach me is a response from your live index during the audit.

Not in scope

Health or clinical AI.
Benchmarks of named commercial products.
US regulatory advice.
Regulatory interpretation. Technical measurements and architecture specifications are delivered for assessment by your counsel.
Formal accredited conformity certification.

Start with the audit.

Up to 5 working days, credited in full against the next stage. Four questions and a card step. The amount is authorised, and released if the scope is not right.