prooftrail

Public Surface Policy

ProofTrail keeps one public storefront story.

That story is made of:

• the GitHub README as the conversion page
• docs/index.md as the public docs map
• a small number of proof and release pages that support evaluation
• a small number of side-road and comparison pages that explain MCP, AI reconstruction, and category fit without pretending they are the default road
• a small current outward matrix that covers audience fit, coding-agent fit, MCP, AI reconstruction, alternatives, and the evidence/recovery/review loop

Public-facing guidance must do three things at the same time:

1. explain the canonical public mainline
2. show where proof comes from
3. avoid mixing current guidance with archive, planning, or rehearsal material

Supporting truth surfaces that do not act as storefront claims:

• DISTRIBUTION.md for current distribution and publication status
• INTEGRATIONS.md for official-vs-repo-native integration boundaries
• docs/release/publication-receipt-bundle.md for live receipts vs review receipts vs contract-only later lanes
• docs/reference/mcp-distribution-contract.md for the MCP package/install contract
• skills/prooftrail-mcp/SKILL.md for the generic install skill consumed by agent shells

If a document cannot help a first-time evaluator answer one of the visitor four questions, it should not be treated as a storefront surface.

The current outward growth matrix is:

1. docs/how-to/prooftrail-for-ai-agents.md
2. docs/how-to/prooftrail-for-coding-agents.md
3. docs/how-to/mcp-quickstart-1pager.md
4. docs/how-to/ai-reconstruction-side-road.md
5. docs/compare/prooftrail-vs-generic-browser-agents.md
6. docs/how-to/evidence-recovery-review-workspace.md

Those six pages explain audience fit, coding-agent fit, side-road value, alternatives framing, and the deepest current evidence/recovery/review loop.

The current storefront landing seeds include:

• docs/getting-started/human-first-10-min.md
• docs/reference/run-evidence-example.md
• docs/reference/recovery-safety-policy.md
• docs/reference/hosted-review-workspace-mvp.md
• docs/reference/final-closeout-wave5.md
• docs/showcase/minimal-success-case.md
• docs/how-to/prooftrail-for-ai-agents.md
• docs/how-to/prooftrail-for-coding-agents.md
• docs/how-to/mcp-quickstart-1pager.md
• docs/how-to/api-builder-quickstart.md
• docs/how-to/ai-reconstruction-side-road.md
• docs/how-to/evidence-recovery-review-workspace.md
• docs/how-to/template-exchange-mvp.md
• docs/compare/prooftrail-vs-generic-browser-agents.md

Those pages should stay cross-linked and truthful:

• the outward matrix explains audience fit, coding-agent fit, and current product shape
• the API builder quickstart explains direct integration
• the README and docs index decide the reading order

This site is open source. Improve this page.