Structure a proposed cross-platform desktop shell around explicit services, view models, dispatch, cancellation, and evidence.
Application services
Separate model catalog/intake, runtime ownership, session orchestration, evidence collection, and local persistence behind host-owned interfaces.
View models
Expose model identity, load state, active session, generation limits, cancellation state, token output, metrics, backend diagnostics, and evidence export through typed properties.
Threading
Run CPU-bound generation away from the UI thread. Batch token-observer updates and marshal them through the Avalonia dispatcher.
Platform adapters
Isolate file selection, trusted-root persistence, window lifetime, memory pressure, packaging, signing, and accessibility behavior per platform.
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
- No finished Avalonia artifact is included.
- Framework selection does not prove mobile or desktop parity.
Operational boundary
What this page covers: Structure a proposed cross-platform desktop shell around explicit services, view models, dispatch, cancellation, and evidence.
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