Why a version number is worth a field of its own
Which version produced an asset is visible in an interface for about as long as that interface exists. Afterwards it is unrecoverable, and it is the field most likely to be the one that matters. As of 2026-09-12.
| Question that arrives late | Answerable with a version field |
|---|---|
| Did this file get the newer provenance layer | Yes |
| Why do two clips from the same month differ | Usually |
| Which documented behaviour applied | Yes, against a dated page |
| What the file actually carries | No; that needs an inspection |
Inclusion rule. Questions a delivery record with a version field can and cannot settle. Order. From the questions it answers to the one it does not.
1Behaviour is attached to versions, and pages are not
A vendor page describing a behaviour from a stated version stays up while the version moves on. Every sentence in it remains true about the version it described and stops being the whole picture.
A reader comparing an old row with a current page should expect the version to be the field that moved. That is only checkable if the file's version was written down at the time.
2Interfaces stop showing what they showed
A model selector that named three versions gets simplified to two, then to a single default. Nothing is preserved about what a request from last year actually ran.
Where a service does not disclose the version it used, the record should say not disclosed rather than leaving the field blank. An explicit unknown is a fact about the route; a blank is a missing entry.
3The field costs nothing and is the one most often missing
Five fields fit in a spreadsheet row and a spreadsheet row gets filled in. Tool, version, settings, what the delivered file carried, and where it went, plus the date.
Anything longer becomes a form nobody completes, which is the same as no record while looking like diligence. The version is the field with the worst ratio of cost to later value.
4A version is not a substitute for an inspection
Knowing which version ran tells a reader which documented behaviour applied. It does not tell them what the delivered file carries, because a route sits between the two.
Both belong in the record for that reason: what produced the asset, and what the asset contained when it was checked. Neither answers the other's question.
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: Re-render is not repair, Limits of a register.