Sora publishes a mark and no route off it
Sora's system card lists a visible moving watermark on downloads among its provenance tooling, and publishes no plan, setting or parameter that alters it. No route off the mark is recorded. As of 2026-09-22.
| The reading | What it holds |
|---|---|
| The recorded value | Not documented |
| The vendor's own words | The watermark is listed among provenance tooling, with nothing published about changing it. |
| How the reading was taken | Read from a safety document, which describes safeguards rather than options a user selects. |
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.
| Generator | User toggle |
|---|---|
| Amazon Nova Reel | Not documented |
| Sora | Not documented |
| Veo | Not documented |
Inclusion rule. Generators whose pages describe a mark on output and publish no plan, parameter or setting that changes it, so no route off the mark is recorded. Order. Alphabetical by generator name.
1Provenance tooling is written as a list of things you get
The card enumerates safeguards: a visible moving watermark on downloads, C2PA metadata on all assets, and internal detection tools. Nothing in that grammar admits an option. A safeguard is described as something the product does, not as something a customer configures, and this cell records the consequence.
Which is not the same as saying the mark cannot be removed. Three rows in this column record no published route, and on all three the register is making a claim about documents. A vendor may well have an internal flag; what a reader can rely on in a contract is what is written down.
2Detection held inside the vendor is the sharper finding
The card describes internal detection tools to help assess whether a certain video or audio was created by the vendor's products. Internal is the operative word: the signal exists and the reader of a file is not the one who can read it. A publisher handed such a file has a mark they cannot verify.
Two other rows in this column pair an unremovable mark with a public reader, which is the arrangement that actually helps a receiving party. Here the mark cannot be removed and cannot be checked from outside, so both halves of the arrangement point back at the vendor.
3Scope, and what an empty control cell does not license
The visible mark is scoped to videos downloaded from the vendor's own website and app, so even the statement this cell qualifies does not cover every route to the model. The register records the scope as written rather than generalising it, and records the absence of a route the same way.
Reading this cell as the mark is permanent would be a claim about the product. Reading it as nothing is published about changing the mark is a claim about the card, and that is the one the register is making. The difference matters most to whoever is about to promise an unmarked deliverable.
4Sources
- Paid tierNot documented on the vendor's public pages (as of 2026-09-22)the system card attaches no plan to the watermark
- 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 control column page. Neighbouring readings: Veo, control, Amazon Nova Reel, control.