v0.99.8.0: date-aware compliance enforcement, EU Registry readiness, and AI Act transparency
The publish gate and the DPP editor now follow the EU Battery Regulation's own timeline: an obligation that the Regulation does not bring into force until 2027 or 2028 no longer blocks publication today, and the editor says so on the field itself. This release also adds an EU Digital Product Passport Registry readiness hub, a compliance deadline tracker, and EU AI Act Article 50 transparency on the public passport.
Date-aware compliance enforcement
Previously the platform required every field its templates marked mandatory, regardless of whether the Regulation had reached that obligation's compliance date. Operators were being asked to publish data today that the law sets for 2027 and 2028. The publish gate, the wizard's step advance, its validation schema, its form rules, and the strict API validator now all consult the same date-aware obligation model.
| Obligation | Provision | Binds from |
|---|---|---|
| EV carbon footprint | Art. 7(1)(a) | Already in force since 18 Feb 2025, still blocks publication |
| Industrial and stationary carbon footprint | Art. 7(1)(b) | 18 Feb 2028 |
| LMT carbon footprint | Art. 7(1)(c) | 18 Aug 2028 |
| Supply chain due diligence | Art. 48, postponed by Regulation (EU) 2025/1561 | 18 Aug 2027 |
This is not a relaxation of any requirement. Each obligation exists in the Regulation now; what has not yet arrived is the date it starts to bind. EV carbon footprint is unaffected and continues to block. Where Traceable cannot resolve a product's battery category, it fails closed and treats every mandatory field as blocking rather than assuming an obligation does not apply.
The editor now shows it on the field
A not-yet-required field no longer carries a red asterisk, gains an amber Not yet required chip, and its tooltip names the specific date and article ("Optional today, becomes mandatory from 18 Feb 2028 under EU Battery Regulation Art. 7(1)"). Previously these fields rendered identically to genuinely mandatory ones. See Create a product.
EU DPP Registry
- EU Registry Readiness hub: a new operator-portal surface for tracking your preparation for the European Commission's central registry, combining a self-tracked enrolment checklist with an automatically computed check of your product data's readiness. It does not submit anything to the registry. See EU Registry Readiness.
- Opaque item-code resolver: a new public route,
/i/<code>, as the item-level carrier and the fallback for products without a GTIN. It is wired to serve a passport but no codes have been minted yet, so every code currently returns Product Not Found. See QR codes and the resolver. - Commodity codes: a code you provide is now validated against the real EU Combined Nomenclature 2026 under heading 8507. The accepted value is the 8-digit CN code, not a 10-digit TARIC code. No operator role is required to supply one.
Compliance deadline tracker
The operator dashboard gains a Compliance Deadlines card listing the EU Battery Regulation milestones that apply to the categories you actually have products in, each with a live countdown. It is computed deterministically from the Regulation's dates, shows upcoming deadlines only, and hides itself when nothing future applies. See Dashboard.
EU AI Act Article 50 transparency
Article 50 of the EU AI Act (Regulation (EU) 2024/1689) has applied since 2 August 2026. On any passport where the AI assistant is enabled, visitors now see an explicit notice that they are interacting with an AI system, and every block of assistant-generated text carries a visible AI-generated label plus a machine-readable marker. Manufacturer-authored passport data is not AI-generated and carries no such label. See AI assistant.
Operator team roles
Team-role enforcement is now applied consistently across the operator portal, and roles resolve from the database rather than from client-supplied metadata, failing closed to the least-privileged role.
- Admin and Approver may sign and publish DPPs.
- Admin, Approver, and Editor may create and edit content, upload documents, and send data requests.
- Viewer is read-only.
- API key management is Admin-only.
See Team management.
Other changes
- Bulk CSV import now converts each value according to the field's declared type instead of guessing from the value. An identifier such as
000342is stored exactly as typed rather than becoming the number342, which matters because GS1 Digital Link resolution matches identifiers as exact text. See Import products. - AI processing consent is enforced server-side, not only in the interface.
- Published passport integrity is verified when a passport is served and re-verified daily on a schedule, so an altered stored snapshot is detected even if nobody requests it.
- Blockchain anchoring and e-signature screens in the admin area are now explicitly disclosed as not in service.
- The QR Scans filter was removed from the system log, where it could only ever return no rows.