Keep acquisition, authority, UI, transport, persistence, prompt assembly, and policy in the host.
Host-owned authority
The host decides what files may be read, what prompts may be constructed, what limits apply, whether cancellation is available, what data is retained, and whether any transport exists.
Runtime-owned execution
The runtime validates explicit inputs, owns model/session resources, and returns bounded results and diagnostics through documented APIs.
No hidden expansion
Do not infer downloaders, provider APIs, telemetry, servers, command execution, memory authority, or persistence from the LocalEndpoint name.
Interface contract
Represent each ownership decision in the UI: trusted artifact, active model, session, cancellation source, selected lane, fallback state, and evidence record.
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
- UAIX context is evidence only.
- The runtime is not a policy engine or server framework.
Operational boundary
What this page covers: Keep acquisition, authority, UI, transport, persistence, prompt assembly, and policy in the host.
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