Package Selection
Choose the narrowest UAIX.LmRuntime package for a host task without inferring capability from package names.
Open record →Task-oriented host documentation
Use filters to move from verified GGUF intake through model and session ownership, bounded generation, cancellation, evidence, backend state, UI architecture, security, and troubleshooting.
Canonical package and API detail remains on LMRuntime.com. Every article identifies host responsibility, non-claims, evidence state, and last review UTC.
18 public records
Choose the narrowest UAIX.LmRuntime package for a host task without inferring capability from package names.
Open record →Admit a local artifact through explicit source, license, path, size, byte-count, hash, and structural checks.
Open record →Inspect bounded metadata and tensor descriptors without starting inference.
Open record →Keep acquisition, authority, UI, transport, persistence, prompt assembly, and policy in the host.
Open record →Represent model ownership, isolated sessions, continuation state, cancellation, and disposal order explicitly.
Open record →Keep model-specific conversation formatting and special-token choices in the host.
Open record →Apply explicit prompt, output, stop-token, memory, and concurrency ceilings.
Open record →Propagate host cancellation, distinguish it from failure, and release session/model ownership deterministically.
Open record →Collect path-specific measurements locally with documented timing and memory methods.
Open record →Display backend package, registration, declarations, probes, selection, fallback, and execution as separate states.
Open record →Use executed-path records rather than package or hardware labels when presenting acceleration.
Open record →Keep trusted roots, file pickers, scoped storage, bookmarks, and path privacy host-owned.
Open record →Structure a proposed cross-platform desktop shell around explicit services, view models, dispatch, cancellation, and evidence.
Open record →Expose a narrowly bounded loopback service without turning model acquisition or filesystem authority into a request API.
Open record →Preserve technical failure classes without leaking paths, prompts, credentials, or private environment data.
Open record →Apply bring-your-own-authority rules to files, memory, network, commands, telemetry, and persistence.
Open record →Retain stable, path-free records that distinguish identities, backend states, load, generation, cancellation, measurements, environment, and limitations.
Open record →Diagnose intake, load, session, backend, generation, cancellation, and resource failures without weakening controls.
Open record →