Authoritative Source
Identity attributes come from source-controlled integrations where confirmed.
VIETNAM · CHECKID
Authoritative Identity Data
Prefer authoritative-source attributes over image-only inference.
PURPOSEScenario-specific
CONTROLSource · policy · standard
OUTCOMEDecision · evidence
VIETNAM DIGITAL IDENTITY
Authoritative Identity Data
Prefer authoritative-source attributes over image-only inference.
Consent / Federation
SSO / ShareInfo patterns are separated from verification evidence.
RAR/C06 fabric
Source → CheckID → RP
↗SOURCE-BOUND REFERENCE
Authoritative data: distinct from document-derived data
Source → Scope → Evidence → Limitation
Source of truth
An authoritative source/system is responsible for data within its service scope; CheckID acts as a consumer/orchestrator and does not become the source of record.
Provenance
Attributes retain source class and verification context so authoritative-source-derived data is not mixed with OCR/document/user-declared data.
Purpose and authority
Query rights depend on purpose, authority, authorization/consent and service agreement.
Freshness
Data freshness comes from source/response semantics where available; does not invent a “freshness” period.
Conflict
Where source and document data conflict, outcome follows policy/process; the website does not automatically label the case fraud.
Audit
Correlation and source/result context should be sufficient to explain a decision where the implementation exposes it.