PKG4-associated standalone technical identity
Model Switching
Model switching is the operational pattern of selecting or changing the model used for a request or task according to implementation policy or criteria.
Why it matters
A bounded technical reference
It provides a neutral reference for routing and selection practices without claiming a standard, automatic optimality, savings, or an LJP-operated router.
Evidence and terminology boundary
What the identity supports
Evidence C for the underlying routing pattern; Model Switching is LJP descriptive terminology, not a formal standard.
Overview of model routing — Google Cloud
The cited source supports its own terminology and material. It does not endorse LJP, this domain, a buyer, or an implementation.
Package context
Independent PKG4-associated identity
This standalone identity is associated with Intent-Based Orchestration for portfolio context. It is not a role in the eight-role End-to-End Intent lifecycle model.
Credibility boundary
What this is not
This domain provides semantic identity and public orientation. It is not an operational service, control plane, runtime, protocol authority, certification, performance guarantee, or third-party affiliation.