Module lint 

Passport plausibility lints — non-binding findings that flag implausible data (arithmetic that doesn’t add up, values outside physically plausible ranges, or fields whose declared values are inconsistent with each other), as distinct from the malformed data JSON Schema catches or the non-compliant data a crate::batteries/crate::textiles-style rule catches. A lint finding never blocks publish — see LintSeverity.

Each lint cites the physics or arithmetic behind it, the way the sector rule modules cite the regulatory article behind a binding rule. Findings are phrased as questions (“intended?”), never verdicts.

Modules

battery

Battery plausibility lints — physically-grounded consistency checks that EU Battery Regulation 2023/1542 does not itself require, but that flag likely data-entry mistakes: energy/capacity arithmetic, unit-conversion consistency, material-composition sums, and date/range plausibility.

textile

Textile plausibility lints — consistency checks the EU textile DPP rules do not themselves require, but that flag likely mistakes or claims made without their usual supporting field.

unsold_goods

Unsold-goods plausibility lints (EU ESPR Article 25 destruction ban reports) — consistency checks the schema does not itself require.

Structs

LintFinding

A single plausibility finding. Phrased as a question, never a verdict — callers should render message as-is.

Enums

LintSeverity

How strongly a lint finding should be read. Never blocking either way — the distinction is tone, not gating (ADR-002: informative only).

Constants

LINT_PACK_VERSION

Version of this crate’s lint pack. Bump whenever a lint is added, removed, or its trigger condition changes — callers surface this alongside findings so a consumer can tell which pack produced them.