MDLCE™ (Murray Deterministic Liability Closure Engine) is a compliance attestation engine for safety-critical and regulated software systems. It generates cryptographically-sealed compliance artifacts that provide durable evidence of how software executed and how safety standards were applied at a specific point in time, reducing the risk of reinterpretation under evolving regulatory frameworks.

01 The problem

Safety-critical software certification can cost several million pounds and take many months per cycle, depending on domain, system scope, and regulatory context. Post-deployment, software behavior can be reinterpreted years later under new regulatory interpretations, creating unbounded liability exposure. The MDLCE attestation engine addresses this by generating non-reinterpretable compliance evidence designed to resist dispute under future regulatory changes.

Prohibitive recertification costs

Every software update requires manual recertification at significant cost and time, limiting agile development in safety-critical systems.

Multi-million pound cycles, extended timelines

Reinterpretable compliance evidence

Traditional documentation and test logs can be reinterpreted under evolving regulatory standards, creating extended liability disputes.

Multi-billion pound exposure in prolonged disputes

Blocked innovation

Over-the-air updates and rapid iteration are impractical when each change requires 18-month recertification cycles.

Competitors iterate weekly vs. 18-month cycles

Industry certification challenges

Examples are illustrative and based on publicly discussed certification challenges; complex incidents typically involve multiple contributing factors.

Aerospace: High-profile aerospace software incidents have involved multi-year recertification efforts and substantial financial exposure following difficulties reproducing execution behaviour.

Medical Devices: Firmware updates in Class C medical devices can require extended recertification periods and significant investment.

Automotive: Traditional OEMs face extended recertification cycles for software updates while software-first competitors iterate more rapidly.

02 The solution

MDLCE generates cryptographically-sealed attestation artifacts that prove exactly what software executed and how it complied with safety standards—creating non-reinterpretable evidence designed to resist dispute under future regulatory changes. It is designed to operate alongside deterministic execution platforms such as MDCP, but can also be integrated into existing safety-critical software environments.

Core design principle

Given an execution trace and safety schema, MDLCE is designed to generate cryptographically-sealed attestation artifacts where reinterpretation under a materially different schema is designed to invalidate the cryptographic seal.

This is achieved through schema hash binding (Patent Claim 11), deterministic execution capture, and cryptographic chaining of evidence.

Five-lock attestation pipeline

Deterministic execution capture

DMU-ME and DTE-E components capture execution state and evidence with bit-perfect reproducibility.

Safety compilation

DSC-E compiles safety properties into verifiable constraints with deterministic SAT-based proof generation.

Schema binding (Patent Claim 11)

DIT-A binds safety interpretation schema to attestation via cryptographic hash, preventing retroactive reinterpretation.

Temporal anchoring

DTA creates RFC 3161 timestamp proof, establishing exact time of compliance assessment under specific standards.

Attestation sealing

Final cryptographic seal combines all components into tamper-evident, non-reinterpretable compliance certificate.

Patent Claim 11: Non-reinterpretable attestation

The core innovation is cryptographic schema binding: the safety interpretation schema is hashed and sealed with the compliance verdict. Any attempt to claim "the standards meant something different" invalidates the cryptographic seal.

This shifts compliance evidence from narrative interpretation toward cryptographically verifiable attestation.

03 Validation

MDLCE has been validated as a proof-of-concept attestation engine through 579 days of continuous operation and 50 million tick processing.

579 Days continuous validation

50M Ticks processed

113 Tests passing (100%)

42ms Verification speed (10K ticks)

Validation includes deterministic execution capture, safety property compilation, schema binding verification, temporal anchoring, and complete attestation pipeline testing. The platform has been designed to align with DO-178C, IEC 62304, ISO 26262, and IEC 61508 safety standards. Formal safety certification and regulatory approval would be completed by the acquiring organization.

Production validation results

Duration: 579 days continuous operation on production workloads

Scale: 50 million ticks processed with consistent attestation generation

Verification: 42ms to verify 10,000-tick attestation artifact

Reliability: No attestation generation failures observed during validation testing, 113/113 tests passing

04 Value

MDLCE is designed to deliver financial, regulatory, and strategic value by transforming certification from manual documentation to automated attestation.

Note: Cost and timeline figures are indicative estimates based on industry benchmarks and published case studies; actual outcomes depend on regulatory context, system scope, and organisational processes.

Cost reduction potential

Per-certification savings

Traditional certification: multi-million pound cycles

Automated attestation: potential order-of-magnitude reduction

Substantially reduced timelines in appropriate contexts

Timeline improvement Months → potentially minutes

Strategic differentiation

Competitive advantage

Over-the-air update capability support

Faster iteration potential vs. traditional cycles

Non-reinterpretable liability closure approach

Patent protection GB2522369.4 (Claim 11 moat)

Potential impact by industry

Aerospace: Non-reinterpretable attestation addresses extended certification disputes and can support faster safety update deployment.

Medical Devices: Potential to reduce per-update costs substantially while accelerating deployment for critical safety patches.

Automotive: Can support over-the-air safety updates with automated attestation, improving software agility for traditional manufacturers.

05 Acquisition relevance

MDLCE is designed to be acquired, licensed, or embedded as certification infrastructure by organizations deploying safety-critical software at scale.

Aerospace

DO-178C certification

Major aerospace manufacturers — Following high-profile incidents, liability closure and accelerated recertification have become strategic priorities. Software changes can require extended manual recertification periods.

Medical Devices

IEC 62304 Class C certification

Leading medical device companies — Firmware updates can require significant investment and extended timelines, limiting rapid deployment of safety improvements and feature updates.

Automotive

ISO 26262 ASIL D certification

Automotive OEMs and software-defined vehicle developers — Traditional manufacturers face extended recertification cycles while software-first competitors iterate more rapidly with over-the-air updates.

Industrial Control

IEC 61508 SIL 4 certification

Industrial automation providers — Safety-critical industrial systems require frequent updates for security patches and operational improvements, which can be constrained by recertification costs.

Development Status: MDLCE is a validated proof-of-concept attestation engine with 579 days production validation, 50M tick processing, and 113/113 tests passing. Integration with specific safety certification workflows (DO-178C, IEC 62304, ISO 26262, IEC 61508) and regulatory acceptance would be completed by the acquiring organization with their certification infrastructure and regulatory relationships.

Strategic certification IP

MDLCE is a validated proof-of-concept attestation engine for safety-critical systems. Detailed technical documentation, 579-day validation results, architectural specifications, Patent Claim 11 analysis, and integration guidance are available under NDA for serious acquisition discussions.

Discuss acquisition Request NDA access

Request Complete Technical Documentation

Full technical specifications, validation data, and patent claims available under NDA for qualified strategic buyers.

Request Technical Brief