gov-model-selection-governance

Assign model metadata profiles by selecting from five canonical options like deep-reasoning or balanced-execution, then populate the package manifest with provider mappings and selection rationale to ensure consistent routing and auditability.

Model profile governance is the process of documenting preferred and availability-safe model defaults across providers, ensuring agents use task-fit models and avoid broken integrations during catalog maintenance and package onboarding.

Populate the provider_models block in the package manifest with preferred defaults and availability-safe alternatives, including recommended fields for cursor and vscode-copilot to prevent blank fallbacks during integration.

Yes, you can audit package manifests using built-in governance commands and audit checks that identify missing model_profile entries, orphaned profile names, and undocumented rationale for non-obvious model selection choices.

Update model metadata and provider mappings during catalog maintenance, new package onboarding, model renames, and provider mapping updates to ensure task-fit model assignment and maintain consistent routing across providers.

Limitations include the need to document rationale for non-obvious choices, maintain provider-safe fallbacks to avoid blank integrations, and regularly run governance checks to prevent orphaned profile names and missing entries.