The Missing Layer Between Documents and Markets
Many assets do not reach a market because the rights, restrictions and evidence behind them remain fragmented across documents and systems. A structured Rights Passport can help bridge the gap without pretending that digitisation, tokenisation or a private record automatically creates ownership, transferability or liquidity.
This starts a temporary private draft. It is not public, listed for sale or shared automatically.
Markets cannot assess what they cannot understand.
A business may hold an unpaid receivable, a contractual revenue right, a licence, a secured claim or another right with economic significance. Yet the right may never reach a financing partner or potential buyer because the information needed to understand it remains scattered across agreements, amendments, invoices, notices, payment records, registries and correspondence.
The problem is not always that the asset lacks value. Nor is it solved merely by creating a token or uploading a PDF.
The missing layer is a structured account of:
- what the underlying right is;
- who is stated to hold or control it;
- which documents support it;
- which restrictions, security interests or competing claims may apply;
- what has happened since the right was created;
- what remains uncertain or unreviewed; and
- what must occur before the right can be assigned, registered, financed or offered to another party.
This is the layer between documents and markets.
Key point: Before an asset can be considered for a market workflow, its rights, evidence, restrictions and current state must be understandable. A digital representation cannot supply missing legal substance by itself.
A folder is not yet a market-ready asset
Document-backed rights often begin as a collection of files rather than a standardised record.
A claim package may contain:
- the original contract;
- invoices or drawdown records;
- amendments;
- payment history;
- default or termination notices;
- correspondence;
- security or guarantee documents;
- assignments or acknowledgements;
- court or enforcement records; and
- calculations prepared on different dates.
Each document may answer part of the story. None necessarily provides the complete current position.
Before another party can assess the asset, someone must connect the documents, identify the relevant versions, reconcile conflicting information and explain what each item is intended to prove.
That preparation is not the same as legal validation. It is the work required to turn an unstructured evidence package into something that can be reviewed responsibly.
The asset and the right are not always the same thing
The word asset can conceal several different legal and economic layers.
For example, a property may be the underlying asset, while different parties hold:
- ownership rights;
- a mortgage or other security right;
- a lease or occupancy right;
- a right to receive rent;
- an option or pre-emption right; or
- an enforcement right following default.
An intellectual-property portfolio may involve:
- ownership of a patent, copyright or trade mark;
- an exclusive or non-exclusive licence;
- territorial and field-of-use restrictions;
- a right to sublicense;
- royalty-payment rights; or
- security granted over the relevant rights.
A civil-law contract may contain payment, performance, termination, assignment, confidentiality and dispute rights that do not all move together.
The useful question is therefore not simply “Who owns the asset?” It is:
Who is stated to hold which right, against whom, under what conditions and supported by what evidence?
Six layers that should not be collapsed
Moving from a document set toward a transaction requires several separate layers.
1. The underlying asset or relationship
This may be a property, receivable, contract, licence, loan, data set, software system or another source of economic rights.
2. The legal right
The relevant object may be ownership, a claim, a security interest, a licence, a usage right, a revenue right or another entitlement recognised under applicable law.
3. The evidence
Contracts, registry extracts, invoices, signatures, notices, payment records and other documents may support the existence, scope and history of the right.
Evidence can be incomplete, inconsistent, outdated or disputed. Organising it does not automatically make it conclusive.
4. The structured rights record
A Rights Passport or rights layer within an Asset Passport can describe the available right, evidence, restrictions, provenance and review state in a consistent format.
This layer makes the package easier to understand. It does not replace the underlying legal right or official registry.
5. The digital representation
A private record, registry entry, identifier, certificate or token may represent information about the right.
Whether controlling or transferring that representation has legal consequences for the underlying right depends on applicable law and the relevant contracts or registry rules.
6. The market and settlement process
A market workflow requires eligible participants, lawful disclosure, an identified transaction object, agreed terms and an effective method for transferring the relevant right and consideration.
Settlement cannot be inferred merely from the fact that a digital record changed hands.
What a Rights Passport could contain
A useful Rights Passport should describe more than the asset's name and nominal amount.
Depending on the asset and purpose, it could contain the following sections.
Asset and right identity
- a unique package or record identifier;
- the asset or relationship being described;
- the specific right or bundle of rights in scope;
- relevant jurisdiction and governing law information;
- important external identifiers; and
- current lifecycle or registry status.
Parties and roles
- stated right holder;
- debtor, obligor, licensee or counterparty;
- assignor and assignee history;
- guarantor or security provider;
- account manager, servicer or representative; and
- the authority under which a person acts.
A party name in a document is not by itself proof of current identity, ownership or authority.
Scope and economic terms
- principal, nominal or contractual amount;
- currency and as-of date;
- payment or performance schedule;
- interest, royalty, fee or revenue terms;
- maturity, expiry or renewal conditions;
- events of default or termination; and
- reported payments, balances or performance events.
These figures may require independent recalculation and should not be treated automatically as market value.
Evidence and provenance
- supporting documents;
- document versions and relationships;
- source of each important fact;
- upload, extraction and review history;
- information supplied by the user;
- AI-assisted findings and confidence; and
- corrections or confirmations made by an authorised reviewer.
Restrictions and competing interests
- assignment or transfer restrictions;
- consent and notice requirements;
- confidentiality and data-use limitations;
- pledges, liens or other security interests;
- licences or pre-existing usage rights;
- set-off, dispute or defence information where recorded;
- territorial or field-of-use restrictions; and
- other facts that may affect priority or exercise of the right.
Readiness and uncertainty
- missing documents;
- conflicting versions or values;
- unresolved ownership or authority questions;
- facts not yet reviewed;
- prerequisites for a proposed next step; and
- areas requiring legal, financial or technical assessment.
The purpose is not to hide uncertainty. It is to make uncertainty visible before another party is asked to rely on the package.
Why standardisation matters
Standardisation does not mean forcing every right into the same legal model.
It means using consistent fields and statuses for recurring questions such as:
- What is the claimed right?
- Who are the relevant parties?
- Which evidence supports it?
- What amount or performance is stated, and as of when?
- Is transfer restricted?
- Are approvals or notices required?
- Is the information user-supplied, extracted or reviewed?
- What happened during the asset's lifecycle?
- What remains unresolved?
Consistent structure can reduce repeated manual work and make packages easier to compare. It cannot remove differences in national law, contract wording, registry rules or evidential standards.
A token is not the right it represents
Tokenisation may improve automation, traceability and technical transfer. It does not automatically establish the relationship between the token and an external asset or legal right.
The UNIDROIT Principles on Digital Assets and Private Law recognise that digital assets may be linked to other assets. They also preserve the role of other applicable law in determining whether a transfer of the digital asset affects the linked asset.
This distinction is critical.
A token that refers to a receivable does not necessarily transfer the receivable. A token associated with real estate does not automatically alter the land register. A token representing a licence does not remove contractual consent or sublicensing restrictions.
The digital representation and the represented right must be connected by a legally effective mechanism.
Electronic does not automatically mean transferable
The UNCITRAL Model Law on Electronic Transferable Records illustrates the level of structure required when an electronic record is intended to function like a transferable paper document or instrument.
Its approach relies on a reliable method to identify the authoritative electronic record, preserve its integrity and establish exclusive control by an identifiable person.
Uploading a scan, extracting its text, creating a hash or recording a token does not automatically create an electronic transferable record within that framework. The applicable jurisdiction must also recognise the relevant legal mechanism and the document or instrument must fall within its scope.
Digital markets still operate inside legal frameworks
The EU DLT Pilot Regime demonstrates that distributed-ledger market infrastructure does not exist outside financial regulation.
The regime applies to crypto-assets that qualify as financial instruments and creates a controlled framework for eligible DLT trading and settlement infrastructure. It includes limits, permissions and safeguards rather than treating tokenisation as an automatic route to unrestricted market trading.
This is an important lesson for non-traditional assets: technology can improve a process, but it does not decide whether the underlying object is a financial instrument, whether it may be offered or traded, or which regulated entity may provide the service.
Why one global depository is not the first step
The idea of one global depository for every type of right is attractive because it promises a common record and simpler transfer.
In practice, rights are created and recognised through different legal systems and institutions:
- land and mortgage registers;
- company and security-interest registers;
- intellectual-property offices;
- courts and enforcement systems;
- securities depositories;
- contractual records; and
- sector-specific registries.
A private platform cannot simply replace these institutions or declare its record legally definitive across jurisdictions.
The more realistic first step is an interoperable information layer that can:
- organise the evidence;
- distinguish different rights;
- preserve provenance and review status;
- record relevant external references;
- connect to official or authoritative systems where available; and
- prepare the package for the next legally appropriate workflow.
Connections are more credible than replacement.
Different assets need different rights models
Claims and receivables
The package may need to describe the underlying obligation, outstanding amount, payment history, assignment restrictions, notices, debtor defences, security and enforcement status.
Contracts and revenue rights
The relevant right may concern payment, performance, termination or a share of future revenue. The contract may restrict assignment or require counterparty consent.
Intellectual property and licences
Ownership, exclusive and non-exclusive licences, sublicensing, territory, duration, field of use and royalty rights must remain separate.
Secured and mortgage-related assets
The debt, security instrument, priority, collateral, registration and enforcement rights may be governed by different documents and systems.
Emerging digital objects
Software, data rights and AI-agent configurations may involve several providers, operators and licensors. A passport can describe the relevant identity, permissions and rights without assuming one indivisible owner or automatic transferability.
Standardisation should therefore provide a common framework while preserving asset-specific fields and legal distinctions.
How DaDepo can contribute
DaDepo's role begins before a market transaction.
The platform can help users:
- upload and organise a document package;
- use AI-assisted analysis to identify available facts and possible gaps;
- connect recorded information to source documents;
- distinguish user-supplied, extracted and reviewed information;
- create an Asset Passport;
- control visibility and document access;
- preserve lifecycle and review history; and
- prepare for registration or buyer review when the applicable workflow allows it.
DaDepo's longer-term direction may include a richer Rights Passport layer, asset-specific readiness models, connections to external registries and depositories, buyer mandates, Offerboard discovery and institutional integrations.
These are development directions. Not every function is currently live or available for every asset, user or jurisdiction.
What DaDepo does not create by recording information
Organising documents or creating an Asset Passport does not by itself:
- create or amend the underlying right;
- prove document authenticity or completeness;
- establish current ownership, title or authority;
- perfect a pledge or security interest;
- satisfy a notice, consent or registration requirement;
- remove a transfer restriction;
- make the right a security or financial instrument;
- create a legally recognised electronic transferable record;
- make an asset suitable for a buyer;
- complete a sale or settlement; or
- guarantee price, liquidity or financial return.
An Asset Passport is an information and workflow tool. Its value comes from clearer structure, visible sources and a more disciplined preparation process—not from replacing the legal acts and institutions that give rights their effect.
From documents to a responsible market path
Many rights will remain difficult to finance or transfer even after their information has been organised. Legal restrictions, weak evidence, disputes, poor economics or lack of buyer demand may still prevent a transaction.
But without a structured rights layer, those questions are often discovered late, repeatedly or inconsistently.
The missing layer between documents and markets is therefore not another token alone. It is a reliable way to describe the right, connect it to evidence, expose its limitations and carry its reviewed information toward the next appropriate system.
That layer does not manufacture liquidity.
It makes responsible assessment possible.
Insights