Education
Chain-of-custody for research compound documentation.
Chain-of-custody in a documentation context tracks who handled the sample, who issued the report, when it was received, and how subsequent revisions are tied back to the original record. It is a documentation trail — not a quality, safety or suitability statement.
Documentation events
- • Sample receipt by the laboratory
- • Report issuance and signatory information
- • Supplier upload of the certificate to PurityLedger
- • PurityLedger review and lab authentication events
Reconciliation points
- • Batch number on the supplier packet matches the certificate ID
- • Test date sits inside a credible review window
- • Document fingerprint is generated and stored at upload
- • Subsequent revisions reference the original record
Audit signals we display
- • Original creation event with hash
- • Status change events with timestamps and actors
- • Retest and dispute events with resolution status
- • Superseded records remain visible for transparency
Limitations
- • Chain-of-custody confirms documentation continuity, not product safety
- • Records remain batch-specific
- • No jurisdiction-specific compliance is implied
- • No medical, veterinary or human-use representation is made
PurityLedger provides documentation review, batch record hosting, CoA verification tools and analytical testing coordination only. PurityLedger does not certify any product as safe, effective, legal, approved, or suitable for human or veterinary use. Testing records are batch-specific and do not constitute medical advice, regulatory approval, or endorsement of any supplier or product. Clients and users are responsible for compliance with applicable laws in their jurisdiction.