Model profiles often collapse several unrelated numbers into one impression of size or capability. MiRust separates them because they affect deployment differently.
Start with the task
Record the intended output, acceptable quality, latency, memory, privacy, and hardware envelope before choosing a model family.
Keep resource measures separate
- Parameter count describes learned values.
- Artifact size depends on format and precision.
- Runtime memory includes weights, context, buffers, and implementation overhead.
- Context size affects state and workload cost.
Require evidence
A compatibility statement should name a source revision, model variant, backend, device, date, and known limitations. A missing field is a reason to narrow the claim, not to guess.