{"version":"2.1.273","anchor":"model-selector-unserved-spelling-telemetry-distinguishes-fam","canonical_anchor":"model-selector-unserved-spelling-telemetry-distinguishes-fam","heading":"Model resolution now distinguishes explicit vs. persisted spelling","tier":"internal","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/model-selector-unserved-spelling-telemetry-distinguishes-fam","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Model resolution now distinguishes explicit vs. persisted spelling\n\nModel-resolution telemetry and helpers now separately track whether a model name was explicitly given or came from persisted settings\n\n**What**\n\n- The `startup_resolve_model` telemetry event, which previously always logged `family_spelling_unserved` when a model name resolves to nothing despite a raw request existing, now logs `persisted_spelling_unserved` instead in that case.\n\n- Model-resolution helpers now pass an explicit `explicit` or `persisted` tag through a renamed function (`XUt`, previously `sFt`), and a companion helper checks whether a model is valid or comes from a persisted source.\n\n**Why** Distinguishing whether an unresolved or unusual model name was typed explicitly versus loaded from persisted settings makes it possible to tell these two situations apart in telemetry and resolution logic, rather than lumping them together as one generic case.\n\n- Area: Models\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}