What the batch left the line under.
A warranty dispute two years later asks two questions: what ambient conditions did the batch leave the line under, and has the batch record itself changed since it was written? A cure that went wrong in the field, an adhesive that failed, a coating that never set: the answer often turns on temperature and humidity on the shop floor at production time, and on whether the QA file produced now is the file recorded then. This page answers both. It returns one signed, independently re-verifiable record of the conditions public sources reported at your plant location, corroborated by a second weather source, and it fingerprints your batch record locally so a notarized hash pins the file to that moment. Every reading is archived, so what the sources said at time T stays re-checkable when the claim lands.
Two signed points, one batch.
Step 1 · ambient conditions at the plant
Enter the plant city, or its coordinates for a precise reading. Dynamic Feed records the live ambient conditions from named public weather sources and returns one Ed25519-signed record produced by the receipt engine. A second independent source corroborates the temperature where it can, and the record is a re-checkable GET you can re-verify years later. Nothing is mocked and nothing is stored about you.
full signed record (JSON)
Step 2 · fingerprint the batch record itself
Pick the batch record (the QA sheet, the CoA, the export from your MES). Your browser computes its SHA-256 fingerprint locally with the Web Crypto API. The file is hashed in your browser and never uploaded. Notarize that hash with the copy-ready curl below and you hold a signed, timestampable fixed point: if the file produced in the dispute differs by one byte, the hash will not match.
curl -X POST https://dynamicfeed.ai/v1/notarize -H "content-type: application/json" -H "X-API-Key: YOUR_FREE_KEY" -d '{"hash":"sha256:<your hash>","ref":"batch-<lot-id>-record"}'
the free key is self-serve at POST /signup; the notarize receipt comes back Ed25519-signed and RFC 3161 timestampable, and re-verifies against the open verifiers with only the hash ever leaving your systems
Field failures are argued on records.
When a batch is blamed for a field failure, your production log and your CoA are each your own record, kept on your own systems, and the customer or their counsel will say exactly that. A contemporaneous reading of the conditions the line ran under, taken from an independent witness, signed at the moment, carrying its source and observation time, and corroborated by a second weather source, is evidence that does not depend on anyone taking your word for it. Pair it with a notarized fingerprint of the batch record and both questions are answered at once: what the conditions were, and that the file has not changed since. Our records work whichever way the dispute runs: anyone can re-check them, including the other side, and the archived reading for time T does not move when the claim does.
Evidence, not a quality ruling.
Dynamic Feed is a neutral witness, not a certifier, auditor or adviser. The conditions record is an advisory record of what public weather sources reported for the plant location at that moment; it reflects outdoor ambient conditions from public models, not a calibrated reading inside your envelope or clean room, and it does not determine whether the batch met spec or caused any failure. The notarized hash proves a byte sequence existed at that time and has not changed since; it does not certify the file's contents are correct. Specifications, tolerances and root-cause stay with your quality people. Advisory evidence, tamper-evident not tamper-proof, zero personal data, and not legal advice.
Where this record travels.
The same receipt pattern runs across the record's whole life: fingerprint the evidence at intake, sign the conditions at the point a sensor reads them, and carry the proof through the chain that moves the goods.
One signed point per lot.
MES and traceability software can mint a signed conditions record and notarize the batch file hash on every lot automatically, keyless to try, self-serve to scale.