Frame it in one breath: the OIML-CS certification chain, running as software, with the committee's text still the source. Say the honesty rules up front: the demo is simulated, the futures are labeled, and every claim on every slide links its proof. If the room has no network, every demo moment below shows its dated capture instead.

Say it kindly and mean it: the current system works, and the people in it are careful. The problem is structural: every hand-off re-keys information, and every re-keying is a chance to drift. No blame in this slide; the room should recognize their day, not feel criticized.

Thirty seconds on the whole picture: the Recommendation model is the single source at the center; the platform derives the workflow surfaces from it; the services (identity, vocab, AI, status) stand beside it; member instances run the same codebase in their own postures; the public surfaces (register, verification) answer without an account. Do not read the diagram box by box; the derivation arrows are the message.

The tour's first live moment. Click into the wizard as the Applicant and dwell on the instrument step: the form was not designed by a programmer, the R 60 model authors it, clause and all. No network: the dated capture shows exactly that step. The full narration is walkthrough 01.

Live: Sign in as the Applicant, open the new-application wizard, pick R 60, and watch the instrument step render from the model. Fallback: the dated capture on the slide (2026-09-01).

Advance: The submit lands the story on the authority's desk, and the application's page never stalls there: its waiting card's Advance control drives the authority's real act — "the Issuing Authority reviews the application and requests the samples" — the audit trail naming you, the presenter, with the role advanced.

The same submit from the other side of the desk. Live: the Issuing Authority account, the review queue, and if the room wants it, the reject-with-reason (the instance resets nightly, so perform it freely). The evaluation project is the word to land: the shared dataspace, not an email thread.

Live: Sign in as the Issuing Authority and open the review queue; the waiting application is flow 01's submit, seen from the other side. Fallback: the dated capture on the slide (2026-09-01).

Advance: Once the samples are requested, the review waits on the applicant's shipment; the review page's Advance control drives it — "the applicant ships the requested samples" — and the authority's story continues from the same screen.

The metrologist's slide. Live: the laboratory console, the model-driven run; the point is that the bench software reads the same model the Recommendation authors, so two laboratories cannot run two different R 60s. The report is generated from the captured evidence, which ends transcription at the hand-off.

Live: Sign in as the Test Laboratory, open the accepted request, and step the model-driven test run at the bench. Fallback: the dated capture on the slide (2026-09-01).

Advance: If the samples still sit with the authority, the request page's Advance control drives the custody move — "the Issuing Authority dispatches the samples to the laboratory" — and the run starts. For the authority-watching lane, the project page carries the counterpart: "the laboratory completes the work and returns its test report".

Two acts, two truths: the platform computes the verdict from the model, and the authority decides; the certificate is data, signed, and the register is public. Live: open the register with no account at all. Governance-sensitive rooms: this slide is where you say the legal acts never moved.

Live: Open the public register (no sign-in): the BIML-registered certificates, browsable by anyone. Fallback: the dated capture on the slide (2026-09-01).

Advance: A stalled review period closes live from the participants' side: the project's Advance control resolves the open threads and takes the authority's decision — "the Issuing Authority resolves the review threads and accepts the test report" (the evaluation report's own beat reads the same way).

The payoff slide, and the 5-minute cut's second live moment. Verification is the surface every constituency shares: the manufacturer's customer, the inspector, the member state. Live: the verify page, the demo certificate number, the ACTIVE verdict. If you show only two live moments all day, make them s04 and this one.

Live: Open the verify page (no sign-in) and enter R60/2021-A-EX1-26.01: the verdict, the registration, the revocation and suspension checks. Fallback: the dated capture on the slide (2026-09-01).

Advance: The journey's spine never waits on the authority in a demo: the application page's Advance control drives the receipt and the acceptance — "the Issuing Authority receives the samples and accepts — the Evaluation Project opens".

The foundation claim: the model is not a copy of the Recommendation, it is derived with clause-level provenance and the text stays the gate. The numbers on this slide come from the model itself. Two section pages carry the depth; link them, do not summarize past them.

The future, labeled as the future. One minute, no more: the twin is where continuous compliance comes from, and the slide says plainly that it is SMART+. Committee members should never be able to say the tour blurred vision into present.

The bridge between present and future: the SMI Simulation is live and carries the classroom and the demo, while its production role is roadmap. Say both halves exactly that way.

One message: the certificate stops being a picture of a decision and becomes the decision, signed. The export formats answer the interop question before it is asked; s15 opens that map fully.

Short and practical: one account, per-organization approval, and the federation posture for members who must keep identity in their own custody. The live service page carries the performed evidence.

The quiet slide that makes verification work: keys and standing, public, anonymous to resolve. The negative proof is worth saying aloud; it is the program's honesty doctrine in miniature.

The interop position in one slide, for the members who arrive worried about a walled garden: the map is public and boring on purpose. Name the standards slowly; they are the answer. The page carries the plane-by-plane table and the fidelity bookkeeping of every export.

The sovereignty and cost answers land here: custody never has to move, and the minimal posture is one service-class deployment. The two pilots are live; the links are on the slide for the room to try later. The matrix page is the quotable reference.

The governance posture, said plainly and without haste: the committee adopts text, the model derives, the platform computes and records, the authorities decide. Gradualness is a design property, not a promise. This slide and s19 are the two the committee should remember.

Adoption as a ramp, not a jump: read, reproduce, pilot, self-host, each step optional and reversible. The entitlement matrix is the single source every page quotes; do not paraphrase it from memory, open it if asked.

Close on the two asks, slowly: pilot members (name the shape: one Recommendation, one authority, one laboratory) and feedback (the address is on the slide). Point at the one-pagers for the members who were not in the room. Then stop talking and take questions.