The demo, walked
Seven guided walkthroughs of the live demo: the OIML-CS certification chain told as five flows, from the manufacturer's application to the registered certificate, the standards-license due process that seats the licensed tiers at the bench, and the audit record behind them. Every step names its console, shows the live surface, and tells you exactly how to try it yourself.
The walkthroughs below are the readable companion to the demo instance: each flow is narrated step by step in plain language, every step carries a scripted capture of the live demo taken this wave (never a stale screenshot), and every step ends with the persona and console that reproduce it. Each flow also carries its presenter script in two lengths, the 5-minute committee slot and the 20-minute working visit, printable from the page.
The arc in one picture
Flow 05 is the same chain from the applicant's seat: the notifications, the progress, the certificate, the public verification. The Evaluation Project is the shared dataspace the three parties work in: the authority owns it, the applicant views it, the laboratory joins it on the accepted assignment. Flow 07 steps beside the chain: the standards-license due process that decides which tier the laboratory's own runs render, and the record the decision leaves behind.
The walkthroughs
The application
6 stepsThe manufacturer applies against a SMART Recommendation: the explicit Recommendation pick, the model-derived instrument step, the authority chosen from cards, the submit.
try it: Applicant · /app/portal
The authority's intake
8 stepsThe review queue at the issuing authority: the honest reject-or-accept, the evaluation project as the shared dataspace, the samples, the dispatch to the laboratory.
try it: Issuing Authority · /app/ia
The laboratory's work
6 stepsThe test laboratory accepts the assignment, joins the project dataspace, runs the model-driven tests at the bench, and submits the test report.
try it: Test Laboratory · /app/lab
The evaluation and the certificate
8 stepsThe authority validates the test reports against the model, runs the review period, issues the signed certificate, and registers it with the BIML.
try it: Issuing Authority · BIML Officer · /app/ia · /app/biml
The applicant's journey
5 stepsThe manufacturer follows every stage, notified at each, downloads the certificate, and anyone can verify it against the public register.
try it: Applicant · /app/portal
The audit findings
4 gap clustersThe engineering record behind the flows: what the step-by-step audit found, what the build answered, and the doctrine decisions taken in the open.
try it: The engineering record · DEMO_FLOWS/
The standards licenses
5 stepsThe due process behind the licensed tiers: the citation tier on the unlicensed run, the scheme operator’s confirmation, the unlocked interactive stepper, and the per-key history.
try it: OIML-CS Administrator · Test Laboratory · /app/cs · /app/lab
The cast, plainly fictional
Five personas carry the flows. Sign-in runs through the OIML SMART identity service: the login page lists the cast as persona cards, and the identity service's account chooser continues the sign-in as the persona, so no cast password is ever published. Every person and organization is invented for the demonstration; the instrument is Steelyard's fictional LC-500 load-cell line evaluated against OIML R 60.
Two ways to walk it
Walk it yourself, freehand. Pick a walkthrough below, assume the persona each step names, and work the consoles at your own pace. The instance resets nightly, so nothing you enter survives: try the reject, type the odd value, watch the gates refuse.
Or let the demo present itself. The login page's Start the guided demo button (or ?demo=full-flow on any app page) opens the built-in presenter script: the whole chain in 22 steps, each naming its persona, its page, and what to do. The walkthroughs on this site are the same chain, narrated for reading.
How the evidence is made
Every capture on these pages is produced by scripts/capture-walkthroughs.ts in the site repository: the script drives the live demo headlessly, performs each act the pages narrate (one real application from the wizard to the laboratory's submitted report, plus the seeded worked example's surfaces), asserts the surface before capturing, and records the act, the URL, and the timestamp in public/img/walkthroughs/manifest.json. An act the script cannot perform produces no capture and lists on no page. Re-running the script regenerates every screenshot at its run date, dark and light.
Where to go next
Enter the app and assume a persona from the login page's cast cards. The Applicant and the Issuing Authority are the two seats to take first.
The step-by-step operator's guide to running the whole certification chain yourself.
info@oimlsmart.org: guided walkthroughs for committees and working visits are the commonest request.
Verified 2026-09-01: the login page, the guided-demo entry, and every step surface on the seven walkthroughs was performed headlessly against the live demo by scripts/capture-walkthroughs.ts; each capture carries its assertion record in public/img/walkthroughs/manifest.json.