One walkthrough, planned to run three ways.

One source, not three separate presentations

The idea is to create the steps, explanations, media, and comprehension checks once. The run mode changes how people move through that single artifact; it does not spin up another copy for someone to maintain. When the product being demonstrated changes, there is one artifact to correct, not three decks that have already drifted apart.

One walkthrough
  — Self-guided tour
  — Presenter-led (inside your existing meeting platform)
  — Classroom projector

Building the single artifact, and switching one artifact between run modes, is planned work — not a shipped capability. It is described here so a buyer can judge the shape of the product, not because it can be run today.

The wedge · planned

Put the check where the misunderstanding happens

The differentiating idea is to place a short question, prediction, or decision point immediately after the step it tests — so the viewer has to consider the workflow, not merely click Next until the tour ends. The first planned response types are simple choice and short response. Scoring, grading, and any claim that a viewer “mastered” something are outside the initial promise.

For a skeptic: these checks are not formal assessments and do not measure mastery. They help a teacher, a presenter, or a learner confirm one concrete point before continuing. Here is the shape of one, with the authored explanation shown — not just a green checkmark:

Before publishing this schedule, what should the administrator review?

A. Conflicts and permissions
B. The page color
C. Nothing — the schedule publishes automatically

Correct: conflicts and permissions should be reviewed before anything is published or communicated.

The example above is an illustration of the format. Placing a check between two live steps, and collecting a response to it, is planned work labelled on the status matrix below.

Planned

The walkthrough should survive the room it enters

The plan is to prepare an artifact before a meeting or a class, then run it when the Wi-Fi is slow, filtered, or unavailable — essential text and checks usable without streaming a large video at every step. We will not flatten it to a bare offline promise: authoring, the first-time download, and shared response collection may still need connectivity, and any step that links out to remotely hosted media still depends on that external service. Those steps will be marked before offline use, rather than pretended to work.

How it stays accurate · planned

A polished walkthrough is useless once the product underneath it changed

The discipline that ships first is visible provenance: every published artifact should identify its source, its owner, and its last-reviewed date, and the page should never hide an old review date. Today, an author reviews the affected steps before republishing. Accuracy is a maintained state, not a one-time publishing event.

Planned drift validation

The planned validator would compare each walkthrough against its reference — expected screens, links, labels, and comprehension anchors — and place a mismatched step into a review queue instead of silently rewriting the demonstration. It flags possible drift for a human to review; it does not keep a demonstration accurate on its own.

What automation will not do

Validation may identify drift; it will not decide that a changed workflow is pedagogically or commercially correct. A human owner approves the repair. A renamed button should not leave a teacher teaching the wrong instruction, or a team presenting a workflow that no longer exists.

What early access does not do yet

demonstration.software is not a finished demonstration platform today. The three runnable modes, external authoring and publishing, embedded comprehension checks and response review, offline artifact playback and synchronisation, drift validation, viewer-response reporting, shared libraries and approvals, district administration, custom domains and white-label operation, and any payment or renewal are planned rather than available.

There are no district names, customer quotes, adoption numbers, or performance metrics on this page, because none exist yet and none may be invented. There is no live checkout and no automatic conversion to a paid plan.