Documentation

The detail behind the workflow.

Two focused engineering guides connect the software path to its integration requirements and evidence limits. Source explanations and synthetic examples are clearly separated from executed runtime proof.

Engineering resources

Choose the question you need to answer.

Integration guide

Where does Clariva fit?

Owned execution seams, authenticated request contracts, tenant context, retries, failure handling and supported-scope checks.

Read the integration guide
Evidence guide

What can a reviewer inspect?

The versioned source walkthrough, a synthetic decision example, test matrix and reviewer acceptance checklist.

Read the evidence guide
Start from the real contract

An integration sketch is not a runnable quickstart.

The source contains a guarded request API and orchestration pipeline. A short example cannot replace its complete trust and request contract.

Confirm the current authenticated endpoint, feature entitlement, tenant setup, policy configuration, challenge lifecycle and SDK version with the engineering owner.

Public SDK contract-adapter sources are present. Current deployed interoperability is not established by this website.

Keep the evidence classes distinct

Ask what was actually exercised.

Implementation and local tests

Code inspection can establish branch ordering. Synthetic tests can exercise the configured cases. Neither establishes a current deployed customer workflow.

Deployed and customer validation

Observe the actual boundary in its environment, then have the designated reviewer assess the stated assertion. Acceptance and production authorization remain separate facts.

Discuss the scope of an evaluation