1.4 KiB
Model installation rationale
The Models view and GET /api/v1/models/installation-rationale answer “Why is this installed?” from registry relations rather than prose.
For each model the projection reports local artifact bytes, capability and contract version, deployment and channel, production/LAB status, declared project consumers, evaluation-run identifiers, last gateway use, deletion eligibility and explicit blockers.
Deletion remains an explicit operator action. Deployment, project, evaluation and provenance dependencies block destructive lifecycle changes. Models with only remote registry metadata are clearly distinguished from installed artifacts. ModelForge can recommend cleanup candidates but never removes artifacts automatically.
M11 adds real active project consumers and immutable project-fit evidence IDs. Only non-deprecated bindings are listed, duplicate project identities are collapsed, and an active scoped client makes the operational dependency explicit. SigLIP2 and Whisper are therefore installed for ExampleVision shadow/LAB flows even though neither is production-promoted.
M12 cleanup dry-runs extend “Why Installed” with active deployment, project, evaluation, migration, rollback-retention and approval/plan evidence dependencies. Reclaimable bytes are displayed separately from blocked bytes; rationale and provenance survive any later location removal.