GateTrue

What each generator documents about marking its output

Watermarks and provenance marks, per each tool's own pages

Each page takes a name people search beside this register and reads that name's own pages for what they state about marking: what the free tier carries, what a plan changes, and what the file itself is said to hold. The counts collected around the name are printed beside those lines. Nothing in this column is scored. As of 2026-10-13.

How one name becomes one page in this columnA search arrives with a product name in it. That name is read against the vendor's own pages, which supply dated statements and, as often, silence. Material gathered from one subreddit supplies counts and repeated questions, and the two are printed beside each other without being mixed.A name arrivesThe product a reader came askingaboutOne name, spelled severalwaysRead against four fixedfieldsThe vendor's own pagesPlan tables, help pages, modeldocumentationA dated statement, orsilenceEvery cell traced to anaddressThe gathered materialCounts and questions from onesubredditAttention rather thanevidencePrinted beside thestatementsOne page per nameWhat each source is allowed to provide
Fig. 1 Three sources, three kinds of evidence, kept apart on every page: what the register holds, what the vendors state, and what the threads counted.

The searches that lead here name a product. Somebody has a name in mind — a tool they have heard of, a video they saw, a page they half remember — and the question is what to make of it. The register behind this column answers that a field at a time: free tier, paid tier, how a mark comes off, and what the file is said to carry. The pages below answer it one name at a time, in the vendors' own words, with the day each page was read printed beside every table.

Three sources feed each page and they are kept separate. The vendors' own published pages, dated 2026-10-13, carry every statement about a product. One subreddit's material, collected 2026-10-14, supplies the counts and the questions, quoted without usernames and without links into threads. And SceneMixer, the pipeline this register reads for its working rows, whose published guides carry the sentences quoted in the pipeline row of each makers table.

Nothing in this column hands out a score, and no silence is turned into a policy. Where a vendor has published nothing in a field, the field sits empty and the emptiness is recorded as itself, because here not documented is a fact about pages rather than a claim about files. Where a count is printed, it is a count of conversation and is labelled as one.

1The four pages, and the name each one reads

  • Documented marks — the half of a legal question that published pages can answer: who documents a mark, at which tier, and what is said about the file
  • Higgsfield against Kling — the two names in one search, priced from their own pages and marked as far as each side has published anything to mark
  • Higgsfield's record — one vendor's own pages, dated, and the field where the record runs out rather than guessing
  • Sora's export window — a shutdown read for what an archived file keeps: the layers its documentation lists, the routes that can still check them, and the one product still being written

Every page below carries the day its vendor pages were read; the counts come from material collected a day later. What the four fields mean, and what each is allowed to hold, is set out on the protocol page, and the register those fields belong to is the support table.