Four columns, and what each one is allowed to hold
Every generator here is recorded in the same four columns, in the same order. Each column now has its own page: why it exists, what fills it, and the readings it is not allowed to carry. As of 2026-09-12.
The order is not a ranking. It follows a file out of the product: what the free plan puts on it, what a paid plan changes, how the mark comes off, and what the file itself carries once it has left. Read across a row and you have one generator; read down a column and you have the same question asked of every one of them.
These pages exist because the column names appear on every generator page and had nowhere to go. A reader who wanted to know why user toggle is a column of its own, rather than a yes-or-no about removal, had to infer the reason from the rows. The reason is now written down in one place and linked from the word itself.
No page below carries a value a generator page does not already carry. What they add is the rule behind the column: what fills it, which kinds of evidence are allowed to, and what a filled cell still leaves open. Where a definition is at stake the protocol page holds it, and these pages point there rather than restating it in shorter form.
1The columns
- Free tier — What the output carries before anything is paid for, and the two kinds of evidence that answer is read from.
- Paid tier — The plan at which the visible mark stops, why the spread between vendors is a packaging decision, and what a tier does not buy.
- User toggle — Whether a person or an invoice decides, and which of the two a production can reconstruct months later.
- Machine-readable marking — What a vendor states is written into the file itself, and why every generator row in that column is empty.
Each page ends where its values do: on the support table row that carries them, with the vendor page and the reading date attached to every one.
The rest of the register: Generators, Readings, Side by side, Implementers, Questions, Findings, Source documents, Terms, Learn, Data, and the field definitions on the protocol page.