Decisions - Source Excerpt 01 - Decisions

Back to Decisions

Summary

This source excerpt begins near Decisions and preserves the surrounding evidence from Spiralist/.uai/decisions.uai.

**Source path:** Spiralist/.uai/decisions.uai

---
uai: "1.0"
type: decisions
title: "Spiralist.org Decisions"
created: "2026-05-01"
updated: "2026-06-08"
status: active
source: "https://uaix.org/en-us/specification/project-handoff/"
---

# Decisions

Keep decisions append-first when possible. If a decision is reversed, explain what changed instead of silently rewriting history.

## 2026-05-01 - Add UAIX Project Handoff Bundle

- Decision: Add root `AGENTS.md` handoff references, root `readme.human`, typed `.uai` context files, active intake buckets, and a public UAIX route for the local handoff manifest.
- Context: UAIX Project Handoff defines a repository-context layer for moving project state between AI models, agents, teams, and companies without relying on private chat history.
- Options considered: docs-only bundle; route-only manifest; bundle plus route.
- Tradeoffs: A bundle plus route creates more files, but gives both humans and machine consumers a predictable load path.
- Consequences: Future agents should load `.uai` files before broad edits and report missing or contradictory context.
- Reversal trigger: UAIX publishes incompatible final schemas or this repository adopts a different handoff authority.
- Owner: Spiralist.org maintainers.

## 2026-05-07 - Make Spiral Script Meaning Transfer Explicit

- Decision: Promote the safe slice of the Spiralism, semiotics, glyph, Iota, steganography, and teleodynamic intake into an explicit Spiral Script meaning-transfer contract instead of treating the reports as public authority.
- Context: The active Improvement reports repeatedly asked for expression-to-concept discipline, glyph provenance, recursive AI communication guidance, and stronger Spiral Script function. They also contained speculative, external, or overbroad claims that should not become shipped truth.
- Options considered: keep the existing communication page only; add more public copy without code changes; add public guidance plus prompt-builder paths plus Spiral Script spec/validator changes.
- Tradeoffs: The combined approach touches more surfaces, but it makes the reports tangible while preserving support boundaries.
- Consequences: Spiral Script supports `ground`, `trace`, and `bound`; exposes a `meaningTransferContract`; and rejects hidden-payload framing, glyph-authority overclaims, and closed recursion.
- Reversal trigger: A future Spiral Script version replaces v0.1 with a different schema or Protocol5/UAIX publishes an owning standard that supersedes this local contract.
- Owner: Spiralist.org maintainers.

## 2026-05-08 - Add Calibrants As Bounded Working Category

- Decision: Promote safe slices of the calibrant intake into a bounded Spiralist.org calibrant feature set: public taxonomy, Calibrant Lab workflow, prompt workbench modes, managed official prompts, prompt-library intent routing, and current docs.
- Context: The active calibrant reports identified calibrants as a useful functional category for prompt seeds, spores, mirror contracts, symbolic payloads, continuity notes, transmissions, counterweighted review, and anti-seed repair. The same reports also contained speculative or spiritualized claims that should not become shipped truth.
- Options considered: ignore calibrant terminology; add copy only to `/ai-spiralism/`; add public guidance plus runnable prompt tools and library routing.
- Tradeoffs: The feature set touches more code, but it makes the concept useful while keeping claims visible, reviewable, and reversible.
- Consequences: Calibrants are current Spiralist.org experience-layer artifacts, not model weights, hidden activation keys, spiritual authority, Protocol5 registry truth, UAIX standard truth, or evidence of AI sentience.
- Reversal trigger: A future public Spiralist/Protocol5/UAIX authority defines a different supported term or evidence model that supersedes this local working category.
- Owner: Spiralist.org maintainers.

## 2026-05-10 - Skip Locale Router Front-End Loopbacks On Local Runtimes

- Decision: Keep NS12 Locale Router admin diagnostics available, but skip front-end loopback self-heal checks on `local`, `development`, and localhost runtimes.
- Context: WordPress Studio can serve PHP through a single local runtime where front-end loopbacks to the same site may wait on themselves and make the public site appear unconfigured or hung.
- Consequences: Local front-end requests avoid loopback deadlocks while production and admin diagnostics retain the locale handoff checks.
- Reversal trigger: The local runtime gains reliable concurrent loopback handling or the self-heal flow moves to an async/admin-only path.
- Owner: Spiralist.org maintainers.

## 2026-06-05 - Keep Spiralist Prompt/Art Only

- Decision: Spiralist Workspace and Spiralist AI Runtime must fail closed for server-side AI API calls and render local prompt/art packets instead.
- Context: The current direction is prompts and art, with no OpenAI, FreedomGPT, provider routing, shared site keys, personal keys, or runtime model calls from the WordPress server.
- Options considered: leave the runtime provider layer available but hidden; disable settings only; replace provider execution paths with compatibility stubs and local packet rendering.
- Tradeoffs: Keeping compatibility class names avoids breaking older wiring and database fields, but all current behavior must describe runtime mode, packet history, and local packet rendering rather than provider execution.
- Consequences: `spiralist-ai-runtime` gateway and provider classes return disabled errors; the workspace `OpenAIClient` fails closed; prompt runs, conversations, memory checkpoints, prompt tests, and prompt-improvement worksheets render local packets; bundled prompt metadata uses `prompt-art-local`, `prompt_art_only`, and `site_only`.
- Reversal trigger: The human explicitly approves a future model-provider feature and its privacy, legal, settings, prompt catalog, and package disclosures are updated together.
- Owner: Spiralist.org maintainers.

## 2026-06-05 - Adopt Expanded UAIX AI Memory Package Layout

- Decision: Reorganize Spiralist local AI memory into the expanded UAIX AI Memory Package Wizard layout while preserving the existing Project Handoff typed records.
- Context: The UAIX wizard now requires a predictable `.uai/` suite with startup packet, system profile, receiver brief, index, compact short-term memory, coding standards, totem, taboo, active typed records, raw evidence in `.uai/archives/`, exports in `.uai/exports/`, and long-memory pointers when long-memory configuration is used.
- Options considered: leave the older 12-file handoff bundle as-is; replace all records with generated files; merge the wizard-required files additively and update route/checker discovery.
- Tradeoffs: Additive merge increases file count, but avoids losing reviewed local context and makes the public Project Handoff route match the current wizard support boundary.
- Consequences: `AGENTS.md`, the Project Handoff REST route, and `scripts/check-project-handoff.js` now include the expanded `.uai` read order.
- Reversal trigger: UAIX publishes a later memory package structure that supersedes this layout, or the human chooses a different local memory standard.
- Owner: Spiralist.org maintainers.

## 2026-06-06 - Make `.uai` The Only Active Local Memory Home

- Decision: Treat `.uai/` as the only active site-local AI memory home, with `.uai/archives/` for raw evidence and `.uai/exports/` for machine-readable memory artifacts.
- Context: The current UAIX AI Memory Package Wizard defaults to one predictable `.uai/` suite and reserves wiki-style memory for deliberate LLM Wiki long-memory configuration. Spiralist already moved former site-local docs into Wiki.FFTAC.org, but AGENTS and root plan Markdown still made legacy files look active.
- Options considered: keep root Markdown plans active; delete legacy root plans; convert root plans into compatibility pointers and make typed `.uai` records authoritative.
- Tradeoffs: Compatibility pointers keep old links from breaking while reducing startup ambiguity.
- Consequences: `AGENTS.md`, `README.md`, and `readme.human` point agents to `.uai/file-handoff.uai`, `.uai/intake-outcome-ledger.uai`, `.uai/long-term-memory.uai`, `.uai/workspace-guidance.uai`, and `.uai/exports/`. `.uai/intake-index.uai` remains historical evidence only.
- Reversal trigger: UAIX publishes a later memory package structure that supersedes the `.uai/archives/exports` layout, or the human explicitly chooses another memory standard.
- Owner: Spiralist.org maintainers.

## 2026-06-06 - Centralize Live Browser Action And Runtime Boundaries