Editorial policy

Accuracy depends on field-level official evidence, bounded automation, and separate release activation.

Effective date: July 23, 2026
Last updated: July 23, 2026

Evidence standard

Every material public claim and action must retain its official source, current source hash, short excerpt, structural location, US market and locale, appliance scope, and model or product-family applicability. Codes that look alike are never merged across brands or unsupported model scopes.

Builder, reviewer, and approval

An automated builder can draft evidence-bound content but cannot approve it. An independent automated review pass can approve, request one revision, or block. Passing content then requires separate owner-delegated technical and publication-candidate approval events bound to the current hashes. These are automated approvals, not human review.

Release activation

Approval alone does not make content visible. Activation is a separate explicit owner action tied to an exact immutable manifest. Publication does not run from crawling, source monitoring, corrections, or ordinary page requests.

Corrections and source changes

A correction signal may trigger an official-source re-audit, a blocking hold, or a corrected private candidate. It never edits public content automatically. Substantive source uncertainty invalidates eligibility and is labeled “Source changed / review pending” or withheld.