CHECKID · ASSURANCE & EVIDENCE

Identity Assurance & Evidence

Identity assurance is not just a score: the decision must be tied to method, source, scope, policy and traceable evidence.

SERVICEPurpose → Method → Result
TRUSTSource → Evidence → Scope
OPERATIONSSaaS · API · SDK · SLA
ASSURANCE & EVIDENCE

Evidence is a service output; assurance is a policy-driven decision

Verification → provenance → policy → decision → evidence

Assurance input

Verification results, provenance, evidence quality, holder binding and configured signals.

Policy context

The relying organisation defines assurance requirements; CheckID provides policy/decision capability only where corresponding implementation evidence exists.

Decision trace

Decisions require reason/context/version where the real contract supports them; conceptual fields are not presented as API fields.

Verification Evidence Package

Service output is modelled as transaction + service + method + source + result + evidence references.

OpenID IDA

OpenID IDA is a reference for verified claims and verification metadata; a mapping is called IMPLEMENTED only with Tier-1 field evidence.

Audit boundary

Evidence supports dispute/audit/investigation, while retention and integrity mechanisms follow the actual source/contract.

EVIDENCE PACKAGE

Keep the conceptual envelope separate from the actual data contract

Do not invent fields.

Concept Meaning Status
Service transaction Service transaction identifier Implementation where an actual ID field exists
Verification method Method used Implementation/reference according to contract
Source/provenance Data/evidence provenance Requires actual source
Result Verification result Contract-exact
Policy/version Decision context Only where implemented
Evidence references Evidence references Called a real field only when source-backed
TECHNICAL REFERENCES

Definition and standards references

A reference does not by itself mean CheckID conforms to or is certified against the document.