← Back to blog
What is Rights Continuity?
Learn 2026-07-07

What is Rights Continuity?

In brief

Rights Continuity is the practice of keeping the evidence-state of a documented right reviewable after it is issued, across every counterparty, system, jurisdiction and moment that touches it.

A documented right (a loan, an invoice, a tokenized bond) is created once and reviewed many times. Today, each new party that looks at it reconstructs the proof from scratch inside its own silo. Rights Continuity is the state in which that reconstruction is no longer necessary, because the evidence behind the right stays reviewable over time.

One right, reviewed many times: the evidence gap and Rights Continuity Rights Continuity keeps the evidence-state of a documented right reviewable across every handoff between parties, instead of rebuilding the proof from scratch in a separate silo each time (Party A, Party B, Party C). The same evidence-state is reviewed by a human reader (counsel, auditor, bank) and read by a machine reader (a contract or agent). Veridex Alethia composes and exposes the evidence-state; it does not determine legal validity, control, admissibility or compliance; those verdicts stay with the parties. THE SAME RIGHT HOW IT WORKS One right, reviewed many times. Today The evidence is rebuilt at every handoff, in a new silo. PARTY A evidence rebuilt from scratch PARTY B evidence rebuilt from scratch PARTY C evidence rebuilt from scratch Rights Continuity One evidence-state, reviewable across the same handoffs. PARTY A PARTY B PARTY C Human reader: counsel, auditor, bank Machine reader: contract or agent Veridex composes and exposes the evidence-state. It does not determine legal validity, control, admissibility or compliance; those verdicts stay with the parties.

Rights Continuity keeps one evidence-state reviewable across every handoff, so counsel, auditors and on-chain contracts review the same right without rebuilding the proof.

Governing principle. Rights Continuity: evidence that stays reviewable across systems, jurisdictions and time.

Key takeaways

  • Digital validity is established at a moment. Continuity is a state that has to be maintained afterwards.
  • VERIDEX composes evidence from other systems (signature, custody, registries, oracles) and keeps it reviewable. It does not certify legal validity, control or compliance; the verdict always belongs to a third party.
  • The same evidence-state is built to be consumed in two worlds: reviewable in a legal or audit setting, and designed to be readable by a smart contract or an AI system.

What problem does it solve?

A right is born once and reviewed many times. Every time a new party examines it, a bank, a counsel, an auditor, a regulator, a smart contract, that party rebuilds the evidence in its own silo: which signature, under which authority, verified against which source, still in force under which conditions.

That repeated reconstruction is slow, expensive and fragile. It is where disputes start, where audits stall, and where the same underlying right can be represented inconsistently across systems that never reconcile. Rights Continuity addresses the reconstruction itself, not any single document.

Why it matters now

The need is structural, not a response to any single deadline. A right born on paper could tolerate broken evidence because reconstruction was slow on all sides. That tolerance disappears when rights move at the speed of software and the reviewer is increasingly a machine that does not call a lawyer.

Two shifts make the gap explicit. First, a wave of transferable-records regimes now lets an electronic record carry the legal effect of paper: the UK Electronic Trade Documents Act 2023, Article 12 of the Uniform Commercial Code in New York (effective 3 June 2026), and China's revised Maritime Code (effective 1 May 2026), all aligned with the UNCITRAL Model Law on Electronic Transferable Records. Alongside them, Europe's identity and trust-services framework (eIDAS 2.0, Regulation (EU) 2024/1183) and its operational-resilience regime (DORA, Regulation (EU) 2022/2554) raise the bar for evidence that stays auditable after execution. Each of these confers or governs validity at a point. None keeps the evidence reviewable for the next party once the right has moved.

Second, regulators have started measuring the quality of regulatory data at scale, and the readings are stark. In the European Union's 2024 DORA dry run, only 6.5% of the 947 registers analysed passed all 116 data-quality checks, and missing mandatory information accounted for 86% of the errors. That exercise measures the quality of ICT third-party registers, not the evidence behind documented rights; it is read here as a signal of the same underlying challenge, not as proof of it. The pattern it points to, structured records that are incomplete the moment they are examined, is the pattern Rights Continuity is built to close.

The cost of the gap is not only regulatory. In voluntary carbon markets, industry estimates put the path from project design to a first issued credit at nine to eighteen months, much of it spent assembling and verifying documentation that later reviewers will have to reconstruct again. The shape repeats wherever a documented right changes hands.

How is it different from digital validity?

Digital validity answers a point-in-time question: is this record valid at the moment of issuance, under an enacting law? Frameworks such as the UNCITRAL Model Law on Electronic Transferable Records (MLETR, 2017), the EU's eIDAS 2.0 regime, and national statutes like China's revised Maritime Code are what confer that status, each within its own scope.

Rights Continuity answers a different question, and a later one: after that moment, as the right changes hands and crosses systems, can its evidence still be reviewed by whoever needs to? Validity is a determination made by a legal framework. Continuity is a property of the evidence that has to survive the lifecycle. One does not replace the other. A right can be validly issued and still lose continuity the moment its evidence fragments across parties.

How is it different from proof of reserves?

Proof of reserves attests, at a check, that the assets backing a product exist. It is a snapshot of backing. Rights Continuity is not about aggregate backing at a moment; it is about the evidence-state of a specific documented right across its whole lifecycle, a cession, a pledge, a waiver, a default, and about keeping that evidence reviewable by both a legal reader and an on-chain consumer.

Rights Continuity Digital validity Proof of reserves
Question it answers Can the evidence still be reviewed, later, by anyone who needs to? Is this record valid at issuance? Do the backing assets exist at this check?
When it applies Across the whole lifecycle, after issuance At a moment, under an enacting law At a point in time, per attestation
What it establishes A reviewable evidence-state A legal status Existence of backing
Who issues the verdict Counsel, auditors, registries, courts (VERIDEX exposes the evidence) The enacting legal framework The attesting party or oracle
Consumable on-chain Designed for dual consumption; on-chain path in testnet (design partner) Not by default Often, as a reserve feed

What does it do?

Rights Continuity preserves the evidence behind a right in a single persistent object, and derives two views from that same object: a human-readable view (a legible record) and a machine-readable view (a structured output a contract or an agent can consume). VERIDEX Alethia builds six operations on that object, each currently offered in a controlled, pre-commercial mode:

  • Live Right Passport, a view of the evidence-state of a right at the current moment: who controlled it, under which authority, verified against which source.
  • Rights Control Tower, a chained record of the acts in its lifecycle (an assignment, a pledge, a payment, a default), so the state stays reviewable as the right moves.
  • Proof Pack, an assembled, source-tagged evidence pack for the moments that matter (an audit, a default, a dispute), with each piece carrying its declared reliance scope, what it is fit for and what it is not.
  • Disclosure Envelope, a disclosure mechanism that exposes to each recipient only what that recipient needs to see, and carries the reliance perimeter into the reader's context.
  • Evidence Continuity Index, a machine-readable signal of how the evidence is ageing over time (available to design partners), which reports on the health of the evidence, not the quality of the asset.
  • Agent Reliance Interface (ARI), a machine-readable endpoint through which an AI agent can request the current evidence-state of a right before acting on it. It relays that evidence-state as recorded, under its declared reliance scope; it does not verify the evidence independently, and it does not authorize or block the agent's action.

Each operation describes what it does mechanically. None of them determines legal validity, control or admissibility. Those verdicts stay with the parties the evidence is prepared for.

What Rights Continuity is NOT

Defining the category by what it excludes is not a disclaimer exercise. In a field built on evidence, the verdict has to belong to a third party, the registry, the auditor, the regulator, the court, and never to the tool. A tool that claims the verdict for itself forfeits the credibility the evidence is meant to earn. Each boundary below has a positive counterpart: what VERIDEX does instead, phrased as a mechanism, not an outcome.

It is not a compliance engine. VERIDEX does not make a right MLETR compliant and does not certify compliance with any regime; conformance is assessed against national law. What it does instead: it supports review of evidence relevant to MLETR-aligned workflows, so the parties who do assess conformance have that evidence assembled and reviewable.

It is not a trust service under eIDAS. VERIDEX is not a Qualified Trust Service Provider and does not issue qualified signatures or timestamps. What it does instead: it references and composes the evidence those systems produce, including qualified evidence where present, and keeps it reviewable. The qualified status stays with the qualified provider.

It is not custody or token issuance. VERIDEX does not hold assets, issue tokens or move value. What it does instead: it preserves and exposes the evidence-state of documented rights that are held, issued and moved in other systems.

It is not legal advice or a determination of admissibility. VERIDEX does not advise on the law and does not determine whether evidence is admissible or a right is valid; those determinations belong to counsel and to the court. What it does instead: it records and exposes control-evidence signals, each tagged by source and declared reliance scope, so counsel can assess them. The terminology is deliberate: VERIDEX deals in evidence, not in validity. Validity is a word for the legal framework to use, not for an evidence output to claim.

It is not a single source of truth. VERIDEX does not constitute the record and does not replace the systems that already hold it. What it does instead: it composes evidence from signature, custody, registry and oracle systems into a reviewable evidence-state, and leaves each of those systems in place.

It is not a rating of the asset. The Evidence Continuity Index reports on how the evidence behind a right is ageing, as certificates expire, trust lists change, or an entity is renamed. It is a statement about the health of the evidence, not the credit, quality or value of the asset, and it is currently available to design partners.

Is Rights Continuity a product or a category?

It is the category. VERIDEX Alethia builds products within it. The category names the problem, evidence that stays reviewable after issuance, and the promise is narrow on purpose: nothing the category cannot support. To see where the gap shows up in real workflows, read Rights Continuity in practice.

Frequently asked questions

Is Rights Continuity the same as a document being legally valid?

No. Legal validity is established at a moment, under an enacting law, and it is determined by that legal framework. Rights Continuity is the state that keeps the evidence behind a right reviewable after that moment, as the right moves between parties and systems.

Does VERIDEX certify compliance or legal control?

No. It composes and exposes evidence from other systems and keeps it reviewable. Compliance, control and admissibility are determined by counsel, auditors, registries and courts, not by VERIDEX.

Does VERIDEX hold or issue tokens or assets?

No. VERIDEX does not provide custody, does not issue tokens and does not move assets. It preserves and exposes the evidence-state of documented rights held and moved elsewhere.

How is it different from proof of reserves?

Proof of reserves attests, at a point in time, that assets backing a product exist. Rights Continuity concerns the evidence-state of a specific documented right across its whole lifecycle, and keeps that evidence reviewable by both legal and on-chain consumers.

Who can review the evidence?

The same evidence-state is designed to be reviewable by banks, counsel, regulators, auditors and AI systems, and readable by on-chain protocols, without each of them reconstructing the evidence from scratch.

Sources

Request a demo →