The Metanated Textbook

Erasure by Code

Every creative work carries a record of who made it — who wrote the part, who played the session, who designed the piece, who owns what share. That record isn't automatic. It has to be captured, and today it almost never is, not because people don't care, but because the tools people actually use were never built to do it. A songwriter finishes a track in a DAW that has no place for splits. A designer ships a file with no record of who contributed what. The credit exists for a moment, in memory, and then it doesn't.

This is erasure by code — not deliberate theft, but a structural gap in the tools themselves. The record disappears not because anyone erased it, but because nothing was built to hold it in the first place. Metanated exists to close that gap: to capture the record at the moment of creation, inside the tools creators already use, before it has the chance to disappear.

Civic Infrastructure

The Vault is not a product creators are asked to adopt — it's infrastructure they use without switching anything. In the same way a city doesn't ask residents to opt into roads or water lines, a well-built cultural registry shouldn't ask creators to opt into having their work properly recorded. It should simply be there, running underneath the work they're already doing.

This is why the go-to-market strategy does not depend on Node Zero, the physical studio in New Orleans. The studio is where the idea was born, but it is not the delivery mechanism — the delivery mechanism is the capture layer, which can onboard an institution without requiring anyone to walk through Node Zero's doors. Infrastructure has to scale independent of any one room.

Why Institutions Need a Registry

The clearest proof point is the university pilot: a single department, one semester, one vendor contract. Universities generate a constant stream of student and faculty creative work — but that work's ownership and credit record is usually reconstructed after the fact, if it's reconstructed at all. A department that adopts the Vault isn't buying a tool. It's buying a system that already exists at the moment the work is made, so nothing has to be rebuilt later.

The Underlying Thesis

Everyone's looking for a miracle — make one. The Vault does not propose that creators change how they work. It proposes that the record of that work stop disappearing. The people who spent their lives in record stores, reading credits, listening for who played what, already understood instinctively that the credit is the story. This textbook formalizes that instinct into a system: something a department, an institution, or a creator can rely on without having to trust that someone remembered to write it down.

Financial Resilience

A creator who doesn't know what they're owed can't collect it. Splits that were never signed, credits that were never recorded, royalties that were never tracked back to a source — all of it quietly erodes a creator's footing over time, not through any single bad actor, but through the accumulated cost of records that were never kept. Financial resilience here is not about earning more. It's about not losing what's already been earned to a gap in the paperwork.

IP Retention

Own master, keep pub. The Vault exists so a creator has the documentation to make that possible — proof of authorship, proof of contribution, a timestamped record of who made what and when. Retention isn't a negotiating stance; it's a byproduct of having the evidence in hand when the negotiation happens.

Succession

Creative work outlives the moment it was made, and often outlives the person who made it. Without a record, a body of work becomes harder to pass on — heirs and collaborators are left reconstructing ownership from memory, contracts that were never signed, or files scattered across formats. A properly accessioned catalog is built to survive its creator: what's passed on is a clear holding, not a dispute.

Legacy Accounts

An artist's catalog is not a single transaction — it's an accumulating body of holdings that should still generate value and clarity years after any individual piece was made. A legacy account treats a creator's full body of work as a standing asset, not a series of disconnected releases each requiring its own reconstruction of who owns what.

Cultural Solvency

Just as a business can be technically operating while quietly going broke, a creative community can keep producing work while quietly losing its own record of itself. Cultural solvency is the same standard applied collectively: a community whose creative output is properly documented is one that can account for its own history, rather than losing it to the same erasure-by-code that affects any single catalog.

Identity

Before a work can be credited, the person or group being credited has to be verifiable. Identity is the baseline: a confirmed record of who a contributor is, so that every other piece — rights, royalties, contracts — attaches to something real rather than a name that could belong to anyone.

Rights

What a creator owns, and what they've licensed away, is often only clear at the moment a deal is signed — and forgotten soon after. The Rights section keeps that clarity standing: which works are wholly owned, which are shared, and under what terms, so ownership doesn't have to be re-litigated every time it matters.

Royalties

A royalty stream disconnected from its source is just a number with no explanation. The Creator Record ties royalties back to the specific holding that generated them, so a creator can see not just what they're being paid, but why — which work, which use, which split.

Contracts

Contracts are usually stored the way they were signed: scattered, in whatever format the other party used, disconnected from the work they govern. The Creator Record catalogs contracts alongside the holdings they apply to, so the terms of a deal stay attached to the work.

Catalog

The Catalog is the accumulated sum of everything above — every accessioned work a creator has made, held together as a single growing body rather than a series of disconnected files. It's the legacy account made visible.

Intake

Work enters the Vault the same way it's made — as raw Contents, unverified and unsealed. Intake is the front door: the point where a session, a file, a contract, or a credit first gets logged, before anything about it has been confirmed. Nothing is trusted yet; it's simply captured, so nothing gets lost between the moment of creation and the moment of formal recordkeeping.

Verification

Contents don't become part of the record just because they were submitted. Verification is where a claim — this person contributed this, this is the correct split, this is the final version — gets checked against whatever evidence exists: session logs, timestamps, signed splits, prior holdings. This is what separates the Vault from a file archive: an archive stores what it's given, the Vault confirms it first.

Accession

Once verified, Contents are formally accessioned — brought into the Registry as a permanent Holding, tied to the Catalog of whoever created them. Accession is the moment a piece of work stops being a submission and becomes part of the permanent record: sealed, dated, and no longer dependent on anyone's memory to prove it exists.

Activation

An accessioned Holding isn't necessarily inert. Activation is what makes a Holding usable — licensable, payable, discoverable — within the systems that depend on the record: royalty tracking, institutional licensing, catalog management. A Holding can sit accessioned and dormant, or it can be activated for whatever purpose the creator or institution needs.

Museum-Grade Recordkeeping

The standard the Vault holds itself to is the standard a museum holds its own collection to: every Holding accounted for, its provenance documented, nothing accepted into the Registry without verification, nothing altered without a record of the change. This is why “Museum” is a defined term here, not a loose metaphor.

Why One Ledger

A creator working across multiple spaces, sessions, or collaborators can easily end up with a scattered record — one project tracked one way, another tracked differently, with no single place that reconciles what's owed, what's been accessioned, and what's been activated. Regardless of where a piece of work was physically made, it resolves to one Ledger, tied to the Registry, so a creator's financial and creative history stays unified.

DIMS and the Production Layer

DIMS is the layer that connects physical production — what happens at Node Zero, or anywhere else work is made — to the Vault's recordkeeping. It ensures a session isn't just recorded artistically, but logged in a way that can eventually be verified, accessioned, and reflected in the Ledger.

Capture

Capture is Intake by another name — the point where Contents first enter the system, unverified. Whatever is created, wherever it's created, has to be captured before anything else can happen to it. A piece of work that is never captured never enters the pipeline at all; it stays outside the record entirely.

Verify

Nothing captured is trusted automatically. Verification checks a claim about the Contents — authorship, contribution, split, version — against available evidence before it's allowed to proceed further.

Accession

Verified Contents become a permanent Holding, sealed into the Registry as part of the creator's Catalog. This is the point where the work stops being provisional and becomes part of the durable record.

Activate

An accessioned Holding is made usable — for licensing, royalty tracking, or whatever purpose the creator or institution requires — through Activation.

Log the Session

Every session — at Node Zero or anywhere else — should be logged as it happens: who was there, what was made, what version it is. A session that isn't logged can still be captured later, but only imperfectly, from memory.

Sign the Splits

A split that exists only as a conversation isn't a split — it's an assumption. Getting splits signed at the time they're agreed to is what turns a verbal understanding into something that can survive Verification. This is the single most common point where creative work loses its financial clarity: not because people disagree, but because no one wrote it down.

Label Files

An unlabeled file is a file that depends on someone remembering what it is. Clear, consistent labeling — of sessions, versions, contributors — is what makes Intake usable rather than a pile of Contents no one can identify later.

Clear Holdings

A Holding isn't finished just because it's accessioned. Clearing a Holding means resolving whatever is still outstanding against it — a pending split, an unconfirmed contributor, a licensing question — so it can be fully activated rather than sitting accessioned but incomplete.

Turn In Receipts

Every expense, session cost, or transaction connected to a piece of work is part of its financial record, the same way a split is. Turning in receipts as they're incurred keeps the financial side of the Ledger as accurate as the creative side of the Catalog.

Read Every Contract

No system of recordkeeping protects a creator from a contract they signed without understanding. Reading every contract — fully, before signing, regardless of pressure to move quickly — is the first discipline, because no Vault entry can undo a right that was already signed away.

Register Before Release

A work released before it's registered is a work whose ownership is provable only in retrospect, often after a dispute has already started. Registering first — accessioning the work, documenting the splits, confirming the rights — means the record exists before the work is public.

Own Master, Keep Pub

Retaining ownership of the master recording while keeping the publishing rights is the default posture the Vault is built to support. It's not a rule for every deal, but the baseline a creator should have to be talked out of, rather than the exception they have to fight for.

Build Table, Then Eat

Prosperity here isn't earn-then-invest; it's build-then-benefit. The infrastructure — registered rights, signed splits, a documented catalog — is the table. Trying to eat before that table exists means operating without the record that protects the value being generated.

Distribute Wealth

A catalog that generates income should generate it in a way that reaches everyone with a documented claim to it — collaborators, co-writers, contributors whose splits were signed and accessioned. Distribution isn't charity; it's what a properly recorded split obligates once income exists to divide.

Inherit Forward

A catalog built on the succession principle isn't just protected from loss — it's built to be passed on. Inheriting forward means treating today's accessioned work as an asset for whoever comes next, not just an asset for right now.

Studio Infrastructure

Node Zero exists in New Orleans as a physical studio operated by The Box Studios USA — where the underlying production work originated, and where DIMS connects that physical work to the Vault's recordkeeping. The studio is not the delivery mechanism for onboarding institutions, but it remains the origin point: proof that the pipeline works in a real production environment before being extended anywhere else.

New Orleans, as a place with a dense, active creative production culture, is where this system was built and tested — not incidentally, but because the problems the Vault addresses are especially visible in a city where so much creative work is made, performed, and recorded every day.

University Workforce Pipelines

The university pilot — one department, one semester, a vendor contract rather than a grant — is the established starting point for institutional adoption. It's a single provable case rather than a broad rollout: proof that a department's creative and intellectual output can be properly registered without requiring new staff or infrastructure.

Museum Governance

The museum-grade recordkeeping standard is what “Museum” means as a defined term: accessioned Holdings, verified provenance, nothing altered without a record of the change. Any institution adopting the Vault inherits that same governance standard for its own holdings, applied to creative and intellectual work rather than physical artifacts.

What is established

The only revenue mechanism established so far is the one built into the university pilot itself: a single-department vendor contract, priced and structured as a service agreement rather than a grant-funded program. Beyond that specific case, no broader revenue model — creator subscriptions, institutional licensing at scale, pipeline fees, placement revenue, or cultural analytics — has been defined.

Founders

The provenance chain described throughout this textbook — Capture, Verify, Accession, Activate — is what a founder or institution adopting the Vault actually receives: a documented, defensible record of ownership and contribution that didn't exist before.

Creators

Creators gain a Catalog that survives them, splits that are signed and honored, and a documented claim to whatever their work generates — the “Live in the Black” standard applied to an individual creative career.

Louisiana

The third leg — a defined outcome for Louisiana as a whole — isn't established beyond the university pilot itself, and is left open for future definition.