SenseDefend

Synthetic-media instruments, by article and effective date

The rows this record keeps on every entry

Every entry in this record is filled in against the same short list of rows: the party a duty binds, what it asks for, what it gives up, and what moves a visible mark on a product. These pages read one row down the whole record instead of across a single entry. As of 2026-09-12.

Why a row is fixed before any entry fills itThe rows are settled from the published wording first, so an entry that does not address one of them leaves a gap on the page instead of dropping a line from its table. A column read end to end is what makes that gap visible.Read the clauseWording takenfrom thepublishedarticle text,with the date itwas readA statementSplit into rowsParty, duty,relief and thelever on aproduct go toseparate rowsFixed rowsLeave the gapA row theparagraph doesnot addressstays unfilledrather thanguessedSilence on fileRead down therowThe same rowacross everyentry is what afield pagereports
Fig. 1 Reading one row across the whole record is a different exercise from reading one entry top to bottom, and it is what these pages do.

A register is worth only as much as the questions it puts to every entry. These rows were fixed before the entries were written, so a paragraph that does not address one of them leaves a visible gap rather than quietly dropping a line from its own table.

Reading down a row is a different exercise from reading a page. One paragraph page answers what that paragraph says; the row read across the whole article shows where the text changes party, where relief is written in, and where the row is absent because nobody in industry is being addressed.

Three of these rows are read from published article text and one from vendor pages. They are never combined into a single verdict, and each page below says which side of that split it sits on.

1The rows

  • Who it binds — The row naming the party a transparency duty falls on.
  • What it asks for — The row holding the duty a paragraph imposes.
  • Who controls it — The row recording what moves a visible mark on a finished file: a paid tier, a switch in settings, or nothing published at all on the vendor's own pages.
  • Carve-out — The row recording relief written into a paragraph.
  • The fourth row — Three rows on a generator entry are fixed.
  • Read from — A pricing table, a system card, an API reference and a paper are four kinds of evidence, and this row records which one a cell came off.
  • Default state — What comes out when nobody changes anything.
  • Reading route — A mark nobody outside the vendor can read answers a narrower question than the clause asks.
  • What survives — Marks fail in different ways.
  • Recorded silence — An empty cell and a documented absence look identical in a table and mean opposite things.

A row earns a page of its own when it appears on more than one entry and the entries disagree about what belongs in it.

Elsewhere in the record: EU, Duties, Generators, Statements, Pairs, Questions, Terms, Learn, Data. How an instrument is read is set out on the sourcing page.