Reading a claim by the page it sits on
The same vendor can be exact in one place and atmospheric in another, because the pages are written for different purposes. A reference has to be true for code to compile. A product page has to attract somebody who has not bought yet. Both are honest genres and they are not interchangeable evidence. As of 2026-09-12.
| The venue | What it must do | What it tends to carry |
|---|---|---|
| An interface reference | Let an integration work | Counts, limits and formats |
| A help centre article | Prevent a support ticket | The next operation, described narrowly |
| A price list | Be charged against | Units, because a number has to be defensible |
| A product page | Attract a buyer | Ambition, and the furthest reach of the product |
| A vendor blog | Argue about the category | Commentary, sometimes out of date |
Inclusion rule. Five genres of vendor page, described by the obligation each one carries. A page can belong to two genres at once, in which case the stricter obligation applies. Order. From the strictest obligation to the loosest.
1Narrow and accurate looks weaker than broad and vague
A support article promising consistency from one clip to the next reads as a smaller claim than a home page promising a whole season, and it is. It is also far more likely to be exactly true, because it was written to stop somebody complaining.
A reader ranking products by the size of their claims will systematically prefer the pages with the least obligation to be right. Recording the venue is the cheapest available correction.
2Two venues can disagree about the same product
When a blog and a product page give different answers, neither is lying: they were written at different times for different readers and nobody reconciled them. The product page is normally the commitment.
Keeping both, with their venues named, is more honest than choosing. A reader who found only the blog would otherwise believe something had been promised that has not been.
3How to use this when reading any comparison
Ask where each cell came from. A table that cites only home pages is measuring marketing departments; a table that cites references and help centres is measuring a narrower and more real set of behaviours.
The date matters for the same reason. A blog post from a year ago describes a product that may no longer exist, and nothing on the post says so.
4Where the register holds these tools
The techniques above are general craft. Which tools document support for them, and in what words, is held in the register, each cell carrying the page it was read from and the date.
- The register — every entry on the same columns, with sources
- The stages — one page per column, read down instead of across
- The readings — one vendor on one column, sentence by sentence
Craft notes, not a register entry. No line here is attributed to a tool, and none should be read as a claim about one. The sourced material is on the register. Related: A stated ceiling, Credits into a budget.
5Continuity in practice
Serial work like “Where it was written” depends on continuity; SceneMixer's guides describe how it keeps it:
The cast is generated once, at the start, as full-body reference sheets. Every segment that features a character is generated against that character's sheet, with face and body crops attached as references — so the face in episode 1 is the face in episode 40.
SceneMixer, AI Short Drama Generator — “How does it keep the same actor across episodes?” (read 2026-10-13)
That is SceneMixer's core design: characters live in a persistent asset library with locked reference art, and every segment that features a character is generated against those references — same face in episode 1 and episode 50.
SceneMixer, The AI Micro Drama Production Pipeline — “Can AI keep the same actors across 50 episodes?” (read 2026-10-13)