Open sample · no signup needed
Follow one certificate family from scattered sources to reviewed versions.
Sunny Bear Plush Toy, family BL-PLSH-001. Inspect the evidence behind a field, see how a disagreement is recorded, and follow a supplier retest into a newly reviewed version.
This entire case is synthetic. Brightline, the factory, the lab, the people and their approvals are fictional. Source files are short demonstration fixtures, not complete laboratory reports. This sample shows the software workflow; it is not a customer result, an expert opinion, a certificate of compliance, or evidence of CPSC acceptance.
What you can check
Sources, decisions, then a portable handoff.
Find the source
A value carries a document reference, a recorded locator, an approver and a timestamp. Download the source and check the mapping yourself.
Keep the judgment visible
A manufacture-date conflict is resolved with a recorded rationale. Internal evidence review and customer data approval remain separate events.
Preserve the prior record
A new fabric supplier leads to a retest. The new report and date appear in v2, while the completed v1 snapshot remains available.
Your designated qualified people or separately engaged advisors make applicability and compliance decisions. The subscription provides the evidence workflow; a named expert service is not implied by these fictional reviewers.
01 · Field provenance
The source behind the v2 value.
These are selected fields from the completed v2 snapshot. The full CSV maps all 12 fields, including the original recorded locators and approval timestamps. Fixture positions below help you inspect the actual downloadable files.
| Field | Reviewed value | Downloadable source / position |
|---|---|---|
| Product | Sunny Bear Plush Toy20-inch plush bear, ages 3+ | Factory spec sheetCSV record 2, product_name and notes |
| Product identifier | SKU BL-PLSH-001 / UPC 0-123456-78901-2 | Factory spec sheetCSV record 3, sku_upc |
| Manufacture date | 2026-03-14Conflicting email retained in the case history | Factory spec sheetCSV record 9, date_of_manufacture |
| Test report ID | VTL-26-09544Replaces VTL-26-08812 in v2 | Retest reportText line 2, Report No |
| Test date | 2026-06-30Replaces 2026-05-22 in v2 | Retest reportText line 5, Date of testing |
| Citation list | ASTM F963-23; 16 CFR 1501Illustrative reviewer scope decision; not a general applicability rule | Initial reportSCOPE section; the recorded locator is “report p.2, scope table” |
02 · A disagreement that needs a person
Two manufacture dates. One recorded decision.
March 14, 2026
Factory sheet, record 9: production schedule revision C. This is the value retained in both completed versions.
February 27, 2026
Factory email dated March 2: an earlier date. The disagreement is retained in the resolved exception history.
Illustrative reviewer rationale: “Factory spec sheet is the controlling production record; email referenced the pilot run. Kept 2026-03-14. Factory asked to confirm in writing.”
The decision history also retains an older 2023 report and a missing-citation scope review. Their resolutions are synthetic judgments, not automatic rules based on report age or a recommendation about toy-testing requirements.
| Gate | Person in this fixture | What the event means |
|---|---|---|
| Internal review | Riley Reviewer (synthetic) | Reviews field provenance and, for v2, the retest change. |
| Customer data approval | Casey Customer (synthetic) | Confirms the data for the stated production run. It is not an agency approval, certification or filing. |
03 · A retest changes the record
Update the evidence without losing v1.
The retest source names a fabric supplier change, trigger CC-2026-19. After new field approvals, internal review and customer data approval, the fixture completes v2.
Initial test evidence
Report VTL-26-08812
Test date 2026-05-22
Retest evidence
Report VTL-26-09544
Test date 2026-06-30
Check the files and version chain yourself
The manifest provides source-file hashes, exact snapshot-content hashes, and the engine-produced version hashes. The README explains the compact, sorted-key JSON header used to reproduce each version hash.
These local demo versions are unsigned. Their digests detect changes against the trusted original; they do not authenticate the publisher. No signing key is included, and these fictional records are not present in the live app’s verification service.
Portable evidence
Take the case apart.
Export is a handoff, not a government submission. No live Registry import, government receipt or current official-schema CSV is asserted by this sample. Your importer team and broker remain responsible for the applicable certificate, filing and shipment decisions.
Does this match your evidence problem?
CertEvidence is designed for importers coordinating recurring certificate families across suppliers and labs. Explore the sample workspace without a card. Adding a payment method starts the 14-day trial for your own records; Starter then costs $750/month for up to 100 certificate families. Your qualified team owns the review decisions.