Spotlight walk

Fresh application checked against requirements

From the order rule to recorded decisions

What you are looking at

Audit log
events.yaml
Records
12
Clock context
Mixed fixture and initialization clocks. Wall-clock duration is not meaningful for this capture. Follow record order and observed values.
Event processor
demo.authoring.generated.OrderProcessor — the sender's claim at capture, not paired against this log
Steps
5 steps
Walk
by the assistant
Walk saved
2026-11-01T14:45:04.035716Z
Reel recorded
2026-11-01T14:45:20.683668Z

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.

Public demonstration review: the embedded frames were inspected before publication. They show synthetic example data and isolated workspace paths; no credentials or customer data were observed. The images remain unchanged. This review is not automatic redaction.

Step 1 of 5

Calculate the amount: the input records 10 units at 1200 pence. The calculation records 12000 pence (£120).

Step 1: Calculate the amount: the input records 10 units at 1200 pence. The calculation records 12000 pence (£120).
  1. Quantity10; price1200p; limit10000p
  2. Recorded value12000p

Step 2 of 5

Apply the rule: this £120 order exceeds its £100 limit. The application records accepted=false and REJECTED.

Step 2: Apply the rule: this £120 order exceeds its £100 limit. The application records accepted=false and REJECTED.
  1. Above the limit: accepted=false
  2. REJECTED

Step 3 of 5

Repeat the same input: the next event records the same values and the same refusal. This checks this repeated fixture, not every possible state.

Step 3: Repeat the same input: the next event records the same values and the same refusal. This checks this repeated fixture, not every possible state.
  1. Same input, same recorded REJECTED

Step 4 of 5

Change the supplied limit to £150: the same £120 value is now accepted, as the requirement specifies.

Step 4: Change the supplied limit to £150: the same £120 value is now accepted, as the requirement specifies.
  1. The supplied limit is now15000p
  2. ACCEPTED under the higher limit

Step 5 of 5

Check equality: a £120 value against a £120 limit is accepted. Invalid inputs are checked separately before dispatch; their refusal is a harness assertion, not a missing-log inference.

Step 5: Check equality: a £120 value against a £120 limit is accepted. Invalid inputs are checked separately before dispatch; their refusal is a harness assertion, not a missing-log inference.
  1. Equality satisfies value <= limit
  2. Boundary case ACCEPTED

The evidence behind this reel

Bundle
authoring-investigation.fexp
Identity
sha256:bdc1a0e9e18297791776aab7abcbe9645a8271289c1d143a6e5618077f6e06b9

Open this bundle in the Fluxtion Audit Log Analyser to reopen and step through the saved investigation against the captured log. The application runner, not the Analyser, executes input replay.

What this bundle does and does not evidence

From the sender

Actual new four-processing-node application, not the earlier reused order sample. Original audit contains12records:7valid Order events plus lifecycle/clock records. Four logged node IDs appear in the …

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

Recorded by the Fluxtion Audit Log Analyser.

Discuss a pilot on your workflow.

Bring one process you need to explain. Agree the checks, run the application and examine the evidence together.

Discuss a pilot with Telamin