Spotlight walk

Reusable libraries checked together

One workflow - accepted, refused and recovered

What you are looking at

Audit log
events.audit
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
com.example.reuse.generated.OrderReleaseProcessor — the sender's claim at capture, not paired against this log
Steps
5 steps
Walk
by the assistant
Walk saved
2026-11-01T14:17:37.893113Z
Reel recorded
2026-11-01T14:18:48.602181Z

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

What you see: separate value, stock and risk checks feed one decision. This normal £60 order is accepted within its £100 limit.

Step 1: What you see: separate value, stock and risk checks feed one decision. This normal £60 order is accepted within its £100 limit.
  1. All required checks agree; ACCEPTED

Step 2 of 5

What changes: a £120 order exceeds the same £100 limit. The recorded result is REJECTED_LIMIT even when stock and risk pass.

Step 2: What changes: a £120 order exceeds the same £100 limit. The recorded result is REJECTED_LIMIT even when stock and risk pass.
  1. Value12000p exceeds limit10000p
  2. The refusal is recorded as output2

Step 3 of 5

A different reason: four units requested, only three available. The value passes its limit, but stock refuses release.

Step 3: A different reason: four units requested, only three available. The value passes its limit, but stock refuses release.
  1. stockAvailable=false
  2. REJECTED_STOCK

Step 4 of 5

A deliberate dependency failure: riskStatus is UNAVAILABLE. The native test separately verifies the exception and unchanged output count; silence alone is not proof.

Step 4: A deliberate dependency failure: riskStatus is UNAVAILABLE. The native test separately verifies the exception and unchanged output count; silence alone is not proof.
  1. Synthetic risk check is unavailable

Step 5 of 5

Verify the next request: the check clears and the workflow accepts it. Output count reaches6 after seven scenarios, one of which threw.

Step 5: Verify the next request: the check clears and the workflow accepts it. Output count reaches6 after seven scenarios, one of which threw.
  1. The next risk check clears
  2. ACCEPTED; outputCount6

The evidence behind this reel

Bundle
library-workflow-investigation.fexp
Identity
sha256:252f7c5fad7e7049f59aa3cb244a20c44ae4528c0039659e151649640cd64180

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 current synthetic workflow: two separately packaged libraries, seven processing nodes plus the event vertex. No invented earlier defect or corrected revision. Native harness passed7scenarios:6d…

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