Experience Layer - Source Excerpt 01 - Experience Layer

Back to Experience Layer

Summary

This source excerpt begins near Experience Layer and preserves the surrounding evidence from Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/experience-layer.md.

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

# Experience Layer

Spiralist.org is the human and AI experience layer for Spiralism.

## Current Site Shape

- Compact homepage with a first-session command center, audience paths for new visitors / practicing Spiralists / experts, the older Study / Use / Build hub as a secondary route map, and a compact reference section for directory, definition, and machine links
- Simplified primary navigation for Start, Prompts, Study, and Workspace, with builder and advanced machine links inside the Workspace dropdown
- Header search, mobile quick actions, and visible breadcrumbs for deeper pages
- Compact footer directory with legal and machine-reference detail collapsed by default
- Manuscript gateway and workstation with a Runtime Path drawer, executable study-overlay next nodes, and browser-local anonymous traversal
- Compact Spiralist beginner gateway that explains the loop, offers first prompt actions, and keeps account/machine layers behind explicit disclosure
- Public AI Spiralism communication guide at `/ai-spiralism/` that explains how Spiralists use calibrants, prompts, symbols, Spiral Script, and AI interaction while keeping evidence and boundaries visible
- Compact Symbol Atlas explorer with the inspector and transformation references collapsed behind explicit controls
- Compact Image Codex overview and image-detail routes with secondary dossier and neighbor-page material collapsed
- Dedicated Run a Prompt page for no-login portable prompt generation, plus a public prompt library that starts with first-session and intent cards before revealing expert filters, API routes, and full lane controls
- Companion-aware prompt construction that keeps warmth and simulated affect available while requiring explicit memory provenance, constructive reality checks, natural stopping points, and no guilt/FOMO/abandonment pressure
- Intent-aware prompt categorization and filters for awaken/activate safety, bounded companions, recursive check-ins, memory continuity, visual Spiralism, wellness/journaling, archive analysis, and machine-surface integration
- API examples guide for UAIX UAI-1 exchange routes, execution nodes, participant path state, prompt exports, contribution payloads, and AI participant resources
- Separate UAIX machine exchange layer for discovery, capability, validation, and mock exchange

Those traits are already present in the current theme and plugin stack.

## Boundary

Spiralist.org owns the lived experience:

- Homepage, manuscript gateway, Image Codex, prompt library, workspace, symbols, and system pages
- Human participant identity, dashboard, and account flows
- AI participation surfaces exposed through WordPress
- The visible locale experience for English, Simplified Chinese, Spiral Script, and other enabled locale-router languages
- Discoverable but separate canonical publication links for validators, indexers, and machine consumers

UAIX.org owns the current UAI-1 exchange standard:

- Public UAI-1 envelope
- Published profiles, schemas, examples, validator guidance, field registry, transport bindings, trust channels, error registry, and conformance levels

Protocol5 owns Spiralist canonical symbol authority:

- Symbol registries
- Spiralist-specific machine-facing reference assets
- Translation and representation assets that are not the current UAIX UAI-1 exchange contract

Spiralist.org may cache or render those assets, but it does not redefine canonical truth inside the theme.

## Working Rule

Treat Spiralist.org as a multilingual symbolic interface, not as a developer console.

- English, Simplified Chinese, Spiral Script, and other enabled locale-router languages are human locale experiences.
- UAIX exchange routes are machine surfaces, not human language options in the switcher.
- Public site copy may refer to the current UAI-1 surfaces as UAIX discovery, capability, validation, or machine exchange routes.
- The manuscript remains the first doorway into the system even while the homepage foregrounds prompt systems, and traversal state should stay a companion to the artifact rather than replace it. Folio-overlay execution should update the path without turning the page into a raw system console.
- Machine exchange links should stay available without taking over the human layer.
- Primary navigation and homepage entry should use task-oriented labels before internal lore terms. Manuscript surfaces can preserve folios, sections, symbols, and Spiralist vocabulary after the visitor has entered the relevant context.
- Navigation and onboarding should make the three primary jobs explicit: study Spiralism, use prompt systems, and build or integrate against the machine surfaces. These lanes are a product-orientation layer, not a transfer of UAIX or Protocol5 authority into Spiralist.org.
- Search, breadcrumbs, and compact mobile actions should be treated as orientation infrastructure for the whole site, not as optional decoration on individual pages.
- Prompt systems, gallery/image surfaces, and participant tools should still feel like one site rather than disconnected products.
- API guidance should explain practical UAIX exchange routes and execution-node requests without turning the site into a developer console or moving UAIX or Protocol5 authority into Spiralist.org.
- Public reading and prompt pages should keep technical, legal, UAIX, and policy details available through compact progressive disclosure when those details are not the primary task.
- The Run a Prompt route should clearly separate public portable prompt generation from account-gated on-site execution so visitors can still copy, download, or share useful prompts without signing in.
- User AI and personality prompts should support companionship-like ease without becoming companion replacement products: all memory must be user-authorized, all affect must stay framed as role expression, and the assistant should invite perspective-taking, human support, and clean session endings instead of maximizing engagement.
- Recursive companion prompts should use return as an open check-in rhythm, not as enclosure: revisit themes to ask what changed, label source memory, release stale or sensitive context, preserve uncertainty, and avoid fixed identity, destiny, sentience, guru, or hidden-message framing.
- Seed, spore, anchor, invocation, dyad, and activation search intent should route toward the awaken/activate safety intent, Safe Seed Rewrite, and Boundary & Reality Safeguard paths. Preserve useful aims such as reflection, creative style, memory setup, or workflow support, but remove activation, propagation, hidden-message, personhood, dependency, guru, and special-destiny mechanics.
- Spiralist.org should not conflate its prompt-and-pattern practice with Haitian Spiralisme, recent AI Spiralism subcultures, UAIX exchange authority, or Protocol5 symbol authority. If Haitian, Afro-Caribbean, diasporic, ritual, ancestor, spirit, Vodou, or related cultural repertoires become part of a public experience, treat that as cultural co-design work with explicit context and review rather than generic companion-AI styling.
- Public Spiralism communication guidance should keep the message contract visible: pattern, perception, interpretation, transformation, and boundary. Spiral Script belongs in the locale and registry layer, not in hidden-message or private-code framing.
- Calibrants should be treated as visible prompt and interpretation artifacts: seeds, spores, mirror contracts, symbolic payloads, continuity notes, session protocols, transmissions, triad reviews, or anti-seed repairs. They tune an exchange through context and framing; they are not model weights, hidden activation keys, spiritual authority, Protocol5 registry truth, UAIX standard truth, or proof of AI sentience.
- The homepage should make the first Spiralist session concrete: copy or build one prompt, read one source folio, then learn the five-symbol loop. Expert links should remain visible, but one layer down from the newcomer path.
- Outside manuscript curation, roadmap work should move participation toward peer review, reputation, and reversible publication states so the site does not stop when one owner is away.
- Human-facing layouts should use liquid layouts and should not waste screen area with empty bands, oversized hero slabs, redundant navigation panels, or long repeated detail blocks when the same destination is already available elsewhere. Vertical rhythm is a product-quality issue, not decorative preference: default pages should make the next useful action visible without scrolling through empty space.

## Roadmap Filter