LocalEndpoint ConnectPrivate AI for Windows
Menu

LocalEndpoint guide

UAIX.LmRuntime Integration

UAIX.LmRuntime integration documentation for the bounded managed GGUF worker adapter and the contract that keeps package parsing, policy, prompts, registry, audit, and public website duties outside the runtime package.

Platform accounting Developer routes

UAIX.LmRuntime integration

The runtime package is a bounded local GGUF worker adapter, not the product brain.

LocalEndpoint owns package loading, prompt assembly, policy, registry, audit, and JSONL event ownership. UAIX.LmRuntime receives an already-approved display-safe runtime request and verifies the reviewed local GGUF expectation before local generation work.

NuGet.org publication: UAIX.LmRuntime 3.3.29 public for the tracked runtime package set Current source package feed: UAIX.LmRuntime.LocalEndpoint 3.3.29 and UAIX.LmRuntime.Backends.Cuda 3.3.29 Managed GGUF worker path No .uaix parsing inside runtime No prompt or generated text persistence
Runtime owns

Local GGUF execution after approval.

The runtime adapter validates the request shape it is given, rechecks the reviewed model expectation, emits ordered token observations, and preserves session identity.

  • Phase 3.542 package evidence carries UAIX.LmRuntime 3.3.29 local package-feed validation and MSIX worker payload validation into the current Desktop 0.2.155.0 tester package.
  • Phase 3.539 package evidence carried UAIX.LmRuntime 3.3.29 local package-feed validation and MSIX worker payload validation into the Desktop 0.2.154.0 tester package.
  • Phase 3.537 package evidence carried UAIX.LmRuntime 3.3.29 local package-feed validation and MSIX worker payload validation into that Desktop 0.2.152.0 tester package.
  • Phase 3.518 package evidence carried UAIX.LmRuntime 3.3.29 local package-feed validation and MSIX worker payload validation into the Desktop 0.2.150.0 tester package.
  • UAIX.LmRuntime 3.3.29 is public on NuGet for all 17 LocalEndpoint-tracked runtime package IDs; the final public verification report is carried by the website runtime download lane.
  • Phase 3.517 package evidence carried UAIX.LmRuntime 3.3.29 local package-feed validation and MSIX worker payload validation into the Desktop 0.2.149.0 tester package.
  • Phase 3.515 package evidence carried UAIX.LmRuntime 3.3.29 local package-feed validation and MSIX worker payload validation into the Desktop 0.2.147.0 tester package.
  • Phase 3.514 package evidence carried UAIX.LmRuntime 3.3.29 local package-feed validation and MSIX worker payload validation into the Desktop 0.2.146.0 tester package.
  • Phase 3.504 source hardening keeps UAIX.LmRuntime terminal output consumption bounded: LocalEndpoint projects token counts, terminal kind, progress phases, and generated-text display availability while registry, audit, and public evidence remain free of prompt and generated text content.
  • Phase 3.512 package evidence carried UAIX.LmRuntime 3.3.29 local package-feed validation and MSIX worker payload validation into that Desktop 0.2.145.0 tester package.
  • Phase 3.482 completed a source/dev managed GGUF prompt run with `UAIX.LmRuntime managed GGUF generation completed`, 10 stream events, 8 token events, and evidence SHA-256 `659cb553e5823284a79f9d4c614c0930c9f99cb538dab8f7664784918fa08756`.
  • The Phase 3.482 run kept local API, provider APIs, command execution, telemetry, network access, prompt persistence, generated-text persistence, website prompt intake, and website model execution disabled.
  • LocalEndpoint current source consumes UAIX.LmRuntime.LocalEndpoint 3.3.29 from the local UAIX NuGet feed for current source validation.
  • LocalEndpoint current source consumes UAIX.LmRuntime.Backends.Cuda 3.3.29 from the local UAIX NuGet feed for diagnostic-only CUDA probe evidence.
  • LocalEndpoint.com accounts for UAIX.LmRuntime 3.3.29 NuGet.org publication as public package status only; runtime implementation ownership remains in the runtime package family and the website does not gain model execution authority.
  • UAIX.LmRuntime.Backends.Cuda 3.3.29 provides bounded CUDA driver probe output; LocalEndpoint.com accounts for it only as LocalEndpoint-owned diagnostics and does not claim actual K80 GGUF inference from that probe.
  • LocalEndpoint-owned CUDA probe diagnostics record driver probe status with inferenceClaimAllowed=false and cannot become terminal GPU device-use evidence.
  • Phase 3.351 adds a repeatable LocalEndpoint-owned Tesla K80 GPU evidence runner that proves driver memory-operation evidence locally while keeping GGUF generation pending unless the explicit proof switch and reviewed native package gates are satisfied.
  • Phase 3.376 proof-readiness evidence records cudaDriverProbeAccepted=true, k80DeviceMatched=true, cudaDriverMemoryOperationProven=true, and inferenceAllowed=false for Tesla K80 at cuda:0.
  • LocalEndpoint `models runtime inventory` reports CPU as selectable and CUDA Tesla K80 as diagnostic-only until native inference assets and proof are present.
  • LocalEndpoint current source references UAIX.LmRuntime.Backends.Cuda.Native.win-x64 and UAIX.LmRuntime.Backends.Cuda.LegacyK80.win-x64 3.3.29 as explicit native asset package lanes.
  • Phase 3.367 native package-lane adoption checklist evidence identifies the modern CUDA expected native binary as uaix-lmruntime-cuda-native-win-x64.dll and the Tesla K80 expected native binary as uaix-lmruntime-cuda-legacy-k80-win-x64.dll.
  • Phase 3.367 native package-lane adoption checklist evidence identifies the required proof receipt files as UAIX.LmRuntime.Backends.Cuda.Native.win-x64.3.3.29.native-generation-execution-evidence.json and UAIX.LmRuntime.Backends.Cuda.LegacyK80.win-x64.3.3.29.native-generation-execution-evidence.json.
  • Phase 3.367 native package-lane adoption checklist evidence identifies the required generation execution artifact files as UAIX.LmRuntime.Backends.Cuda.Native.win-x64.3.3.29.native-generation-execution-artifact.json and UAIX.LmRuntime.Backends.Cuda.LegacyK80.win-x64.3.3.29.native-generation-execution-artifact.json.
  • The Phase 3.367 package-feed report remains Blocked: readyForWorkerLaunch=false, workerLaunchBlocked=true, modelSessionAllocationBlocked=true, promptTokenizationBlocked=true, and inferenceBlocked=true for the native CUDA and Tesla K80 lanes.
  • UAIX.LmRuntime 3.3.29 backend capabilities provide display-safe Required For Native Generation package-lane and session-lane requirement findings that LocalEndpoint projects without letting the runtime own .uaix parsing, policy, registry, audit, provider APIs, telemetry, or command execution.
  • UAIX.LmRuntime 3.3.29 generation results expose runtime device-use evidence, so LocalEndpoint can accept managed CPU generation evidence and reject selected GPU evidence when the completed generation reports CPU.
  • Phase 3.328 selector candidates keep UAIX.LmRuntime backend inventory display-safe: CPU and diagnostic GPU candidates can fill the Runtime page selector editor while LocalEndpoint retains runtime readiness, worker launch, prompt assembly, registry, audit, and GPU-claim authority.
  • Native GPU asset package lane presence is public accounting evidence only; GenerationAssetsAccepted remains false until reviewed native generation binaries and terminal token evidence exist.
  • Package-bound generation execution evidence is Required For native lane acceptance; a standalone generation execution SHA-256 cannot authorize CUDA or K80 generation readiness.
  • Reviewed package manifest evidence, manifest-derived native binary identity, native binary SHA-256, runtime library identity matching package identity, and generation execution evidence SHA-256 must agree before generation assets can pass.
  • Native generation proof receipts are local evidence files bound to package ID, package version, package SHA-256, native binary file name, native binary SHA-256, runtime library identity, and generation execution evidence SHA-256.
  • Runtime inventory and Runtime page proof receipt fields are display evidence only; they do not claim actual GPU inference.
  • GPU generation readiness requires accepted proof receipt identity and remains blocked until terminal token and device-use evidence prove actual GPU execution.
  • K80 proof-readiness requirement projection is Required For automation-friendly GPU smoke gates: CUDA driver proof can be satisfied while native package lane, Tesla K80 package lane, terminal token, completed-token, ordered-token, completed-token comparison, and actual GPU runtime device-use requirements remain blocked.
  • K80 package-lane blocker identity projection is Required For actionable smoke review: package ID, runtime identifier, and reviewed candidate text are visible when proof receipt identity remains absent.
  • Release evidence validation preserves tester ZIP package discovery and UAIX.LmRuntime package-feed facts before release evidence, handoff packet, or final release discovery can pass.
  • Active GGUF model identity evidence is Required For Active GGUF Model Smoke Evidence: active entry ID, model name, GGUF format, artifact SHA-256, and artifact byte count must all validate before smoke evidence is accepted.
  • Native generation proof artifact binding is Required For GPU generation proof receipt advancement: the receipt must reference a display-safe same-feed JSON artifact file and the file hash must match the receipt.
  • Native generation artifact identity binding is Required For native generation artifact acceptance: schema, package identity, native binary identity, runtime library identity, and generation execution identity must match the receipt.
  • Native generation artifact identity-only validation is Required For LocalEndpoint-owned artifact acceptance: prompt text, generated text, command lines, and non-contract fields block evidence acceptance.
  • Package-feed native generation artifact identity-only validation is Required For release evidence acceptance: same-feed artifacts must contain only identity contract fields before proof receipt evidence can pass.
  • Accepted package-lane readiness is Required For native backend selection; raw generation asset acceptance alone cannot make CUDA or K80 selectable for generation.
  • UAIX.LmRuntime receives an already-approved display-safe LocalEndpoint request context and reviewed GGUF expectation.
  • UAIX.LmRuntime does not parse .uaix packages, own prompts, own policies, own registry or audit stores, call providers, access networks, collect telemetry, or persist prompt/generated text.
  • LocalEndpoint creates LocalChatViabilityEvidence before worker envelope creation; UAIX.LmRuntime only receives a viable, already-assembled local worker request.
Runtime does not own

Product authority stays with LocalEndpoint.

The runtime package does not become responsible for memory packages, prompt assembly, policy decisions, registry persistence, audit persistence, provider calls, network access, telemetry, or model download.

  • LocalEndpoint passes display-safe uaixRuntimeContext.
  • LocalChatViabilityEvidence blocks non-viable context before worker envelope creation.
  • Missing, malformed, non-isolated, or authority-bearing context is blocked before allocation.
  • LocalEndpoints.com records UAIX.LmRuntime 3.3.29 NuGet publication as package status; it does not grant model execution authority to the public site.
  • CUDA probe diagnostics carry inferenceClaimAllowed=false and are not terminal GPU device-use evidence.
Runtime claim boundary NuGet.org publication is publicly verified for the tracked 3.3.29 runtime package set Package-feed 3.3.29 adoption is accounted for current source and the Phase 3.335 tester package evidence CUDA diagnostics are not actual GGUF GPU inference evidence Runtime package publication does not certify LocalEndpoint desktop runtime safety LocalEndpoints.com does not prove runtime package version promotion readiness Website deployment evidence does not certify runtime safety

Operating boundary

Public clarity, local authority.

Public product, docs, download, and validation pages do not dispatch desktop commands, probe localhost, upload files, collect runtime telemetry, or claim runtime safety certification. Account credentials are accepted only on dedicated account routes.

Website explainsNo public command dispatch Browser checksNo upload intake Your work stays localNo localhost probing Verify downloadsChecksum-backed artifacts