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

Example 06 · Original: captured order sequence

Original: captured order sequence

What you are looking at

Audit log
events.audit
Records
14
Recorded timestamps — mixed clock sources, not elapsed duration
2023-11-14 22:13:20.000 → 2026-11-01 18:37:18.829 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:38.337819Z
Reel recorded
2026-11-01T19:07:15.327695Z

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

Original build accepts equality at 10000p.

Step 1: Original build accepts equality at 10000p.
  1. Original build accepts equality at 10000p.

Step 2 of 2

Original build accepts the second boundary at 6000p.

Step 2: Original build accepts the second boundary at 6000p.
  1. Original build accepts the second boundary at 6000p.

The evidence behind this reel

Bundle
replay-original.fexp
Identity
sha256:1531f33177d53ed6fd8792bb3a073dc78b8a3436375e0c35ae5c8f840b98aa98

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

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.