A practical evidence loop for public recall and compliance data

A recall or compliance source is only useful when a team can explain what it observed, what changed, and who needs to review it next.

A compact evidence loop starts with the public source record. It stores the observation time and important fields, compares the next snapshot against the prior one, and keeps the difference readable enough for a human to inspect. That does not make a legal conclusion; it makes the underlying change easier to review alongside the organisation’s own product, supplier, and regulatory context.

Four focused tools can support different parts of that workflow:

• Product Recall Unified Monitor follows supported public recall-source changes. Find it here: https://apify.com/zentrafoundry/product-recall-unified-monitor
• EU Battery Charger Recall Monitor is a separate route for supported charger-recall sources. Get it here: https://apify.com/zentrafoundry/eu-battery-charger-recall-monitor
• EU Battery Passport Readiness Auditor helps review supplied battery-product evidence and surface missing fields or conflicts. Find it here: https://apify.com/zentrafoundry/eu-battery-passport-readiness-auditor
• Dataset Diff & Schema Drift API is a local-first option for comparing supported CSV or JSON snapshots. Get it here: https://zentrafoundry.gumroad.com/l/dataset-diff-and-schema-drift-api

The goal is a reviewable hand-off, not an automated compliance verdict. These tools support evidence collection and comparison; they do not provide legal advice or replace accountable regulatory, security, or product-safety review.