Corrections
Material changes are versioned.
A product rename, policy change, stale source, calculation error, or credible conflicting report sends affected results back to review. Corrections should state what changed and when.
Report a correctionEditorial policy
The label on every claim must match the work behind it.
This policy governs data collection, compatibility conclusions, corrections, commercial relationships, and the use of automated tools.
From source to result
Five gates before a claim can stand.
- 1
Identify the exact entity
Model, SKU, market, formula, firmware, route, and effective date are resolved before a relationship is assessed.
- 2
Capture the controlling source
The relevant manufacturer, airline, or government wording is recorded with its URL and access date.
- 3
Apply rules without upgrading evidence
A class or dimension rule may produce an Estimate. It does not become Tested until the exact pair follows a published protocol.
- 4
Review conflicts and context
Contradictory wording, product changes, aircraft differences, and report disagreements remain visible and can lower the verdict to Conditional or Unknown.
- 5
Open indexing separately
A page can exist for private review while remaining unavailable to search engines. Evidence and editorial review control publication.
Commercial independence
Payment cannot change evidence.
Affiliate relationships, free samples, or sponsorships must be disclosed. They cannot change a rule, remove a documented limitation, or raise an evidence level.
AI and automation
Tools can assist; sources must decide.
Automated tools may help locate candidate pages, normalize fields, compare text, or flag changes. They cannot invent specifications, replace a cited source, or turn an Estimate into a test.
Search publication
Programmatic does not mean indexable.
Generated relationship pages remain out of search until exact entities, pair-specific reasoning, current sources, sufficient evidence, and editorial review are all present.
See evidence levels