The trust map for AI-era products
Maps what your product claims, what proves it, where trust is missing or stale, and what humans or AI agents need to verify next.
$ surface report --input examples/surface-fixtures.json --format summary
Kontour Surface report surface-1777090239260
Source: kontour-surface-validation-fixtures
Claims: 4 (unknown: 1, verified: 2, stale: 1)
Surfaces: veritas.developer-proof: 1, campfit.public-data: 1,
taxes.financial-facts: 1, surface.roadmap: 1
High-impact unsupported: none
Stale: claim.campfit.registration-status
Disputed: none
No prior verification exists.
Submitted but not yet verified.
Evidence supports it. Currently valid.
Was valid. Freshness window exceeded.
Conflicting evidence or policy.
Explicitly failed verification.
Replaced by a newer verified claim.
Developer proof
Repo surfaces, policy packs, proof lanes, and evidence artifacts. Claim that code changes passed the proof required for the surface they touched.
Public data verification
Crawls, attestations, review flags, and freshness signals. Claim that a camp registration is open — with evidence from public sources.
High-stakes fact verification
Extraction, resolution, citations, and review signals for financial claims. Verify that a W2 wage figure came from a specific document line.