SenseDefend

Synthetic-media instruments, by article and effective date

Default value, the fact that describes most files

A default is the value a parameter takes when a request says nothing. It is a less impressive fact than a capability and a far more useful one, because most output is produced by nobody deciding anything. As of 2026-09-12.

Which mistake each direction makes cheapA default that applies nothing produces files that should have carried something, discovered late by whoever is asked a question. A default that applies something produces a deliverable somebody notices immediately.Which way does the default run?Applies nothingA slow failureAn unmarked file ships; the question arrivesmonths later, from outsideApplies somethingA fast failureA branded deliverable reaches a client, andsomebody sees it at onceCapability sells; the default describes what actually happened
Fig. 1 They trade a fast visible failure against a slow invisible one, and only the first can be fixed before anybody outside the team sees it.
Default value, as published. Recorded 2026-09-12.
Kind of statementWhat it describes
A capabilityWhat the tool can be made to do
A defaultWhat the tool does when left alone
A stated defaultThe same, and quotable
An undocumented defaultAnswerable only by inspecting output

Inclusion rule. Kinds of statement about configuration found in interface and product documentation. Order. From the least informative to the most.

1Capability sells and defaults describe

Documentation leads with what is possible, because that is what a reader deciding whether to adopt something wants. The default is usually a clause at the end of a parameter description, if it is there at all.

For anybody explaining a library of existing files, the priority is reversed. What the tool did matters and what it could have done does not, and only one of those is prominent on the page.

2Defaults move, quietly

Nothing obliges a vendor to announce a changed default, and there is rarely a reason to. A value recorded once is a statement about the day it was read, not a permanent property of the product.

Which argues for verifying behaviour on the route in use rather than reading it off a page. The route produces the files, and it can be checked whenever something upstream is replaced.

3Which direction a default runs decides which mistake is cheap

A default that applies nothing produces files that should have carried something, discovered late by whoever is asked. A default that applies something produces a deliverable somebody notices immediately.

Neither is safer in the abstract. They trade a fast visible failure against a slow invisible one, and only the first can be fixed before anybody outside the team sees it.

4Writing it down is the whole remedy

A current setting explains nothing about last quarter. A note made at render time explains it permanently and costs one field in a row somebody is already filling in.

That is the cheapest available insurance against a late question, and the one piece of record-keeping no amount of subsequent reading can reconstruct.

5Published material behind this entry

A term in this record: what it means, and what the published material says about it, each figure read on 2026-09-12. Related: Content moderation, AIGC label.