CITAQ needs visible policy routes because public verification fails when schema, disclosure, discovery, and language rules stay implicit.

This hub gathers the policy-facing parts of the public platform: route-level schema governance, crawler discovery rules, structured-data boundaries, public disclosure expectations, legal language constraints, and verification vocabulary choices.

These policy routes are part of the product surface. They help keep the public graph inspectable for humans and machines without drifting into exaggerated authority or unbounded claim language.

Use This Page
Use this route when you need the public governance layer behind the site.

It connects policy docs, legal disclosures, trust boundaries, and schema/discovery surfaces into one coherent public policy cluster.

The governance topics this hub should connect

Schema Governance

Schema policy matters because each important route owns its own structured-data treatment and claim boundaries.

Crawler Discovery

Discovery policy explains how machine consumers reach public routes without turning discovery into authority theater.

Structured-Data Boundaries

Boundary routes explain what structured data should support and what it should not pretend to do.

Public Verification Disclosures

Disclosure routes help keep point-in-time interpretation and limitations visible across trust surfaces.

Legal Language Boundaries

Language rules prevent the public platform from overstating verification as certification or permanent approval.

Verification Vocabulary

Vocabulary policy keeps public language aligned with what the architecture actually supports.

Open the main policy and governance pages

Use the adjacent trust, legal, and discovery hubs

Open the reference center if you want the supporting vocabularies and route maps next.

Policy explains the rules, while reference routes provide the terms, maps, and route-taxonomy materials that keep those rules usable.