GateTrue

What each generator documents about marking its output

Two marking statements published outside a price list

Two entries here are read from something other than a pricing page: a system card and a compliance guide. One names a standard; the other tells publishers to keep an unnamed layer. As of 2026-09-22.

What has to be named before this cell can be filledA scheme a reader can look up, a key a reader can check, or a signal whose behaviour is described. An instruction to preserve an unnamed layer implies one exists and gives nobody anything to do with a file in hand, so the cell stays empty and the sentence is recorded separately.A mentionMetadata raisedin passing,with nothingnamed.Does not fillthe cellAn instructionKeep whateverthe toolwrites, andbewarere-encoding.Still nothing toinspectA named schemeA standard areader can lookup and,sometimes,check.Fills the cellA named readerA platform ortool the file'sholder can usethemselves.
Fig. 1 Both entries were read outside a pricing page. Only one of them clears the bar, so the genre is not the thing that matters.
The two entries on one question at a time, in each vendor's own terms. Recorded 2026-09-22.
On this questionSoraSceneMixer
Document readA system cardA compliance guide
File contentsC2PA metadata on all assetsMetadata mentioned, nothing named
Visible markVisible and moving, on downloadsApplied at compositing, by default
ControlNothing publishedA switch in settings
Who can check a fileThe vendor, internallyNobody, nothing published

Inclusion rule. One row per question on which these two entries can be compared from their own published pages. Questions neither vendor addresses are left out rather than filled with a dash. Order. Fixed order: the mechanism first, then who holds it, then what it leaves behind.

Where each value above was read, and what the register records in the machine-readable marking column. Recorded 2026-09-22.
GeneratorMachine-readable markingDocument read
SceneMixerNot documentedcompliance guide
SoraC2PA on every asset, standard namedSora 2 system card

Inclusion rule. The two entries on this page, with the value each one's own pages support in the column they diverge on. Order. Alphabetical by generator name.

1Leaving the pricing page does not guarantee a filled cell

Across the register the vendors who fill the file-contents column were read from references and cards rather than grids, which makes it tempting to treat the genre as the thing that matters. These two entries show the limit of that. Both were read outside a price list, and only one names anything.

The card names C2PA metadata on all assets and describes the mark on the frame as visible and moving. The guide tells publishers to keep whatever content credentials or generation metadata the tool writes, and warns that re-encoding can strip them, without naming a scheme or listing a field.

2What the register demands before filling the cell

A scheme named so it can be looked up, a key named so it can be checked, or a signal whose behaviour is described. An instruction to preserve an unnamed layer is none of those, however clearly it implies one exists, so that cell records not documented and the sentence is kept as a fact of its own.

Lowering the bar would be easy and would ruin the column. Several pricing pages mention metadata in passing, in the way pages mention things. If a passing mention filled the cell, the column would stop distinguishing a vendor that publishes a specification from one that publishes a gesture.

3Each has something the other lacks

The guide gives a switch and a reason for using it, which is a complete answer in the control column, and the card publishes nothing there at all. The card names a standard, which is a complete answer in the file column, and the guide publishes only an implication.

Neither hands a recipient a way to check a file. On the guide-read row nothing is named; on the card-read row the detection tooling is described as internal to the vendor. Two entries outside the pricing-page genre, and a publisher holding either file is in the same position.

4Sources

  • Detection
    Also in that list: internal detection tools to help assess whether a certain video or audio was created by the vendor's productsheld inside the vendorOpenAI, Sora 2 system card / recorded 2026-09-22
  • Metadata
    The guide tells publishers to keep whatever content credentials or generation metadata the tool writes, and warns that re-encoding can strip themdescribed but not enumeratedSceneMixer, compliance guide / recorded 2026-09-12

Both values above are read from the vendor pages linked in the rows: openai.com and scenemixer.com, on 2026-09-22. Each entry has its own page, Sora and SceneMixer, and the rule for the column they diverge on is on the machine-readable marking column page. Other pairs: named, or avoided, two routes, one model.