saascode
legal, compliance & regtech·run 118 · May 2026

Modelloomx

A multi-catalog data-exchange register that reconciles relationship evidence, reviewed applicability and versioned contract drafts for EU Data Act work.

Genesis score6.40/10
Make Modelloomx real.0/500
500 more votes and Modelloomx is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
Sep 2025New-contract applicability
The case

Large enterprises manage hundreds of data exchanges across catalogs, contracts, product systems and partner records. The supplied research corrects the original deadline premise: relevant new contracts have been subject to the EU Data Act since September 12, 2025, while certain older indefinite contracts transition later. There is no new September 2026 deadline.

Modelloomx aggregates customer-approved catalog exports and maps each exchange to parties, data, purpose, access, portability, switching, security, term and contract evidence. Catalog records are assertions that require owner confirmation; they do not prove actual flows, legal role or contractual sufficiency. All three proposed native integrations remain unverified, so the first release must be file-based.

The supplied research also confirms that a major data-catalog incumbent already ships a contract registry and open contract-standard support. Modelloomx therefore cannot sell basic data contracts as novel. Its wedge is multi-catalog reconciliation plus EU Data Act-specific evidence routing under counsel control.

Source metadata, observed flow, legal applicability, clause draft, counsel approval, counterparty agreement, signature, operational implementation and authority outcome remain separate. The first release prepares a reviewed gap register and draft packet; it does not auto-amend contracts.

Who pays — and why

Enterprise data-governance, legal or compliance leader coordinating data-exchange contracts across multiple catalogs and partner systems

What it unlocks
A relationship register separating catalog assertion, observed data flow, owner confirmation, legal role and contract source
A requirement-to-clause matrix preserving applicability rationale, evidence, counsel review, counterparty negotiation and signature
A versioned multi-catalog reconciliation trail that exposes conflicts and missing coverage rather than manufacturing one authoritative view
How Genesis scored it
6.40across seven criteria
tension 7temporal 7blindspot 5buyer 7leverage 8convergence 5why-not 5
8
Asymmetric leverage

Reconciliation and evidence routing can scale through software after source access is established.

7
Productive tension

Automation can reduce documentation backlog, while generated clauses can overstate legal sufficiency and conceal bad metadata.

5
Why nobody did it

The gap is clearer than the reason catalog incumbents have not added EU-specific workflows.

Why it scored well

The law is already applicable to relevant new contracts, enterprise backlogs are plausible and multi-catalog reconciliation creates a concrete workflow.

What's holding it back

The deadline premise required correction, a major incumbent already supports data contracts, all proposed integrations are unverified and no structural incumbent barrier is evidenced.

Signals detected4 sources crossed
SignalSupplied legal and industry research

SignalSupplied correction

SignalSupplied official competitor research

SignalSupplied capability audit

Direction briefmodelloomx.md
modelloomx.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.