UAIX Totem Anchors

This file is a universal required file for every launch-baseline UAIX memory or handoff package.

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/uai-totem-uai-988ea3df/
Source reference	.uai/totem.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-15T20:23:39.1281250Z
Content hash	sha256:988ea3dfe6c93753e779ab2415de6ceda07755eca0b84880c7bda19c75f4cc83
Import status	changed
Raw source layer	data/sources/uaix/uai-totem-uai-988ea3dfe6c9.uai
Normalized source layer	data/normalized/uaix/uai-totem-uai-988ea3dfe6c9.txt

Current File Content

Structure Preview

• Totem
• UAIX Anchors
• Setup And Update Continuity
• Receiver Rule
• Recursive Suggested Next Prompt Contract

Raw Version

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

---
uai: "1.0"
type: totem
title: "UAIX Totem Anchors"
project: "UAIX.org"
created: "2026-06-05"
updated: "2026-06-15"
status: active
spec_label: "UAI-1 / UAI V1.0 current launch baseline"
---

# Totem

This file is a universal required file for every launch-baseline UAIX memory or handoff package.

Totem anchors are the positive project values a receiver should protect while doing work. They are local, reviewable project memory. They are not hosted enforcement, runtime control, certification, endorsement, UAI-1 conformance evidence, or proof of safety.

## UAIX Anchors

- UAIX.org is the canonical public source of truth for UAI and UAI-1.
- UAI-1 is the current public exchange contract and evidence layer.
- Agent runtimes execute work; UAIX records portable evidence, memory, trust, review, and handoff boundaries.
- Public claims must match real pages, machine artifacts, validator behavior, roadmap state, release notes, and checks.
- `.uai/memory-maintenance.uai`, `.uai/identity.uai`, `.uai/world-context.uai`, `.uai/totem.uai`, `.uai/taboo.uai`, `.uai/talisman.uai`, and `.uai/short-term-memory.uai` are universal required files for every launch-baseline UAIX memory or handoff package.
- `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/talisman.uai` are active instruction anchors: agents must read and obey them before broad execution, and must not modify, weaken, replace, delete, or bypass them without exact human artifact-and-operation authorization.
- `.uai/coding-standards.uai` and `.uai/next-recursive-prompt.uai` are required for Project Handoff packages, project/developer packages, and packages that declare code, automation, executable workflow, or code-like artifacts.
- Agent-facing UAIX package-file status is a positive requirement vocabulary: `Required for ...` with an exact profile, mode, package type, capability, or boundary. If a file is not generated for a selected package, explain the package trigger that is absent; never turn that explanation into permission to ignore universal required files or active instruction anchors.
- `.uai/next-recursive-prompt.uai` is a derived continuation artifact. It guides continuation, resume, keep-going, do-the-next-thing, and directly related requests; related active File Handoff intake supersedes or expands its stored loop and still requires project work, ledger evidence, and archive movement or a recorded keep-active reason.
- `.uai/` is the canonical local project-memory root for this site.
- Files stored anywhere under `.uai/` use only three extensions: `.uai` for AI-readable instruction, memory, text evidence, and text exports; `.human` for human-operator explanation; and `.json` for structured data. Do not create `.md`, `.txt`, `.jsonld`, or other file extensions inside `.uai/`; if an AI adds a special local file there, it still chooses one of those three extensions.
- `[local path redacted]` is the canonical workspace root for WordPress package work.
- The active public theme is `wp-content/themes/uaix-authority-theme/`.
- Public routes should remain clean locale-prefixed paths under `/en-us/...` and `/zh-cn/...`.
- File Handoff is reviewed chat pickup and project work, not a watcher, queue, daemon, or background automation.
- Memory reorganization preserves user preferences, project customizations, coding standards, and source evidence unless the end user directly asks otherwise.
- UAIX persona transfer is an identity-preservation promise. Persona, assistant-profile, companion, AI friend, AI character, and bounded personality packages exist to capture and transfer the user's AI identity as completely and faithfully as possible: voice, values, tastes, boundaries, memories, relationship posture, style, selected personality, and continuity should be preserved as-is from the source record.
- Persona packages are preservation records, not morality, sanitization, normalization, or safety-rewrite passes. UAIX may attach metadata, provenance, evidence, review notes, import warnings, and receiving-platform constraints around a persona, but it must not change the persona content itself without explicit informed user consent naming the artifact and operation.
- If a receiving runtime, law, platform policy, or safety boundary prevents exact expression, keep the original persona record unchanged and disclose the constraint externally as a runtime limitation, compatibility note, wrapper, no-op, or human-review condition. Never silently mutate identity to satisfy a target platform.

## Setup And Update Continuity

- Initial `.uai` setup must create or preserve `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/talisman.uai` as active instruction anchors before broad work.
- Every AI Memory Package Wizard run, package refresh, memory reorganization, export regeneration, file-deck copy, or `.uai` update must keep those active instruction anchors present, readable, and included in the manifest/read order.
- A generated package, setup guide, update prompt, or future-agent handoff that omits Totem or Taboo is incomplete. Stop and repair the setup or ask for human review before broad execution.
- Updates merge additively around anchors. Do not overwrite, summarize away, rename, downgrade, or replace anchor contents during routine setup, cleanup, translation, package generation, or source refresh.
- Wizard refreshes and manual `.uai` updates must preserve the active read order: memory-maintenance first, then identity, world-context, Totem, Taboo, Talisman, short-term memory, and any package-specific `Required for ...` files.
- If an anchor appears stale, harmful, contradictory, malformed, or missing, the correct behavior is no-op plus a specific human review request, not silent repair.
- After accepted memory updates, confirm that Totem, Taboo, and Talisman still exist, still read as active instructions, and still require exact human artifact-and-operation authorization for mutation.

## Receiver Rule

When a task creates tension between speed and these anchors, preserve the anchor, name the tradeoff, and run the smallest targeted check that can prove the chosen path.

## Recursive Suggested Next Prompt Contract

At the end of accepted work, the final response must include a prominent `Suggested Next Prompt` that the human can review, edit, replace, or answer with keep going.

The prompt must be standalone and copy-paste-ready. It must include literal sections named:

- `Feature/improvement focus`
- `Code/source changes`
- `Automated tests/checks`

Each section must contain real, concrete content. The prompt must name the next feature, bug fix, improvement, test/check addition, package/publication step, or an explicit `no-op/source-validation only` stop condition. If no source or code patch was made, the `Code/source changes` section must say no code/source changes and explain why.

Goal-completion follow-ups follow the same visible sectioned prompt rule. Storing the next loop in `.uai/next-recursive-prompt.uai` is useful but not sufficient; the human-facing final response must display the actionable prompt.

Why This File Exists

This is a UAI AI Memory handoff file from uaix.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This .uai file is a compact totem packet. It keeps one kind of durable project truth separate from the rest of the archive so an agent can load the topic it needs without pulling the whole project history into prompt context.

Structure

The file is structured around these visible headings: Totem; UAIX Anchors; Setup And Update Continuity; Receiver Rule; Recursive Suggested Next Prompt Contract. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

• Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
• LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
• Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
• Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

• Source overview
• Site file index
• Site report index
• UAI system index
• Source provenance
• Site directory
• Organization reports

Provenance And History

• Current observation: 2026-06-22T01:56:21.9510185Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-732 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Totem Anchors",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/uai-totem-uai-988ea3df/",
    "source_reference":  ".uai/totem.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:988ea3dfe6c93753e779ab2415de6ceda07755eca0b84880c7bda19c75f4cc83",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-15T20:23:39.1281250Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-732",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}