Trust surface 01
Evidence References
Public-safe references to the existence, class, lineage, issuer, time, and integrity posture of evidence without exposing private evidence content.
Review evidence architectureOpen Trust Surface
Evidence, proof, passports, badges, and bounded verification
KSAI Trust exposes public-safe status and verification without exposing private evidence, payloads, secrets, policy internals, tenant authority, or protected runtime controls. Every trust object has a defined issuer, subject, scope, policy, version, expiry, revocation, and claim boundary.
Trust product surfaces
Each trust object answers a different question.
The interface prevents Evidence, Proof Receipt, Passport, Badge, Verifier, SVER, and Billing Eligibility from being presented as interchangeable labels.
Trust surface 02
Proof Receipt
A bounded record that an approved execution and evidence evaluation reached a defined proof decision under a specific contract and verifier policy.
Review proof-only surfacesTrust surface 03
AI Passport
A portable identity and status record for a model, agent, tool, provider, or packaged capability, including provenance, version, scope, expiry, and revocation references.
Explore passportsTrust surface 04
Trust Badge
A visual projection of bounded status that always links back to the signed record, issuer, scope, expiry, and verifier rather than acting as a standalone certification.
Explore trust badgesTrust surface 05
Verifier
A public-safe interface for checking signed status, scope, bounded claims, expiry, revocation, and proof references without gaining evidence access or runtime authority.
Open verifierTrust surface 06
SVER and Commercial Qualification
A governed determination that remains separate from technical success, public verification, activation authorization, qualified outcome, value claim, and billing eligibility.
Understand decision separationClaims boundary
The interface states what a trust status does—and does not—mean.
This protects customers from overclaiming, protects KSAI from accidental certification language, and makes disputes traceable to the exact record and decision policy.
Boundary 01
Evidence is not proof
Evidence supports evaluation. It does not automatically establish a proof decision, qualified outcome, or public claim.
Boundary 02
Proof is not public disclosure
A Proof Receipt can exist while the public projection exposes only a safe subset of status and references.
Boundary 03
Verification is not approval
The verifier checks a signed bounded record. It does not grant legal approval, runtime authority, or institutional activation.
Boundary 04
SVER is not billing
SVER qualification can be necessary for a value claim while billing remains blocked by entitlement, contract, authorization, or dispute conditions.
Boundary 05
Badge is not certification
The badge is a visual status projection whose meaning depends on issuer, scope, policy, version, expiry, revocation, and verifier context.
Boundary 06
Public trust is not tenant access
Public surfaces never grant access to private evidence vaults, secrets, payloads, policy internals, or protected operating consoles.
Verifier journey
Verification is fast to use but strict in meaning.
- 01Submit or resolve a record
Use a verifier token, passport identifier, badge link, signed record reference, or supported trust address.
- 02Validate integrity and issuer
Check signature, issuer, status source, record version, expiry, revocation, and supported policy profile.
- 03Read bounded status
Display only the allowed scope, status, claims, evidence references, limitations, and unresolved conditions.
- 04Preserve decision boundaries
State clearly which later decisions—SVER, activation, qualified outcome, value claim, or billing—are not established by verification.
Public-safe by design