One operational question
DELTA does not attempt to govern the entire AI lifecycle inside one questionnaire.
About DELTA
Decision infrastructure for systems that do not stand still.
DELTA turns lifecycle discipline into a practical release-control method.
The idea
Approvals expire when their assumptions stop being true.
Organisations often approve an AI or automated system at one moment, then change the model, data, purpose, population, interface, supplier or degree of autonomy without reopening the original reasoning.
DELTA addresses that gap. It treats the approval as a versioned claim supported by facts, evidence and controls. A later change must show which parts of that claim still stand.
Product lineage
Built from the same discipline as TRACE and the AUIA.
TRACE asks what a data artefact is, for whom a status claim applies, how the artefact may circulate and what evidence keeps the claim valid. The Anonymisation and Utility Impact Assessment supplies the deeper dossier beneath that passport.
DELTA carries the same product grammar into AI change control: define the object, actors, operation, version, evidence, controls, uncertainty and expiry. The product does not rely on a floating label such as “approved” any more than TRACE relies on a floating label such as “anonymous”.
Design principles
Focused tools, not compliance theatre.
Plain language first
The product states the decision before introducing the technical and legal machinery.
Reasons before scores
Every route identifies the facts and evidence that produced it.
Preserve valid work
A change should reopen affected modules, not force needless repetition.
Local by default
The browser assessment need not transmit confidential facts to an assessment server.
Conclusions expire
Reports record versions, dates, conditions and trigger events rather than claiming permanent approval.
Method owner
Developed by Dr M.R. Leiser through DigiData Consulting Ltd.
Dr Mark Leiser’s work spans AI regulation, data protection, consumer protection, deceptive design and the governance of digital systems. DELTA translates that legal and regulatory research into a product that multidisciplinary teams can use before release.
DigiData remains responsible for the methodology, question architecture, explanations, outcome language and standard rule packs. Production deployments require defined responsibility for licensing, updates, support and technical maintenance.
About DigiDataProduct status
Pilot, test, review, then rely.
Interface version 0.3 remains a pilot product. The core workflow functions, but commercial deployment still requires controlled user testing, external legal review, security review, accessibility testing and confirmation of the current rule packs.
That boundary appears throughout the product. DELTA should reach production through evidence, not through a badge placed on an unfinished tool.
See the version history