.NET NuGet Package

What this page is for#

This page gives .NET and C# implementers one UAIX.org-owned place to find the official UAIX UAI-1 package identities, NuGet.org links, install commands, package roles, and authority boundary.

Current listed releases: UAIX.UAI.Abstractions 1.0.4, UAIX.UAI.Memory 1.0.4, UAIX.Talisman.AgentClient 0.1.10, and UAIX.Talisman.EcosystemManager 0.1.1. Current pending targets: UAIX.UAI 1.0.4 and UAIX.UAI.Build 1.0.4. A version is publicly installable only after NuGet.org lists that exact package and version.

Current NuGet.org listing status: UAIX.UAI.Abstractions 1.0.4, UAIX.UAI.Memory 1.0.4, UAIX.Talisman.AgentClient 0.1.10, and UAIX.Talisman.EcosystemManager 0.1.1 are listed. UAIX.UAI 1.0.4 and UAIX.UAI.Build 1.0.4 remain pending until NuGet.org lists those exact package IDs and versions.

Official UAIX package family#

Install#

Use only the package IDs that NuGet.org currently lists. Pending targets should be installed only after their exact package/version appears on NuGet.org.

dotnet add package UAIX.UAI.Abstractions --version 1.0.4
dotnet add package UAIX.UAI.Memory --version 1.0.4
dotnet add package UAIX.Talisman.AgentClient --version 0.1.10
dotnet add package UAIX.Talisman.EcosystemManager --version 0.1.1

Minimal UAI-1 message shape#

using System.Text.Json;
using UAIX.UAI.Core;

var body = JsonSerializer.SerializeToElement(new
{
    text = "Summarize the last support conversation.",
    intent = "summarize"
});

var message = UaiMessage.Create(
    profile: "agent.request",
    source: new Participant("agent", "source-agent"),
    target: new Participant("service", "target-service"),
    body: body);

var json = new UaiJsonSerializer().Serialize(message);

What the package line supports#

• Typed UAI-1 message models and validation helpers.
• JSON serialization helpers using the public UAI-1 field names.
• Safe routing discovery clients for UAIX .well-known route maps and route arrays.
• HTTP UAI sends that validate messages and reject non-HTTP endpoints before network use.
• Local AI memory stores that return defensive copies and write file-backed memory through temporary files.
• .uaix desktop AI memory package manifest generation, validation, import, export, activation preview, bundle removal, bundle activation state, and explicit active-bundle runtime context.
• A LocalEndpoint-style sample showing package import, activation preview, active bundle selection, and explicit running-instance send boundaries.
• A Talisman client package for protected-anchor policy gates, no-op talk-back, and evidence packets when an ecosystem chooses a Talisman hub such as Teleodynamic.com.
• A Talisman ecosystem-manager package that can host AgentClient-compatible ASP.NET Core hub routes for local/service dogfooding, including LocalEndpoint-style anchor sync, review queues, audit records, client-agent messages, and OpenAPI discovery.

Quality and safety contract#

• .uaix imports validate before extraction and reject path traversal, absolute paths, drive-root paths, Windows device names, path segment whitespace, duplicate normalized paths, symlinks, manifest/ZIP coverage mismatches, unsupported manifest values, and hash mismatches.
• Imports replace the target bundle content directory rather than merging into stale files and use a staged replacement path to avoid stale partial imports.
• Exports can synthesize the newer manifest files array, hashes, scopes, entrypoints, and support boundary when a source folder does not already contain .uai/manifest.uaix.json; exports must write the .uaix file outside the source directory so a package cannot accidentally include itself.
• Activation previews compare current and candidate bundle scopes, entrypoints, and support boundaries before active state changes.
• Bundle activation is local state only; it does not send, approve, apply, synchronize, or mutate a running AI instance.
• Runtime bundle context is attached only when an application explicitly sends a UAI message through the runtime channel.
• Talisman client hub responses are evidence for review, not approval to mutate totem.uai, taboo.uai, or talisman.uai.

Authority boundary#

• Use UAI-1, Schemas, Registry, Examples, the Validator, and the .uaix Package Format as the public standards and package-format record.
• Use this page for official UAIX-owned .NET package identity, install guidance, and support boundary.
• Use the UAIX Talisman Client guide for protected-anchor client behavior and the Talisman System page for the underlying Talisman memory pattern.
• Do not treat package installation as certification, endorsement, conformance approval, hosted import, automatic repository write, automatic LLM Wiki sync, credential validation, CLI support, or general runtime availability.
• Keep release evidence attached to the relevant .NET Bridge Track, Changelog, and News entry before making public support claims.

Adaptive interoperability track#

The planned .NET Adaptive Interoperability Track is where UAIX records the future package goal for capability-profile reading, fallback-chain resolution, ASP.NET Core route metadata, typed HttpClient support, UAI-1 evidence export, and optional MCP/A2A adapters. Keep that track planned until code, fixtures, tests, NuGet package evidence, and release notes exist.

Next step#

Open the listed NuGet package pages above to confirm the exact target version, treat pending package IDs as source/release targets until NuGet.org lists them, then return to the .NET Bridge Track and Validator to keep implementation evidence attached to the public UAI-1 record.