Public package registry

NuGet packages by Michael.Kappel.

Public NuGet packages are a credible .NET ecosystem signal: reusable libraries with package identities, documentation surfaces, and registry-backed distribution. This page organizes the package family by responsibility without embedding package version numbers. Use the NuGet profile as the current source for install commands, package history, and registry metadata.

Open NuGet Profile Runtime Projects Evidence Map

25public packages mapped

5responsibility groups

.NETcredible package ecosystem signal

NuGet.orgsource for current package metadata

NuGet family

UAI and AI Memory

Packages for UAI message contracts, local memory stores, build-time support, and adaptive interoperability boundaries.

Package

UAIX.UAI

UAI-1 message envelopes, JSON serialization, route discovery, HTTP sends, and package validation surfaces.

UAI AI Memory Package Validation

Open package

Package

UAIX.UAI.Abstractions

Shared interfaces and models for clients, memory stores, project handoff integrations, and libraries that need UAI contracts.

Contracts Interfaces Memory Models

Open package

Package

UAIX.UAI.Memory

Local in-memory and file-backed memory stores for project handoff, preferences, release notes, and operational context.

Memory Stores File Backing Handoff

Open package

Package

UAIX.UAI.Build

Build-time support assets for projects that need repeatable UAIX/UAI package and handoff behavior.

MSBuild Package Support Automation

Open package

Package

UAIX.AdaptiveInteroperability

Capability profiling, fallback-chain resolution, ASP.NET route metadata, typed HTTP discovery, and protocol adapter boundaries.

Interoperability Fallbacks Route Metadata

Open package

NuGet family

Talisman and Agent Ecosystem

Client and hub packages for protected-anchor synchronization, policy evidence, review queues, and local agent message flow.

Package

UAIX.Talisman.AgentClient

Protected-anchor client surfaces for Talisman policy gates, no-op talk-back, local evidence packets, and hub configuration.

Agent Client Protected Anchors Evidence

Open package

Package

UAIX.Talisman.EcosystemManager

ASP.NET Core hub patterns for client sync, client-agent messages, UAI bundle ingest, review queues, and audit records.

ASP.NET Core Hub Audit

Open package

NuGet family

Local LLM Runtime

A layered .NET runtime package family for GGUF intake, LLaMA-oriented model execution, tokenization, sampling, tensors, and local endpoint integration.

Package

UAIX.LmRuntime.LocalEndpoint

High-level local-only GGUF facade for verified file intake, bounded loading, isolated sessions, and deterministic generation.

LocalEndpoint GGUF Application Facade

Open package

Package

UAIX.LmRuntime.Abstractions

Stable public interfaces, inference contracts, runtime settings, and diagnostics shared by the runtime stack.

Contracts Diagnostics Runtime Settings

Open package

Package

UAIX.LmRuntime.Gguf

GGUF parser, metadata model, tensor catalog, sharding awareness, and validation-oriented model-file handling.

GGUF Metadata Tensor Catalog

Open package

Package

UAIX.LmRuntime.Models.Llama

LLaMA-family graph configuration and reference model primitives for local runtime integration.

LLaMA Model Graph Reference Primitives

Open package

Package

UAIX.LmRuntime.Tokenization

Tokenizer and chat-template rendering surfaces for local model prompts and deterministic runtime plumbing.

Tokenization Chat Templates Prompts

Open package

Package

UAIX.LmRuntime.Sampling

Sampler and logits-processor surfaces for generation behavior, output control, and repeatable inference experiments.

Sampling Logits Generation

Open package

Package

UAIX.LmRuntime.Tensors

Tensor descriptors, memory descriptors, layout metadata, and quantization-aware data shapes.

Tensors Layouts Quantization

Open package

Package

UAIX.LmRuntime.Kernels.Cpu

CPU kernel primitives for scalar and vector-friendly local execution paths.

CPU Kernels Execution Math Primitives

Open package

Package

UAIX.LmRuntime.Acceleration

Portable acceleration contracts, backend registration, device probing, selection policies, fallback reporting, and diagnostics.

Acceleration Backend Registry Fallbacks

Open package

NuGet family

Runtime Backends

Backend identity and integration packages that keep device probing, native assets, and acceleration choices explicit.

Package

UAIX.LmRuntime.Backends.CpuManaged

Managed CPU backend path for hosts that need portable local execution and explicit capability reporting.

CPU Managed Portable

Open package

Package

UAIX.LmRuntime.Backends.Cuda

CUDA backend integration identity and registration surface for GPU-aware runtime hosts.

CUDA GPU Backend

Open package

Package

UAIX.LmRuntime.Backends.Cuda.Native.win-x64

Windows x64 native CUDA asset package for hosts that own the matching GPU deployment boundary.

CUDA Native Windows x64 Native Assets

Open package

Package

UAIX.LmRuntime.Backends.Cuda.LegacyK80.win-x64

Windows x64 CUDA asset identity for legacy K80-class diagnostic and compatibility boundaries.

CUDA Legacy K80 Diagnostics

Open package

Package

UAIX.LmRuntime.Backends.DirectML

DirectML backend identity for Windows acceleration planning and device capability separation.

DirectML Windows Acceleration

Open package

Package

UAIX.LmRuntime.Backends.Vulkan

Vulkan backend identity for cross-platform GPU acceleration planning.

Vulkan GPU Cross-Platform

Open package

Package

UAIX.LmRuntime.Backends.Metal

Metal backend identity for Apple platform acceleration planning.

Metal Apple GPU

Open package

Package

UAIX.LmRuntime.Backends.Rocm

ROCm backend identity for AMD GPU acceleration planning and device-boundary documentation.

ROCm AMD GPU Backend

Open package

NuGet family

ErrorNotifier

Logging package for sending .NET application errors into ErrorNotifier-oriented operational workflows without blocking request paths.

Package

ErrorNotifier.Extensions.Logging

Non-blocking Microsoft.Extensions.Logging provider with bounded channels, batching, retry, fallback storage, and hosted or self-hosted endpoint overrides.

Logging ErrorNotifier Microsoft.Extensions.Logging

Open package

Boundary

Registry authority stays on NuGet.

The portfolio page explains how the package names fit together. NuGet remains the source for install syntax, current metadata, downloads, package history, and deprecation or replacement notices.

No stale versionsThis route intentionally avoids hard-coded package version numbers.

Responsibility firstCards describe what each package owns so reviewers can route into the right package quickly.

Evidence linkedEach package has a direct NuGet link rather than a copied package body.

FAQ

Common review questions.

Short answers are rendered in the HTML source and mirrored into JSON-LD where appropriate.

Why are package version numbers omitted?

The page intentionally avoids hard-coded package version numbers so NuGet remains the current source for installs, package history, downloads, and registry metadata.

What does this page add beyond the NuGet profile?

It groups the public package names by responsibility so reviewers can understand the UAI memory, Talisman, local LLM runtime, backend, and logging package boundaries before opening NuGet.

Where should a developer verify package state?

Developers should use the direct NuGet package links for current metadata, commands, package history, and replacement or deprecation notices.

FAQ

Common reviewer questions.

Visible page content matches the route-specific FAQ structured data.

Why does the NuGet page omit package version numbers?

NuGet is the registry authority for current versions, install commands, package history, and metadata, so the portfolio keeps stable responsibility summaries and direct package links while still treating public packages as a credible .NET ecosystem signal.

How should the package groups be used?

The groups help technical reviewers route into UAI memory, Talisman, local LLM runtime, runtime backend, or ErrorNotifier package responsibilities without reading every package first.