SenseDefend

Synthetic-media instruments, by article and effective date

Sora on the route the visible mark is scoped to

Two named surfaces carry the notice. Nothing is said about files that leave by any other means, so the scope of the visible layer here is a workflow question rather than a billing one. As of 2026-09-22.

Wide scope on one layer, narrow on the otherOn this entry the manifest is described as applied to all assets with no route, tier or version attached, while the visible notice is scoped to two named surfaces. That is the reverse of the usual pattern in this record.The manifestThe visible noticeScoped toAll assetsDownloads from the site or the appDepends onNothing statedHow the file was obtainedRecoverable laterRead it from the fileOnly if the workflow logged itWho benefitsA platform or an auditorA viewer, if it is presentOne entry, two opposite scopes
Fig. 1 Most entries here describe a visible mark broadly and say nothing about anything a parser could read.
OpenAI Sora on the stated scope column, and what that column leaves open. Recorded 2026-09-22.
PointWhat the record holds
Stated scopeVideos downloaded from the vendor's site or app
Read fromA system card listing the measure among three
What it does not settleWhat a programmatic or shared copy carries

Inclusion rule. One cell of this generator's entry, quoted from the page the entry names. Coverage, commentary and third-hand summaries are not admitted, in either direction. Order. Fixed order: the cell, the page it came off, then the limit on reading it.

1Scoping a notice to a route is unusual and consequential

Every other visible mark in this record is scoped to what was paid or what was set. This one is scoped to how the file was obtained, which means the same generation can exist in two states.

For a production that is the state hardest to reconstruct. Neither an invoice nor an account page records which surface a clip was pulled from, and nothing in the file necessarily says either.

2The metadata layer is scoped differently on the same entry

The manifest is described as applied to all assets, with no route, tier or version attached. So within one entry the wide scope belongs to the machine-readable layer and the narrow one to the visible layer.

That is worth noticing because it is the reverse of the usual pattern here. Most entries describe a visible mark broadly and say nothing at all about anything a parser could read.

3What a scoped visible mark leaves to the publisher

A viewer only benefits from a notice that is in the file they watch. Where the notice depends on the route, a publisher cannot rely on it without controlling the route, and the article's disclosure duty does not move to accommodate that.

The cell therefore records the scope rather than treating the mark as a property of the model. Read strictly, it is a property of two named surfaces.

  • OpenAI Sora
    A visible moving watermark on videos downloaded from sora.com or the Sora appthe layer tied to the download routeSora 2 System Card, OpenAI / recorded 2026-09-22
  • Article 50(2)
    Machine-readable marking does not apply to assistive standard editing that does not substantially alter the inputsecond exemptionAI Act Explorer, Article 50 / recorded 2026-09-12

4Sources

Wording taken from the Sora 2 system card at cdn.openai.com, consulted 2026-09-22. All four rows for this generator sit on OpenAI Sora; the same column across every entry is read down on The fourth row. Filed beside it: Wan on the words in the corner, Kling on the word brand.