```json { "table_name": "telco", "primary_key": "Customer ID", "candidates": [ { "rank": 0, "partition_key": "Customer ID", "partition_key_label": "primary_identifier", "partition_key_reasoning": "Customer ID is the unique identifier with RPUV=1.00, uniqueness=1.000, and 7043 distinct values matching row count. Perfect for dimension table partitioning as each customer has exactly one row.", "clustering_key": null, "clustering_key_label": null, "clustering_key_reasoning": "Dimension tables do not require clustering — no temporal or sequential ordering needed within customer records.", "world_line": null, "session_column": null, "confidence": "HIGH", "notes": "This is a classic customer dimension table with one row per customer. Customer ID is both the primary key and the natural partition key. No temporal axis exists (Quarter is constant 'Q3', _ingestion_timestamp is constant). All other columns are attributes describing customer demographics, service subscriptions, and churn status. No alternative partitioning perspectives are viable — this is purely a customer-centric dimension." } ] } ```