{"version":"2.1.251","anchor":"startup-telemetry-now-classifies-where-the-active-model-came","canonical_anchor":"startup-telemetry-now-classifies-where-the-active-model-came","heading":"Startup telemetry now classifies where the active model came from","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/startup-telemetry-now-classifies-where-the-active-model-came","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Startup telemetry now classifies where the active model came from\n\nStartup telemetry classifies how your active model was defined and selected.\n\n**What**\n\nTwo new helpers label the active model by how it was defined, such as the compiled catalog, a legacy entry, an environment-supplied custom option, a tier pin, or gateway discovery, and by how it was selected, such as an org default, an entitlement default, a CLI flag or an SDK option.\n\n**Details**\n\n- Computed on every startup with no flag; unrecognized is used when neither classification matches.\n\n**Evidence**\n\n`model_definition_source`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}