Conformance

Draft · protocol 3.0.0-draft

Conformance is per profile and per version. Passing schema validation is necessary but not sufficient for methodological validity or verified physical performance.

Profiles

Profile	Requirements
Core Producer	Valid claim identity, provenance, versioning and at least one typed event
Mitigation Producer	Mitigation events with area, activity, readings or equipment, and evidence references
Waste Producer	Waste events with measurement basis, disposition status and evidence references
Materials Producer	Estimate-to-requirement mapping, product identity and quantity provenance
Option Evaluator	Baseline and candidate comparison, gates, costs, impact and decision status
Claim Reporter	Declared perspective, boundary, results, exclusions and a reproducibility manifest
Consumer	Parses compatible versions, preserves unknown extension fields where feasible and reports validation failures

No conformance program or logo exists yet. Do not describe a product as “TRP certified.”

What this repository validates today

The repository runs pnpm validate, which checks every file in examples/**/valid against the published schemas and confirms that every file in examples/**/invalid fails. Both checks run in CI.

Target validation suite

The full suite is planned to cover:

1. required IDs, timestamps, enumerations and schema versions;
2. unit conversion and decimal precision;
3. invalid quantities, negative mass and impossible dates;
4. duplicate facility tickets and idempotent event replays;
5. missing product category rules, expired declarations and incompatible functional units;
6. comparison of different lifecycle boundaries;
7. cross-currency price comparison without exchange-rate metadata;
8. organizational fuel double counted as job transport;
9. a recycling receipt without downstream processing proof;
10. an LKQ candidate failing a fire-rating or code gate;
11. supplier stock changing after decision approval;
12. a supplement superseding an estimate without deleting history;
13. a report with a missing domain labeled complete;
14. unauthorized tenant access and insecure evidence URLs;
15. recalculation with pinned versions yielding identical output.