Standards Hub
Standards matter on CITAQ where machine-verifiable trust has to stay inspectable, bounded, and connected to evidence.
This hub collects the standards-aligned parts of the public platform: verifiable credentials, DID and SSI concepts, GS1 Digital Link, C2PA provenance, status-list revocation, and the integrity controls that help public verification stay machine-readable.
The goal is not standards theater. These routes exist because CITAQ operates at the boundary between evidence, public trust surfaces, and machine consumers that increasingly need inspectable product claims.
It exists for operators, evaluators, and machine-discovery paths that need clearer access to identity, provenance, revocation, and structured proof concepts.
Core Standards
The standards families this hub should connect
Credential routes explain one standards-aligned way to express attestable product facts and supporting status.
Identity routes matter where issuer identity, resolution, and trust transport affect how public proof is interpreted.
Identifier routes connect products, packaging, or physical scans to richer digital trust and verification surfaces.
Provenance routes matter when media authenticity supports the larger product trust story.
Revocation-aware routes explain how credential state can stay legible to machine consumers over time.
Integrity routes explain how artifacts, pages, and evidence references can be checked more rigorously.
Priority Routes
Open the main standards-oriented public pages
See how credential-shaped trust objects fit into the CITAQ infrastructure model.
Open the identity layer behind issuer resolution, authenticity, and machine trust transport.
See how standards-aligned product identifiers can connect to richer verification surfaces.
Explore the media-provenance layer where asset authenticity supports public trust output.
Inspect the revocation-oriented route for machine-readable credential-state handling.
Open the integrity route that explains how referenced artifacts can stay more defensible.
Related Knowledge
Use the adjacent docs, resources, and index routes
Use the documentation route when you need model-level explanation around credentials.
Open the documentation page for the identifier and route-resolution side of GS1.
Use the docs route for provenance-specific framing and implementation detail.
Read the evergreen explainer for a less technical path into credential concepts.
Use the evergreen guide for how identifier-linked trust surfaces fit the public model.
Move into the evidence-governance hub for the support model behind these standards-oriented routes.
Open the methods hub for verification model, evidence model, integrity, and badge semantics tied to these standards.
Open the machine-readable access hub for MCP, discovery files, APIs, and crawler-facing route behavior.
Browse the wider standards-oriented route family through the verification directory system.
Why This Exists
Standards need their own public route cluster
The architecture source treats credentials, DID resolution, GS1, C2PA, revocation, and cryptographic integrity as distinct system layers rather than one generic trust bullet.
As more verification journeys start with agents and crawlers, standards-oriented public routes help the platform stay inspectable for non-human readers too.
A dedicated standards hub keeps these topics connected to trust boundaries, docs, resources, and the larger verification directory instead of isolating them.
Next Step
Open the verification directory if you want the larger indexed route graph.
The standards hub is one cluster inside a much broader public system of trust, docs, resources, integrations, and verification surfaces.