GateTrue

What each generator documents about marking its output

Two-route product: where the door decides the file

A two-route product reaches the same models more than one way: a console and an interface, or plans and an interface. The route can decide what the output carries. In September 2026 one entry documented both sides; that reading is now a dated record. As of 2026-10-25.

Three ways of documenting more than one doorBoth routes documented, with statements that disagree, lets an integrator plan around the split. One route documented leaves the other an open question. A statement scoped to one route neither includes nor excludes the rest, and the register records the scope as written.Both documentedA console that stamps, a fielddefaulting to falseTwo statements, disagreeingA split that can be plannedaroundOne documentedPlans remove the mark; interfacepages silentOne statementAn open question about theother routeScoped to a routeDownloads from the vendor's ownpropertiesA statement with an edge onitOther routes neither in noroutSame commercial shape, three documentation practicesNo file from any of them records which door it came through
Fig. 1 The September reading showed that assuming the second route matches the first can be exactly wrong.
How this register uses the term, and what it excludes. Written 2026-10-25.
The termTwo-route product
What it namesA product whose models are reachable by more than one route
What it is notTwo products, or two models
Where the register uses itTwo entries today; a third until 2026-10-25

Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.

1Three degrees of documentation

A vendor can publish a marking statement for each route and have the two disagree, publish a line on its consumer plans and not repeat it on its interface pages, or scope a statement to downloads from its own properties and address nothing else. The first lets an integrator plan. The second and third leave an open question that no published page closes.

The register records the consumer statement where it exists and does not extend it across a boundary the vendor did not extend it across, because a case where both routes were documented showed that the inference can be exactly wrong.

2What changed on 2026-10-25

That case was one entry whose console guide said the console always stamped while its API defaulted to not stamping. The guide has since been replaced and the new page carries no console statement, so the register now documents that entry on its API route only. The two entries that were always documented on one route are unchanged.

The September comparison is kept on two pages: the finding Products on more than one surface: September 2026 and the contrast Wan and Runway: two routes, as read in September 2026.

3What a recipient can tell afterwards

Very little. A clean file proves nothing, because it could come from a caller who set a field or one who never knew the field existed. A stamped file can prove the stamping route only where a vendor documents it.

And none of the entries names a provenance standard, so no file from any of them records the route it came through. The door matters and the file does not remember it, which is the ceiling on this whole distinction.

Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the user toggle column, source documents. Nearby terms: download route, burned-in mark, corner stamp.

4From the production side

Next to the marking question in “Two-route product”, SceneMixer's pages describe its output like this:

The product image is always redrawn from your original photo so it stays your product.

SceneMixer, Ad Projects and Remake Projects: What Looks Different in the Wizard and the Editor, and Why — “Can I redraw the product from text?” (read 2026-10-13)

Downloads and the asset library follow your Music switch; a shared link always plays the version with the episode’s music.

SceneMixer, Background Music in an AI Short Drama: The Built-in Score — “Does the music carry into downloads, the library and shared links?” (read 2026-10-13)