Source and Corrections Policy

Source types

Distinguish supplier-published catalogue references, controlled project documents, official platform or regulatory publications, and authorized customer/test records. Each supports a different scope. A processor feature does not establish a board capability, and a component report does not automatically approve a finished device.

Evidence and claims

Specific performance, reliability, certification, delivery, supply-duration and customer-outcome statements should be supported by identifiable records. When the record is unavailable, describe the requirement or verification step instead of presenting an unsupported result.

Dates and revision scope

Publication and modification dates describe website maintenance. They do not establish an engineering test, professional sign-off or regulatory approval. Confirm the model, hardware revision, software build and document issue date separately.

Corrections

Send a correction to Androidsbc@163.com, including the exact page URL, disputed statement, proposed correction and supporting source. Keep confidential files and credentials out of public comments.

Implementation boundary

This policy explains source distinctions and a correction contact. It does not certify all historical content or claim that a named engineer has reviewed every page. Model-specific documentation and actual review records remain the basis for technical decisions.