Sora names the standard and keeps the reader
Sora's system card names C2PA metadata on all assets, providing verifiable origin through an industry standard, and describes its detection tools as internal to the vendor. As of 2026-09-22.
| The reading | What it holds |
|---|---|
| The recorded value | C2PA on every asset, standard named |
| The vendor's own words | C2PA metadata on all assets, with internal detection tools described separately. |
| How the reading was taken | Read from a system card that names the standard, in the same list as the visible mark and the detection tooling. |
Inclusion rule. One row for the value, one for the sentence or absence behind it, one for the method. Nothing here is drawn from output, support replies or coverage by anyone else. Order. Fixed order: the value, then its evidence, then the method.
1Naming a standard is what fills this column
A cell here needs something a reader can act on: a scheme named so it can be looked up, a metadata key named so it can be checked, or a signal whose behaviour is described. C2PA metadata on all assets clears that bar on the first count, and the phrase verifiable origin through an industry standard is the vendor's own framing of why.
Twelve generators here record not documented in this column, so a filled cell is worth reading closely rather than filing as a tick. What this one supports is that the file is supposed to carry a manifest in a published format, which is a claim with a specification behind it.
2Internal detection is a separate row for a reason
The card also describes internal detection tools to help assess whether a certain video or audio was created by the vendor's products. Internal is doing the work. The file may carry a signal, and the party who can interrogate that signal is the company that made it, not the publisher holding the file.
That is the difference between marking and detection, and it is why the register keeps them as separate rows instead of merging them into a provenance column. Two other generators here name a public route by which anybody can check a file; this one names a standard and keeps the reading capability.
3What a manifest does not survive, and what is unsaid about it
A C2PA manifest is attached to the container around the picture rather than embedded in the picture, which is what makes it readable and what makes it fragile. An ordinary re-encode through an editor is the operation that separates the two, and nothing on this card addresses that.
One other generator in this register publishes exactly that caveat about its own credentials. Its absence here is not evidence that the manifest is robust; it is the ordinary state of this subject, where the fragile layer is named and its fragility is left to the reader.
4Sources
- Machine-readable markingIn the same list: C2PA metadata on all assets, providing verifiable origin through an industry standardstandard named
- DetectionAlso in that list: internal detection tools to help assess whether a certain video or audio was created by the vendor's productsheld inside the vendor
The value above is read from openai.com, the vendor's Sora 2 system card, on 2026-09-22. The whole row for this generator is on its own page, and the rule for what this column may hold is on the machine-readable marking column page. Neighbouring readings: Veo, file contents, Amazon Nova Reel, file contents.