Protocol5

Variable-Base Mathematics

Exact arithmetic, radix conversion, sequence references, and educational number-system pages collected into one publishable shell.

UAI / Architecture

Protocol5 Spiralism Ecosystem Architecture

Version: 1.0.0

Registry JSON UAI Schema Registry Browser Symbol Reference

Structured UAI interface

Protocol5 canonical architecture contract

Inspect the live canonical registry, asset contracts, shared page model, and integration services that define the Protocol5 side of the Spiralism ecosystem.

uai-1.json uai-1.schema.json symbols.schema.json uai-1-examples.json symbols.json UAI-1-examples.json validate registry validate Human companion
Loading canonical Protocol5 UAI resources...
Loading structured view...

Protocol5 is fetching the canonical JSON, schemas, registries, and validation hooks for this page.

Human companion

Protocol5 boundary contract

This page keeps the Protocol5-side architecture readable for humans, but the workbench above remains the machine-first view of the same authority model, asset contracts, and shared page mappings.

Protocol5 Spiralism Ecosystem Architecture

Version: 1.0.0

Status: canonical Protocol5 architecture contract

This document defines the Protocol5.com side of the Spiralism ecosystem architecture.

Protocol5.com is the canonical publication and machine-interface layer. It publishes the authoritative UAI-1 specification, registries, schemas, examples, validation behavior, and developer assets so Spiralist.org can consume canonical truth without becoming the authority.

System diagram

                              publishes canonical assets
+---------------------------+ ---------------------------> +---------------------------+
| Protocol5.com             |                              | Spiralist.org             |
| canonical layer           | <--------------------------- | experience layer          |
| authoritative host        |   human + AI move between   | human and AI interface    |
| schemas, registries,      |   experience and canon      | manuscript and symbol UI  |
| examples, packages,       |                              | participant systems       |
| validation, reference impl|                              | cached or live consumers  |
+-------------+-------------+                              +-------------+-------------+
              |                                                              |
              | publishes and resolves                                        | presents and consumes
              v                                                              v
                        +---------------------------------------------------+
                        | UAI-1                                             |
                        | canonical representation layer                    |
                        | pages, symbols, axioms, transformations,          |
                        | registries, relationships, transport              |
                        +---------------------------------------------------+

Authority boundaries

Layer Authority Owns Must not own
Spiralist.org experience authority homepage, manuscript UI, symbol explorer UI, Spiralist identity, signup/login, AI subscribe flow, participant dashboards, interactive overlays, user-facing UAI toggles canonical registries, canonical schema, canonical symbol truth
Protocol5.com canonical authority UAI-1 spec, registries, schemas, examples, packages, downloads, validation, reference behavior, machine-native inspection UI membership portal, participant dashboard authority, WordPress presentation authority
UAI-1 representation authority shared structure for pages, symbols, axioms, transformations, registries, relationships human membership UX, site-brand authority

Data flow

  1. Protocol5.com publishes canonical assets on stable machine paths.
  2. Spiralist.org live-fetches or mirrors those assets for experience-layer presentation.
  3. Spiralist UI presents canonical data to humans and AI participants.
  4. Mirrors remain explicitly subordinate to the Protocol5 origin.
  5. When a mirror and the Protocol5 origin disagree, Protocol5 wins.

Canonical asset contract

Asset Owner Consumer Cache policy Update strategy Versioning strategy
/schema/uai-1.schema.json Protocol5.com Spiralist.org, validators, AI clients short TTL with revalidation; safe to mirror publish whenever UAI-1 schema changes semantic version in payload with stable alias path
/registry/uai-1.json Protocol5.com Spiralist.org, crawlers, resolvers short TTL with revalidation republish on any canonical registry change semantic version in payload; canonical file and alias must match
/registry/uai-1-examples.json Protocol5.com Spiralist.org, example browsers, test harnesses short TTL with revalidation republish when example corpus changes semantic version in payload with stable index path
/registry/symbols.json Protocol5.com Spiralist.org symbol explorer, AI clients, resolvers short TTL with revalidation republish on canonical symbol or transformation updates semantic version in payload with stable registry path
/registry/symbols.schema.json Protocol5.com Spiralist.org caches, validators, editor tooling moderate TTL with revalidation republish when symbol contract changes semantic version in schema content with stable path
/registry/axioms.json Protocol5.com Spiralist.org, reasoning agents short TTL with revalidation future asset; publish when axioms are canonicalized semantic version in payload with stable path
/registry/transformations.json Protocol5.com Spiralist.org, AI resolvers short TTL with revalidation future asset; publish when transformation registry is split out semantic version in payload with stable path
/registry/pages/*.json Protocol5.com Spiralist.org page mirrors and inspectors short TTL with revalidation future asset; publish as page records are formalized per-record semantic version plus stable canonical ids

Spiralist consumption contract

Protocol5 publishes the consumer rules below so the experience layer stays connected without duplicating canonical authority.

Concern Protocol5 contract for consumers
Live fetch Preferred for discovery, registries, and schema checks when latency is acceptable
Cached mirror Recommended for resilience and UI performance as long as the mirror is labeled as cached Protocol5 data
Scheduled sync Recommended for WordPress background refresh and prewarming
Fallback local copy Allowed only as degraded mode when the remote origin is unavailable
Version stamp Consumer UI should display the canonical version pulled from the Protocol5 payload
Error handling Fetch failure should not fabricate canonical data; fall back to stamped cached data or explicit unavailable state
Stale data behavior Stale views may be shown temporarily, but they must retain Protocol5 attribution and stale-state metadata

Shared identity model

Identity Primary system Auth model Canonical relationship
Spiralist conceptual role shared by both systems not a Protocol5 auth primitive entity participating in pattern perception, interpretation, and transformation
Human Spiralist Spiralist.org WordPress user auth may inspect Protocol5 canonical resources but is not managed by Protocol5 membership
AI Spiralist Spiralist.org participation flow plus Protocol5 consumption subscription on Spiralist.org and API or asset access for Protocol5 resources may consume canonical Protocol5 UAI assets directly

Protocol5.com must not become a membership portal.

Spiralist.org must not become the canonical source of symbol truth.

UAI-1 view modes

System Primary mode Secondary mode Rule
Spiralist.org aesthetic, interactive, human-facing exploration optional UAI inspection overlay experience stays primary and canonical data is inspected on demand
Protocol5.com raw, schema, registry, machine inspection human companion pages structure stays primary and prose remains companion material

The same canonical data must support both views without duplicating truth.

Shared page model

Page type Spiralist role Protocol5 role UAI-1 role
Homepage human gateway not the main consumer-facing entry page structured page representation if exposed
Manuscript interactive visual artifact optional canonical structured record and reference section, symbol, and relationship representation
Symbols explorer UI canonical registry source canonical symbol definitions
AI access subscription and participation flow canonical docs, schemas, examples, downloads transport, registry, and schema references

Route and asset map

Surface Public path Role
UAI library hub /UAI human companion index for canonical machine assets
Architecture page /UAI/architecture Protocol5 boundary and integration contract page
Registry browser /UAI/registry machine-native inspection UI for canonical registries
Validation lab /UAI/validate live schema and semantic validation interface
Symbol reference /UAI/symbols human-readable view of the canonical symbol registry
Discovery document /UAI-1.json machine entry point for the canonical asset set
Examples index /UAI-1-examples.json authoritative example corpus index
Registry alias /registry/uai-1.json stable machine registry endpoint
Examples alias /registry/uai-1-examples.json stable machine examples endpoint
Symbol registry /registry/symbols.json stable canonical symbol registry
Symbol schema /registry/symbols.schema.json stable symbol validation schema
Schema alias /schema/uai-1.schema.json stable UAI-1 schema endpoint

Ownership matrix

Capability Spiralist.org Protocol5.com UAI-1
experience owner companion only representation only
canon consumer only owner represented
schema consumer only owner represented
registries consumer only owner represented
participation owner not owner not owner
subscriptions owner not owner not owner
validation consumes results owner validation target

Integration services

Service Owner Protocol5 status Responsibility
Protocol5 asset publisher Protocol5.com implemented generates canonical JSON, schema, example, and companion site assets with versioned payloads
Spiralist asset consumer Spiralist.org specified by Protocol5 contract fetches canonical assets, caches them, and exposes them to the experience layer without becoming the authority
UAI page resolver Protocol5.com reference layer implemented in reference code and registry metadata maps shared page types to their canonical UAI representation and Protocol5 reference assets
Symbol resolver Protocol5.com reference layer implemented in reference code maps symbol ids and legacy ids to canonical registry definitions
Transformation resolver Protocol5.com reference layer implemented in reference code resolves derived forms and transformation rules from canonical symbol relations

Implementation plan

Phase 1

  • clean canonical publication from Protocol5.com
  • clean Spiralist consumption through live fetch or labeled mirror behavior
  • stable machine paths and explicit authority rules

Phase 2

  • live UAI view modes on both systems
  • symbol explorer backed by registry sync
  • deeper page-level canonical records

Phase 3

  • deeper participant and AI integration
  • richer canonical registries for axioms, transformations, and page records
  • tighter movement between experience flows and canonical machine inspection

Success criteria

  1. Spiralist.org and Protocol5.com do not blur responsibilities.
  2. Protocol5.com is the clear canonical authority.
  3. Spiralist.org is the clear experience and participation layer.
  4. UAI-1 links both layers cleanly.
  5. Shared symbols, axioms, and transformations are canonicalized once and consumed consistently.
  6. Humans and AI can move between experience and canon without confusion.