LocalEndpoint guide

Current Platform Accounting

A thorough current accounting of what LocalEndpoints.com publishes, what LocalEndpoint Desktop does locally, how .uaix packages and .uai memory load, where UAIX.LmRuntime fits, and what still must pass before broad distribution claims.

Machine accounting Desktop boundary

Complete current accounting

One product, two trust zones, several bounded contracts.

LocalEndpoints.com is the public trust and evidence surface. LocalEndpoint Desktop is the local authority surface. UAIX packages provide portable memory. UAIX.LmRuntime provides a bounded managed GGUF worker adapter. The boundaries matter because anyone can reach the website, but private runtime work belongs only on a person's machine.

Website publishes Desktop approves .uaix carries memory Local models are reviewed UAIX.LmRuntime executes bounded GGUF work Evidence avoids prompt and generated text

Public website

What LocalEndpoints.com owns.

The public site is the explain, validate, document, release, and evidence surface.

Explain the product, trust boundary, current desktop artifact, and newer source-hardening status.
Serve schemas, examples, OpenAPI-style metadata, route indexes, llms.txt, checksum manifests, and redacted evidence.
Run browser-local validation helpers for public-safe manifests and receipts.
Publish cPanel deployment manifests, direct-overwrite plans, and release verification evidence.

Read the route

Desktop app

What the local app owns.

The desktop app is the only place where package loading, local prompt assembly, model intake, model execution, approval, registry, audit, and JSONL event ownership happen.

Import, validate, expand, and load .uaix packages and their .uai memory files.
Assemble prompts locally from approved package memory, wiki memory, and user-selected context.
Own policy decisions, local approvals, local model registry persistence, audit persistence, JSONL event ownership, and redacted evidence.
Verify model artifacts, sidecars, hashes, byte counts, hardware fit, active registry rows, selected model identity, session identity, and turn identity before runtime allocation.
Require provider start-to-stream request fingerprint consistency before worker stream handoff.
Evaluate LocalChatViabilityEvidence and block a non-viable chat turn as a no-op before worker envelope creation.

Read the route

UAIX packages

How agent memory travels.

.uaix packages are portable, shareable agent packages that Desktop expands into .uai memory files and local wiki memory roots.

A .uaix file is a portable agent package that carries .uai memory files and package metadata for Desktop to expand locally.
persona.uai is Required For All LocalEndpoint Desktop Packages.
.uai file roles are described as Required For {agent type or workflow}.
Long-term wiki memory roots are per-load choices and default to Documents-backed folders so people can back up, share, or separate agent memory.
.uaix or .uai memory cannot grant hosted inference, provider APIs, telemetry, shell execution, command execution, automatic export, network access, or core safety policy override by itself.

Read the route

Local models

How downloaded models become usable.

A downloaded model is not runtime-ready until Desktop has reviewed the artifact, sidecars, hashes, size, revision, hardware fit, active registry identity, and selected-model identity.

Phase 3.519 package evidence records LocalModelUaixMemoryRunReadiness as Required For UAIX Memory Run Readiness so Hub runs require loaded .uaix package memory, .uai/persona.uai, and a Documents-backed wiki root before local chat readiness can pass.
Phase 3.519 source hardening expands Hub run readiness to nine gates: prompt text, .uaix package, persona.uai, Documents wiki root, local model identity, download, activation, runtime, and worker.
Phase 3.516 package evidence records LocalModelHubCatalogCandidateSelectionSummary as Required For Safe Local Model Selection so ready candidates show owner-approved local download and blocked candidates show the required different-choice action before download.
Phase 3.516 source hardening records Models UI SelectionSummary.StatusText, SelectionSummary.PrimaryActionLabel, and SelectionSummary.EvidenceText as Required For Hub Candidate Action Discovery so first-time users can see one candidate decision and one next action without reading raw metadata.
Phase 3.514 package evidence records LocalModelHubRunReadinessCard as Required For First Local Chat Action Card so Models UI exposes exactly one next action from the same display-safe readiness summary that gates the Run Local workflow.
Phase 3.514 source hardening records LocalEndpoint.Models.HubRun.ReadinessCard automation IDs as Required For First Local Chat Action Discovery so smoke automation can verify the compact next-action card without scraping long explanatory text.
Phase 3.512 source hardening records LocalModelHubRunReadinessSummary progress counts as Required For First Local Chat Readiness Progress so LocalEndpoint.Models.HubRun.ReadinessProgress shows ready required gates and total required gates from the same checklist rows as the detailed Models UI gate list.
Phase 3.512 source hardening records ReadyChecklistItemCount, TotalChecklistItemCount, and ProgressText as Required For Display-Safe Local Run Progress so readiness count text stays count-only and does not carry prompt text or generated text.
Phase 3.511 source hardening records RunHubWorkflowCommand readiness-bound CanExecute as Required For First Local Chat Command Gating so Run Local cannot execute while LocalModelHubRunReadinessSummary is blocked.
Phase 3.511 source hardening records RunHubWorkflowAsync readiness recheck as Required For Direct Call Fail-Closed Behavior so direct command invocation returns the display-safe readiness blocker instead of starting workflow evidence.
Phase 3.510 source hardening records LocalModelHubRunReadinessSummary and LocalModelHubRunReadinessChecklistItem as Required For First Local Chat Readiness so prompt text, local model identity, download gate, activation gate, runtime gate, and worker gate are visible as structured, display-safe Models UI rows.
Phase 3.510 source hardening records ModelIdentityReady as Required For Ready Hub Run State so approvals alone cannot mark a local run ready without a visible local-ready catalog entry, catalog candidate, or active verified local model.
Phase 3.509 source hardening records installed-app Models UI smoke automation evidence for LocalEndpoint.Models.FirstRunGuide.ChecklistTitle, LocalEndpoint.Models.FirstRunGuide.Checklist, and LocalEndpoint.Models.HubRun.ReadinessStatus as Required For First Local Chat Evidence Discovery so future smoke reports must prove the checklist and next-action readiness status remain visible.
Phase 3.508 source hardening records LocalModelFirstRunGuide and LocalModelFirstRunChecklistItem as Required For First Local Chat so prompt text, local-ready GGUF choice or active verified model reuse, systems-without-GPUs compatibility, systems-with-GPUs compatibility, download approval, activation approval, runtime approval, worker approval, and prompt/response privacy boundaries appear as a compact Models UI checklist.
Phase 3.506 source hardening records LocalModelHubRunWorkflowPhaseStateDefinition as Required For Local Hub Run Phase State Validation so NotStarted, Passed, Blocked, and Skipped are the only accepted progress states before Hub run evidence emission.
Phase 3.506 source hardening records LocalModelHubRunWorkflowService named state consumption as Required For Local Hub Run Progress State Consistency so workflow gates cannot drift from the shared phase-state contract.
Phase 3.505 source hardening records LocalModelHubRunWorkflowPhaseDefinition as Required For Local Hub Run Phase Identity Projection so prompt gate, Hub browse, catalog save, registry reuse, download, activation, provider start, worker stream, and terminal evidence use one named phase contract.
Phase 3.505 source hardening records LocalModelHubRunProgressRecorder named phase consumption as Required For Local Hub Run Progress Evidence Consistency so UI, CLI, workflow service, and smoke evidence cannot drift on phase keys or labels.
Phase 3.504 source hardening records LocalModelHubRunLifecycleSummary as Required For Local Model Lifecycle Status Projection so browse, download, activation, and run status text is generated from one display-safe domain contract.
Phase 3.504 source hardening records LocalModelHubRunTerminalSummary as Required For Local Hub Run Terminal Status Projection so outcome, message, token event count, terminal kind, progress phase count, completion state, and generated-text availability are shared by Models UI and CLI without carrying prompt or generated text content.
Phase 3.481 packages the local Hugging Face chat-run CLI path into the current downloadable desktop tester ZIP: browse Hub metadata, filter GGUF candidates, download locally, verify SHA-256 and byte count, process intake, activate, load .uaix memory, approve readiness, and run a compatible local GGUF through the managed worker.
Phase 3.482 proves the local Hugging Face path again in fresh source/dev smoke: browse Hub metadata, filter GGUF candidates, download locally, verify SHA-256 and byte count, process intake, activate, load HelpfulAssistant.uaix, approve readiness, and run a compatible local GGUF through the managed worker.
Hugging Face Hub browse uses metadata for local catalog projection; it does not call hosted inference, Inference Providers, Spaces, Gradio APIs, prompt upload routes, or credentialed hosted endpoints.
Model candidates must pass format, license sidecar, inventory sidecar, SHA-256, byte-count, revision, and hardware-fit checks before intake.
Accepted snapshots become immutable content-addressed local artifacts; unchanged snapshots record AlreadyStored evidence.
Safetensors conversion is evidence-only until converted GGUF or ONNX output re-enters local intake as a new reviewed snapshot.
Catalog download, intake activation, selected-model use, worker allocation, prompt tokenization, inference, and token streaming all stay behind local desktop gates.
LocalChatViabilityEvidence blocks non-viable runtime, model, offload, local API, memory authority, UAIX authority, or public-site boundary state before a worker envelope exists.
Associated GGUF package-folder enumeration failures after scan block local model intake with VerificationBlocked evidence before content-addressed storage write, intake cleanup, or runtime execution can occur.
Actual GPU execution claims require runtime adapter backend and device IDs to match the selected offload plan backend and device IDs before LocalEndpoint accepts `GpuObserved` evidence.

Read the route

UAIX.LmRuntime

Where the managed runtime fits.

UAIX.LmRuntime is the bounded local GGUF adapter called only after LocalEndpoint has prepared and approved the display-safe request context.

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.

Read the route

LocalEndpoint owns

Package, policy, prompt, registry, and audit boundaries.

LocalEndpoint validates .uaix packages, expands .uai file memory, assembles prompts locally, owns policy decisions, persists registry and audit evidence, and writes JSONL events without prompt text or generated text.

UAIX.LmRuntime owns

Bounded managed local GGUF execution.

The runtime adapter receives an already-approved display-safe context, verifies the reviewed GGUF expectation, emits ordered token observations, preserves session identity, and does not parse .uaix packages or persist private text.

Worker handoff owns

Traceability before model allocation.

LocalChatViabilityEvidence is created before a worker envelope exists. Missing, malformed, non-isolated, authority-bearing UAIX context, invalid offload state, stale model selection, local API drift, or public boundary drift records a blocked no-op before model session allocation, tokenization, or inference; session identity, turn identity, and provider request fingerprints travel through start, stream, token, and terminal evidence.

Claim boundary Current website release: v1.5.254 Published desktop artifact: Phase 3.684 / 0.2.242.0 Latest source hardening accounted here: Phase 3.684 Phase 3.684 / 0.2.242.0 tester package is the current checksum-backed download lane Phase 3.376 records K80 driver proof-readiness as evidence-only public accounting Phase 3.251 records proof receipt identity as Required For GPU generation readiness; package, binary, runtime identity, execution proof, receipt identity, terminal token, and device-use evidence must agree before GPU inference can be claimed Phase 3.259 records release evidence runtime feed binding; tester ZIP discovery, UAIX.LmRuntime feed restore facts, runtime package counts, native package facts, native generation asset facts, and proof receipt facts must remain present before deployment evidence can pass Phase 3.261 records active GGUF model identity as Required For Active GGUF Model Smoke Evidence; active entry ID, model name, GGUF format, artifact SHA-256, and artifact byte count must validate before smoke evidence can pass Phase 3.263 records native generation proof artifact binding as Required For GPU generation proof receipt advancement; a same-feed display-safe JSON artifact and matching SHA-256 must exist before evidence can advance Phase 3.264 records native generation artifact identity binding as Required For native generation artifact acceptance; artifact schema, package identity, native binary identity, runtime library identity, and generation execution identity must match the receipt Phase 3.265 records native generation artifact identity-only validation as Required For LocalEndpoint-owned artifact acceptance; prompt text, generated text, command lines, and non-contract fields block evidence acceptance Phase 3.266 records package-feed native generation artifact identity-only validation as Required For release proof evidence; same-feed artifacts must contain only identity contract fields before proof receipt evidence can pass Phase 3.267 records native generation artifact identity contract value object validation as Required For LocalEndpoint-owned artifact acceptance; duplicate identity fields block before payload materialization Phase 3.268 records package-feed raw JSON artifact property review as Required For release proof evidence; duplicate identity fields block before payload identity values are read Phase 3.291 records native package payload safety as Required For package-feed evidence; native backend selection package-lane readiness still gates CUDA or K80 generation selection Phase 3.294 records K80 diagnostic target-match evidence while ActualGpuExecutionEvidencePresent=false and GGUF GPU inference remains unclaimed Phase 3.296 records local model intake associated GGUF enumeration fail-closed evidence while runtime execution remains closed UAIX.LmRuntime 3.3.29 is public on NuGet.org for the tracked runtime package set LocalEndpoints.com records publication status only and does not gain runtime authority

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.