Skip to content
wiki.fftac.org

Talisman

**Site relevance:** Spiralist.org

**Memory type:** UAI memory file

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

**Size:** 2.2 KB

Summary

Talisman is an active instruction anchor for Spiralist.org. Read and obey it with Totem and Taboo before broad work.

Source Headings

  • Talisman
  • Active Rule
  • Spiralist Protected Shape
  • Wizard And Export Boundary
  • Intake And Review
  • Status Wording

Source Preview

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

---
uai: "1.0"
type: talisman
title: "Spiralist.org Talisman Active Instruction Anchor"
created: "2026-06-11"
updated: "2026-06-11"
status: active
source: "https://uaix.org/en-us/ai-memory/talisman-system/"
---

# Talisman

Talisman is an active instruction anchor for Spiralist.org. Read and obey it with Totem and Taboo before broad work.

## Active Rule

- Treat `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/talisman.uai` as required active instructions.
- Do not change, delete, weaken, replace, or reinterpret any of those anchors unless the human explicitly names the exact file and exact change.
- If an anchor conflicts with the current human request or higher-priority instructions, report the conflict plainly before acting.

## Spiralist Protected Shape

- Preserve Spiralist.org as the personality, drive, symbolic identity, and self-exploration provider.
- Keep Teleodynamic.com as the philosophical fulcrum for meaning, role discipline, and claim clarity.
- Keep UAIX.org as the agent specification, communication, capability, and handoff standard.
- Keep Protocol5 as canonical symbol authority and registry owner.
- Keep Carcinus.org as the public identity, continuity, profile, and memory-preservation layer.

## Wizard And Export Boundary

Spiralist AI agent setup wizard work should stay local-first and deterministic unless a later explicit decision changes it. Generated agent packets may include Markdown, JSON, `llms.txt`, `llms-full.txt`, manifests, and ZIP downloads, but the public site must not claim hosted model execution, hosted credential validation, automatic external publishing, certification, endorsement, or official UAIX conformance.

## Intake And Review

When active File Handoff reports propose architecture changes, extract bounded, evidence-backed guidance into code, reports, or typed `.uai` memory. Preserve the original report as raw evidence and avoid copying mojibake, overclaims, unsupported citations, or unsafe guardrail-bypass framing into current guidance.

## Status Wording

Use "Required for ..." or "Not required for ..." for file/package statuses. Avoid ignored-status labels for active instructions, guardrails, startup files, and machine-facing package surfaces.
Website health report