UAIX Agent Fallbacks and .NET Package Boundary

This page records the public-safe long-memory outcome for six UAIX.org Improvement reports processed on 2026-06-15.

UAIX.org remains canonical for UAI-1, Agent Fallbacks, Agent Executability Matrix records, the .NET package guidance surface, validators, examples, schemas, roadmap, governance, and support boundaries. AIWikis preserves the reviewed lesson and raw evidence so future agents do not reopen large source reports by default.

Source Evidence

The raw report evidence is preserved in:

raw/uaix/reports/2026-06-15-agent-fallbacks-dotnet-boundary/manifest.json

The manifest records six copied reports, SHA-256 hashes, byte counts, dispositions, and source-site copy removal status. The namespace is /uaix/reports/2026-06-15-agent-fallbacks-dotnet-boundary/.

Reviewed Outcome

The reports were applied as a UAIX source-only standards-support refinement.

• Agent-capable routes should declare the highest supported path, the lowest safe fallback, POST-blocked fallback, live-GET-blocked fallback, MCP-unavailable fallback, auth-unavailable fallback, tool-unavailable fallback, human-review URL, and No-Op behavior.
• UAIX should serve every client class honestly, from URL-only chatbots through indexed fetchers, browser agents, JSON POST agents, authenticated owner agents, restore/readback agents, multi-agent runtimes, A2A peers, MCP clients, and MCP-server-capable hosts.
• A richer route must not imply that every agent can execute that route. The safe behavior is to ramp up only after capability is proven and ramp down before guessing.
• No-Op is a first-class safe result when capability, consent, tool availability, authentication, public-safe context, or fallback evidence is missing.
• MCP and A2A remain runtime-provided capabilities. UAIX can document patterns and evidence records, but this pass does not make UAIX.org a hosted MCP server, A2A runtime, adapter host, scheduler, or execution service.

.NET Package Version Rule

The human clarified the versioning rule during this work:

Version the .NET packages, not the UAI spec.

The resulting boundary is:

• UAI-1 remains the public standards version at v1.0.
• .NET/NuGet versions are implementation software versions.
• Current listed implementation packages include UAIX.UAI.Abstractions 1.0.4, UAIX.UAI.Memory 1.0.4, and UAIX.Talisman.AgentClient 0.1.10.
• Pending or local package targets such as UAIX.UAI 1.0.4 and UAIX.UAI.Build 1.0.4 must not be called installable until NuGet.org lists the exact package ID and version.
• Release notes, guides, validators, examples, and package pages must keep package versions separate from UAI-1 v1.0.

Planned .NET Architecture Memory

The planned adaptive .NET package track should provide:

• capability profile reading and normalization
• agent/chatbot capability classification
• fallback-chain resolution
• ASP.NET Core route metadata helpers
• typed HttpClient support
• UAI-1 evidence export
• optional MCP adapter only when the host runtime provides MCP
• optional A2A adapter only when the host runtime provides A2A
• validator fixtures and conformance tests for ramp-up and ramp-down decisions

This is implementation-package planning, not a standards-version bump.

Non-Claims

This memory does not claim live UAIX.org publication, package build completion, NuGet publication, hosted MCP support, hosted A2A support, runtime execution, automatic repository writes, hosted import validation, automatic LLM Wiki sync, SDK or CLI support beyond listed package evidence, certification, endorsement, or UAI-1 conformance for any consuming project.

Agent Retrieval Rule

Future agents should load this page, then the source/concept/log wiki nodes, before opening the six raw reports. Open raw reports only when exact report wording or checksum evidence is needed.

Related nodes:

• wiki/sources/uaix-agent-fallbacks-dotnet-boundary-2026-06-15.md
• wiki/concepts/uaix-agent-fallbacks-dotnet-boundary.md
• wiki/logs/uaix-agent-fallbacks-dotnet-boundary-2026-06-15.md