Technical source policy

Make the evidence boundary visible.

Product statements should identify whether they come from a catalog, a project document, a test record or an independent source.

Source levels

Four labels for technical information.

Stronger publication claims require stronger, more specific records.

Catalog-described

Supplier-published product information without an attached model-specific report.

Project document

A drawing, map or interface file released for a named model and revision.

Test-supported

A result linked to model, configuration, conditions, method and acceptance criteria.

Independently verifiable

An official registry, readable certificate or third-party source with scope and validity.

Publication rules

What this website does not infer.

Missing evidence is shown as a request or status—not filled with marketing assumptions.

No global deployment claim from a marketing map
No certification mark without readable scope and validity
No refrigerant compatibility inferred from adjacent products
No corrected value silently substituted for conflicting source data
No customer name or case result without publication permission

Corrections

Trace changes to a source and revision.

When an underlying product value changes, the related page and document should identify the new source and revision date. Contact YACI with the affected model, page and value.

Report a technical correction