Buyer resource · JSON and CSV
Machine-Readable Proof Ledger
A structured map from public claims to evidence routes, evidence types, maturity status, related services, and confidentiality boundaries.
Who should use this
Technical evaluators, procurement teams, AI agents, crawlers, and buyers who want to distinguish method proof from approved outcome evidence.
Problem it helps evaluate
Marketing claims become difficult to verify when evidence, status, and boundary notes are distributed across many pages.
Version: 1.14.0 · Modified: 2026-06-17 UTC
How to use it
- Start with the human-readable Proof page.
- Use JSON for programmatic inspection or CSV for spreadsheet review.
- Follow evidence URLs to the narrower route.
- Check maturity and boundary fields before repeating a claim.
- Do not interpret public-safe templates as approved client outcomes.
What it does not prove
The ledger is not certification, an independent audit, a guarantee, or authority to widen claims.