{
  "metadata": {
    "version": "v5",
    "last_updated": "2026-06-10",
    "purpose": "How to use the AI DB package when updating pages."
  },
  "workflow": [
    "Start with the commercial page URL and desired primary intent.",
    "Look up related materials/applications in material-application-map.json and process-zone-map.json.",
    "Check product-category-map.json and product-validation-map.json before naming models.",
    "Check compliance-glossary.md, compliance-risk-map-v3.json and product-claim-validation-map-v4.json before any ORD LOC/NFPA/HEPA/explosion-proof claims.",
    "Use comparison-topics.md and buyer-question-map-v3.json to add FAQs and decision blocks.",
    "Use live-url-canonical-inventory.json to avoid linking to stale, misspelled, duplicate, or legacy URLs.",
    "After publishing, add the canonical URL/summary back into llms.txt, llms-full.txt, page-topic-map.md, and page-topic-index.json."
  ],
  "page_copy_guardrails": [
    "Use product/category language that matches live product pages and current U.S. naming.",
    "Use ATEX only for international/historical/case-study context where appropriate; use ORD LOC/explosion-proof/combustible dust for current U.S. site language.",
    "Do not imply one vacuum guarantees OSHA/NFPA compliance.",
    "Avoid generic “industrial vacuum” copy when a material/application page needs specific media, process, filter/discharge and product-family routing."
  ]
}