Skip to content
wiki.fftac.org

Spiral Script Implementation Report For Spiralist

**Site relevance:** Spiralist.org

**Memory type:** docs archive

**Source path:** Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/research/Spiral Script Implementation Report for Spiralist.org.md

**Size:** 1.9 KB

Summary

Spiral Script Implementation Report for Spiralist.org

Source Headings

  • Spiral Script Implementation Report for Spiralist.org
  • Superseded Decision
  • Stable Conclusions Retained
  • What Was Removed
  • Current Use

Source Preview

This source file is short enough to preview directly on its source-memory page.

# Spiral Script Implementation Report for Spiralist.org

Status: superseded research archive. The original report proposed a pseudo-locale and UI-toggle approach. That is not the live contract.

Current behavior is documented in:

- [Localization And Spiral Script](../localization.md)
- [Publication Boundaries](../publication-boundaries.md)
- [Spiral Script v0.1 Language Draft](../planning/spiral-script-v0.1.md)

## Superseded Decision

Do not treat Spiral Script as a browser-side mode, hidden developer toggle, or raw machine language exposed in the visible UI. Live behavior treats Spiral Script like other locale-router languages: it has a locale tag, JSON dictionary, locale-prefixed URLs, sitemap coverage, and directly shareable page links.

## Stable Conclusions Retained

- Spiral Script should remain a human-readable symbolic locale, not an opaque machine payload.
- Human pages and machine exchange routes should stay separate.
- Visible Spiral strings should resolve through deterministic keys or registry-backed meanings, not glyph guessing.
- Accessibility matters: symbolic labels need usable fallbacks, and controls must remain understandable to assistive technology.
- Unicode handling should be conservative: normalize visible strings, avoid invisible control characters, and test layout budgets.
- UAIX and Protocol5 authority should not be redefined inside Spiralist.org.

## What Was Removed

- The obsolete pseudo-locale rollout plan.
- Large UI-string inventories from a past crawl.
- Detailed string-budget tables that should be regenerated from current templates when needed.
- Long external standards summaries and raw citation artifacts.

## Current Use

Use this file only to understand why the project rejected a hidden symbolic UI mode. Use the localization doc for shipped behavior and the planning draft for language design.
Website health report