canonical_cluster_date_end | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It bounded the linked STORY’s cluster date — a third date vocabulary on an endpoint that already has two (date_start/date_end for when the event happened, observed_start/observed_end for when we coded it), and the only one named after an internal join rather than after anything a reader of the data would recognise. It also forced the request off the daily snapshots: measured 6,487 ms live against 1,144 ms settled on the identical window, which made it the single largest latency cost on this endpoint. Use date_start/date_end to bound when events happened, or observed_start/observed_end to bound when they were coded. Each linked story’s own date is on the card under story_refs. |
canonical_cluster_date_start | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It bounded the linked STORY’s cluster date — a third date vocabulary on an endpoint that already has two (date_start/date_end for when the event happened, observed_start/observed_end for when we coded it), and the only one named after an internal join rather than after anything a reader of the data would recognise. It also forced the request off the daily snapshots: measured 6,487 ms live against 1,144 ms settled on the identical window, which made it the single largest latency cost on this endpoint. Use date_start/date_end to bound when events happened, or observed_start/observed_end to bound when they were coded. Each linked story’s own date is on the card under story_refs. |
canonicalClusterDateEnd | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It bounded the linked STORY’s cluster date — a third date vocabulary on an endpoint that already has two (date_start/date_end for when the event happened, observed_start/observed_end for when we coded it), and the only one named after an internal join rather than after anything a reader of the data would recognise. It also forced the request off the daily snapshots: measured 6,487 ms live against 1,144 ms settled on the identical window, which made it the single largest latency cost on this endpoint. Use date_start/date_end to bound when events happened, or observed_start/observed_end to bound when they were coded. Each linked story’s own date is on the card under story_refs. |
canonicalClusterDateStart | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It bounded the linked STORY’s cluster date — a third date vocabulary on an endpoint that already has two (date_start/date_end for when the event happened, observed_start/observed_end for when we coded it), and the only one named after an internal join rather than after anything a reader of the data would recognise. It also forced the request off the daily snapshots: measured 6,487 ms live against 1,144 ms settled on the identical window, which made it the single largest latency cost on this endpoint. Use date_start/date_end to bound when events happened, or observed_start/observed_end to bound when they were coded. Each linked story’s own date is on the card under story_refs. |
confidence_profile | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a preset over INTERNAL story-cluster grades, not a confidence filter: any value other than loose required visibility_tier=primary and story_family_grade=strong, which discarded roughly 61% of retrievable Stories — including clusters graded weak at creation that later grew to hundreds of articles, because that grade is stamped once and never revised. Use confidence_min for a floor on the coder confidence score. |
goldstein_max | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
goldstein_min | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
goldstein_severity_max | 2026-08-15 | Retired 2026-08-15 and no longer affects results. Goldstein severity is not a separate metric — it is the ABSOLUTE VALUE of goldstein_scale, which is served on every card, so the same screen is goldstein_scale_min / goldstein_scale_max (a signed band) or one line of arithmetic on the value you already receive. Filtering on it also forced the request off the daily snapshots, so it was materially slower than the filter it duplicated. The goldstein_severity STATISTICS on /api/v2/events/summary are unchanged — an aggregate is not something a caller can compute from a single card, which is exactly why that one stays and this one does not. |
goldstein_severity_min | 2026-08-15 | Retired 2026-08-15 and no longer affects results. Goldstein severity is not a separate metric — it is the ABSOLUTE VALUE of goldstein_scale, which is served on every card, so the same screen is goldstein_scale_min / goldstein_scale_max (a signed band) or one line of arithmetic on the value you already receive. Filtering on it also forced the request off the daily snapshots, so it was materially slower than the filter it duplicated. The goldstein_severity STATISTICS on /api/v2/events/summary are unchanged — an aggregate is not something a caller can compute from a single card, which is exactly why that one stays and this one does not. |
max_confidence | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
max_geo_precision | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
max_goldstein | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
max_goldstein_scale | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
max_goldstein_severity | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
max_magnitude | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
max_market_sensitivity | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
max_propagation_potential | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
max_significance | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
max_systemic_importance | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
min_confidence | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of confidence_min, kept only for compatibility, and sitting beside confidence_profile it made three unrelated things look like one. Use confidence_min. |
min_geo_precision | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
min_goldstein | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
min_goldstein_scale | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
min_goldstein_severity | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
min_magnitude | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
min_market_sensitivity | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
min_propagation_potential | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
min_significance | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
min_systemic_importance | 2026-08-15 | Retired 2026-08-15 and no longer affects results. It was a second spelling of the canonical <metric>_min / <metric>_max filter, which is unchanged and still applied — so if you were sending this, switch the spelling and your results are identical. Nine metrics each accepted two spellings per bound (plus four short goldstein forms), which meant two names to learn per filter, two names in the docs, and a precedence rule for the case where a caller sent both. Across 90 days every alias spelling put together carried about two successful calls, so the surface cost was permanent and the usage was not. |
