SenseDefend

Synthetic-media instruments, by article and effective date

Three people who can change what a file carries

Whatever a published asset contains was decided by somebody. In practice it is one of three people, and which one depends on where the tool put its control rather than on how the organisation is arranged. As of 2026-09-12.

Three people, and the product decides which oneA studio can have a policy about published work and still deliver whatever a junior operator's session produced, because the control was a switch in the session. The outcome follows the packaging rather than the org chart.Who decided what this file carries?A switch in the productWhoever was logged inImmediate, no approval, andonly the product's logsrememberA tier or a membershipWhoever approves spendSlow, and it leaves aninvoice that answers thequestion laterA request parameterWhoever wrote the codeDecided once, applied toeverything, recorded nowhereby the vendorThree questions worth answering before a series starts
Fig. 1 Where is the control, who can move it, and what gets written down when it moves.
Who each kind of control puts in charge. Recorded 2026-09-12.
Where the control sitsWho is deciding
A switch in the productWhoever is logged in when the file is made
A tier or a membershipWhoever approves the spend
A request parameterWhoever wrote the integration
Nothing offeredNobody; the behaviour is fixed

Inclusion rule. Control locations observed across generation tools. Order. From the most immediate decision-maker to the least.

1The org chart does not decide this; the product does

A studio can have a policy about what published work carries and still deliver whatever a junior operator's session produced, because the control was a switch and the switch was in the session.

Conversely a team with no policy at all can deliver consistently marked files because the mark is priced into a tier nobody is going to change. The outcome follows the packaging.

2Each of the three leaves a different trace

A purchase leaves an invoice. A setting leaves a current value and rarely a history. A request parameter leaves nothing unless the pipeline wrote it down.

So the question who decided and the question what can be proved have different answers, and the second one is usually the one that matters when somebody asks about a specific file.

3Nobody deciding is also an arrangement

Where a tool applies something with no documented way to remove it, every file from that tool is in the same state and nobody in the production made a choice. That is the easiest case to describe.

It is also the case a client occasionally refuses, which is why the alternative exists. Both arrangements are product decisions rather than positions about anything wider.

4What to ask before a series starts

Where is the control, who can move it, and what will be written down when it moves. Three questions, answerable in an afternoon, and unanswerable once four hundred clips exist.

The alternative is discovering the answer during whatever conversation prompted the question, which is the one moment when nobody has time to investigate their own pipeline.

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: What a transcode costs, Safe areas and crops.