Operating Record

The Operating Record.

Every contested split, every delayed royalty, every disputed valuation traces back to one structural fault. SplitGraf is the operating record that removes it.

Ring 01 — running todayWorkRecordingTerritoryProof

The root — structural, not anecdotal

The fault is in the data, and it has been for years.

175%

Ownership claims on a single work routinely exceed 100%. The U.S. Copyright Office documented disputed splits totaling 175 percent — money held until the parties reconcile.

Same song, other data

Labels supply different metadata for the same recording to different platforms, and each normalizes it on ingest. The same recording is matched, reported, and paid differently depending on where it played.

$4B

Catalogs change hands for billions on this operating data. One catalog implied at roughly $4 billion had already produced a 7.6 percent NAV error on the same reconciliation problem.

In 2024 a federal court described the largest streaming service as having licensed catalogs without knowing, in any detail, what they contained. The reprocessing loop the industry runs on isn't a bug — it's the correction mechanism for a record that was never verifiable.

The operating record

One connected record. The products and frontiers grow from it.

A single, verifiable record of who owns what — and the workflows and frontiers built on top of it. Select any node to see what it is and whether it's live or emerging.

The Operating Record connected graphLuminous nodes connected by thin edges show the operating record, product workflows, live governance, proof, and emerging UGC attribution.ISWCWriter APublisher BWorkSplitGraf StudioMaster ownerRecordingRemixRadio editTerritoryAI consentSigned proofAudit ledgerSplitGraf IntegrityUGC attribution
click a node
live todayemerging

The answer

One operating record.
Verified, connected, never forked.

SplitGraf holds a single record of who owns what, how it connects, and what can be proved. Because it is one record, it is exposed as the two workflows that meet these problems where they live.

Creation side

SplitGraf Studio

Collaboration, splits, derivatives, and lineage — resolved cleanly before they ever reach a catalog.

Capital side

SplitGraf Integrity

Diligence, territorial ownership, verification, and consent governance — for the teams that underwrite catalogs.

One record underneath. Two products on top.

What runs today

The record is provable now.

Today it resolves splits, models territorial ownership, catches incomplete scope, governs AI consent, and produces verification anyone can check — without seeing private evidence.

  • Public verification, private evidence stays private
  • Manifest hash and signed ledger checkpoint
  • Independently checkable, by anyone, right now
SplitGraf trust verificationTidal Trace

Subject musical_work · publishing · active

Manifest checkvalid
Ledger checkpointvalid
Trust stateproof-backed
manifest15cf8ae7…677002b

Why it compounds

Everything downstream depends on the record being right.

Settlement, diligence, valuation — every decision in music rights inherits whatever the record says. When the record can't be trusted, the error compounds at every step and arrives, eventually, as someone's loss. SplitGraf makes the record provable, and starts where it breaks first. That is the whole company.