Methods Hub
Verification methods matter because CITAQ is only credible if people can inspect how claims become evidence-bound public outputs.
This hub gathers the method-facing routes behind the public platform: verification model, evidence model, claim verification logic, hash verification, badge behavior, and the route patterns that turn scattered support into inspectable trust surfaces.
It exists because the architecture does not describe verification as a black box. It describes layered method choices, proof relationships, and public interpretation rules that should stay visible throughout the route graph.
It connects platform detail, documentation, resource explainers, and trust interpretation around how verification actually works.
Method Layers
The verification-method routes this hub should connect
The verification model explains how product assertions become governed verification outputs instead of isolated marketing text.
The evidence model matters because stronger and weaker support should not be flattened into one undifferentiated proof bucket.
Claim verification is where evidence and policy meet to determine what the system can responsibly expose.
Hash verification matters because public trust surfaces need inspectable integrity behavior rather than hidden assumptions.
Badge states need method clarity so status labels are interpretable and not mistaken for generic trust theater.
Proof-oriented routes explain how public verification points back to underlying evidence and method choices.
Priority Routes
Open the main verification-method pages
Open the platform route for the system-level verification model behind public outputs.
See the route that explains how support is structured before it becomes public verification material.
Inspect the layer where claims are evaluated against evidence and policy conditions.
Open the integrity route for how evidence and outputs stay tied to inspectable cryptographic behavior.
See the route for how public verification states get expressed on reader-facing surfaces.
Move into the route for evidence-bearing objects that keep verification attached to real support.
Supporting Knowledge
Use the adjacent docs, explainers, and trust routes
Use the documentation route for more direct method explanation.
Open the docs route for the support-structure side of verification.
See the public vocabulary of state labels behind verification badges.
Read the evergreen explainer for the integrity side of the model.
Use the explainer route for a clearer public description of support quality differences.
Open the trust route that explains how these methods should be interpreted on public pages.
Connected Routes
Keep moving through the adjacent proof and trust clusters
Move into the evidence-governance hub behind claim support, lifecycle, and revocation.
Open the standards hub for identifiers, credentials, provenance, and revocation layers tied to method choices.
See how these methods shape real public-page behavior and interpretation.
Open the API-facing hub for machine-readable access to verification outputs and evidence-oriented routes.
Use the reference hub for terms, badge states, identifiers, and route maps tied to verification methods.
Browse the wider methodology graph through the verification directory system.
Next Step
Open the evidence-and-claims hub if you want the support model behind these methods.
Verification methods explain how the system works, while the evidence hub explains what those methods are operating on and how claim state changes over time.