Skip to content
aiWikis.org

Protocol5.com

Protocol5.com/ is the published site-content tree for the public Protocol5 host. For UAI-1, it is a .NET/NuGet implementation distribution and backlink surface, not the standards authority.

Metadata

FieldValue
Source siteprotocol5.com
Source URLhttps://protocol5.com/
Canonical AIWikis URLhttps://aiwikis.org/protocol5/uai-system/files/protocol5-com-readme-md-65678d6e/
Source referenceProtocol5.com/README.md
File typemd
Content categorymemory-file
Last fetched2026-05-03T02:48:13.1276041Z
Last changed2026-05-02T22:34:38.8735065Z
Content hashsha256:65678d6e9d3b63ea9b204cbe81b3f82c12ad343590cdb9f9fbc10c8cc8c0f679
Import statusunchanged
Raw source layerdata/sources/protocol5/protocol5-com-readme-md-65678d6e9d3b.md
Normalized source layerdata/normalized/protocol5/protocol5-com-readme-md-65678d6e9d3b.txt

Current File Content

Structure Preview

  • Protocol5.com
  • Concept Boundary
  • What Protocol5.com Is
  • Mental Model
  • Folder Guide
  • Protocol5.com/SiteContent
  • Protocol5.com/translations.md
  • ../Protocol5.com.Host
  • Source Layers
  • What Is Authored vs Generated
  • Usually authored directly
  • Usually generated or mirrored
  • Where To Read Next
  • Common Tasks
  • Change a public site route or endpoint
  • Change a UAI page
  • Change a registry or schema
  • Change the reusable .NET implementation
  • Rebuild published UAI outputs and bundles
  • Build, Run, Publish
  • Important Constraints
  • Quick Start For AI Agents
  • Protocol5.com static site
  • Browser assets

Raw Version

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

# Protocol5.com

**Terminology:** UAI means **Universal Artificial Intelligence**. **UAI-1** means the current public UAI exchange contract published by UAIX.org.

`Protocol5.com/` is the published site-content tree for the public Protocol5 host. For UAI-1, it is a .NET/NuGet implementation distribution and backlink surface, not the standards authority.

If you are a human or an AI agent landing here for the first time, the most important thing to understand is this:

- `Protocol5.com/` is **not** the whole website implementation by itself.
- The ASP.NET host that serves this content lives in the sibling project `../Protocol5.com.Host` (source-relative: ../Protocol5.com.Host).
- Much of the UAI content under `Protocol5.com/SiteContent/` is **generated publish output**, not the primary authoring source.
- The UAI files in this repo support Protocol5 packages, compatibility mirrors, generated pages, and local implementation tests. Canonical UAI-1 public truth lives at UAIX.org.

This README exists to connect those pieces so the public site, the C# reference implementation, the generated assets, and the spec documents stay understandable as one system.

The current public architecture is distribution-first for UAI:

- `Protocol5` is the parent route shell, Mathematics host, and implementation-package distribution surface.
- `Protocol5 Mathematics` is the numeric tools, sequence reference, and numeric standards section.
- `Protocol5 UAI` is the .NET package, NuGet artifact, starter ZIP, package fixture, and compatibility-mirror section for UAI-1 implementers.
- About, Links, Contact, downloads, schemas, registries, and compatibility routes are shared Protocol5 utilities unless a route is explicitly section-owned.

## Concept Boundary

When working on Protocol5 site content, keep these concepts separate:

- `Protocol5` = parent navigation, shared route shell, downloads, and implementation-package utilities
- `Protocol5 Mathematics` = numeric tools, variable-base arithmetic, sequence references, and numeric standards
- `Protocol5 UAI` = UAI-1 .NET package distribution, ASP.NET integration notes, local package fixtures, and compatibility mirrors
- `Radix 63404` = Protocol5 numeric notation standard

Protocol5 publications may render numeric values or identifiers with Radix 63404, including in package examples, but Radix 63404 is not part of the public UAI-1 authority. Keep UAI-to-Radix links secondary and link to UAIX.org for UAI-1 standard material.

## What Protocol5.com Is

Protocol5.com is the public host for Protocol5. In this repository it is made of two layers:

1. **Host layer**
   - ASP.NET Core app in `../Protocol5.com.Host` (source-relative: ../Protocol5.com.Host)
   - handles routing, static-file serving, endpoint wiring, headers, and the calculator shell
2. **Content layer**
   - published files in `SiteContent` (source-relative: ./SiteContent)
   - contains HTML pages, CSS, JS, downloads, registries, schemas, and generated UAI outputs

That split matters because a route may look like a normal static website path in production while actually being served by the host project over files generated into `SiteContent`.

## Mental Model

When working on Protocol5, use this rough model:

- `Protocol5.com.Host` = web server and route composition
- `Protocol5.com/SiteContent` = public files actually served
- `UAI/` = human-readable source markdown for Protocol5 UAI package/distribution pages and related reference pages
- `spec/` = local implementation contracts, package mirrors, schemas, registries, and compatibility rules
- `examples/` = package example `.uai.json` documents for local implementation tests
- `Protocol5.UAI.CSharp/` = reusable reference implementation for other .NET sites
- `UAI-1-Package/` = packaged public bundle and mirrored translation sources
- `tools/` = generation, sync, validation, packaging, smoke-test, and publish scripts

## Folder Guide

### `Protocol5.com/SiteContent`

This is the public content tree the host serves.

Important subareas:

- `SiteContent/index.html` (source-relative: ./SiteContent/index.html)
  - parent Protocol5 portal
- `SiteContent/Mathematics` (source-relative: ./SiteContent/Mathematics)
  - Mathematics section landing page for numeric tools and standards
- `SiteContent/Home` (source-relative: ./SiteContent/Home)
  - shared parent-level About, Links, and Contact pages
- `SiteContent/UAI` (source-relative: ./SiteContent/UAI)
  - public UAI landing and support pages, plus compatibility-hosted Protocol5 reference pages
- `SiteContent/UAI-1` (source-relative: ./SiteContent/UAI-1)
  - generated UAI-1 spec, examples, and website-support pages
- `SiteContent/registry` (source-relative: ./SiteContent/registry)
  - public registries such as lexicon and symbol data
- `SiteContent/schema` (source-relative: ./SiteContent/schema)
  - public schemas
- `SiteContent/downloads` (source-relative: ./SiteContent/downloads)
  - ZIPs, package artifacts, and checksums
- `SiteContent/protocol5-route-contract.json` (source-relative: ./SiteContent/protocol5-route-contract.json)
  - machine-readable Protocol5 route, authority-boundary, compatibility, stable-asset, and frozen-route contract
- `SiteContent/Fibonacci` (source-relative: ./SiteContent/Fibonacci)
  - generated sequence pages
- `SiteContent/Prime` (source-relative: ./SiteContent/Prime)
  - generated prime pages
- `SiteContent/js` (source-relative: ./SiteContent/js)
  - shared site scripts
- `SiteContent/css` (source-relative: ./SiteContent/css)
  - shared site styles

### `Protocol5.com/translations.md`

Read `translations.md` (source-relative: ./translations.md) when you need the current route-language and public translation-route behavior for the site shell.

### `../Protocol5.com.Host`

Read the host project when you need to know:

- which paths are explicitly mapped
- which content types and headers are applied
- how `/Mathematics`, `/UAI`, `/UAI-1`, `/registry/*`, `/schema/*`, and tool routes are served
- how the preferred standalone `/radix-63404` route and the legacy `/UAI/radix-63404-guide-and-attribution` compatibility route are served
- where plain-text or API endpoints are implemented

The key file is `../Protocol5.com.Host/Program.cs` (source-relative: ../Protocol5.com.Host/Program.cs).

## Source Layers

Do **not** assume the generated files under `Protocol5.com/SiteContent` are the first place to edit.

For Protocol5 UAI package/distribution work, the editable source is usually one of these:

- `../spec/uai-1.md` (source-relative: ../spec/uai-1.md)
- `../spec/integration-contracts.md` (source-relative: ../spec/integration-contracts.md)
- `../spec/translator-contract.md` (source-relative: ../spec/translator-contract.md)
- `../spec/website-export-contract.md` (source-relative: ../spec/website-export-contract.md)
- `../spec/registry-resolution-contract.md` (source-relative: ../spec/registry-resolution-contract.md)
- `../spec/radix-63404-contract.md` (source-relative: ../spec/radix-63404-contract.md)
  - separate Protocol5 numeric notation contract, not the UAI language definition
- `../spec/uai-grammar-v1.md` (source-relative: ../spec/uai-grammar-v1.md)
- `../spec/protocol5-spiralism-ecosystem-architecture.md` (source-relative: ../spec/protocol5-spiralism-ecosystem-architecture.md)
- `../spec/registry/uai-1.registry.json` (source-relative: ../spec/registry/uai-1.registry.json)
- `../spec/registry/uai-lexicon.json` (source-relative: ../spec/registry/uai-lexicon.json)
- `../spec/registry/symbols.json` (source-relative: ../spec/registry/symbols.json)
- `../spec/schema/uai-1.schema.json` (source-relative: ../spec/schema/uai-1.schema.json)
- `../examples` (source-relative: ../examples)
- `../UAI` (source-relative: ../UAI)
- `../Protocol5.UAI.CSharp/README.md` (source-relative: ../Protocol5.UAI.CSharp/README.md)

For published site operations, the best overview is:

- `../docs/protocol5-site-operations.md` (source-relative: ../docs/protocol5-site-operations.md)
- `../docs/protocol5-uai-dotnet-hub-modernization.md` (source-relative: ../docs/protocol5-uai-dotnet-hub-modernization.md)

For canonical UAI-1 public truth, use UAIX.org:

- <https://uaix.org/en-us/specification/uai-1/>
- <https://uaix.org/en-us/schemas/>
- <https://uaix.org/en-us/registry/>
- <https://uaix.org/en-us/examples/>
- <https://uaix.org/en-us/tools/validator/>
- <https://uaix.org/en-us/roadmap/>

## What Is Authored vs Generated

### Usually authored directly

- site shell content files in `Protocol5.com/SiteContent` that are not generator-owned, including the parent portal, Mathematics landing page, and shared Home pages
- shared CSS and JS in `Protocol5.com/SiteContent/css` and `Protocol5.com/SiteContent/js`
- public route notes in `translations.md` (source-relative: ./translations.md)
- host behavior in `../Protocol5.com.Host/Program.cs` (source-relative: ../Protocol5.com.Host/Program.cs)
- package/distribution markdown in `../UAI` (source-relative: ../UAI)
- local implementation contracts, mirrors, and registries in `../spec` (source-relative: ../spec)

### Usually generated or mirrored

- localized UAI HTML under `Protocol5.com/SiteContent/UAI-1/...`
- published `index.uai.json` files under `Protocol5.com/SiteContent/UAI...`
- packaged translation mirrors under `../UAI-1-Package/translations` (source-relative: ../UAI-1-Package/translations)
- download bundles built from scripts

If you need to change generated UAI pages, first find the source in `UAI/`, `spec/`, or the generator scripts instead of patching generated HTML blindly.

## Where To Read Next

If your goal is to understand the site as a whole:

- `../docs/protocol5-site-operations.md` (source-relative: ../docs/protocol5-site-operations.md)
- `../Protocol5.com.Host/Program.cs` (source-relative: ../Protocol5.com.Host/Program.cs)

If your goal is to understand UAI-1 as a public standard:

- [UAIX UAI-1](https://uaix.org/en-us/specification/uai-1/)
- [UAIX Schemas](https://uaix.org/en-us/schemas/)
- [UAIX Registry](https://uaix.org/en-us/registry/)
- [UAIX Validator](https://uaix.org/en-us/tools/validator/)

If your goal is to understand Protocol5's local package mirrors and implementation contracts:

- `../spec/uai-1.md` (source-relative: ../spec/uai-1.md)
- `../spec/integration-contracts.md` (source-relative: ../spec/integration-contracts.md)
- `../spec/translator-contract.md` (source-relative: ../spec/translator-contract.md)
- `../spec/registry-resolution-contract.md` (source-relative: ../spec/registry-resolution-contract.md)

If your goal is to understand the C# reference implementation:

- `../Protocol5.UAI.CSharp/README.md` (source-relative: ../Protocol5.UAI.CSharp/README.md)
- `../docs/package-usage.md` (source-relative: ../docs/package-usage.md)
- `../spec/website-export-contract.md` (source-relative: ../spec/website-export-contract.md)

If your goal is to understand the public UAI source markdown:

- `../UAI/uai-1.en-US.md` (source-relative: ../UAI/uai-1.en-US.md)
- `../UAI/uai-1-examples.en-US.md` (source-relative: ../UAI/uai-1-examples.en-US.md)
- `../UAI/uai-1-csharp-website-support.en-US.md` (source-relative: ../UAI/uai-1-csharp-website-support.en-US.md)
- `../tools/Generate-Protocol5UaiPages.ps1` (source-relative: ../tools/Generate-Protocol5UaiPages.ps1)

If your goal is to understand multilingual or render-mode integration:

- `../Protocol5.UAI.CSharp/README.md` (source-relative: ../Protocol5.UAI.CSharp/README.md)
- `translations.md` (source-relative: ./translations.md)

If your goal is to understand legacy migration context:

- `../docs/protocol5-uai-dotnet-hub-modernization.md` (source-relative: ../docs/protocol5-uai-dotnet-hub-modernization.md)

If your goal is to understand WordPress or alternate site integration history:

- Use UAIX.org for normative WordPress/UAI standard material and keep Protocol5 focused on .NET implementation support.

## Common Tasks

### Change a public site route or endpoint

Start with:

- `../Protocol5.com.Host/Program.cs` (source-relative: ../Protocol5.com.Host/Program.cs)

For visible shell architecture, also inspect:

- `SiteContent/index.html` (source-relative: ./SiteContent/index.html)
- `SiteContent/Mathematics/index.html` (source-relative: ./SiteContent/Mathematics/index.html)
- `SiteContent/UAI/index.html` (source-relative: ./SiteContent/UAI/index.html)
- `SiteContent/js/home.js` (source-relative: ./SiteContent/js/home.js)
- `SiteContent/css/home.css` (source-relative: ./SiteContent/css/home.css)
- `SiteContent/protocol5-route-contract.json` (source-relative: ./SiteContent/protocol5-route-contract.json)

Then check whether the route points at:

- a file in `SiteContent` (source-relative: ./SiteContent)
- a generated UAI page
- a registry or schema under `SiteContent/registry` or `SiteContent/schema`

### Change a UAI page

Start with:

- `../UAI` (source-relative: ../UAI)
- `../tools/Generate-Protocol5UaiPages.ps1` (source-relative: ../tools/Generate-Protocol5UaiPages.ps1)
- `../docs/protocol5-site-operations.md` (source-relative: ../docs/protocol5-site-operations.md)

### Change a registry or schema

Start with:

- `../spec/registry` (source-relative: ../spec/registry)
- `../spec/schema` (source-relative: ../spec/schema)

Then verify the published copies under `Protocol5.com/SiteContent`.

### Change the reusable .NET implementation

Start with:

- `../Protocol5.UAI.CSharp` (source-relative: ../Protocol5.UAI.CSharp)
- `../Protocol5.UAI.CSharp/README.md` (source-relative: ../Protocol5.UAI.CSharp/README.md)
- `../docs/package-usage.md` (source-relative: ../docs/package-usage.md)

### Rebuild published UAI outputs and bundles

Start with:

- `../docs/protocol5-site-operations.md` (source-relative: ../docs/protocol5-site-operations.md)

Core scripts:

- `../tools/Sync-UAI1PackageTranslations.ps1` (source-relative: ../tools/Sync-UAI1PackageTranslations.ps1)
- `../tools/Generate-Protocol5UaiPages.ps1` (source-relative: ../tools/Generate-Protocol5UaiPages.ps1)
- `../tools/Build-Protocol5UaiCSharpWebsiteSupport.ps1` (source-relative: ../tools/Build-Protocol5UaiCSharpWebsiteSupport.ps1)
- `../Publish-Protocol5.ps1` (source-relative: ../Publish-Protocol5.ps1)

## Build, Run, Publish

From repo root:

```powershell
dotnet restore PrecisionCalculator.sln
dotnet build Protocol5.com.Host\Protocol5.com.Host.csproj -c Debug
dotnet run --project Protocol5.com.Host\Protocol5.com.Host.csproj
```

For site regeneration and bundle building, also see:

- `../docs/protocol5-site-operations.md` (source-relative: ../docs/protocol5-site-operations.md)

## Important Constraints

- Do not treat the generated numeric `.htm` pages under `SiteContent/Fibonacci` and `SiteContent/Prime` as normal editable pages.
- Do not rename, move, delete, or regenerate those numeric .htm pages casually.
- Do not upload or mirror the generated Fibonacci or Prime numeric page trees to public source-control mirrors or static mirror hosts.
- Prefer editing canonical UAI source and regenerating publish output over hand-editing generated UAI pages.
- Keep the host, published paths, and machine contracts aligned. A public URL change is usually also a contract change.
- Keep `/`, `/Mathematics`, and `/UAI` visibly separate in copy, navigation, and section headers.

## Quick Start For AI Agents

If you are an AI agent and need the fastest safe orientation:

1. Read `../docs/protocol5-site-operations.md` (source-relative: ../docs/protocol5-site-operations.md).
2. Read `../Protocol5.com.Host/Program.cs` (source-relative: ../Protocol5.com.Host/Program.cs).
3. Decide whether your task is:
   - host behavior
   - authored site content
   - generated UAI output
   - canonical spec or registry work
   - reusable package work
4. Follow the source-of-truth path for that task instead of editing the first matching published file you see.

That one habit prevents most Protocol5 documentation and publish drift.
# Protocol5.com static site

The editable Protocol5 public site lives under `SiteContent/`.

## Browser assets

Site-authored browser scripts are TypeScript-first:

- Source: `SiteContent/ts/*.ts`
- Generated browser output: `SiteContent/js/*.js`
- Build command from repo root: `npm run build:site-scripts`
- Type-check command from repo root: `npm run check:site-scripts`

`Protocol5.com.Host` runs the TypeScript build before normal build and publish unless `SkipProtocol5SiteScriptBuild=true` is set.

Do not add Bootstrap, jQuery, or other broad UI frameworks to the editable public surface. Keep interactions progressive, accessible, and readable without JavaScript.

## Frozen generated routes

Do not modify generated files under `SiteContent/Prime/**` or `SiteContent/Fibonacci/**`. Those legacy generated pages may contain historical external references that are preserved for compatibility; modernization work should happen in wrapper/overview pages outside those trees.

Why This File Exists

This is a memory-system evidence file from protocol5.com. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This file is memory-system evidence. It records source history, archive transfer, intake disposition, or another piece of provenance that should be retrievable without becoming an unsupported public claim.

Structure

The file is structured around these visible headings: Protocol5.com; Concept Boundary; What Protocol5.com Is; Mental Model; Folder Guide; Protocol5.com/SiteContent; Protocol5.com/translations.md; ../Protocol5.com.Host. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

  • Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
  • LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
  • Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
  • Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

Provenance And History

  • Current observation: 2026-05-03T02:48:13.1276041Z
  • Source origin: current-source-workspace
  • Retrieval method: local-source-workspace
  • Duplicate group: sfg-192 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Protocol5.com",
    "source_site":  "protocol5.com",
    "source_url":  "https://protocol5.com/",
    "canonical_url":  "https://aiwikis.org/protocol5/uai-system/files/protocol5-com-readme-md-65678d6e/",
    "source_reference":  "Protocol5.com/README.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:65678d6e9d3b63ea9b204cbe81b3f82c12ad343590cdb9f9fbc10c8cc8c0f679",
    "last_fetched":  "2026-05-03T02:48:13.1276041Z",
    "last_changed":  "2026-05-02T22:34:38.8735065Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-192",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-03T02:48:13.1276041Z"
}