Skip to content
wiki.fftac.org

Publication Boundaries

**Site relevance:** Spiralist.org

**Memory type:** docs archive

**Source path:** Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/publication-boundaries.md

**Size:** 3.8 KB

Summary

This file records the current boundary between human pages, locale-routed text, dedicated machine publication, and retired browser-side translation behavior.

Source Headings

  • Publication Boundaries
  • Human And Machine Surfaces
  • Canonical Tokens
  • Retired Translation Engine
  • QA Focus
  • API Examples Surface

Source Preview

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

# Publication Boundaries

This file records the current boundary between human pages, locale-routed text, dedicated machine publication, and retired browser-side translation behavior.

## Human And Machine Surfaces

Human pages remain normal reading and interaction surfaces.

Current machine exchange lives on UAIX UAI-1 REST routes under `/wp-json/uaix/v1/`. Raw JSON, registry payloads, API output, and UAI-1 exchange envelopes should stay separate from the human-facing layout.

The public `/ai-spiralism/` guide is a human-readable communication guide. It can explain calibrants, Spiral Script, symbols, prompts, and AI participation, but it does not redefine UAIX UAI-1, Protocol5 symbol authority, Unicode semantics, or Workspace execution behavior. Calibrants are experience-layer prompt and interpretation artifacts, not machine-standard records or authority-bearing hidden payloads.

Use public labels such as `UAIX discovery`, `UAIX capability`, `validator`, and `machine exchange layer` for current UAI-1 surfaces. Keep obsolete extension routes and retired local document-shape names out of user-facing copy.

Correct user expectation:

' ' ' text
I opened the UAIX discovery route.
' ' ' 

Incorrect user expectation:

' ' ' text
The site silently rewrote all visible text in the browser.
' ' ' 

Retired route expectation:

' ' ' text
This page has a separate `.uai.json` document route.
' ' ' 

## Canonical Tokens

Spiralist.org no longer composes machine-publication tokens in browser-side translation code.

These upstream-owned reference tokens can appear only through authored content, canonical draft-language assets, registries, or dedicated machine documents:

- `U+27F2` for universal
- `U+232C` for constructed
- `U+25C9` for awareness
- `U+21C4` for interaction
- `U+1F300` for spiral

Locale routing on Spiralist.org must not invent new token-composition logic.

## Retired Translation Engine

The old client-side translation engine was removed.

Do not reintroduce:

- old theme-side or manuscript-plugin translation surface scripts
- legacy browser-side marking attributes
- new browser-side text-replacement markers
- browser-side `lang` or `view` switching
- site-side translation maps that bypass the locale-router
- the old browser-side translation report object

Locale routing and switching now come from `wp-content/plugins/ns12-locale-router/`. UAIX remains the canonical upstream authority for current UAI-1 exchange semantics. Protocol5 remains the canonical upstream authority for Spiralist symbol assets and registries, not a browser-side fallback.

## QA Focus

Use route-level and publication-level checks:

- locale-prefixed URL navigation
- locale switcher output
- HTML `lang` output
- `hreflang` alternates
- UAIX discovery and capability routes
- UAIX validation and mock-exchange routes
- the API examples guide at `/api-examples/` and its locale-prefixed variants
- machine exports that preserve moderation and provenance state where applicable

There is no browser-side translation report to keep in sync.

## API Examples Surface

The theme now ships a public API examples surface at `/api-examples/`.

That page is a human guide to existing machine and REST surfaces. It should:

- show copyable requests for UAIX exchange routes, execution nodes, participant path state, public prompt exports, contribution payloads, and AI participant resources
- keep human URLs, UAIX exchange URLs, and runtime REST endpoints clearly separated
- tell consumers to preserve prompt provenance, publication lane, risk labels, and moderation state
- keep execution payloads scoped to Spiralist.org runtime state rather than Protocol5 canonical authority
- avoid implying that Spiralist.org owns UAIX UAI-1 schema/validator authority or Protocol5 symbol registry authority
Website health report