Retain stable, path-free records that distinguish identities, backend states, load, generation, cancellation, measurements, environment, and limitations.
Stable schema
Use a schema identifier, generated UTC timestamp, host application identifier, package identity/version, model hash/byte count/display name, and session identifier.
Backend ladder
Record registration, probe, selected backend, CPU fallback, model load, inference, and retained result separately.
Measurements
Include timing method, time to first token, throughput, memory measurement method, environment, and known limitations.
Review
Record reviewer and review state. Keep the explicit statement that the record is not a benchmark, safety, production, or compatibility certificate.
Available now
- The public UAIX.LmRuntime package family and canonical package documentation.
- The host-facing workflow and evidence distinctions described on this page.
Host responsibilities
- Select and trust inputs, define policy and limits, integrate the UI or service, retain application evidence, and test the exact deployment.
Not claimed
- Evidence is scenario-specific.
- Do not include private paths, prompts, secrets, or WordPress database identifiers.
Operational boundary
What this page covers: Retain stable, path-free records that distinguish identities, backend states, load, generation, cancellation, measurements, environment, and limitations.
Available now: The documented package surfaces and this host-facing guidance are public.
Host responsibility: Own acquisition, trust, configuration, presentation, persistence, transport, policy, tests, and deployment.
Not claimed: Universal compatibility, production certification, safety certification, hidden fallbacks, or behavior beyond retained evidence.
Canonical sources: Canonical package documentation · Current release metadata
Last reviewed UTC:
Source and review record
Prerequisites
- Read Get Started
- Review host/runtime boundaries