CDM 7: From Common Data Towards Common Execution

How the Smart Contracts Framework begins to close the abstraction gap between contractual obligations and post-trade workflows

By Richard Baker, Founder and CEO, Tokenovate

CDM 7 is a significant production milestone for the FINOS Common Domain Model. It expands legal and lifecycle coverage, creates a more practical route from FpML into CDM, and introduces the first major components of a standards-based framework for deterministic lifecycle execution

Capital markets already have highly developed legal and product standards. The persistent challenge is operational translation. The same rights and obligations are repeatedly converted into confirmations, trade records, local processing logic, settlement instructions and reporting outputs. Each conversion creates scope for divergence, reconciliation and delay.

That problem becomes more acute as settlement cycles compress and markets adopt new forms of digital infrastructure. Less time is available to identify inconsistent data, repair exceptions and establish whether an operational action still reflects the governing agreement. The industry therefore needs a common semantic foundation that can preserve meaning as a transaction moves from contract to lifecycle event and, ultimately, to settlement.

A production milestone beyond data standardisation

FINOS describes CDM 7 as one of the most significant releases in the model’s evolution. The 7.0 production milestone consolidated more than 130 upgrades delivered over the preceding year, including expanded legal agreement, product, collateral and lifecycle coverage, functional FpML ingestion mappings, Event Model enhancements and the first major components of the Smart Contracts Framework.

The importance of the release lies in the way these developments reinforce one another. Functional ingestion makes established source data easier to transform into native CDM representations. Expanded legal agreement modelling brings more contractual context alongside transaction data. Event Model improvements make state transitions clearer and more auditable. The Smart Contracts Framework begins to standardise how a contractual process progresses through a sequence of operational steps.

Taken together, CDM is moving beyond a common description of a transaction towards a common framework for how that transaction evolves. FINOS itself characterises this as reducing the distance between financial contracts, source data and executable business processes.

The first foundation for common execution

The central development is the Instruction Composition Framework. It introduces a state-machine approach for multi-step lifecycle processes, with the ability to track workflow progress, accumulate intermediate state and determine the next valid operational step.

The initial implementation focuses on interest-rate reset processing. Observations, rate determinations, calculation inputs and audit information can be assembled within lifecycle instructions before the resulting event is applied to trade state. Each stage is therefore bounded, inspectable and capable of being reused as part of a governed process.

This matters because the framework is technology-agnostic. It is expressed in Rune, the domain-specific language underpinning CDM, and is designed as a functional recipe for contractual performance. The same standardised logic can be implemented within existing enterprise systems, shared services or emerging settlement infrastructure without being tied to a particular network or rail.

The 7.0 release established the production foundation. Subsequent releases in the CDM 7 series are already extending the eight-step reset sequence, demonstrating that the framework can evolve incrementally while preserving a consistent state and audit model.

“Capital markets become genuinely programmable when contractual meaning can move through data, workflow and settlement without being reinterpreted at every stage. CDM 7 provides an important standards-based bridge between legal obligations and deterministic lifecycle execution. Interest-rate resets are the first proof point, but the architecture is reusable across products, firms and infrastructure.”

Why interest-rate reset is the right first proof point

An interest-rate reset is a familiar process, but it is not a single calculation. It requires a governed sequence of observations, business-day adjustments, benchmark data, calculation conventions, determinations and resulting lifecycle instructions. Those steps are shaped by the 2021 ISDA Interest Rate Derivatives Definitions and by the economic terms of the transaction.

Historically, firms have implemented that sequence independently. The governing industry standard may be common, while the procedural logic, intermediate data and audit evidence differ across institutions and vendors. That fragmentation increases implementation cost and makes consistent outcomes harder to demonstrate.

Representing the reset sequence within CDM creates the possibility of shared, reusable business logic with explicit state progression and evidence at each stage. It also provides a practical pattern for other processes that combine contractual rules, observations, calculations and controlled actions, including equity and foreign-exchange resets, transfers, collateral processes and settlement instructions.

The significance of the reset work is therefore architectural. It shows how a declarative model can become the basis for deterministic execution without losing the transparency, governance and technology independence required in regulated markets

Tokenovate’s role in moving from concept to implementation

Tokenovate has played a central implementation role in this work alongside ISDA and the FINOS community. In October 2025, Tokenovate and ISDA announced the CDM Operationalisation Taskforce, with an initial focus on automating post-trade events beginning with interest-rate resets under the 2021 ISDA Definitions.

Tokenovate subsequently presented a granular model that decomposed the reset process into modular steps, implemented in Rune so that the framework remained technology-agnostic. The design used accumulated workflow state and history to preserve the output and lineage of each stage before the final reset instruction was produced.

The first major components of that work were incorporated into CDM 7.0 through the Instruction Composition Framework, supporting functions and Event Model changes. Tokenovate continues to contribute to the remaining reset stages and to the wider effort to make CDM lifecycle logic practical for production use.

In parallel, Tokenovate’s work with the FINOS CDM Tokenized Assets Working Group applies the same principle to emerging infrastructure: common asset and lifecycle semantics should allow established and new settlement environments to interoperate without requiring every participant to adopt the same underlying technology.

Closing the abstraction gap

For Tokenovate, this development goes to the heart of a legal-first operating model. Legal meaning remains the source authority. CDM provides the semantic representation of products, agreements, events and state. Deterministic workflow logic applies validated rules to that state. Custody, payment and settlement infrastructure then records or completes the resulting outcome at the appropriate venue of legal finality.

01 LEGAL MEANING

Rights, obligations and elections.

02 CDM SEMANTICS

Products, events and lifecycle state.

03 DETERMINISTIC WORKFLOW

Validated actions and state transitions.

04 SETTLEMENT OUTCOME

Custody, payment or finality.

This ordering matters. A system event should remain traceable to the contractual obligation and lifecycle event that gave it authority. Equally, settlement should be the controlled consequence of a validated workflow rather than the end of a chain of disconnected transformations.

Tokenovate operationalises this model through its Data Normalisation and Workflows-as-a-Service capabilities. Source information is mapped and validated into a CDM-based Unique Trade Record. Lifecycle workflows then act on that common state to generate calculations, events, instructions, regulatory outputs and settlement actions with consistent lineage.

The architecture is designed for regulated-market use, with permissioned access and known identities. It remains independent of a native token, ledger or settlement rail, allowing firms to preserve technology choice while using CDM as the common semantic layer across custodians, asset managers and market infrastructures.

FpML as a practical adoption bridge

CDM 7 also makes adoption more practical by completing the transition from legacy synonym-based mappings to functional FpML ingestion. Rates, foreign exchange, credit, equity and commodity confirmations can be transformed into native CDM representations through mappings that are more transparent, reviewable and maintainable.

FpML remains deeply embedded in derivatives infrastructure. A credible path to common execution must therefore work with the installed market rather than depend on wholesale replacement. Functional ingestion creates a bridge from existing confirmations and messages into a common semantic state from which new workflows can operate.

For Tokenovate, that progression is direct: source data is ingested, normalised and validated into the Unique Trade Record; standards-based workflows then support resets, amendments, novations, transfers, reporting and settlement orchestration. As more processes act on the same economic meaning, exception management can move earlier and repeated reconciliation can reduce.

What this enables next

1. Compressed settlement cycles

T+1 and further compression reduce the time available to identify inconsistent data and repair operational breaks. CDM-native normalisation and deterministic lifecycle workflows can surface exceptions earlier, preserve a clearer decision trail and support more automated processing within shorter timeframes.

2. Interoperability across market infrastructure

Custodians, asset managers, banks and financial market infrastructures do not need identical technology stacks to share consistent lifecycle meaning. CDM can operate as the semantic layer that synchronises products, obligations, events and state while each participant retains its own governance, controls and systems of record.

3. Reusable post-trade services

Common market processes are currently implemented repeatedly from the same legal and product standards. Standardised execution patterns allow those processes to be delivered as reusable services, reducing duplicated implementation effort and enabling proprietary investment to focus on genuine areas of differentiation.

A standard becoming infrastructure

CDM 7 matters because several foundations are converging. Functional ingestion provides a route from established formats. Legal agreement modelling brings contractual context closer to transaction data. Lifecycle improvements strengthen state transitions. The Instruction Composition Framework creates a reusable pattern for deterministic, auditable execution.

For Tokenovate, the resulting model is clear: CDM provides the semantic layer; the Unique Trade Record provides a trusted operational representation; Workflows-as-a-Service applies governed lifecycle logic; and custody, payment or settlement infrastructure completes the outcome. The same framework can support existing market operations and the transition to new rails without fragmenting legal or economic meaning.

The importance of CDM 7 therefore lies in both what it delivers and what it makes possible. A common language for transactions is becoming a common framework for action. That is a critical foundation for closing the abstraction gap and building safer, more interoperable capital markets under T+1, intraday and increasingly programmable settlement cycles.