Skip to content
GGUF RuntimeC# host application portal
Public technical index

Search the developer portal

Search public pages, documentation, examples, packages, topics, status labels, roadmap records, updates, and glossary terms. Queries are not sent to a third-party service.

Enter at least two characters.

    Architecture

    The host application is the authority boundary. UAIX.LmRuntime supplies explicit local runtime layers; it does not become the application, server, model catalog, downloader, policy engine, or persistence system.

    Responsibility map

    LayerOwnsDoes not imply
    Host applicationModel acquisition, license review, trusted roots, prompt assembly, limits, cancellation, persistence, transport, UI policy.That runtime package defaults are sufficient for the application threat model.
    LocalEndpoint facadeVerified file intake, bounded loading, isolated sessions, deterministic greedy generation.A finished application or hidden provider fallback.
    GGUF and tensor layersContainer parsing, metadata, tensor descriptors, mapped ownership.Architecture or tokenizer compatibility.
    Model, tokenization, sampling, CPU kernelsExplicit model/session execution components.Universal model coverage or GPU proof.
    Backend registry and probesDeclarations, local probes, selection inputs, diagnostics.Executed inference merely because a backend is registered.

    Package and responsibility layers

    Host and UIAuthority, trust, policy, transport, persistence
    LocalEndpointVerified intake and isolated generation
    GGUF · Tokenization · LLaMA · SamplingContainer, prompt tokens, model/session, selection
    Backends and kernelsRegistration, probe, selection, execution evidence
    The host owns authority and application behavior. LocalEndpoint coordinates verified local execution. Lower packages own explicit runtime primitives. Backend state remains evidence that must progress through registration, probing, selection, and executed work.

    Text equivalent: The host owns authority and application behavior. LocalEndpoint coordinates verified local execution. Lower packages own explicit runtime primitives. Backend state remains evidence that must progress through registration, probing, selection, and executed work.

    Verified model-load sequence

    Host intake recordSource, license, digest, byte count, trusted root
    Path and identity verificationContainment, reparse policy, stable length, SHA-256
    GGUF parse and bindBounded metadata, tensors, tokenizer and model checks
    Load resultPath-free result and diagnostics
    The host supplies trusted identity and path policy before runtime parsing. The runtime verifies current bytes, performs bounded parsing and binding, then returns a load result. A successful load is narrower than universal compatibility.

    Text equivalent: The host supplies trusted identity and path policy before runtime parsing. The runtime verifies current bytes, performs bounded parsing and binding, then returns a load result. A successful load is narrower than universal compatibility.

    Session lifecycle

    Create host session IDOne conversation or worker
    Create LocalGgufSessionOwn position, KV state, UAIX evidence
    Generate with limitsPrepared prompt, cancellation, token ceiling
    Dispose session then modelDeterministic ownership order
    A loaded model can own multiple isolated sessions. Each session is host-identified, receives prepared prompts and bounds, and must be disposed before the parent model.

    Text equivalent: A loaded model can own multiple isolated sessions. Each session is host-identified, receives prepared prompts and bounds, and must be disposed before the parent model.

    Backend evidence lifecycle

    Package presentDependency identity only
    Backend registeredFactory and declaration available
    Local probe completedCurrent environment inspected
    Backend selectedPolicy selected a lane
    Inference executedRetained path-specific result
    Package presence, registration, compatibility declaration, probe completion, selection, model loading, and executed inference are separate states. Only retained execution evidence supports an executed-path claim.

    Text equivalent: Package presence, registration, compatibility declaration, probe completion, selection, model loading, and executed inference are separate states. Only retained execution evidence supports an executed-path claim.

    UI-thread and cancellation flow

    UI eventValidate input and create CancellationTokenSource
    Background workerRun CPU-bound generation off the render thread
    Token observerReturn committed token evidence synchronously
    UI dispatcherBatch display updates and expose stop state
    Cancellation and disposalSurface cancellation separately and release resources
    The UI remains responsive by moving CPU-bound generation off the render thread. Token observations are marshaled back in bounded batches. The host owns cancellation presentation and disposal.

    Text equivalent: The UI remains responsive by moving CPU-bound generation off the render thread. Token observations are marshaled back in bounded batches. The host owns cancellation presentation and disposal.

    Boundary details

    • Persistence boundary: runtime objects are not a hidden conversation database.
    • UAIX context boundary: profile and memory fields are immutable evidence and grant no authority.
    • Network boundary: no network, provider, URL-fetch, or cloud fallback authority is inferred.
    • Tool and command boundary: memory files and prompts cannot authorize commands or subprocesses.
    • Telemetry boundary: the host decides what local measurements to collect and retain.

    Operational boundary

    What this page covers: Package layers, verified loading, session ownership, backend evidence, cancellation, telemetry, persistence, UAIX context, network, and tool boundaries.

    Available now: Managed CPU application integration and explicit lower package layers are publicly documented.

    Host responsibility: Compose the application, select and trust artifacts, marshal UI work, own transport/persistence, define backend policy, and retain evidence.

    Not claimed: A finished cross-platform application, universal hardware support, silent fallback, or authority granted by memory files.

    Canonical sources: Runtime architecture · Package family · UAIX Project Handoff

    Last reviewed UTC: