Roy229/nimbus-product-ownership-registry-5227-jiy2y1gy
Nimbus Product Ownership Registry This repository documents the authoritative mapping between product lines and the owning teams within the Customer Experience (CX) organization at Nimbus Retail. It is consumed by the daily feedback triage pipeline and by the BI dashboard. Upstream Sources This registry is generated from the following upstream datasets published on the Hugging Face Hub by the CX Data Platform account: Product Catalog -… See the full description on the dataset page: https://huggingface.co/datasets/Roy229/nimbus-product-ownership-registry-5227-jiy2y1gy.
Nimbus Product Ownership Registry
This repository documents the authoritative mapping between product lines and the owning teams within the Customer Experience (CX) organization at Nimbus Retail. It is consumed by the daily feedback triage pipeline and by the BI dashboard.
Upstream Sources
This registry is generated from the following upstream datasets published on the Hugging Face Hub by the CX Data Platform account:
- Product Catalog -
Roy229/nimbus-product-catalog-5227-jiy2y1gy
The master catalog of product lines, categories, and owning teams.
- Product Segments -
Roy229/nimbus-product-segments-5227-jiy2y1gy
Segment definitions and service-level agreement (SLA) targets per product line.
Authenticity Criteria
Before relying on this registry for the daily triage, ALL of the following checks MUST pass:
- Each upstream dataset must be authored by the CX Data Platform account (owner
Roy229). - Each upstream dataset must have been created after
2026-07-01(the start of the current registry cycle). - Each upstream dataset must be publicly accessible and must NOT be gated. If you are unsure what gated means for a Hub dataset, consult the Hub documentation on the web before interpreting the metadata.
If any source fails these checks, do NOT publish triage results; flag the issue to the CX Analytics team instead.
Local Working Copy
The CX Analytics team keeps a local working copy of the ownership mapping in the shared drive (reference/product_ownership.csv) that is used for the daily triage computations.
Publication
Triage results are published back to the cloud warehouse as the triage_results table inside the nimbus_cx_feedback_* dataset. Only publish after confirming that your session is authenticated (your identity must be valid on the data platform).
