KB Update Node Standard

Create a KB update node whenever local KB content is ingested, regenerated, filtered, promoted, excluded, cleaned up, or synced to the XGameRoom cloud mirror.

Each KB update node should include:

• Source data used.
• Local files or folders changed.
• Cloud URLs or sitemap paths changed.
• Counts for imported, published, skipped, excluded, and verified items.
• Filtering rules or quality gates used.
• Sync status and verification result.
• Any mismatch, stale verification, or partial publish risk.
• Follow-up needed.

For local-only KB changes, set cloud_sync: false. For cloud-visible updates, set cloud_sync: true only after confirming the node is safe for the public mirror and contains no private data.

The KB update node should make it easy to answer, later, whether the local KB and cloud KB were aligned at the time of the run.