Skip to content

    Hub one of three · Read to learn

    The Living Textbook

    Living means dated. Every chapter, article, and listing carries the day it was written and can be revised in place — nothing here claims to be finished.

    Core curriculum

    Six Standing Lessons

    Lesson 01

    Read Every Contract

    The deal is the document. Learn the seven clauses that decide your life: term, territory, recoupment, splits, reversion, audit rights, and assignment. If you can't define them, you can't sign them.

    Practice: Mark up one old contract this week. Highlight what you'd renegotiate now.

    Lesson 02

    Register Before You Release

    Copyright, ISWC, ISRC, trademark, IPI. Registration is not paperwork — it is proof of existence. The unregistered work is the un-defended work.

    Practice: Catalog every finished piece with metadata before it touches a platform.

    Lesson 03

    Own the Master, Keep the Pub

    Ownership compounds. A streaming check fades; a master earns for a century. Trade sparingly, license generously, sell almost never.

    Practice: Audit who owns each side of every release: master, publishing, neighboring rights.

    Lesson 04

    Build the Table, Then Eat

    Lawyers, CPAs, business managers, mentors — assembled before the money, not after the lawsuit. The team is the moat.

    Practice: Name the five professionals on speed-dial before your next big release.

    Lesson 05

    Distribute Wealth, Not Just Songs

    Hire from the neighborhood. Mentor the next class. Royalty splits to collaborators are how a generation, not a person, gets free.

    Practice: Reserve a percentage of every project for a younger creator credited and paid.

    Lesson 06

    Inherit Forward

    Your catalog is an estate. Wills, trusts, successor publishers, beneficiary letters. Solvency only becomes legacy when it survives you.

    Practice: Draft a one-page legacy plan: who receives what, who manages it, how to find it.

    The practice

    Six Rules of Clean Metadata

    A file is only as citable as its metadata. These six rules run at the moment of creation — not patched after a dispute. The Seal is the tool that stamps them into the file.

    Name It Once

    A file gets one canonical title at intake, and every copy, export, and reference uses it.

    No final_final_v3. If a version changes, the accession record notes the revision — the filename stays stable.

    Credit Completely

    Every contributor is named with a role before release — writers, performers, producers, engineers, photographers.

    Splits and identifiers (IPI/CAE, ISNI) are captured at session close, not reconstructed later from memory.

    Attach Identifiers

    Works carry their ISWC, recordings their ISRC, releases their UPC — embedded or filed alongside the file.

    An unidentified recording is unpayable. Identifiers go in before distribution, never after.

    State the Rights

    Every file carries a rights line — owner, year, and terms of use — in writing, inside the file.

    A missing rights line reads as a free license to anyone who finds the file out of context.

    Hash the Payload

    The file's contents are hashed (SHA-256) at seal time and the hash is filed with the accession record.

    Change one byte and the hash no longer matches — that is what makes the record evidence rather than assertion.

    Re-Read Before Release

    A sealed file is parsed again after writing to prove the metadata survived intact.

    If the sealed file does not re-parse cleanly, nothing ships. The seal validates itself or it does not happen.

    The method

    Five-Step Audit Pass

    Run this pass on every intake batch before anything is published. A file that fails the audit does not leave the room.

    1. 1

      Scan the intake folder

      List files with missing titles, generic camera names, or no credited creator. These are the hygiene failures.

    2. 2

      Match each file to an accession

      Every kept file gets an accession number — MET-YYYY-CLS-NNNN. Files without one are unfiled work, not catalog.

    3. 3

      Complete the credit block

      Creator, contributors, roles, splits, identifiers — filled from session records, confirmed by the people named.

    4. 4

      Seal the file

      Run it through The Seal: metadata embedded, hashes computed, manifest filed, file re-parsed to prove it took.

    5. 5

      Verify on a schedule

      Quarterly, re-hash a sample of sealed files against the ledger. A mismatch means the file changed — find out why.

    The tool

    The Seal

    The Seal embeds accession metadata, a rights line, and a SHA-256 content hash directly into the file — XMP for JPEG and PNG, ID3v2.3 for MP3, a signed manifest for every other format. The media payload is never re-rendered. Change one byte after sealing and the hash no longer matches.

    What it stamps

    • · The media payload is never re-rendered — only header/metadata space is rewritten.
    • · The SHA-256 is taken from the sealed file. Change one byte and the hash no longer matches.
    • · The accession number travels with the file wherever it is shared.
    • · Formats without a writer yet are sealed by manifest — the JSON is the proof of record.

    Pipeline steps

    1. 1Ingestion & parsing — read the raw binary structure and detect the format.
    2. 2Schema mapping — map accession, creator, rights, and terms to XMP/IPTC/ID3 fields.
    3. 3Binary modification — write metadata into the reserved header space; media payload untouched.
    4. 4Validation — re-parse the output and confirm the structure and the embedded fields.
    5. 5Export — serve the tagged file plus its manifest JSON.

    Worked Example

    Room 7367 — A Studio Pass Through the Six Rules and the Seal

    This is the house pass documented in our own room at Node Zero, 7367 Chef Menteur Hwy: one eight-song session taken from an unlabeled drive to a sealed, citable set of deliverables. It is published as a teaching example of the standard we hold ourselves to.

    Outside-studio case studies are published here only after the studio reviews and verifies its own record. No client name, revenue figure, or performance result appears on this page until it has been confirmed in writing by the studio it belongs to.
    RuleBefore the passAfter the pass
    Name it onceEight mixes across two drives as FINAL_v3_REAL.wav, mix_new_new.wav, and untitled_4.wav, with no way to tell which one shipped.One naming convention applied at the source: project, track number, title, version, date. Every duplicate resolved to a single authoritative file.
    Credit completelyCredits held in a group chat and two people's memories. Two contributors were absent from every file.A credit list captured at close of session — performer, writer, engineer, producer — attached to each file before it left the room.
    Attach identifiersNo ISRC, no accession number, no internal project ID. Nothing linked the mix to the stems or the session log.An accession number issued per deliverable and written into the file, linking mix, stems, session log, and release record to one another.
    State the rightsTwo sampled elements and one guest verse with no written clearance on file.A rights line written into each file plus clearances held with the work. The two uncleared elements were flagged and held back from release rather than discovered later.
    Hash the payloadNo way to prove a file had not been altered after the handoff.A SHA-256 content hash generated at seal time. Any byte changed after sealing breaks the hash, which makes tampering visible instead of silent.
    Re-read before releaseFiles went out unread; metadata was assumed rather than verified.Every sealed file re-parsed before release. Three files failed the read on the first pass and were corrected before they shipped.

    Before

    Unlabeled drives, credits from memory, no identifiers, no rights line, no hash, nothing verified.

    After

    One named set, complete credits, an accession number per deliverable, a stated rights line, a content hash, and a verified read.

    What changed in practice

    Two missing contributors were restored to the credit list, two uncleared elements were caught before release, and three metadata failures were corrected at the read rather than after distribution.

    The pass, step by step

    1. 1Inventory — every candidate file gathered to one place before anything is renamed.
    2. 2Resolve duplicates — one authoritative version chosen per deliverable, the rest marked as alternates.
    3. 3Capture credits and rights while the room is still assembled, not afterward.
    4. 4Issue the accession number and write the record.
    5. 5Seal — metadata and rights written into the file, hash generated.
    6. 6Re-read every sealed file and correct anything that fails the parse.

    A teaching example drawn from our own room. Results describe what the pass corrected in that session; they are not a projection, a guarantee, or a claim about any other studio's outcomes.

    Added chapters

    Units in Progress

    Loading chapters…

    We are the first generation with the tools to register, the receipts to prove it, and the bandwidth to teach the next. Prosperity is not a vibe — it is a curriculum.

    Learn it. Live it. Leave it.

    Notices

    • · This is working practice, not legal, tax, accounting, or investment advice.
    • · Prices shown are planning ranges or quoted per engagement; nothing here is an offer of securities.
    • · Listings are inquiries — a purchase exists only under a signed agreement.
    • · Chapters and articles are revised in place; a dated entry reflects the day it was written.
    • · Metadata hygiene is a documentation practice, not legal protection by itself. Embedded metadata and hashes support ownership claims and chain of custody; they do not register a copyright, guarantee payment, or replace agreements between contributors. Registration with the appropriate rights organizations remains a separate step.