Protocol5.com Source Memory Guide

This page explains how AIWikis.org should remember Protocol5.com in detail without turning AIWikis into the Protocol5 source of truth or the UAI standards authority.

Protocol5.com remains the parent public brand for Mathematics and the official UAI .NET Hub. UAIX.org remains normative for UAI standards, schemas, validator behavior, registry, governance, roadmap, changelog, and conformance. AIWikis preserves Protocol5 source memory so humans and agents can inspect package, route, and distribution evidence with the boundary still visible.

What Protocol5 Owns

Protocol5 owns the public Protocol5 brand and two sibling public areas:

Area	Protocol5 Role
Mathematics	Exact arithmetic, variable-base tools, Radix 63404, calculator surfaces, and preserved generated Prime/Fibonacci reference routes.
UAI .NET Hub	Protocol5-owned .NET implementation guidance, NuGet artifacts, starter ZIPs, ASP.NET support notes, compatibility mirrors, route contracts, and local inspection pages.

Protocol5 does not own UAI-1 standards truth. When a Protocol5 page mentions UAI-1 standards, schemas, registry, validator authority, governance, roadmap, changelog, or conformance, the authority route must point back to UAIX.org.

Public Truth Shape

Use Protocol5.com first when a claim is about Protocol5-owned implementation packages or public routes.

Need	Protocol5 Route Or File
Parent brand	https://protocol5.com/
UAI implementation hub	https://protocol5.com/uai and https://protocol5.com/uai/dotnet
Architecture and distribution boundary	https://protocol5.com/UAI/architecture
Route contract	https://protocol5.com/protocol5-route-contract.json
Package discovery	https://protocol5.com/UAI-1.json
.NET package artifact	https://protocol5.com/downloads/Protocol5.UAI.CSharp.1.0.0.nupkg
.NET web starter package	https://protocol5.com/downloads/protocol5-uai-1-csharp-web-starter-v2.7.0.zip
Registry and schema mirrors	https://protocol5.com/registry/uai-1.json and https://protocol5.com/schema/uai-1.schema.json

Use UAIX.org first when the claim is about UAI-1 public authority. Use AIWikis only for preserved source memory, generated file pages, provenance, and cross-site routing.

What AIWikis Preserves

AIWikis preserves Protocol5 memory through several layers:

• /protocol5/ gives the Protocol5 source-system entry route.
• /protocol5/public/ summarizes current Protocol5 public content and discovery files.
• /protocol5/uai-system/ exposes Protocol5 AI Memory files, .uai records, route contracts, package-support docs, and implementation-boundary evidence as focused pages.
• /protocol5/uai-system/files/... gives individual source-file pages with raw public content, generated explanation, provenance, update history, and machine-readable metadata.
• /protocol5/provenance/ lists imported Protocol5 source references and hashes.
• /concepts/protocol5/, /files/, and /reports/ support retrieval by concept, file, and evidence type.
• wiki/sources/protocol5-uai-memory-seed-2026-05-01.md records the first Protocol5 UAI AI Memory seed.
• raw/system-archives/2026-05-02-protocol5-report-preservation.json records the 2026-05-02 copy/hash manifest for Protocol5 reports, modernization docs, and active Improvement design screenshots.
• wiki/sources/protocol5-report-preservation-2026-05-02.md and wiki/logs/protocol5-report-preservation-2026-05-02.md summarize that preservation pass without publishing the raw reports as public truth.
• .uai/ files keep compact AIWikis handoff truth about Protocol5 coverage and non-claims.

This lets AIWikis remember Protocol5 in detail while keeping Protocol5.com as the source for Protocol5 package behavior and UAIX.org as the source for UAI standards truth.

Frozen Route Boundary

Protocol5 has a special compatibility rule: generated Prime and Fibonacci route families are frozen. AIWikis should not sync those generated numeric page trees as public source memory. It may preserve wrapper pages, route contracts, and high-level references, but not the generated {number}.htm families.

Do not edit, restyle, regenerate, rename, move, mirror, or package those generated route families from AIWikis work. Protocol5 source memory should explain the boundary rather than absorbing the frozen artifacts.

Update Triggers

Update this AIWikis memory whenever Protocol5 changes:

• UAI .NET Hub package pages, downloads, package names, checksums, or version labels.
• Protocol5.UAI.CSharp package support notes, route contracts, starter ZIPs, or ASP.NET guidance.
• Public route shape such as /uai, /uai/dotnet, /mathematics, /UAI-1.json, registry mirrors, schema mirrors, or compatibility aliases.
• The boundary between Protocol5 implementation mirrors and UAIX.org standards authority.
• Frozen Prime/Fibonacci route policy or compatibility constraints.
• Protocol5 AI Memory starter files, .uai records, or LLM Wiki memory plan.

Do Not Claim

AIWikis must not claim:

• It is the Protocol5 source of truth.
• Protocol5.com is the UAI-1 standards site, validator authority, registry authority, roadmap authority, governance authority, certification authority, or endorsement surface.
• Protocol5 package mirrors override UAIX.org.
• Protocol5 .NET package existence proves UAI-1 conformance, certification, endorsement, or production readiness.
• AIWikis owns Protocol5 packages, NuGet artifacts, route contracts, or generated Mathematics references.
• AIWikis should sync generated Prime or Fibonacci route trees into public memory.

When in doubt, AIWikis should say "Protocol5.com owns implementation package distribution; UAIX.org remains normative for UAI-1."

AI-Agent Use

When an AI agent needs Protocol5 truth, it should:

1. Start with Protocol5 source files or public routes for Protocol5 implementation/package claims.
2. Start with UAIX.org for UAI-1 standards, validator, registry, roadmap, governance, changelog, and conformance claims.
3. Use AIWikis for preserved Protocol5 memory, provenance, generated explanations, and cross-site claim routing.
4. Avoid the generated Prime and Fibonacci route trees unless the human explicitly asks for compatibility analysis.
5. Keep Protocol5 Mathematics, Protocol5 UAI .NET Hub, UAIX standards authority, and AIWikis long memory separate.

AIWikis is strongest when it answers: what does Protocol5 own, where is the implementation evidence, which UAIX route owns the standard, and what must not be overstated?