Purpose
Route assurance, exceptions, review and decisions through policy.
PLATFORM · CHECKID
Risk & Policy
Route assurance, exceptions, review and decisions through policy.
CAPABILITYInput → Processing → Output
CONTROLPolicy · risk · standard
EVIDENCEResult · trace · scope
PLATFORM
Risk & Policy
Route assurance, exceptions, review and decisions through policy.
Trust boundary
Capability is published only within source/evidence scope.
Developer integration
SDK · REST API · evidence contract
↗TECHNICAL REFERENCE
Decision architecture: signals, policy and evidence
Signal → context → rule → assurance requirement → decision → action → evidence
A signal is not a decision
Document results, authoritative-source responses, biometric/PAD outcomes and transaction context are signals. Public documentation does not describe a single signal as an identity approval without a corresponding decision policy.
Policy context
Policy should be bound to transaction purpose, available methods/evidence and the required assurance context. Numeric thresholds are published only when a policy or benchmark source exists.
Outcome and reason
An enterprise decision model should distinguish outcome, reason, required next action and evidence references. If the implementation does not publicly expose reason codes or policy versions, the publication remains explicitly conceptual.
Lifecycle governance
Draft/review/approval/effective/superseded/retired is a governance reference model, not an asserted CheckID workflow unless supported by an administrative-policy source.
Change control
Bank and government deployments need traceability for actor, policy version/effective time, approval and impact on new transactions. Maker-checker and rollback are not claimed without evidence.
Audit linkage
The architectural objective is to connect evidence source → signal → policy context → decision → action. Where the implementation schema is not public, the evidence publication records that limitation rather than inventing fields.
DECISION ARCHITECTURE
Signal → policy context → decision → action → evidence
Risk/Policy is described through explicit decision layers rather than a generic “AI risk engine”.
Signal
Document/eID/biometric/source results and process metadata are inputs; a signal is not a decision.
Policy context
Use case, required evidence and assurance requirements are configuration/contract matters; thresholds/rules are public only when sourced.
Decision
Outcome/reason/provenance use only taxonomies exposed by actual sources; no invented approve/reject model.
Evidence
Decision correlation to process/source/result/policy version appears only when the actual evidence model supports it.