Evidence Hub
Evidence and claims are the operating core of CITAQ, because public verification only works when assertions stay tied to inspectable support.
This hub gathers the routes that explain how CITAQ models evidence, separates stronger and weaker support, governs claim lifecycle, and represents expiry or revocation when the public trust surface changes.
The architecture source treats these as real system layers. Evidence levels, evidence-bound claims, proof objects, expiry, and revocation are not side notes. They define whether the public route graph remains defensible.
It is for readers who need to understand how claim support is modeled, how status changes over time, and how trust output stays connected to underlying proof.
Core Concepts
The evidence and claim layers this hub should connect
Evidence levels explain why different support sources should not be treated as equal in public verification.
Claims only become durable public assertions when they can point to inspectable supporting artifacts or records.
Claims need rules for creation, change, downgrade, retirement, and public-state transition over time.
Proof objects are the concrete evidence-bearing references that keep verification pages from collapsing into vague promise language.
Time-sensitive support needs explicit recency handling so stale artifacts do not silently keep live claims afloat.
A credible public trust system must show changed and withdrawn states, not only positive ones.
Priority Routes
Open the main evidence and claim pages
Inspect the infrastructure route for how support quality affects claim interpretation.
See the layer where public assertions get evaluated against evidence state.
Open the route for how claims are created, changed, downgraded, or retired over time.
See how evidence-bearing objects anchor verification to concrete support.
Inspect the route for how time-sensitive support changes what can still be shown publicly.
Open the route that explains state changes, withdrawn trust, and public status transitions.
Supporting Knowledge
Use the adjacent docs, resources, and trust pages
Use the documentation route for model-level explanation of evidence structure.
Open the dedicated hub for verification model, evidence model, hash verification, badges, and proof-oriented method routes.
Open the docs route when you need a more direct explanation of evidence-level behavior.
Use the reference route for the public vocabulary of evidence-bearing inputs.
Open the claim-types reference for the public vocabulary of assertion categories.
Read the evergreen explainer for how operators should prepare support before making stronger claims.
See how evidence quality influences the public interpretation of claims on trust surfaces.
Connected Systems
Evidence and claims should stay connected to adjacent clusters
Public interpretation breaks down when trust pages do not explain the support model, expiry behavior, and status logic underneath them.
Credentials, DID, GS1, C2PA, and status lists matter here because they can shape how evidence and status become more machine-readable.
Verification model, evidence model, hash integrity, and badge semantics need their own connected public hub so method discovery is not trapped inside leaf pages.
Large public systems need indexing surfaces so evidence topics remain connected to docs, resources, standards, and verification pages.
Next Step
Open the standards hub if you want the machine-readable proof layer next.
Evidence and claims define the support model, while standards routes explain how identity, credentials, provenance, and revocation strengthen public verification.