Why the default decides almost every file
Almost nothing produced at volume reflects a decision. It reflects whatever the tool does when nobody intervenes, because nobody revisits a setting while rendering the ninetieth clip of a season. As of 2026-09-12.
| Where the default lives | What an untouched workflow yields |
|---|---|
| A request parameter documented as off | Nothing is applied, to anything |
| A product setting that ships on | Everything is applied, unless switched |
| A tier a customer already pays for | Whatever that tier includes |
| Undocumented behaviour | Unknown until somebody inspects a file |
Inclusion rule. Places a default can sit in a generation workflow. Order. From the most explicit to the least.
1The lazy path is the real path
A capability is a fact about a product. A default is a fact about the files that product will produce for most people, most of the time, which is usually the question somebody is actually asking.
Documentation tends to lead with capability, because capability sells. The default is often a clause at the end of a parameter description, and it is the more informative half of the page.
2Which mistake each direction makes cheap
A default that applies nothing produces files that should have carried something and do not, discovered months later by whoever is asked a question. A default that applies something produces a deliverable somebody notices immediately.
Neither is safer in general. They move the cost of the error between a fast, visible failure and a slow, invisible one, and only one of those can be fixed before anybody outside the team sees it.
3Defaults move, and moving them is not an announcement
Nothing obliges a vendor to publicise a changed default, and a value recorded once is a statement about the day it was read. A pipeline that worked in one quarter can behave differently in the next.
Which is the argument for verifying behaviour on the route rather than reading it off a page. The route produces the files, and it can be checked in an afternoon whenever something upstream changes.
4Writing the default down at delivery
A current setting explains nothing about last quarter's output. 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 insurance available against a question arriving late, and it is the one piece of record-keeping that cannot be reconstructed afterwards by any amount of reading.
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: Per-call controls, Who holds the lever.