ALL SYSTEMS LIVE·FOOD SAFETY · ADVISORY EVIDENCE · NEUTRAL WITNESS
DATA WITH RECEIPTS · ED25519 · RFC 3161·--:--:-- UTC
Home  /  Cold-chain evidence  /  Food safety record
FOOD SAFETY · TRACEABILITY · RECALL EVIDENCE

When a batch is questioned, this is the file they read first.

A supplier hears the batch might be tainted. Before anyone argues, the first thing an insurer or regulator wants is the plain record: what was publicly recalled, and when. This page returns a signed, independently re-verifiable record of the recent food and product recalls the FDA enforcement feeds reported, with each recall's source and observation time, keyless. Read it beside your own storage and transport windows: the cold-chain condition receipts that show the batch was held in spec. An Ed25519-signed, RFC 3161 timestampable record that sits with your own logs as one independent input.

LIVE

The recall timeline, signed at read time.

Search a product term, an ingredient, or a firm (or leave it blank for the most recent), pick the recall universe, and Dynamic Feed records what the openFDA enforcement feeds report as observed evidence and returns one Ed25519-signed Decision Receipt produced by /v1/answer. Nothing is mocked and nothing is stored about you.

two feeds are recorded together: the FDA enforcement index (fda_recalls, searchable, classification and initiation date) and the consumer recall index (product_recalls); each recall carries its source and the time it was observed
WHY IT MATTERS

Recalls are decided on records, in order.

A withdrawal, a rejected shipment, a spoilage claim, a supplier-liability dispute: each one turns on a sequence. What was recalled, at what classification of severity, on what date, and what condition your batch was held in across the same window. A screenshot of a recall notice proves nothing about when it was taken or whether it was edited, and your own timeline is necessary but it is your own word. A record from an independent witness, signed at the moment it was read, carrying each recall's named public source and observation time, and re-verifiable years later against a published key, is corroboration both sides can check. Pair it with the cold-chain condition receipts for the storage and transport windows, and you have the file an assessor opens first.

Data with Receipts. The receipt proves what the named public recall feeds reported at that time, and that the record has not been altered since. It is one independent input beside your own traceability and condition records, not a replacement for them and not the official recall notice.
THE FILE, ASSEMBLED

Three receipts, one story.

A batch dispute is a timeline, and a timeline is built from independent receipts. Follow the links below to the pieces that sit beside this recall record.

THE BOUNDARY

Evidence, not a compliance ruling.

held on purpose

Dynamic Feed is a neutral witness, not a government agency, a certifier, or an adviser. This receipt is not the official FDA recall notice and does not decide whether a batch is safe, whether a recall applies to your product, or whether any duty was met; those are questions for the regulator, the contract, and the parties. Laws and contracts vary by jurisdiction, and the recall feeds shown here are US FDA and openFDA enforcement records. Always confirm against the official FDA record before acting. Advisory evidence, tamper-evident not tamper-proof, zero personal data, one input beside your own records, and not legal advice.

FOR SUPPLIERS, INSURERS & TRACEABILITY SOFTWARE

One API call per batch question.

Traceability and claims software can mint a signed recall record the moment a batch is questioned, keyless to try, self-serve to scale.