This is a saved investigation, not application execution. Mixed fixture and initialization clocks: displayed date ranges are not meaningful elapsed durations. Follow record order and observed values.

Spotlight walk

replay-repeat

Replay Repeat

What you are looking at

Audit log: events.audit
Records: 14
Time span: 2023-11-14 22:13:20.000 → 2026-11-01 18:37:18.900 UTC
Event processor: com.example.reuse.generated.OrderReleaseProcessor — the sender's claim at capture, not paired against this log
Steps: 2 steps
Walk: by the assistant
Walk saved: 2026-11-01T18:44:40.858375Z
Reel recorded: 2026-11-01T19:07:15.968908Z

Every frame below is the analyser's own window, painted as it stood at that step. The evidence behind them is named at the end of this page.

Machine paths in this page's text are replaced with ‹path removed›. The frame images are screenshots of the analyser's window and are NOT redacted: they may show local file paths.

Step 1 of 2

Replayed captured inputs reproduce acceptance at 10000p.

Replayed captured inputs reproduce acceptance at 10000p.

Step 2 of 2

Replayed inputs reproduce the second boundary at 6000p.

Replayed inputs reproduce the second boundary at 6000p.

The evidence behind this reel

Bundle: replay-repeat.fexp
Identity: sha256:9b1dcdf50439130d5fc3ad26f31238720726122612ea250a194787739a86441b

Open this bundle in the Fluxtion Audit Log Analyser to reopen this saved walkthrough yourself against the real log.

What this bundle does and does not evidence

unsigned: verification detects a changed member; it does not authenticate the sender
no replay: this bundle shows an investigation; it does not reproduce or fix it

From the sender

Synthetic local demonstration. Saved investigation, not execution replay. Source and runner supplied separately. Unsigned member hashes establish integrity only. Mixed initialization and fixture clock…

The sender's words, not a fact about the evidence.

Recorded by the Fluxtion Audit Log Analyser.