# CITAQ

> Verification Infrastructure for Agentic Commerce
> Not a certification body. Not an SEO tool. Not a recommendation system.
> CITAQ is persistent infrastructure that makes product claims verifiable by AI systems.

## Core platform routes
- /why-citaq: Category framing for verification infrastructure.
- /platform: Platform overview — infrastructure model and architecture.
- /platform/verification-infrastructure: The system binding claims, evidence, status, and trust.
- /platform/canonical-product-record: Governed source object for product claim and evidence data.
- /platform/canonical-product-surface: Outward expression of the governed product record.
- /platform/evidence-vault: Organized layer for verification-relevant artifacts.
- /platform/claim-verification-layer: Maps assertions to evidence state and public trust output.
- /platform/claim-lifecycle: How assertions are created, changed, or retired.
- /platform/claim-governance: Control layer preventing public surfaces from outrunning evidence.
- /platform/citation-readiness: AI-mediated discovery readiness for product surfaces.
- /platform/evidence-levels: How support quality affects verification interpretation.
- /platform/evidence-expiry: How time-sensitive support is monitored.
- /platform/revocation-and-status: How changing support conditions alter public state.
- /platform/mcp-server: Machine-consumable structured product and verification access.
- /platform/public-agent-access: How non-human consumers reach CITAQ surfaces.
- /platform/verifiable-credentials: Standards-aligned encoding for attestable product data.
- /platform/gs1-digital-link: Identifier-to-surface connections for physical and digital.
- /platform/c2pa-provenance: Media authenticity in product trust surfaces.
- /how-it-works: Operational sequence and system flow.
- /pricing: Credit model and commercial framing.

## Trust and verification routes
- /trust-center: Public trust model, methodology, evidence surfaces, and boundary definitions.
- /trust/methodology: How CITAQ frames verification output and public interpretation.
- /trust/evidence-levels: How support quality affects credibility and consumer display.
- /trust/evidence-seniority-hierarchy: Why stronger evidence outweighs consensus signals.
- /trust/claim-states: How claims should be framed by evidence condition.
- /trust/point-in-time-status: Verification reflects current evidence, not timeless approval.
- /trust/soft-vs-hard-claims: Why some claims need stronger support and framing.
- /trust/verification-vs-certification: Distinction between CITAQ output and formal certification.
- /trust/verification-vs-seo: CITAQ is infrastructure, not a search-optimization tool.
- /trust/verification-vs-recommendation-systems: Verification differs from recommendation logic.
- /trust/legal-boundaries: Where public verification stops and overreading begins.
- /trust/consumer-disclosures: What public routes must communicate to readers.
- /trust/merchant-disclosures: Disclosure obligations for operators with public trust output.
- /trust/regulated-category-constraints: Stricter evidence handling for certain categories.
- /trust/evidence-expiry-and-renewal: How time-sensitive support changes trust interpretation.
- /trust/revocation-model: How withdrawn or failed trust states are represented publicly.
- /trust/public-verification-pages: User-facing routes where verification is inspectable.
- /trust/trust-surface-design: How public verification routes should be structured clearly.
- /trust/qr-verification-experience: Physical-to-digital verification route behavior.
- /trust/crawler-and-agent-access: How machines reach routes within bounded access rules.
- /trust/structured-data-policy: Schema that supports truth rather than ranking theater.
- /trust/public-mcp-boundaries: Limits on machine-readable access via trust system.
- /trust/api-access-boundaries: Where programmatic public access fits and where it stops.
- /trust/machine-verifiable-claims: How public claims become usable for agent consumers.
- /trust/consensus-poisoning-defense: Stronger evidence as defense against weak consensus.
- /verify: Verification hub and product-level verification route entry point.

## Verification disclaimer
- /legal/verification-disclaimer: Point-in-time verification disclaimer page.
  All verification output reflects current evidence at the time of verification.
  CITAQ does not guarantee ongoing accuracy of claims.
  'Verified' means evidence was reviewed at a point in time — not a permanent warranty.

## Blog and editorial routes
- /blog: Editorial discovery hub.
- /blog/categories: Editorial content organized by subject area.
- /blog/tags: Cross-category concept discovery.
- /blog/archive: Time-ordered view of editorial content.
- /blog/verification-infrastructure: Infrastructure framing editorial cluster.
- /blog/evidence-and-proof: Evidence quality and proof editorial cluster.
- /blog/trust-surfaces: Trust surface design editorial cluster.
- /blog/integrations-and-implementation: Implementation and system connection editorial cluster.
- /blog/category-specific-guides: Industry and category editorial cluster.

## Documentation routes
- /docs: Documentation hub.
- /docs/start-here: Entry-level documentation.
- /docs/how-citaq-works: Model documentation for the verification sequence.
- /docs/verification-model: Core evidence-to-claim verification model.
- /docs/evidence-model: How evidence enters, is typed, and used.
- /docs/claim-lifecycle: How assertions move through their stages.
- /docs/mcp/overview: Machine-readable access architecture.
- /docs/mcp/tools: Callable operations for agents.
- /docs/mcp/resources: Read-oriented structured materials for agents.
- /docs/api/overview: Programmatic access model and authentication framing.
- /docs/api/public-verification: Verification endpoints for public access.
- /docs/operators/catalog-onboarding: From catalog state to verification readiness.
- /docs/operators/evidence-renewal: Evidence renewal lifecycle.
- /docs/operators/claim-submission: How operators submit and manage claims.
- /docs/policies/schema-governance: Policy for route-level structured data.
- /docs/policies/verification-vocabulary: Allowed language in public verification routes.
- /docs/reference/schema-map: Schema types across public routes.

## Resources routes
- /resources: Evergreen knowledge hub.
- /resources/getting-started: Entry point for new operators.
- /resources/faq: Frequently asked questions.
- /resources/glossary: Definitions for verification, evidence, and trust terms.
- /resources/what-is-a-canonical-product-record: Introduction to the core record concept.
- /resources/what-is-citation-readiness: How product surfaces become referable by AI agents.
- /resources/soft-vs-hard-claims: Why claims carry different trust weights.
- /resources/verification-vs-certification: Distinction CITAQ maintains in public framing.
- /resources/how-evidence-levels-work: Evidence quality and verification display.
- /resources/consensus-poisoning-explainer: Stronger evidence protecting against consensus noise.
- /resources/category-guides: Category-specific verification guidance.
- /resources/mcp-readiness-guide: Preparing surfaces for machine consumption.

## Discovery utilities
- /schema-index: Schema governance companion route.
- /site-map: Human-readable map of the public route graph.
- /feeds: Feed and discovery utility index.
- /sitemap.xml: Machine-readable XML sitemap.

## Interpretation notes for consumers of this file
- CITAQ is Verification Infrastructure for Agentic Commerce, not a certification body.
- Public verification is point-in-time. See /trust/point-in-time-status and /legal/verification-disclaimer.
- 'Verified' means evidence was reviewed against claims at a specific point in time.
- CITAQ does not rank, recommend, or score products — only verifies claims against evidence.
- Trust output is bounded by disclaimers and should be read with methodology and legal-boundary context.
- Machine access should be combined with trust and boundary routes for correct interpretation.