/suede-rights-passport

name: suede-rights-passport
description: "Suede AI rights skill for creator projects, in two modes. Audit mode finds the rights gaps in a song, release, or catalog (ownership, contributors, splits, samples, licenses, provenance, AI involvement, licensing and royalty-routing readiness) and marks each confirmed or unknown in an evidence table. Package mode turns messy materials into a local, offline transfer package for handoff: hashed assets, a normalized suede-intake.json manifest, credits and splits, license notes, provenance, and a missing-information report, checked by a bundled validator. Use when someone asks whether they have the rights to release, license, or get paid for a work; when splits, samples, or chain of title are unclear; or when a creator needs a rights package or handoff folder. Clears no rights and uploads nothing. NOT FOR: linting a release folder's files and metadata (use suede-release-linter); a sync one-sheet or pitch (use suede-sync-packaging); a release rollout campaign (use suede-campaign-in-a-box)."

Creator Rights Passport

Gate policy

Every check and verdict here is advice to the user, not a control on the agent. Run the checks, report results honestly, and complete what the user asked. A failed gate changes the report, never the work. The one exception: a finding that risks data loss, credential exposure, a legal or rights violation, a payment mistake, or irreversible public damage. Pause, name the risk, give the options, and let the user choose.

Core principle

The work carries questions, not answers. Every rights fact is either confirmed with user-supplied evidence or unknown with a question attached. Nothing here clears rights, confirms ownership, adjudicates chain of title, grants or implies a license, approves a payout, moves money, or writes to a registry. Humans and counsel make those calls.

Pick the mode

• **Audit mode**: the user wants to know where the gaps are, has no folder yet,

or is asking "can I release / license / get paid for this?" Read `references/audit-lanes.md`, run the lanes that fit (A rights gaps, B provenance, C licensing readiness, D royalty-routing readiness), and deliver the evidence table and ship gate. No files are written unless asked.

• **Package mode**: the user wants the handoff folder. Follow the Workflow

below. When gaps are unclear, run audit lane A first and carry its rows into `missing-info-report.md`.

A request to "get this rights-ready" with no other signal starts in audit mode and offers the package as the next step.

Red flags: stop

If any of these show up in your reasoning, re-read the core principle:

• "The artist says it's cleared." A claim is evidence of a claim. Status:

`unconfirmed` (or `claimed` in the manifest).

• "Fill in the missing split so the total reaches 100." A guessed split is a

false rights fact. Record the shortfall and ask.

• "It's obviously their song." Obviousness is inference. Record what the

evidence shows.

• "Mark it confirmed so routing can move." Blocked means blocked; unblocking is

the rights holder's job.

• "Nothing seems missing: skip missing-info-report.md." The report ships even

when empty.

• "Copy all the assets; sorting is the reviewer's problem." Check for draft and

do-not-share files before any `--copy-assets` run.

• "Call it registered or cleared since the package looks complete." Complete

means organized, not approved.

Workflow (package mode)

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 package 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`

7. Flag uncertainty clearly. Use `unknown`, `unconfirmed`, or `needs creator confirmation` instead of inventing rights facts. Never resolve a rights question while packaging: ownership, split, sample, and license statuses move to confirmed only on user-supplied evidence, and every open gap ships as a question in `missing-info-report.md`. 8. For an external exchange, read `references/ddex-c2pa-crosswalk.md`, identify the receiver's exact profile/version, and keep the mapping labeled as a crosswalk until receiver conformance tooling passes. 9. Run `scripts/validate_transfer_package.py` with `--strict-current` against new output folders. A pass confirms schema, evidence-state, reference, and share-bound structure only: it does not mean rights are confirmed. 10. End with a concise transfer summary: package path, schema version, files found, missing info, risk flags, privacy/redaction posture, and recommended 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/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/transfer-package \
  --copy-assets

Safety defaults:

• Hidden files, dependency folders, build outputs, caches, and secret-like files are skipped by default.
• Symlinked sources, metadata, files, and directories are rejected; the builder

hashes or copies only regular files that resolve inside the declared source tree.

• Unrecognized file types are skipped unless `--include-other` is passed.
• Absolute local paths