SenseDefend

Synthetic-media instruments, by article and effective date

Which party can actually answer your question

A question about what a file carries has several possible addressees: the tool vendor, the platform, whoever operated the tool, and whoever published the result. Only some of them can answer. As of 2026-09-12.

Four questions with four different addresseesWhat a tool applies is the vendor's to describe. What a request asked for belongs to whoever wrote the integration. What a delivered file carried belongs to whoever inspected it, and what survived an upload is a question for a test.The vendorPages about the toolAnswers what is applied, bydefaultCannot see anybody else'spipelineThe operatorSettings and parametersAnswers what was asked forLeaves the organisation,unless recordedThe platformA transcode nobody documentsAnswered by a test, not bysupportCovers everything throughthat routeA question about a published assetThe publisher owns the question either way
Fig. 1 Asking the vendor produces an accurate answer to a different question, which is worse than no answer because it sounds authoritative.
Who can answer each kind of question about a published asset. Recorded 2026-09-12.
QuestionWho can answer it
What does this tool apply by defaultThe vendor, on a page
What did this request ask forWhoever wrote the integration
What did the delivered file carryWhoever inspected it, if anybody
What survived the uploadThe platform, or a test

Inclusion rule. Question types that arrive about a generated asset after publication. Order. Grouped by addressee, earliest in the chain first.

1A vendor cannot answer questions about somebody else's pipeline

What a tool applies is the vendor's to describe. What arrived at an audience depends on an editor, an export, an upload and a platform, none of which the vendor controls or can see.

Asking the vendor produces an accurate answer to a different question, which is worse than no answer because it sounds authoritative. The chain has to be walked rather than delegated.

2The operator is usually the sole witness

Settings in force, parameters sent and which version was selected are visible at the moment of production and nowhere afterwards. Whoever was at the keyboard is the record, unless a record was kept.

Which is the entire argument for keeping one. It converts a person's memory, which leaves the organisation, into a field in a row, which does not.

3Platforms are testable even when they are not answerable

Support channels rarely produce a statement about what a transcode preserves. Publishing one asset and inspecting the copy an audience receives produces the answer in an afternoon.

That answer covers everything through the same route until the route changes, which makes it better than a statement would have been. A test describes the pipeline in use rather than the pipeline in general.

4The publisher owns the question whether or not they own the answer

Whatever the tool did and whatever the platform kept, the party that published generated work is the one asked about it. Nothing in any vendor's arrangements moves that.

So the useful posture is to assume the answer will have to come from inside the production, and to arrange the record accordingly before there is any question to answer.

Background on mechanism and practice. Nothing here is attributed to a product, and nothing here is a reading of any instrument. The sourced material is on the generator table. Related: Three kinds of marking, Keeping a record.