SenseDefend

Synthetic-media instruments, by article and effective date

What a per-request control costs to account for

A control exercised per call is the most flexible arrangement available and the hardest to reconstruct. Two files made on the same account an hour apart can differ, with no external record of which is which. As of 2026-09-12.

Where a past value survives, by kind of controlA purchase leaves an invoice readable years later. A setting leaves a current value and rarely a history. A parameter carried by one request leaves nothing at all unless the caller's own pipeline wrote it down.Most recoverable firstA purchaseAn invoice. Survives staff turnover and interface redesigns.An account settingA current value. History is rarely kept by anybody.A session switchWhatever the product logs, if it logs anything.A request parameterNothing, unless the integration chose to record it.
Fig. 1 No vendor undertakes to remember on a caller's behalf, and none of them is being unreasonable about it.
Where a past value can be found, by kind of control. Recorded 2026-09-12.
Kind of controlWhere a past value survives
A purchaseAn invoice, readable years later
An account settingA current value only; history is rarely kept
A session switchWhatever the product chose to log
A request parameterOnly the caller's own logs, if any exist

Inclusion rule. Controls that can change what a generated file carries. Order. Most recoverable first.

1Flexibility and accountability trade against each other

Per-file control lets a production mark some deliverables and not others on purpose. It also lets them do it by accident, and afterwards nothing distinguishes the deliberate case from the mistake.

An account-level control cannot express the nuance and is trivial to describe to somebody asking. Choosing between them is choosing which of those two problems to have.

2The decision is made by whoever writes the code

A parameter is chosen once, in an integration, often months before the first delivery and usually without anybody raising the question it answers. Everything afterwards inherits that choice.

That person is rarely the one publishing the result, and they are rarely in the conversation about what published work should carry. Knowing where the lever sits is the point of asking who holds it.

3Logging one field solves the whole problem

The value is knowable at the moment of the call and unknowable an hour later. A pipeline that writes it into a delivery record turns every future question into a lookup, at no ongoing cost.

No vendor undertakes to remember on a caller's behalf, and none of them is being unreasonable about that. The request was the caller's; the record has to be too.

4Why references are the source for this and plan pages are not

Only a reference describes parameters, types and defaults, because only a reference has readers who would notice an error. A plan page has no reason to mention a field nobody buying a tier will ever set.

So a register reading a plan page will find a price and a register reading a reference will find a mechanism. Neither page is wrong; they answer different questions for different readers.

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: Who holds the lever, What a transcode costs.