The verification system, running on sample data.
Clearlot has not launched. No batch has been received and none has been tested, so the live site publishes no lots — showing you an invented purity figure would defeat the entire point of the site.
It swaps the catalogue for a fabricated dataset of eight sample lots, every lot id prefixed DEMO- and every laboratory name fictional. A red banner sits on every page while it is on. It is stored for your browser session only, changes nothing for anyone else, and never touches the real data.
Why it exists
The interesting part of this project is not the storefront, it is what sits under it: a normalised catalogue, a schema contract, a lot state machine, and a validator that refuses to publish a batch that has not been tested. None of that is visible with an empty register, and the honest live site has an empty register. So the demo has data and the real site does not.
The lot lifecycle
Every lot moves through defined states. The validator rejects any history that is not a legal walk of this machine — a lot cannot go from draft straight to published:
One lot in each state
The sample data covers all six, so the verification page can be seen handling the states that are not the happy path. Enter demo mode first, then follow any of these:
| Lot | State | What the page says |
|---|---|---|
| DEMO-0001 | published | Tested, released, full report shown |
| DEMO-0004 | verified | Tested, report received, not released yet |
| DEMO-0005 | testing | Sample is at the lab, nothing measured yet |
| DEMO-0007 | pending-testing | Logged, not yet sent for testing |
| DEMO-0008 | draft | Recorded, not yet queued |
| DEMO-0006 | archived | Retired, report kept so old vials still check out |
| DEMO-9999 | — | No such lot — the not-found path |
One product, many lots
BPC-157 carries two lots in the sample data: DEMO-0001, which is published, and DEMO-0006, the older batch it replaced. That is the whole reason products and lots are separate files — a purity figure describes a batch, never a product name.
Source
The data model, the schemas, the validator and its tests are in the repository, along with a README explaining the architecture. The sample data lives in data/demo/ and is held to exactly the same schema and the same state machine as production data.