Evidence policy¶
At a glance
A verified URL is not a verified technical claim. Record source type, version and the depth of checking.
Evidence labels¶
| Label | Meaning |
|---|---|
| PRIMARY | Standard or original technical documentation with bounded scope/version |
| CODE | Inspected at a specific commit; static observation, not automatically runtime proof |
| DEVELOPER / MANUFACTURER | The project's or vendor's own statement; not independent measurement |
| FIRST-HAND REPORT / REVIEW | An author's own inspection; edition, method and missing raw data still matter |
| COMMUNITY REGISTER | A maintained index for finding candidates; not a substitute for per-disc evidence |
| MEASURED-EXTERNAL | An original external test whose method/setup has been reviewed |
| MEASURED-LOCAL | Reproducible local test with raw data and hashes |
| FORUM / VIDEO | Source format; author and evidence still need evaluation |
| EDITORIAL | Our framework, inference or test proposal |
| TODO | Missing or insufficiently verified evidence |
Labels attach to claims, not just whole websites. A developer can be a primary source for its implementation without being an independent authority on competing products. “Link verified”, “read” and “method audited” are different states.
Minimum source record¶
Record title, author/organisation, URL, publication/version information, access date and exact location: function/line, section or video timestamp. State what the source supports and what it does not. Pin code to commit hashes. Mark changing product pages as dynamic.
For film classifications, record territory, edition, release date, barcode/cut and tool report. A title alone is not a format identifier. An HDR10-only disc, P7 MEL and an EL-discarded conversion are not interchangeable categories.
Earlier AI replies are research leads, never evidence. Preserve disagreements with their sources and version boundaries. A newer release may supersede old support information, but recency alone does not make a source correct.
Claims requiring a defined test¶
“Bit-identical”, “reference quality”, “lossless Atmos”, “all objects preserved” and “best” need a comparison point and evidence. Attribute a developer claim explicitly when that is the available support.
Sources · Contribution workflow · Test design
Reviewed 6 November 2026 · EDITORIAL · project evidence policy