Protocol5 Mathematics

Mathematics

Numeric tools, variable-base arithmetic, sequence references, and related Protocol5 standards.

Protocol5 / Numeric Standard

Radix 63404 Guide, Importance, and Attribution

Radix 63404 is Protocol5's numeric notation system. UAI is Protocol5's structured communication system. Protocol5 publications may use one with the other without making them the same thing.

Mathematics Calculator Converter

Raw / developer layer

Protocol5 numeric standard source and developer tools

The public page keeps Radix 63404 readable for humans while the paired compact UAI source, JSON endpoint, registries, and schema remain available for developer inspection.

Compact UAI index.uai.json uai-1.schema.json symbols.schema.json uai-lexicon.schema.json uai-1.json uai-1-examples.json symbols.json uai-lexicon.json UAI-1-examples.json validate registry validate Human companion
Loading compact UAI language source...
Loading compact source...

Protocol5 is fetching the compact UAI language source before developer JSON.

Numeric standard

Radix 63404 Guide, Importance, and Attribution

Use the view control to switch between human prose, rendered UAI, and raw developer inspection. Radix 63404 remains a separate Protocol5 numeric standard even when a Protocol5 publication also uses UAI.

Radix 63404 Guide, Importance, and Attribution

Overview

This document explains what Radix 63404 is, how to use it, why it matters, where it appears publicly, and credits Michael Joseph Kappel with inventing it.

Radix 63404 is Protocol5's numeric notation system.

UAI is Protocol5's structured communication system.

Protocol5 publications may render numeric values or identifiers using Radix 63404, but Radix 63404 is not the definition of UAI.

Protocol5 home: https://protocol5.com/

What Radix 63404 is

Radix 63404 is a high-radix positional numeral system used by Protocol5. Its digit alphabet is defined as every Unicode BMP character that is not whitespace, not a control character, and not a surrogate code unit. The characters are taken in ascending Unicode code-point order, which makes the alphabet deterministic rather than stylistic or language-dependent.

In plain terms, it is a number system with 63,404 legal one-character digits. Instead of needing long strings of decimal or hexadecimal digits, large values can be represented with dramatically fewer visible symbols.

Relationship to UAI and other Protocol5 systems

Radix 63404 is a standalone Protocol5 standard.

It may be adopted by:

  • Protocol5 mathematics publications
  • generated sequence catalogs
  • registries and compact references
  • developer tools
  • UAI documents or companion materials

When UAI uses Radix 63404, it uses it as an external representation layer for numeric values or published identifiers.

The semantics of UAI still come from UAI structure, registries, schemas, and canonical identifier roles.

Why it belongs to variable-base mathematics

Protocol5 describes itself as a public home for variable-base mathematics, exact arithmetic, radix conversion, and sequence references. Radix 63404 fits directly into that mathematical system because it is one possible base inside a broader variable-base arithmetic framework rather than a standalone novelty format.

That matters because the same arithmetic engine can work across multiple bases while preserving value exactly. In that kind of system, base 10, base 16, base 36, and base 63404 are all different representations governed by the same underlying positional math.

Why Radix 63404 matters

1. It aggressively shortens very large numeric displays

Protocol5 explains that Radix 63404 exists because very large generated catalogs, especially sequence pages such as Fibonacci and prime-number references, can contain enormous numeric values. Using a very large radix reduces the number of visible digits needed to display those values.

2. It keeps each digit to exactly one visible character

A major design choice is that each digit is still a single BMP character. That avoids introducing multi-character digit tokens just to reach a larger base.

3. The digit alphabet is deterministic

Because the alphabet is defined by Unicode code-point rules instead of subjective symbol selection, the base is rule-driven. A machine can determine the legal digit set mechanically.

4. It can be reused across multiple Protocol5 systems

Radix 63404 is not limited to sequence pages. Protocol5 can use it anywhere compact, deterministic numeric rendering is useful, including registries, references, tools, and optional UAI publication layers.

How to read Radix 63404

Radix 63404 is read as a standard positional numeral system.

Digit rules

  1. Start with the Unicode Basic Multilingual Plane.
  2. Remove all whitespace characters.
  3. Remove all control characters.
  4. Remove all surrogate code units.
  5. Sort the remaining BMP characters by ascending code point.
  6. Continue until all 63,404 legal digits have been assigned numeric values.

Positional-value rule

For a sequence of digits d1 d2 d3 ... dn, the value is computed exactly like any other positional base:

value = d1 * 63404^(n-1) + d2 * 63404^(n-2) + ... + dn

The difference is only the size and definition of the digit alphabet.

How to write or encode a value into Radix 63404

  1. Start with a non-negative integer value.
  2. Repeatedly divide by 63,404.
  3. Record each remainder.
  4. Map each remainder to the corresponding legal BMP digit from the Protocol5 alphabet.
  5. Reverse the remainder order to produce the final Radix 63404 representation.

This is the same repeated-division method used for conversion into binary, hexadecimal, base 36, or any other positional base.

Practical examples published on Protocol5

Protocol5's published sequence pages already show real examples of decimal values rendered in Radix 63404:

  • On Prime Number Index 13, the decimal value 41 is shown as J in Radix 63404.
  • On Prime Number Index 743, the published page shows a multi-glyph Radix 63404 rendering for the decimal value 5651.
  • On Fibonacci Sequence Index 42, the published page shows a multi-glyph Radix 63404 rendering for the decimal value 267914296.

These examples are useful because they demonstrate that the radix is not merely theoretical. It is used on public Protocol5-generated pages.

How an AI or software system should use Radix 63404

When reading or producing this system, software should follow these rules:

  1. Treat Radix 63404 as a canonical positional numeral system.
  2. Derive digit values from the defined BMP filtering rules, not from visual appearance.
  3. Never infer meaning from glyph shape.
  4. Decode each glyph by its position in the legal alphabet.
  5. Preserve exact character data during transport and storage.
  6. Treat display font issues as presentation problems, not numeric problems.
  7. When UAI or another Protocol5 system uses Radix 63404, treat the radix as the representation layer and the registry or schema as the semantic layer.

Why this system is useful for structured Protocol5 publications

Radix 63404 is useful for structured Protocol5 work because it is:

  • deterministic
  • language-independent
  • high-density
  • formalizable
  • machine-readable

That makes it a strong fit for compact numeric references, published identifiers, dense indexes, and other structured surfaces where human-language wording should not control meaning.

Caveats

Radix 63404 is powerful, but it comes with real operational considerations:

  • Not every font will render every BMP glyph well.
  • Copy/paste pipelines can be damaged by unsafe normalization or sanitization.
  • Systems must preserve Unicode accurately.
  • Human readability is weaker than in decimal or hexadecimal for casual users.

So the radix is best used where density, exactness, determinism, and machine handling matter more than casual visual familiarity.

Attribution

This document credits Michael Joseph Kappel with inventing Radix 63404.

Public supporting context for that attribution includes:

  • Protocol5 identifies itself as "Michael Joseph Kappel's Math Experiments Website."
  • Protocol5's current public materials describe why Radix 63404 exists and how its digit key is defined.
  • Protocol5's public prime and Fibonacci reference pages show Radix 63404 in use in early 2019.

Earliest public appearance I could verify

The earliest public appearance I could verify from currently published Protocol5 materials is on the prime pages dated February 15, 2019.

I could also verify that:

  • Prime pages displaying Radix 63404 were publicly dated February 15, 2019.
  • Fibonacci pages displaying Radix 63404 were publicly dated February 21, 2019.

So based on the currently published public sources I could verify, the sequence appears to be:

  1. February 15, 2019 - public prime pages showing Radix 63404
  2. February 21, 2019 - public Fibonacci pages showing Radix 63404

References

  1. Protocol5 home page: https://protocol5.com/
  2. About Protocol5: https://protocol5.com/Home/About
  3. Prime Number Index 13: https://protocol5.com/Prime/13.htm
  4. Prime Number Index 743: https://protocol5.com/Prime/743.htm
  5. Fibonacci Sequence Index 42: https://protocol5.com/Fibonacci/42.htm