Skip to content

    Marketplace · From the signal to the receipt

    The Buyer Journey

    Find a creative project, agree on what you are buying, and carry its record into the accession ledger.

    Browse and document now. Paid checkout is not yet available.

    This walkthrough explains the complete intended journey without claiming a live sale, automatic ticket issuance, or a transfer of rights.

    Worked case study · An eight-track studio package

    An illustrative continuation of the Textbook’s six-rule studio example—not evidence of a real posting, payment, client result, or issued accession. No real amount, buyer, or transaction is assumed.

    Read the six-rule case study

    01 · Studio or rights holder

    Post the project

    Submit the finished work for review with its title, description, deliverables, credits, and rights. An administrator approves it before it appears in the public catalog and Marketplace; posting is not instant self-publishing.

    In the case study: Illustrative brief: a studio submits an eight-track session package. Rights and deliverables are reviewed before listing; no project has been posted by this walkthrough.

    Submit a work for review

    02 · Buyer

    Find the right work

    Browse the Marketplace’s creator-listed works and search by title or tag. Review the description and distinguish buying a deliverable from licensing rights or commissioning new work. Confirm availability and terms with the rights holder before agreeing.

    In the case study: The buyer searches for the session title, checks the offered files, and agrees which uses are permitted. A visible listing is not proof that every right is cleared.

    Browse the Marketplace

    03 · Buyer + seller · payment not enabled

    Agree, then pay

    Agree the scope, currency, price, due date, delivery terms, and refund terms first. A project purchase and an accession-ticket fee are separate charges unless explicitly bundled. Metanated currently has no checkout, ticket price, or automatic payouts.

    In the case study: Payment stops here in today’s app. No charge, purchase confirmation, or paid accession number is generated. When checkout is enabled, retain the confirmed payment receipt—not merely an invoice or a success screen.

    Review current offerings

    04 · Creator or steward

    Credit and seal the files

    Apply the six rules: name it once, credit completely, attach identifiers, state the rights, hash the payload, and re-read before release. Use The Seal to document the deliverable and retain its metadata and content hash.

    In the case study: In this example, inconsistent filenames and incomplete credits are corrected before handoff. These are teaching outcomes, not verified results from a completed sale. A seal does not transfer copyright or prove payment.

    Open The Seal

    05 · Signed-in record owner

    Document the accession

    Draft the catalog record with the Accessionist, then file the project in the Ticket Ledger: title, medium, project date, signal, accession number, contributors, rights statement, content hash, and seal date. The number is entered by you; saving does not issue a paid number.

    In the case study: Save the project as a private draft. Use the identifier assigned through your accession process consistently across the file and ticket. Do not invent a receipt or enter card details in notes. Published ticket notes are public.

    Open the Ticket Ledger

    06 · Seller → buyer

    Deliver the record

    Review the record before publishing. Share the accession number and the agreed deliverables with the buyer. Keep the payment receipt separately and distinguish unpaid, invoiced, and received amounts. The ledger documents a project; it is not a payment receipt.

    In the case study: The intended end state is a delivered project, a verified payment receipt, and a matching accession record. Today, the documentation can be completed manually, but the paid journey remains blocked at checkout.

    Follow the daily close
    Draft the record with the Accessionist

    What the buyer keeps

    • The agreed scope and rights terms.
    • The delivered files and their metadata record.
    • The accession number matching the ledger record.
    • A separate verified receipt, only after payment actually occurs.

    The right brain makes the traffic light and the left brain makes the ticket.