Product

One product family.
Two working modules.

TRAILFLOW is built around Recording Agent for session capture and Trail Verifier for later review, verification, and export.

The product is oriented to workstation-based execution trails. Depending on the context, recorded sessions may support evidence review, knowledge transfer, on-the-job training, internal verification, or other structured review needs.

Explore use cases See download options

Trail Verifier – current review view aligned to the product screens

Trailflow Verifier
Preview Selected Event Artifacts Activity Summary Technical Trace
C:/TRAILFLOW/recordings/testregcode_rec_20260405_180957_Recording_2026-04-05_1809
Evidence Package Summary
Record IDtestregcode_rec_20260405_180957
Captured At2026-04-05T18:09:57Z
Captured ByUser
MachineBLACK10
Duration00:11.423
Verified Duration00:11.422
Duration Checkok
Content Integrityok
Event Chainok
Event Hash Chainok
Timeline Orderok
Evidence Filesok
Verification completed successfully.
No inconsistencies found in this package.
Recorded Actions
IDTimeAction description
100:00.141user moved mouse (103 points)
2-3-400:01.769user selected window agent_full - File Explorer
500:05.217user click with left at (1113, 1057)
6-7-800:06.950selected window Steam; user click with left
9-10-1100:09.631user selected window agent_full - File Explorer
12-1300:11.334user selected window TRAILFLOW Recorder
Preview / Actions
Open Event Screenshot Open Event Anchor Open Cover Sheet Open Package Seal Open Recording Folder
Selected Event
{
  "event_id": 8,
  "edited": false,
  "type": "mouse_path",
  "t": 37678.221,
  "path_ref": "mouse_paths/mouse_path_0008.json",
  "point_count": 53
}
summary view available
technical trace view available
per-event inspection available
verification results visible in-session
Trailflow Verifier Review and verification view

Product structure

TRAILFLOW is the overall solution.
Recording Agent and Trail Verifier are the modules.

The current screens support a practical split: one module captures sessions on the device, and the other reopens those sessions for later review, verification, and related outputs.

Module 01
Recording Agent
Recording Agent runs on the workstation and captures sessions into a local recordings library. The current interface supports starting capture, reviewing recent recordings, opening the library, and working in a local/manual mode.
  • Purpose: capture workstation sessions for later review
  • Current UI concepts: Home, Device Records Library, Start Capture, Open Recording, Open Folder, Create Video Preview, Open Video Preview
  • Session library: recordings are shown with recording name, reference, created date, and event count
  • Operation model: local device recording is supported; cloud-connected operation may be added where relevant
  • Practical fit: in many environments the aim is to work around existing systems rather than require those systems to change
Module 02
Trail Verifier
Trail Verifier reopens recorded sessions for review. The current interface presents evidence package summary data, verification status, recorded actions, activity summary, technical trace, and selected-event inspection.
  • Purpose: review, verify, and inspect previously captured sessions
  • Current UI concepts: Evidence Package Summary, Recorded Actions, Activity Summary, Technical Trace, Selected Event, Artifacts
  • Review depth: supports both higher-level summary reading and lower-level event inspection
  • Outputs: depending on version and license state, sessions may also be previewed, packaged, or exported
  • Use model: suited to later review by the same team or another reviewer

What the product supports

Capture first.
Then review according to need.

The same recorded session can serve different purposes depending on the team, process, and context.

📋
Process evidence
A recorded session may support process evidence or internal controls review where teams need more than a documented procedure.
🎓
Knowledge transfer
A real session can be reviewed step by step during handover, onboarding, or operational walkthroughs.
🧭
On-the-job training
Recorded actions and later replay can support guided learning based on actual work patterns.
🔎
Internal verification
Teams can compare expected execution with recorded execution and review where they align or differ.
🔁
Session reconstruction
Where needed, a recorded session may help revisit what happened during a particular interaction or operational flow.
🖥️
Mixed workstation environments
The approach is oriented to workstation activity, which can be useful where processes span several desktop tools or older systems.

License behaviour

The current screens already show an important split

Capture and basic review may remain available while some outputs or presentation features depend on licensing or edition.

// Unlicensed evaluation state
  • ✓Recording Agent can still capture sessions
  • ✓Trail Verifier can still open and display sessions
  • ✓Summary and recorded action views remain visible
  • ✓Verification results remain visible in the current UI
  • ~Some generated outputs may carry evaluation marking or remain limited
  • –Some export-oriented features may depend on licensed state
// Licensed state
  • ✓Capture remains available
  • ✓Review and verification remain available
  • ✓Additional output and packaging features can be enabled according to edition
  • ✓Operational use is better aligned with formal review or delivery scenarios
  • ~Exact feature scope should be stated consistently with the final pricing/download model

// Recommendation: keep licensing statements on this page consistent with the actual behaviour shown in the current Recorder and Verifier screens.

Review outputs

What a reviewed session can include

This should stay close to what is already present in the UI and only describe outputs that are actually available or clearly planned.

Evidence Package Summary
Core session metadata such as record ID, captured time, user, machine, duration, verified duration, and visible check results.
Visible in current UI
Recorded Actions
Action lists that support summary reading and deeper review of what occurred during the session.
Visible in current UI
Activity Summary / Technical Trace
Two reading modes for the same session: a more condensed operational summary and a more technical inspection path.
Visible in current UI
Selected Event inspection
Per-event detail can be inspected through the selected-event area and related artifacts.
Visible in current UI
Video preview
The Recorder screens show video preview creation and opening, indicating a presentation-oriented playback path for some sessions.
Shown in current Recorder UI
Cover sheet / package seal / export artifacts
These can stay on the product page as output concepts, but wording should remain conditional until their exact availability and edition mapping are frozen.
Use careful wording

Verification

Verification should be described carefully and concretely

The current UI already exposes check-oriented fields. The product page should describe them in a restrained way and avoid stronger claims than the implementation supports.

Content integrity
The current review screen exposes content integrity as a visible check result on the session summary.
Event chain
The current review screen exposes event chain as a visible check result on the session summary.
Event hash chain
The current review screen exposes event hash chain as a visible check result on the session summary.
Timeline order
The current review screen exposes timeline order as a visible check result on the session summary.
Duration check
The current review screen exposes duration and verified duration together with a duration check result.
Evidence files
The current review screen exposes evidence files as a visible check result on the session summary.
What this product page should and should not do
This page should define the product structure and the current module behaviour. Detailed scenario language, including compliance-heavy narratives, can live under Use Cases where the context is narrower and clearer.
Requirement-led evaluation remains relevant
Where organisations have formal or semi-formal requirements, the practical question is how far the current solution covers them, where configuration or adaptation may help, and where boundaries remain. That discussion can sit behind Contact or specific use-case paths.

Use the product page to understand the structure.

Then use the use-case pages to decide where the recorded session model fits: evidence, knowledge transfer, training, internal verification, or a more specific operational need.

Go to use cases Discuss fit