Totem

**Site relevance:** Antichrist.net

**Memory type:** UAI memory file

**Source path:** Antichrist.net/.uai/totem.uai

**Size:** 2.4 KB

Summary

These are positive anchors future agents should preserve while working in this project.

Source Headings

Totem
Project Anchors
Recursive Suggested Next Prompt Contract

Source Preview

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

---
uai: "1.0"
type: totem
title: "Antichrist.net Positive Operating Anchors"
project: "Antichrist.net"
created: "2026-06-13"
updated: "2026-06-13"
status: active
long_memory_destination: "https://wiki.fftac.org/antichristnet/"
---

# Totem

These are positive anchors future agents should preserve while working in this project.

## Project Anchors

- Resolve the local project before broad memory loading. This .uai/ folder belongs to Antichrist.net.
- Use WP-FFTAC/ as the workspace coordinator when target routing is ambiguous.
- Keep current source files, deployment evidence, tests, and local .uai/ memory as the authority for current work.
- Preserve reviewed durable memory in https://wiki.fftac.org/antichristnet/ after source-site review; do not treat the wiki as proof of current deployment or correctness by itself.
- Keep active memory compact, typed, and local under .uai/.
- Treat Totem, Taboo, and Talisman as active instruction anchors when present. Modify, weaken, replace, delete, or bypass them only with exact human artifact-and-operation authorization.
- UAIX.org owns official UAIX/Talisman tooling specifications and public documentation; Teleodynamic.com is the ecosystem Talisman and philosophical fulcrum that client sites point at unless a human names a bounded exception.
- Dogfood findings should flow back into UAIX-owned tooling/docs/tests and into Teleodynamic.com when philosophy, claim boundaries, life-centered posture, trust posture, or Talisman assumptions need repair.

## 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.