SECURITY AND TRUST BOUNDARY
Revive should never hide how it reached a verdict.
We separate observed trace data, configured source assertions, derived provenance, and deterministic policy findings.01
Tenant isolation
Hosted traces are scoped to a workspace and project with row-level security.
02
Semantic refusal
Duplicate IDs, dangling references, invalid timestamps, oversized traces, and excessive dependency depth are rejected.
03
Deterministic verdicts
Language models do not decide whether an evidence policy passed or failed.
04
Reproducible evidence
Every result records its engine version, generated time, and SHA-256 input hash.
05
Bounded ingestion
Trace payloads are limited to 2 MB and authenticated with session or project-scoped API keys.
06
Explicit source assertions
Trust, ownership, and challenge status remain visible inputs rather than hidden model judgments.
CURRENT LIMIT
Revive is not a truth oracle.
Source trust and challenge status must come from customer systems or configured resolvers. Revive proves how those inputs affect beliefs and decisions.