Terms are defined narrowly so package presence, declarations, probes, selected paths, and executed results are not conflated.
- Artifact identity
- A current SHA-256 digest and byte count used to compare exact bytes; not a license, provenance, compatibility, quality, or safety result.
- Backend registered
- A backend factory or declaration is available to the registry. It does not prove local probing, selection, loading, or inference.
- Evidence available
- A retained, reviewable record supports the narrow statement attached to it.
- GGUF
- A binary container for model metadata, tensor descriptors, and tensor data. Container validity is separate from model compatibility.
- Host application
- The application that owns authority, model acquisition, trust, prompt assembly, cancellation, UI, transport, persistence, and policy.
- Isolated session
- A host-identified runtime session with independent model position, KV state, and context evidence.
- LocalEndpoint
- The high-level local-only UAIX.LmRuntime facade for verified intake, bounded loading, isolated sessions, and deterministic greedy generation.
- Probe
- A local environment inspection performed by a backend implementation; declaration alone is not a probe result.
- Released
- The described website or package surface is publicly available; the term does not imply production or safety certification.
- Runtime evidence record
- A host-retained observation of identities, state transitions, results, timing method, environment, and limitations; not a certificate.
- Trusted root
- A host-selected canonical directory boundary within which model artifacts are allowed.
- UAIX context evidence
- Validated profile and memory identifiers retained as context evidence with every authority flag closed.
Operational boundary
What this page covers: Shared terminology for host, runtime, GGUF, backend, status, and evidence records.
Available now: The portal uses these terms consistently in visible and machine-readable content.
Host responsibility: Apply narrower project-specific definitions when a consuming application requires them.
Not claimed: That a glossary definition itself proves a capability or execution result.
Canonical sources: LMRuntime glossary · Status
Last reviewed UTC: