Deliverable: the file a policy is checked against
A deliverable is the finished file somebody is actually handed. It is the only file whose marking state is reliably looked at, which is why a register about marking is mostly a register about deliverables. As of 2026-09-22.
| The term | Deliverable |
|---|---|
| What it names | The finished file handed to a client or a platform |
| What it is not | Everything else a project produced along the way |
| Where the register uses it | The implicit subject of every recorded value |
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.
1The file the whole subject is about
Disclosure obligations, client expectations and platform policies all attach to the file that reaches somebody. Marking on anything else is a workflow detail. So when a vendor says output carries a mark, the reading that matters is what the person receiving the file will see.
That is also the only point where anybody checks. Nobody inspects a proxy for a watermark, and nobody runs a credential reader over a review cut, so a mark's presence elsewhere in a pipeline is unobserved by construction.
2Where the deliverable is not what the tool produced
Between a generator's output and a deliverable there is usually an edit, an export, an upload and a platform transcode. Each of those is an opportunity for an attached provenance record to be lost, and none of them is addressed by any vendor page in this register.
So the file-contents column describes the file as handed over by the tool, and a reader reasoning about what a viewer's copy carries is reasoning about a longer chain than the column covers. The visible layer is the one that reliably makes it to the end.
3Why the register is still about tools
Because the tool is the only actor whose behaviour is documented. Editors, pipelines and platforms all affect the outcome, and none of them publishes a statement a register could cite about generated video specifically.
That is a limit stated rather than hidden. The columns record what the generating tool says it does, and the readings say where the chain continues past what any page here covers.
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 machine-readable column, what survives an export. Nearby terms: console surface, api surface, request parameter.