SentraMind

Explainer

Scenario replays and the honesty band

A replay steps through a specified workflow. The band on the page says whether that workflow is current behaviour or a roadmap specification.

Pace is the feature, and the band is the claim

A replay walks a published case one step at a time, so a meeting can stay on a single beat instead of skimming a whole timeline. The words on the steps are the case’s own words. The new thing on the page is the pace, and the honesty band above the steps. The band says whether the workflow is behaviour the current POC can exercise or a specification for a module this build does not contain.

Platform Core and GenAI Prompt DLP are the two crews whose cases take the first band. That band points at a path a reviewer can run, including the prompt sandbox where the decision is the same kind of decision. Every other case takes the second band, which says the steps are the specification the roadmap holds the module to: actor, trigger, ordinary path, exceptions, end state, and the evidence the design expects. The second band describes a specification, never a recording of software running.

The frame has to agree with the band

The frame around a current-behaviour case is the ordinary frame. The frame around a specification case is marked as unbuilt, so a dashed edge and the band say the same thing. Colour is not the only signal. A presenter who covers the band and leaves the animation running has hidden the only sentence that tells the audience which kind of case this is.

The band is recomputed from the case, not remembered from the previous one. Ten cases share the page. Two of them are the crews available for this POC. The others stay specifications until a promotion, which takes evidence and an owner decision rather than a polished walkthrough. Order in the picker is a reading order and implies no delivery date.

Motion is optional, and the page still reads

Play advances the step on a timer, and it does not start by itself. Pause stops it. Previous, next, and restart are there for a group that wants to talk. Under reduced motion the play control is omitted, not merely disabled, and the steps remain on the page in text. Motion is one way to keep a meeting together, and the case reads without it.

With scripts unavailable, the steps, the outcome, and the evidence list are already in the document. The cursor treatment that dims later steps is an enhancement for a scripted page, and the dimming uses a readable ink so a later step is still text. The no-script document shows the whole case, including how it ended and what evidence the case says it left. A replay that failed closed into an empty box would be a video. This one is a document that can also move.

Changing the case resets the step and the band

Choosing another case returns the walk to the first step and stops play. The band, the frame, the outcome, and the evidence list all belong to the newly selected case. A replay that kept the previous band after the case changed would be describing the wrong workflow, which is the failure this control exists to prevent.

The outcome and the evidence list appear with the last step, because that is when the case has finished saying what it came to. Moving back into the middle of the timeline leaves those closing blocks for the end again. A reader who needs them without stepping can use the no-script document, or can jump to the end. The dossier for the same case remains the long form.

What a replay must not be asked to prove

A current-behaviour replay can send the audience to a synthetic sample they can run. Pacing it measures no latency, names no customer, and shows no live fleet. The stand-in labels on software keys, the software CA, and the simulated inventory still apply to anything the sandbox actually enforces.

A specification replay must not be narrated in the past tense as something the product did. The band’s sentence is the one to read aloud before the first step. A team that wants a result picks a case whose band says the workflow can be exercised, runs the sample, and writes down the action and the limit together. The other cases are for agreeing what a future module would have to show. They are not a result this evaluation can sign.

How to read this

How to read this
Read it asWhich meansDo not read it as
The band Says current behaviour or roadmap specification Decoration
Reduced motion No play control; the steps stay readable A blank page
Scripts off Steps, outcome, and evidence list remain A video with nothing behind it

Product statements on this page follow the POC maturity ladder. A coming-next or roadmap item is not available for the current evaluation.