prooftrail

Docs Index

This is the public docs map for ProofTrail.

Start here when the README tells you the product story and you now want the next layer of proof, operating detail, and governance boundaries.

ProofTrail is evidence-first browser automation with recovery and MCP. The pages below help you evaluate that story from first run to side-road integrations without pretending the repo is a generic AI bot platform.

If you only need the fastest truthful route, stay on the first-run lane:

  1. docs/getting-started/human-first-10-min.md
  2. docs/showcase/minimal-success-case.md
  3. docs/reference/run-evidence-example.md

If you arrived here because you are evaluating a browser-evidence layer for Codex, Claude Code, OpenHands, OpenCode, OpenClaw, or another AI-agent shell, finish the first-run lane first, then continue into the second ring below.

ProofTrail proof loop ProofTrail storefront loop

The first-run UI lane stays intentionally strict: Quick Launch -> Task Center -> Recovery Center -> Flow Workshop.

Start Here

Second Ring: Ecosystem And Builder Discovery

These six pages are the current outward matrix after the first-run lane:

  1. ProofTrail for AI Agents
  2. ProofTrail for Coding Agents and Agent Ecosystems
  3. MCP for Browser Automation
  4. AI Reconstruction Side Road
  5. ProofTrail vs Generic Browser Agents
  6. Evidence, Recovery, and Review Workspace

Read them as a connected second ring, not as six co-equal first-run entry points:

Use API builder quickstart alongside that second ring when your main question is integration rather than evaluation.

Release And Publication Proof

Only open this shelf after the first-run lane and second-ring product fit are already clear:

If you want the one-screen visual before reading deeper pages, the README now also includes an ecosystem-fit map that shows the current MCP-first versus API-first split for Codex, Claude Code, OpenHands, OpenCode, and OpenClaw.

If you arrived here from a high-intent coding-agent search such as:

start with ProofTrail for AI Agents, then choose either the API builder quickstart or MCP for Browser Automation as the next layer after the first-run proof path.

Use that matrix after the first-run docs, not instead of them. It is the growth layer that explains audience fit, governed side roads, and the deepest current evidence/recovery/review loop.

Builder Entry

MCP Install Surfaces

Distribution And Integration Status

Coding-Agent And Agent-Stack Search Path

If you arrived here after searching for:

use this route:

  1. ProofTrail for AI Agents
  2. MCP for Browser Automation
  3. API builder quickstart

Truth boundary:

Product and Operator Guides

Contracts and Policies

Generated Governance Views

Maintainer Canon

Optional Localized Help

This is optional reading help for Chinese-speaking readers. It is not a second default front door and it does not replace the English canonical public mainline.

Archive Boundary

This site is open source. Improve this page.