Build Diagnostics

Some compliance rules are checked by the build itself. When one fires, you get a diagnostic id — look it up here for what the build wants and how to satisfy it.

These checks are a floor, not the whole rule. A clean build means the mechanical violations are absent; the rule's judgement still applies to everything a compiler cannot see.

Id	Rule	What it reports
PQC232	Event publication must be encapsulated in the owning Thing	A class publishes an event through a reference to a Thing it does not own
PQC257	Set the device clock from the wall clock, never a re-projected local time	GetLocalNow().LocalDateTime re-projects the device wall clock onto the host process zone

Severity

Diagnostics arrive as warnings while adapters are brought into line, then become errors. Treat a warning as a defect with a deadline, not as advice.

Suppression

Do not suppress a compliance diagnostic. If you believe a report is wrong, it is a bug in the check — say so, with the code that triggered it. Every rule here exists because the failure it prevents reached a customer at least once.