LLMWikis Positive Operating Anchors
These are positive anchors future agents should preserve while working in this project.
Metadata
| Field | Value |
|---|---|
| Source site | llmwikis.org |
| Source URL | https://llmwikis.org/ |
| Canonical AIWikis URL | https://aiwikis.org/llmwikis/files/uai-totem-uai-ec4f9528/ |
| Source reference | .uai/totem.uai |
| File type | uai |
| Content category | uai-system |
| Last fetched | 2026-06-22T01:56:21.9510185Z |
| Last changed | 2026-06-13T14:10:58.4836417Z |
| Content hash | sha256:ec4f95285dc94422e753a9f9b0e2eb4fbb065ad68617d0d138d9f9f2d7b060f9 |
| Import status | unchanged |
| Raw source layer | data/sources/llmwikis/uai-totem-uai-ec4f95285dc9.uai |
| Normalized source layer | data/normalized/llmwikis/uai-totem-uai-ec4f95285dc9.txt |
Current File Content
Structure Preview
- Totem
- Project Anchors
- 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: "LlmWikis Positive Operating Anchors"
project: "LlmWikis"
created: "2026-06-13"
updated: "2026-06-13"
status: active
long_memory_destination: "https://AIWikis.org/llmwikis/"
---
# 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 LlmWikis.
- Use [local path redacted] 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://AIWikis.org/llmwikis/ 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.
Why This File Exists
This is a UAI AI Memory handoff file from llmwikis.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; Project Anchors; 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-1133(primary) - Historical hash records are stored in
data/hashes/source-file-history.jsonl.
Machine-Readable Metadata
{
"title": "LLMWikis Positive Operating Anchors",
"source_site": "llmwikis.org",
"source_url": "https://llmwikis.org/",
"canonical_url": "https://aiwikis.org/llmwikis/files/uai-totem-uai-ec4f9528/",
"source_reference": ".uai/totem.uai",
"file_type": "uai",
"content_category": "uai-system",
"content_hash": "sha256:ec4f95285dc94422e753a9f9b0e2eb4fbb065ad68617d0d138d9f9f2d7b060f9",
"last_fetched": "2026-06-22T01:56:21.9510185Z",
"last_changed": "2026-06-13T14:10:58.4836417Z",
"import_status": "unchanged",
"duplicate_group_id": "sfg-1133",
"duplicate_role": "primary",
"related_files": [
],
"generated_explanation": true,
"explanation_last_generated": "2026-06-22T01:56:21.9510185Z"
} Next Useful Routes
- Start Here A task-first reading path for AIWikis.org, separating newcomer learning, source-memory lookup, maintainer workflow, and AI-agent retrieval.
- Topic Index A tag-oriented index for LLM Wiki, AI memory, UAI, source governance, crawling, and retrieval topics.
- Source Map AIWikis source-governed page for durable AI memory, evidence routing, and agent-readable retrieval.
- LLMWikis.org LLMWikis.org source-system overview for transparent AIWikis memory demonstration.
- LLMWikis.org Source Memory Guide AIWikis source-governed page for durable AI memory, evidence routing, and agent-readable retrieval.
- LLMWikis.org Files Site-scoped current-source file index for LLMWikis.org.