# songseal-ai-disclosure-v1

**Status:** `PUBLISHED` · **Frozen:** 2026-08-16

> ## THIS DOCUMENT IS IMMUTABLE
>
> Sealed records commit to the string `songseal-ai-disclosure-v1` inside an
> anchored digest. A record says *"my disclosure is written in this vocabulary"*
> and can say nothing more — so if this document changes, every record that
> cited it now means something it did not mean when it was sealed, and no reader
> can tell.
>
> **Corrections are a NEW VERSION, never an edit.** `…-v2` is a different string
> and old records go on pointing at this one. A checksum of this file is
> recorded in `CHECKSUMS.json` beside it and enforced by the build gate, so an
> edit fails loudly rather than silently rewriting the past.

---

## 1. What a disclosure is, here

A statement by the artist about **how much AI was involved in making a thing**.
Not a detection result, not our opinion, and not a judgement about the work.

```json
"aiDisclosure": {
  "audio":       { "value": "none",     "scope": "version" },
  "composition": { "value": "some",     "scope": "version" },
  "artwork":     { "value": "material", "scope": "work"    }
}
```

Every entry has a `value` and a `scope`. Both are required. An asset with no
disclosure is **omitted entirely** — there is no "unknown" value, because a
record must not be able to imply an answer nobody gave.

## 2. `value` — the vocabulary

Four values, ordered, from MOAD's `AiUsageEnum`:

```text
none      no AI involvement in this asset
some      AI used as a tool, incidental to the result
material  AI involvement a listener or viewer would consider significant
all       this asset is fully AI-generated
```

**These are the artist's judgement, not a measurement.** The boundary between
`some` and `material` is not sharply defined and this document does not pretend
otherwise. It is drawn where the artist draws it, which is the only place it can
honestly be drawn by a disclosure-based system.

**`none` is a real answer and must be given, not assumed.** A record where the
disclosure is absent and a record where the artist said `none` are different
records. The seal path refuses to default it.

## 3. `scope` — what the value is about

```text
version   this sealed version specifically (this rung, these bytes)
work      the song as a whole, across every version of it
```

This exists because the two are genuinely different claims and were being
published as though they were the same. `audio` and `composition` are frozen per
version; `artwork` is a property of the song. Three sibling keys with no scope
read as one grain, and `artwork: some` next to `audio: none` would be taken as a
claim about this recording's artwork when it is a claim about the song's.

A reader must never have to know our schema to read our record.

## 4. `key` — the assets

```text
audio        the recording: performance, production, post-production
composition  the song itself: melody, harmony, lyrics, structure
artwork      the cover image
```

**This axis is ours, and it is not the industry's.** Stated plainly because the
alternative is a reader assuming otherwise — see §5.

New keys may be added in a later version. A key is never redefined or removed,
for the same reason this document is immutable.

## 5. How this maps to the standards that matter — and where it does not

**We are not a standards body.** This section is our reading of other people's
work, it is dated, and their documents are canonical over ours. Where we are
uncertain we say so rather than guessing, because a confident wrong mapping is
worse for a reader than an acknowledged gap.

Industry facts below are carried from `MOAD_BUILD_TRUTH/ai_disclosure_00_CANON.MD`,
verified first-hand against live sources in June 2026. **They will age.** Re-verify
before relying on them; do not edit them here (§0 — this file is frozen).

```text
DDEX          The disclosure standard MOAD binds to. Its asset axis is
              vocals / lyrics / instruments / post-production.

              OUR GAP, BOTH WAYS:
                · our `audio` collapses DDEX's vocals + instruments +
                  post-production into one value. A DDEX consumer reading our
                  record gets LESS grain than DDEX allows, and cannot recover it.
                · our `composition` overlaps DDEX's `lyrics` but is wider — it
                  covers melody, harmony and structure too.
                · our `artwork` has NO DDEX equivalent on the recording axis.
                  Cover art is not a DDEX recording asset.

              A faithful mapping is therefore LOSSY IN BOTH DIRECTIONS and this
              document does not claim one. Producing a verified field-level
              mapping against the actual DDEX schema is unfinished work.

APPLE         Transparency Tags, phasing in from March 2026, for AI use in a
              MATERIAL PORTION of a recording or lyrics. That threshold aligns
              with our `material` and `all`, on `audio` and `composition`. We
              have NOT verified their exact threshold definition against ours;
              treat the alignment as approximate.

C2PA          Content Credentials. A DIFFERENT KIND OF THING — cryptographic
              provenance assertions attached to a file, not an artist's summary
              judgement. It is complementary to this vocabulary rather than a
              target to map onto: C2PA can say which tool touched which bytes;
              this says how much AI the artist considers to be in the work.
              A record could honestly carry both. Neither derives the other.

DEEZER,       DETECTION-based, not disclosure-based. They scan and decide;
QOBUZ         this vocabulary is what the artist declares. Their penalties
              target FULLY AI-generated tracks (our `all`); work that uses AI
              tools remains available. Nothing here maps to their tags, and a
              disclosure of `all` is not an admission of anything — it is a
              true statement that some platforms treat differently.
```

## 6. What this vocabulary deliberately does NOT do

```text
NO PER-PERSON TRACKING     AI is a tool, never a credited contributor. There is
                           no field recording which human used which tool. MOAD
                           scrapped this deliberately (canon DSC-1) as a
                           misframing: the industry tracks AI by ASSET, and
                           per-person tracking turns a disclosure into an audit.

NO ITEMIZATION             production assistance raises the asset's value; it
                           does not trigger a tool-by-tool inventory. Not even
                           the strictest enforcer demands one.

NO INFERENCE               we never derive a disclosure from anything —
                           not from file metadata, not from a detector, not
                           from a previous version. It is a statement or it is
                           absent.

NO JUDGEMENT               `all` is not a confession and `none` is not a boast.
                           This vocabulary describes; it does not rank.
```

## 7. The point of all this

An artist who wrote something alone, at 3am, on a phone, is increasingly likely
to be told by a confidently-wrong detector that a machine made it. The burden of
proof is landing on the people least equipped to carry it.

A dated, anchored, artist-made disclosure is the other half of that argument.
The ladder shows the work took time and had versions; the disclosure says, in
the artist's own words and frozen at the moment they said it, what part a machine
played. **Honest assistance, disclosed, is a first-class outcome — not an
asterisk.**

That is also why this vocabulary must be able to stop being ours. Standards for
this are arriving from outside and will keep arriving. A record that names its
scheme can be mapped onto whatever wins; a record that does not can only be
guessed at.
