Authenticity
Confirms origin and integrity; it does not automatically guarantee current validity.
Authenticity · current validity · revocation · Candeia internal documents
Document verification
Verifying a document means confirming only what is necessary: who issued it, whether it has been altered, its type and version, and whether it remains valid. This does not require copying the person’s entire identity, and GOV does not replace the competent official registry.
In brief
The essentials
Verification should answer the necessary question and nothing beyond it. A verifier can confirm authenticity, validity or a specific attribute without exposing the entire document, and must distinguish an authentic document from a document that is still in force.
How it works
Minimum verification flow
01RequestThe verifier defines which document or attribute needs to be confirmed.
02ProofThe presentation supplies only the data and evidence necessary for the purpose.
03ValidationIssuer, integrity, linkage, version and status are checked where applicable.
04ResponseThe result communicates only what is necessary, indicating limits and the time of the query.
Principles
What makes a document trustworthy
Current validity
Indicates whether the document is within its valid period/status when that concept applies.
Revocation
Makes it possible to detect suspension, cancellation or replacement.
Minimum disclosure
The response need not return all of the holder’s attributes.
Source
Status comes from the competent module, not from a copy kept by GOV.
Challenge
A failure or discrepancy must be capable of being routed to the responsible channel.
Representation and source
Verify without creating a universal profile
The architecture should favour minimum requests and identifiers appropriate to the context, preventing each verification from becoming unrestricted correlation across services.
In practice
What a verification response should say
A good response distinguishes “valid signature”, “issuer recognised internally”, “document currently valid” and “attribute confirmed”. These statements are not interchangeable, and none of them, by itself, proves acceptance by an external entity.
Limits
Protections and limits
GOV does not receive or store a personal document for “testing” on this static page.
An internal verification result does not prove acceptance by third parties.
A QR code that opens a page is not, by itself, sufficient cryptographic or legal proof.
Constitutional basis
Read the full text
Consult the related provisions in the Proposed Constitution.
Keep exploring
Related pages
How this page connects to Sistema Candeia
FunctionVerification confirms technical evidence associated with an institutional source; it does not turn a nonexistent document into a valid act.
PrivacyThe verifier should request only what is necessary and avoid public exposure of unnecessary attributes.
Current stateThe verification interface exists on the portal; institutional validity depends on the issuing source and the chains that have actually been activated.