Suede Rights Passport

Overview

Create a Suede-ready transfer package from messy creator materials. The package should make the work easier for Suede to review, optimize, register, route royalties for, license, and expose to agent-readable commerce systems.

Public v1 is offline-first: prepare files and metadata, do not upload to Suede, write to a registry, request private keys, or claim legal clearance.

Workflow

1. Identify the source folder or supplied files.
2. Ask for the output location if it is not obvious.
3. Read references/package-standard.md for the expected transfer package shape.
4. If working on a local folder, run scripts/create_transfer_package.py to inventory files, hash assets, and create starter reports.
5. Read references/creator-questions.md and ask only for missing information that blocks intake quality.
6. Fill or refine the generated package files:

• RIGHTS_PASSPORT.md
• suede-intake.json
• provenance.md
• credits-and-splits.md
• license-notes.md
• optimization-brief.md
• missing-info-report.md

1. Flag uncertainty clearly. Use unknown, unconfirmed, or needs creator confirmation instead of inventing rights facts.
2. End with a concise transfer summary: package path, files found, missing info, risk flags, and recommended Suede next step.

Quick Start

For a local project folder:

python3 /path/to/suede-rights-passport/scripts/create_transfer_package.py \
  /path/to/source-project \
  --output /path/to/suede-transfer-package \
  --metadata /path/to/source-project/metadata.json \
  --project-title "Project Title" \
  --artist "Artist Name"

To copy media into the transfer package as well as inventory it:

python3 /path/to/suede-rights-passport/scripts/create_transfer_package.py \
  /path/to/source-project \
  --output /path/to/suede-transfer-package \
  --copy-assets

Safety defaults:

• Hidden files, dependency folders, build outputs, caches, and secret-like files are skipped by default.
• Unrecognized file types are skipped unless --include-other is passed.
• Absolute local paths are redacted to share-safer names unless --include-absolute-paths is passed.
• Existing generated package files are not overwritten unless --force is passed.
• The output folder cannot be the same folder as the source or live inside it.
• Public-safe JSON, YAML, or key=value text metadata can prefill known project,

rights, contributor, release, wallet, and provenance facts. Do not point metadata at real .env, credential, wallet, or deployment config files. Unknown facts remain flagged. YAML metadata requires PyYAML.

Package Standards

Use the bundled references only as needed:

• references/package-standard.md: required output files, folder structure, risk language, and quality bar.
• references/intake-schema.md: field definitions for suede-intake.json.
• references/optimization-checklist.md: Suede optimization categories and recommendation language.
• references/creator-questions.md: concise questions to resolve missing rights, provenance, and release data.

Use the bundled assets as templates when creating or repairing a package:

• assets/rights-passport.template.md
• assets/suede-intake.template.json
• assets/provenance.template.md
• assets/credits-and-splits.template.md
• assets/license-notes.template.md
• assets/optimization-brief.template.md
• assets/missing-info-report.template.md

Public Safety Rules

• Do not say Suede owns, controls, or has cleared a work unless the user provides explicit proof.
• Do not call the package a legal contract.
• Do not ask for private keys, seed phrases, unreleased account secrets, or full payment credentials.
• Do not include private Suede implementation details, private endpoints, internal provider names, or non-public pricing.
• Do not upload files or call live Suede services unless the user explicitly asks and provides the relevant authenticated workflow.
• Treat generated reports and transfer packages as private drafts until a

creator or operator reviews and redacts them for the intended audience.

• Keep public positioning focused on creator ownership infrastructure, programmable IP, provenance, registry readiness, royalty routing, licensing, and agent commerce.

Completion Checklist

Before reporting that a package is ready:

• Confirm every media/document file is either inventoried or intentionally excluded.
• Confirm every asset in suede-intake.json has a stable relative path and SHA-256 hash when available.
• Mark contributors, splits, licenses, samples, and ownership facts as confirmed or unknown.
• Include a missing-info-report.md section even when nothing is missing.
• Include an optimization-brief.md with concrete next actions for Suede.
• State that final rights clearance requires creator/legal confirmation when any rights fact is uncertain.

Suede Passport Context

Artifacts produced by this skill (RIGHTS_PASSPORT.md, suede-intake.json, provenance.md, credits-and-splits.md, license-notes.md) are the raw material of a Suede Creator Passport entry: the creator's portable, verifiable record of registered IP, declared rights, and signed transfers.

The Passport is a forward-looking surface: stamps for "Rights Passport produced", "IP registered on Base", "Suede Holder", and similar signals will be issued by Suede once the registry stamping API is live. Today this skill emits the artifacts; the Passport will recognize them later. See references/passport-context.md for install-safe context and the repo-root PASSPORT.md for the full public concept.