claims, evidence, freshness, and gaps in one inspectable shape
Every product makes claims. AI makes those claims faster, more polished, and harder to inspect. Surface gives a product one shape for the claim, the evidence behind it, the policy that decides what counts, how fresh the evidence is, and the gaps that should slow anyone down before they rely on it. Surface does not decide domain truth; it makes the trust state portable and inspectable.
$ npx surface report --input examples/surface-fixtures.json --format summary
Kontour Surface trust snapshot surface-1777090239260
Source: kontour-surface-validation-fixtures
Claims: 4 (unknown: 1, verified: 2, stale: 1)
Claim types: repo-governance.developer-evidence: 1, field-attested-records.public-data: 1,
fact-resolution.financial-facts: 1, surface.roadmap: 1
Claim Groups: 1
High-impact unsupported: none
Stale: claim.field-attested-records.registration-status
Conflicts: none
Transparency gaps: 3
What Surface answers
Example use case
A support agent says, "This provider directory listing is current." Surface turns that into an inspectable claim with a source anchor, freshness policy, last verification time, and any gap that should slow the agent down before it recommends the listing.
claim: provider directory listing is current
source: registry export · row 1842
evidence: verified 2026-06-07
freshness: recheck in 7 days
gap: phone number attestation private
action: show uncertainty beside recommendation
What Surface gives you
Inspect the trust state behind a product answer, report, recommendation, or agent output before they rely on it. Surface shows the claim, the evidence behind it, how current that evidence is, and what's still uncertain.
Emit claims, evidence, and policies from your product. Surface gives you a shared shape so the same trust state can be read by people, agents, and other systems downstream.
Manage the claims your product makes - ownership, evidence review, policies, transparency gaps, conflicts - from one workspace. Surface Console runs locally. No cloud, no login.
Trust vocabulary
Trust status model
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.
Surface Console
surface console serves a live view from
.surface/runs/latest.json.
Each new run updates automatically. No cloud, no login.
$ npx surface console
Surface Console running at http://localhost:4242
Reading: .surface/runs/latest.json
Source: latest Surface run snapshot
GET / 200 console shell
GET /api/read-model 200 current trust snapshot
GET /api/runs 200 [run-a, run-b, run-c]
───────────────────────────────
verified 8 claims
attention 2 claims
eval accepted · confidence: high
More than a status
A claim can depend on supporting claims. When an upstream claim goes stale or disputed, that state propagates to everything built on it — no silent rot.
Producers can advertise how to recheck a claim’s evidence, authority, freshness, or integrity — so a stale claim has a path back to verified instead of staying a dead end.
Beyond the human summary, an analytics format exposes evidence and gaps as queryable data for dashboards, audits, and trust intelligence.
Products built with Surface
Products built with Surface keep their own workflow vocabulary while exposing Claims, Evidence, Policies, Trust Snapshots, and Transparency Gaps in a shared shape humans and agents can inspect.
Merge autonomy for AI-authored code
Turns Repo Standards, evidence checks, boundary crossings, and readiness outcomes into Surface-backed trust state. Veritas users stay in repo-native language while downstream systems can inspect the evidence behind merge readiness.
Explore Veritas →Anything that needs product transparency
Public-data records, fact resolution, audit pipelines, fitness tracking, compliance filings, marketplace listings — anywhere a product needs to show the work behind what it asks people and agents to trust.
Build with Surface →