prooftrail

ProofTrail is an auditable browser automation platform for teams that need repeatable runs, inspectable evidence, and a recoverable path when workflows break.

Docs | Quickstart | Minimal Success Case | Release Guide

> ProofTrail is for people who want browser automation to feel like an > inspectable product workflow, not a pile of one-off scripts that become > impossible to debug a week later.

How do we make browser automation reproducible, inspectable, and recoverable?

ProofTrail gives you one public mainline for running a workflow, one evidence bundle for understanding what happened, and one shared repo for the backend, web command center, automation runner, and MCP adapter that support that flow.

The canonical public mainline is:

1. run just setup
2. run just run
3. inspect .runtime-cache/artifacts/runs/<runId>/

just run is the canonical public mainline wrapper for pnpm uiq run --profile pr --target web.local.

just run-legacy remains available for lower-level workshop troubleshooting, but it is not the canonical public mainline.

• Fewer mystery failures: every canonical run writes a manifest-anchored

evidence bundle with summary, index, and proof reports instead of leaving you with scattered logs and screenshots.

• Easier recovery: the web command center, run records, and flow workshop

are built to help you inspect, replay, and repair workflows after something breaks.

• One repo, one story: backend orchestration, operator UI, automation

runner, and release proof surfaces live together, so docs and runtime truth can stay aligned.

Requirements:

• Python 3