// The Sealer

Records That Defend Themselves

Portable Proof for Digital Records

LexDelta seals digital records at the moment of capture. It packages the record representation with integrity proof, independent timestamp evidence, certificate-status material, organizational attribution evidence, and a human-readable verification guide -- so the evidence set can be checked later offline by an auditor, counterparty, or verifier.

Built in Ireland

// Live Proof

Running in Production. Daily. Automated.

[SEAL OK]EU

EUR-Lex

European Union regulations, directives, decisions, and proposals. Sealed daily from the EU Publications Office.

[SEAL OK]US

Federal Register

US federal rules, proposed rules, notices, and pre-publication documents. Sealed daily from the Federal Register API.

Live pilot. Last verified: 10 June 2026.

The sealing pipeline is source-extensible. Today it seals public regulatory data as a live proof of operation. The same sealing path is designed to work with new adapters without changing the cryptographic core.

UK PLANNEDIreland PLANNEDCanada PLANNED

// The Problem

Can You Defend the Record?

Pick one record your company may need to defend. Run this check.

EVIDENCE CHECK: CORPORATE RECORD

FILE EXISTSYES

CONTENT AT TIME OF EVENTNOT INDEPENDENTLY PROVEN

INDEPENDENT TIME PROOFNOT INDEPENDENTLY PROVEN

CHANGED SINCE CAPTURE?NOT INDEPENDENTLY PROVEN

VERIFIABLE WITHOUT YOUR SYSTEMNO

Logs are not evidence.Backups are not proof.A folder proves possession, not integrity.

Regulation now pulls in two directions. GDPR can require erasure when Article 17 conditions apply. The EU AI Act requires providers of high-risk AI systems to retain key technical and quality-management documentation for ten years. DORA increases pressure on financial entities to maintain defensible evidence around ICT risk and third-party arrangements.

The audit question is no longer only “do you have the record?” It is “can you prove what it was, when it existed, and whether it changed?”

// Inside a Sealed Evidence Set

Six Layers. One Seal.

Each sealed evidence set wraps the record in six layers of cryptographic proof. Altering any layer breaks the seal.

06Self-DescribingHuman-readable

Verification guide, glossary, schemas -- all tamper-protected as Merkle leaves.

05Organizational AttributionPKCS#1 / RSA-4096

Detached organizational signature attributing the seal to the signing authority, with independent counter-timestamp.

04Long-Term ValidationRFC 5280 / RFC 6960

Certificate chain, revocation snapshots, and OCSP responses captured at seal time.

03Temporal ProofRFC 3161

Independent timestamp on the integrity root, verified before the evidence set ships.

02Integrity ProofSHA-256 / SHA-512

Dual-hash manifests and domain-separated Merkle tree.

01The Sealed Record

Source data captured, normalized, and constrained by allow-list rules before sealing.

The organizational signature is stored alongside the evidence set, not inside it. This is deliberate: the signature covers the complete, final sealed content without a circular dependency. An independent counter-timestamp proves when the signature was made. If the sidecar is unavailable, integrity and timestamp checks can still be evaluated, but organizational attribution cannot pass.

// The Sealing Pipeline

How Records Become Evidence

CAPTUREConnect to source. Retrieve the record.

NORMALIZESanitize by allow-list. Canonicalize to deterministic byte representation.

ANALYZEDetect changes. Score materiality. Seal the analysis outcome into the evidence set -- success or failure.

SEALBuild the evidence set. Compute domain-separated Merkle tree. Write dual-hash manifests.

TIMESTAMPAcquire independent RFC 3161 timestamp on the Merkle root. Verify it before shipping. Capture certificate-status material.

ATTESTSign with organizational key. Counter-timestamp the signature. Detach and store alongside.

// Comparison

Not Just a Timestamp. Not Just a Signature.

	Plain Timestamping	E-Signature	WORM / Object Lock	LexDelta
What does it mainly prove?	A hash existed at a time	A party approved something	Retention controls applied	Evidence set captured, sealed, timestamped, attributed, and made checkable
Packages verification context?	Usually not	Platform-dependent	No	Yes -- record, proof structure, cert-status, attribution, verification guide
Travels outside platform?	Hash/token only	Platform/export dependent	No	Yes, as a portable evidence set
Checkable offline?	Only if validation material retained	Platform/package dependent	Not meaningfully	Evidence set carries data, proof, chain, and revocation state. Verifier supplies standard trusted roots.
Explains itself to an auditor?	Usually not	Usually not	Usually not	Yes -- guide, glossary, and schemas sealed in
Proves signer consent?	No	Yes	No	No -- use e-signatures for that

// What Makes This Different

Four Things No Timestamp API Ships

Self-Describing, Self-Defending

Every evidence set ships with its own verification guide, glossary, and schemas. These are not attachments -- they are bound as leaves within the Merkle tree. Alter a single word in the instructions and the entire cryptographic proof breaks.

Vendor-Independent Verification

FACTUM verifies sealed evidence sets with zero network access and zero connection to LexDelta. Your auditor, your counterparty, or your regulator can check a seal on their own machine.

Long-Term Checkability

Certificate chain, revocation snapshots, and OCSP responses are captured at the moment of sealing. The evidence set can be checked against its original trust context even after the certificates used to create it have expired.

Failures Are Sealed, Not Silenced

Once a record enters the sealing path, the analysis outcome -- success or failure -- is cryptographically bound into the evidence set. The record of what happened cannot be silently rewritten.

// Technical Foundation

Built on Published Standards

Published standards make the seal independently checkable. Formal third-party security review is on the commercial roadmap.

PACKAGINGBagIt with dual-hash manifests (SHA-256 + SHA-512)

INTEGRITYDomain-separated Merkle tree, full tree shipped

TIMESTAMPINGIndependent RFC 3161 timestamps, verified at seal time

CERTIFICATESChain validation, OCSP, CRL snapshots captured at seal

CANONICAL FORMRFC 8785 JCS (deterministic byte-level representation)

SIGNINGRSA-4096, detached sidecar with independent counter-timestamp

PAYLOAD RULESAllow-list contracts with forbidden-field detection

Sealed by LexDelta. Checked Without Trusting LexDelta.

LexDelta creates the sealed evidence set. FACTUM verifies it independently, with no network connection, no account, and no callback to LexDelta. Your auditor, your counterparty, or your regulator can check a seal on their own machine. FACTUM is distributed independently from LexDelta so recipients can verify sealed evidence sets without calling back to the sealer.

See the verification pipeline in action

// Hard Questions

Ten Answers

01Has this been independently audited?

Not yet. LexDelta is built on published IETF standards and FACTUM verifies evidence sets offline, but formal third-party security review is on the commercial roadmap.

02Why is the organizational signature detached?

The signature covers the complete, final sealed content. Putting the signature inside would create a circular dependency. The detached sidecar is cryptographically bound to the evidence set and independently counter-timestamped. If the sidecar is unavailable, integrity and timestamp checks can still be evaluated, but organizational attribution cannot pass.

03What happens if the timestamp authority changes?

Timestamp tokens follow the RFC 3161 standard, which is supported by multiple independent authorities. Previously sealed evidence sets remain bound to the timestamp evidence captured at seal time. Changing timestamp providers does not require resealing those evidence sets, although future trust policy may affect how any timestamp evidence is evaluated.

04Are these qualified timestamps under eIDAS?

The current timestamp authority issues independent RFC 3161 timestamps. Qualified timestamp status under eIDAS is not confirmed at this time.

05What data has been sealed in production?

The engine currently seals public regulatory data from EU and US sources daily as a live proof of operation. The same sealing path is designed to apply to private records through the adapter architecture.

06What BagIt version do evidence sets use?

Evidence sets use BagIt packaging with dual-hash manifests (SHA-256 and SHA-512).

07What happens if sealing fails?

If the timestamp cannot be independently verified, the seal is not issued. The pipeline is fail-closed: uncertain or incomplete evidence is never shipped as verified.

08How will LexDelta be licensed?

LexDelta is a commercial product. FACTUM is distributed independently so recipients can check sealed evidence sets without calling back to LexDelta. Full licensing terms will be published at launch.

09How is pilot data handled?

Pilot data handling, residency, retention, and deletion terms are defined in a scoped agreement before work begins. Sealed evidence sets are delivered to the pilot partner.

10Why not blockchain anchoring?

Blockchain anchoring proves a hash was published on a chain. LexDelta packages the record representation, proof structure, certificate-status material, attribution evidence, and verification guide into a portable evidence set with no dependency on any external chain existing or being reachable.

// Next Step

Request a Sealed Sample

Tell us which jurisdiction matters to your organization. We will seal a sample of official public regulatory data from that jurisdiction and send you the evidence set along with the FACTUM verifier, so you can check it on your own machine before we ever have a second conversation.

The sample shows you exactly what your auditor would receive: the sealed evidence set, the verification guide inside it, and the verifier that checks it offline.

Private-record pilots are available by scoped agreement.

We take on a small number of pilots at a time so each gets direct founder attention. Live since April 2026.

Your Records, Same Engine

Today the engine seals EUR-Lex and Federal Register publication streams, daily, in production. The same pipeline is designed to seal your contracts, your policy documents, your compliance records. Tell us which ones.

More jurisdictions (UK, Ireland, Canada) PLANNEDClient dashboard PLANNEDSelf-sealing for organizations PLANNED