Model or supplier
A new model, provider, fine-tune, retrieval layer or system prompt may invalidate earlier testing and supplier assurance.
Pilot edition · Method 0.1
DELTA · AI change control
Before you ship the change, know what else it changes.
DELTA compares the AI or automated system you approved with the version you now plan to release. It shows what changed, what still stands and what you need to reopen before deployment.
DELTADeployment Evolution and Legal Trigger Assessment
One baseline. One proposed release. One reasoned route.
Release notes say what changed.
DELTA says what follows.
Keep what still stands.
Reopen what no longer does.
The problem
New version. Old approval. Unknown consequence.
A release ticket records the engineering change. It rarely tells legal, compliance, risk or audit teams whether the organisation can still rely on the original approval.
A model update may alter capability. A new data source may alter inference. A new tool connection may give the system power to act. A change in purpose may move the system into a different legal or governance category.
The question is not only “What changed?” It is “What does the change disturb?”
Data or inference
New inputs, derived attributes or monitoring data may alter privacy, fairness, security and transparency analysis.
Purpose or people
A system approved for support may now rank, select, reject, price or act for a new population or market.
Autonomy or tools
New permissions, APIs, credentials or action channels may turn a recommender into an operational decision-maker.
What it is · what it is not
One focused product. One bounded decision.
DELTA is
An AI change-impact and release-control assessment.
- A structured comparison between an approved baseline and a proposed release.
- A map of the legal, technical, governance and evidence work that the change affects.
- A reasoned route to record, update, reassess or hold the release.
- A versioned decision record that product, engineering, legal, risk and audit teams can all use.
DELTA is not
A scanner, certificate or all-purpose compliance platform.
- It does not inventory every AI system in the organisation.
- It does not test model performance or monitor a live deployment.
- It does not compress compliance into an unexplained score.
- It does not replace a DPIA, FRIA, conformity assessment, validation exercise or legal opinion.
DELTA does not redo everything. It tells you what to reopen.
How it works
Five stages. One release decision.
DELTA follows the change from a factual comparison to an authorised route. Each stage uses the same colour language as the TRACE product family.
Define
Fix the approved baseline, proposed release, decision owner, scope and date.
Examine
Describe the factual changes to purpose, people, data, model, architecture, autonomy, actors and controls.
Locate
Identify the assumptions, approvals, assessments, tests and notices that the change touches.
Test
Check evidence, validation, oversight, supplier assurance, transparency, rollback and unresolved gaps.
Authorise
Record the route, reasons, conditions, owners and events that will require another review.
The result
Five possible routes. No meaningless score.
DELTA gives the organisation a provisional route and explains why.
Record only
Keep the change history. The recorded facts do not trigger further work.
Documentation update
Correct records, notices or technical descriptions before release.
Targeted reassessment
Review defined modules while preserving unaffected evidence.
Full reassessment
Rebuild the approval basis because a foundational assumption no longer holds.
Deployment hold
Resolve a blocking issue and obtain authority before release.
Outputs
A release decision you can reconstruct.
DELTA creates a small set of usable records rather than a generic compliance dashboard.
01
Change Record — the approved baseline, proposed release and material differences.
02
Reassessment Map — the approvals, assessments, controls and evidence that the change affects.
03
Release Route — the outcome, reasons, unresolved gaps and conditions.
04
Action Register — owners, deadlines, evidence needs and future review triggers.
Who it is for
Built for the gap between engineering and governance.
Engineering knows what changed. Governance teams must decide what follows. DELTA gives both sides one structured comparison and one common record.
ProductEngineeringLegalComplianceData protectionResponsible AIRiskProcurementSecurityInternal audit
The decision owner remains accountable. DELTA structures the work; it does not assume authority.
The technicals
Simple on the surface. Inspectable underneath.
DELTA runs as a deterministic browser application. It compares one approved baseline with one proposed release, tests the recorded facts across defined trigger domains and applies a transparent outcome hierarchy. The core result does not depend on generative AI.
ProcessingOn the user’s device
Decision logicDeterministic and inspectable
StorageOptional browser save and JSON export
ReportingReasoned record and print-ready PDF
Access and licensing
Try it. Use it once. Make it part of every release.
Public demonstration
£0
Explore a complete fictional change and see how DELTA reaches its result.
- Pre-loaded sample facts
- Interactive rule logic
- Watermarked sample report
Single assessment
£395 + VAT
Use DELTA for one named system and one defined change event.
- Local save and reopen
- Full reasoning record
- JSON and print-ready export
Organisation licence
£7,500 / year + VAT
Put DELTA into the internal release process for one named legal entity.
- Unlimited internal assessments
- Method and rule-pack updates
- Standard sector profiles
A narrow promise
No badge. No black box. No false certainty.
DELTA produces structured decision support. It does not certify compliance, replace professional judgement or bind a regulator, court, auditor or notified body. The result remains conditional on the facts, evidence, law and rule pack recorded at the assessment date.
Read the product boundaryStart with one real change
Put the baseline and proposed release side by side.
Use the public example first. For a pilot or licence, identify the system, approved version, proposed version and decision timetable.