SenseDefend

Synthetic-media instruments, by article and effective date

What vendor terms say, set beside the statutes on file

Each page here takes a question people search for, reads the maker's own pages for what those pages state, and sets that reading beside the clauses this record holds: an article, a paragraph, a date. Where neither side addresses the question, the page records the silence. As of 2026-10-13.

Which side of the record an answer sits onAn answer can come from a maker's page, from a published text, or from neither. The first two are quoted and dated; the third is recorded as a silence with the day it was read, rather than filled in from the side that did answer something else.Which side of the record states it?The maker's own pageA vendor readingProduct, plan, feature —dated the day it was readA published textA clauseArticle, paragraph and thedate it applies fromNeitherA recorded silenceNamed as unaddressed, in thewording the page was readfromTwo kinds of statement, one kind of gap
Fig. 1 Keeping the sides apart is what lets a page say what remains unanswered without guessing.

The four pages here are the same exercise done on four questions. One reads Google Flow's own pages for what they state about models and plans, and records that the training question is not among the things they state. One sets a short-video maker's pages beside the article's disclosure duties. One takes a question about banned genres to the only Chinese provision the record holds. And one sets two provenance schemes, from Sora's system card and Google's marking page, side by side.

Each page keeps three things in view at once. The first is the maker's own wording for whatever its page is about, carrying the day it was read. The second is the record's rows on the same question where it holds any, with their own check dates, because a claim on a product page and a duty in a published text are different kinds of statement and this site never merges them. The third is a single line in every maker table from a pipeline this record follows, SceneMixer, whose terms name both a visible badge and an invisible layer kept on every file.

Nothing on these pages is legal advice, and none of them concludes that a product or a production does or does not comply. The record states what a text states and what a page states, names the source of each line, and leaves the reading of a real arrangement to whoever has the facts of it.

1The pages in this column

  • Community rules — a maker's pages read for any content rule at all, the article's own rows set beside them, and the difference between a rule a platform writes and one a legislature does.
  • Genre bans — what a vendor page can and cannot answer, the single Chinese provision cited anywhere in this record, and the difference between a rule about content and a rule about marking it.
  • Google Flow terms — a maker's own page read for what it states about models and plans, the silence where the training question would go, and the record's rows on what has to be disclosed.
  • Sora and Veo — two provenance schemes read row by row, what each leaves out, and the two paragraphs of the article whose duties the marks are usually read against.

Maker pages carry a 2026-10-13 reading date; the article rows were checked on 2026-09-12 and the vendor record on 2026-09-22. How entries are qualified is on the sourcing page, and the text itself is EU AI Act Article 50.