TTrustAccept
Public documentation

Authorization, enforcement, and evidence—kept distinct.

These public documents describe the product contract and claim boundaries without publishing credentials, private deployment configuration, customer data, or proprietary operating details.

Evidence

Wire Evidence

Exact request/response byte fingerprints, signed manifest, evidence chaining, verification, and scope limits.

Machine-readable

Wire Evidence schema

Public JSON Schema for the signed manifest shape.

Trust posture

Security

High-level secure-by-design, disclosure, and deployment-boundary statements.

Distribution

Marketplace paths

Scoped program and partner-review routes.

Canonical product contract

Approval records accountability. A separate, short-lived authorization grants exact target authority. The production execution boundary must verify that authorization and reject material mutation, expiry, revocation, or replay. Signed receipts preserve evidence of the governed path.

Not claimed by default
  • No vendor certification or endorsement.
  • No proof of target enforcement unless the target-side verifier is configured and tested.
  • No proof of downstream completion from a decision receipt alone.
  • No bypass resistance while alternate privileged routes remain.
  • No custody claim for evidence not retained under the customer’s approved process.