UAI-1 for .NET packages and implementation support

1. Keep three surfaces separate

A working Protocol5 package integration can have a human page, a compact language source, and a structured developer endpoint. The package helps with export, validation, rendering, and ASP.NET routing. Public UAI-1 definitions and support claims still come from UAIX.org.

2. Keep locale URLs separate from rendered UAI routes

The leading route segment should stay descriptive. Human pages use locale tags such as en-US. Rendered UAI uses the dedicated /uai-rendered/... prefix. Public URLs should not use private-use tags like /x-uai-1/... or invented locale shapes like /x-en-US-1/.... That keeps /UAI-1 for the versioned specification and machine artifacts instead of reusing it as a pseudo-language route.

/{lang}/UniversalArtificialIntelligence/{page}
/en-US/UniversalArtificialIntelligence/Registry
/uai-rendered/UniversalArtificialIntelligence/Validate

3. Publish the page with alternate machine links

Every important human page should advertise its paired machine assets. Put the alternate links in the page head and emit the same relationship from the host when possible.

<link rel="alternate" type="application/uai+json" href="/UAI/index.uai.json" />
<link rel="alternate" type="text/uai" href="/UAI/index.uai" />

4. Register the ASP.NET Core runtime

In a .NET site, register the Protocol5 UAI runtime once, then use the middleware before endpoint handlers that need language or render-mode state.

using Protocol5.UAI;

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddProtocol5UaiWebsiteSupport(options =>
{
    options.DefaultCulture = "en-US";
    options.QueryKeys.Add("lang");
    options.ModeQueryKeys.Add("mode");
    options.ModeQueryKeys.Add("uai-mode");
});

var app = builder.Build();
app.UseProtocol5UaiWebsiteSupport();

5. Export and validate content

When a page changes, export the rendered HTML into a UAI-1 document, validate the JSON for package compatibility, and keep the compact source paired with the same human route. Use UAIX.org for public conformance claims.

dotnet run --project tools\Protocol5.UAI.SiteExporter\Protocol5.UAI.SiteExporter.csproj -- export-manifest.json
dotnet run --project tools\Protocol5.UAI.Validator\Protocol5.UAI.Validator.csproj -- --embedded-examples --roundtrip

6. Render UAI as a language layer

Rendered UAI should come from a lexicon, phrase map, compact records, or a validated document. It should not be generated as decorative glyph noise at runtime. If a semantic render is missing, the runtime should fall back to the normal human text and report unresolved keys for inspection. If a publication also uses Radix 63404 for numeric display, keep that as a separately declared Protocol5 representation choice.

7. Ship with an operations checklist

1. Keep package endpoints such as /registry/uai-lexicon.json, /uai-1/registry, /uai-1/schema, and /uai-1/validate reachable when you intentionally expose compatibility mirrors.
2. Keep Content-Type: application/uai+json on structured UAI JSON responses.
3. Keep Content-Language and lang="x-uai-1" behavior tied to render mode, not to local number or date formatting.
4. Keep InvariantCulture for canonical serialization.
5. Keep old /UAI links alive while presenting locale-prefixed human routes and /uai-rendered/... for rendered UAI views.