SenseDefend

Synthetic-media instruments, by article and effective date

Sora and Nova Reel on one standard and two reading routes

Adopting the same format makes two vendors' files readable by the same software. What it does not settle is who each vendor tells you to ask, and these two answer that question differently. As of 2026-09-22.

One format, two answers about who to askAdopting the same manifest specification makes two vendors' files readable by the same software. What it does not settle is the route each page points a reader at, and these two point in opposite directions.One entryThe other entryManifest scopeAll assetsFrom a stated versionRoute the page namesInternal detection toolsPublicly available toolsSecond layerA visible mark on downloadsAn invisible signal on all videosReaches a viewerYes, on two surfacesNoThree useful properties between them, and neither has all three
Fig. 1 Recognising a standard on a page is not the same as knowing what a file carries or who can confirm it.
OpenAI Sora and Amazon Nova Reel on the same column, point by point. Recorded 2026-09-22.
PointOpenAI SoraAmazon Nova Reel
Manifest formatC2PA metadata on all assetsCredentials based on C2PA, from version 1.1
Checking route the page namesDetection tools described as internalPublicly available verification tools
Second layer describedA visible moving watermark on downloadsAn invisible watermark on all videos

Inclusion rule. Two entries whose published answers to one column pull in different directions. Cells hold each vendor's own wording from the page its entry names; pairs that agree on the column are not filed at all. Order. Fixed order, and the two columns are in the order the heading gives them.

1The format travels whether or not the vendor helps

A manifest in a published format can be read by anybody who implements the format. Nothing a vendor says about its own tooling changes that, which is why both of these entries reach outsiders on the manifest layer.

What differs is the route the page points at. One sends a reader to its own internal capability; the other sends them to tools somebody else built. Only the second is usable by a reader with no vendor relationship.

2Each pairs the manifest with a different second layer

One adds a visible notice scoped to two download surfaces. The other adds an invisible signal applied to all videos. The first reaches a viewer; the second survives a container rebuild.

So the pair covers three of the four useful properties between them and neither entry has all three. A reader who needs viewer-facing disclosure and container survival has to take one from each.

3What a shared format does not promise

Coverage differs: one says all assets, the other names a version boundary. Readability differs: one names public tools, the other names none. Format alone predicts nothing about either.

This is the clearest place in the record to see that recognising a standard on a page is not the same as knowing what a file from that vendor carries, or who can confirm it.

  • OpenAI Sora
    Internal detection tools to help assess whether a video or audio was created by the vendor's productsthird item on the same listSora 2 System Card, OpenAI / recorded 2026-09-22
  • Amazon Nova Reel
    Version 1.1 adds Content Credentials based on the C2PA specification, carrying the model and the platform usedthe second provenance layerAWS AI Service Card, Amazon Nova Reel / recorded 2026-09-22

4Sources

Read from the Sora 2 system card at cdn.openai.com and the AI service card at docs.aws.amazon.com, consulted 2026-09-22. Full entries: OpenAI Sora and Amazon Nova Reel. The column itself is on Reading route. Other pairs on file: SynthID and Synthesia, AudioSeal and Firefly.