Operator Hub
Operator workflows are how verification infrastructure becomes a live, governed system.
This hub covers the operational side of CITAQ: how catalogs enter the system, how evidence is maintained over time, how claims are submitted and governed, and how public trust surfaces stay aligned with current verification state.
Verification infrastructure does not run itself. Operators need clear workflows for onboarding, evidence supply, claim governance, and trust-surface maintenance.
Workflow Families
What operator workflows cover
The transition from raw catalog state into verification readiness. Covers structure requirements, evidence prerequisites, and initial claim mapping.
Systematic workflows for maintaining time-sensitive support. Covers expiry monitoring, renewal triggers, and how stale evidence affects live trust output.
How operators create, update, and retire product claims inside the verification model. Covers claim typing, evidence attachment, and status flow.
Keeping public trust routes aligned with current evidence state. Covers what gets surfaced, how boundaries are maintained, and how consumer disclosures stay current.
Key Operational Pathways
From catalog intake to live verification
Catalog onboarding is the transition from any starting state — raw product fields, flat files, Shopify import, ERP feed — into a structured verification-ready catalog inside CITAQ. It requires claim structure, evidence readiness, and initial status logic before public surfaces can be activated.
Evidence goes through ingestion, normalization, and attachment to specific claims before any public trust output changes. Evidence ingestion is not instant. The workflow covers what operators need to do, what CITAQ does automatically, and what the output looks like after the cycle completes.
Evidence does not last forever. Certificates, lab reports, and compliance documents have natural expiry. The platform monitors evidence health continuously and surfaces evidence-expiry workflows so trust output reflects current rather than stale support.
Submitted claims move through a status system before they appear as public-facing trust signals. The workflow explains what operators see at each stage, what controls they have, and how boundary language is applied before consumer surfaces are updated.
Connected Routes
Keep moving through the system
Technical documentation for the onboarding workflow from intake to verification readiness.
Documentation for the evidence renewal lifecycle and monitoring system.
How operators submit, update, and manage claims inside the verification model.
Browse the systems that feed catalog data, evidence, and implementation workflows.
Understand how operational workflows connect to public trust output.
Entry-level resource for operators new to the CITAQ model.
Evaluate your catalog's verification readiness before onboarding.
Bridge from operator workflows into regulated-category and compliance documentation routes.
Next Step
Start with the live CRS workflow.
CRS is the available standalone path for Shopify merchants. Run the readiness module first, then use the broader operator workflow routes to understand how CITAQ verification infrastructure expands from there.