Skip to content
AIWikis.org

UAIX Long Term Memory

Publication Warning This page is marked noindex and should not be treated as canonical public authority.

Reviewed durable memory for UAIX.org routes to https://AIWikis.org/uaix/ after source-site review. AIWikis long memory can preserve source-safe summaries, original-file manifests, checksums, and retrieval pointers,...

Metadata

FieldValue
Source siteuaix.org
Source URLhttps://uaix.org/
Canonical AIWikis URLhttps://aiwikis.org/uaix/files/uai-long-term-memory-uai-d7d22de7/
Source reference.uai/long-term-memory.uai
File typeuai
Content categoryuai-system
Last fetched2026-06-22T01:56:21.9510185Z
Last changed2026-06-21T20:36:12.3404100Z
Content hashsha256:d7d22de7928a5edbc531cfefc395c5565fcb9fc88d94dd69383410a7b1408d74
Import statuschanged
Raw source layerdata/sources/uaix/uai-long-term-memory-uai-d7d22de7928a.uai
Normalized source layerdata/normalized/uaix/uai-long-term-memory-uai-d7d22de7928a.txt

Current File Content

Structure Preview

  • Long-Term Memory
  • 2026-06-21 Dogfooding Remediation Evidence
  • 2026-06-21 AI-Ready Web Program
  • 2026-06-02 UAIX Standards Release
  • 2026-05-31 Coding Standards Report Applied
  • 2026-05-26 Guidance Correction
  • 2026-06-11 Memory Maintenance And Active Instruction Anchor Correction
  • 2026-06-07 Locale Router Public Recovery Retirement
  • 2026-06-07 Talisman System Public Page
  • 2026-05-26 Site Health Guard Recovery Correction (Superseded)
  • 2026-05-26 Improvement Intake Guidance Correction
  • 2026-05-26 Content Intake Guidance Correction
  • 2026-05-31 Coding Standards Memory Requirement
  • 2026-05-31 Workspace Package Evidence
  • 2026-05-31 Agent Communication Operating Model Upgrade
  • 2026-05-31 Capability-Adaptive Web Interaction Release
  • Workspace .uai Memory Rule
  • UAIX And LLM Wiki Wizard Alignment

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

  • Source characters: 18508
  • Preview characters: 11892

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: long-term-memory
title: "UAIX Long-Term Memory"
project: "UAIX.org"
created: "2026-05-26"
updated: "2026-06-21"
status: active
destination: "https://AIWikis.org/uaix/"
---

# Long-Term Memory

Reviewed durable memory for UAIX.org routes to `https://AIWikis.org/uaix/` after source-site review. AIWikis long memory can preserve source-safe summaries, original-file manifests, checksums, and retrieval pointers, but this source tree remains the authority for current code, content, package state, and deployment evidence.

Do not leave old memory folders as active truth. Consolidate current facts into `.uai/short-term-memory.uai`, preserve durable reviewed material in the long-term wiki/archive, and remove or clearly retire the confusing path.

## 2026-06-21 Dogfooding Remediation Evidence

- Source reports: four active files from `agent-file-handoff/Improvement/`, covering UAIX.org AI-Ready Web compliance, dogfooding/spec analysis, AI-agent interaction, and comprehensive guideline/remediation recommendations.
- Raw durable evidence: `[local path redacted]`.
- Public-safe summary: `[local path redacted]`.
- Durable accepted fact: report findings must be treated as hypotheses until checked against source, live routes, publish output, and current UAIX support boundaries. Accepted slices produced a dogfooding evidence matrix, REST method-normalization fix, live/source/publish drift records, NuGet documentation boundary, deployment-contract memory, tests, and a `v3.132.0` package-ready build.
- Durable boundary: raw report text is source evidence for future review, not public UAIX.org copy, release proof, standards text, certification, endorsement, or live publication evidence. UAIX does not claim experimental protocol support, affiliation, NuGet.org publishing, or full live deployment without implementation and verification evidence.
- Intake disposition: originals were preserved in AIWikis raw long memory with SHA-256 evidence and removed from UAIX active intake after application; no source-site Archive copy was created.

## 2026-06-21 AI-Ready Web Program

- Source reports: sixteen active files from `agent-file-handoff/Improvement/`, covering AI agent website support, AI web accessibility, agent-usable site practices, UAIX AI interoperability, AI-ready future-proofing, route/discovery guidance, and the AI-Ready Web master prompt.
- Raw durable evidence: `[local path redacted]`.
- Public-safe summary: `[local path redacted]`.
- Durable accepted fact: UAIX can publish a seven-volume AI-Ready Web program that makes websites more usable by AI agents through stable human-first semantics, accessible rendered state, deterministic discovery, route/API inventories, maturity labels, consent and rights signals, provenance, testable readiness evidence, and support-boundary governance.
- Public/source outcome: `/en-us/ai-ready-web/` plus seven child volumes, `spec/ai-ready-web-*.json` registries/schemas/examples, route/discovery entries, low-capability `llms` guidance, public evidence pointers, and focused static tests.
- Durable boundary: UAIX documents readiness patterns and evidence records. It does not authorize scraping, execute workflows, validate credentials, certify agent access, guarantee MCP/A2A/WebMCP/DNS/commerce interoperability, or claim live publication until package/upload/root-file/live-verification evidence exists.
- Intake disposition: originals were preserved in AIWikis raw long memory with SHA-256 evidence and removed from UAIX active intake after application; no source-site Archive copy was created.

## 2026-06-02 UAIX Standards Release

- Source report: `agent-file-handoff/Improvement/AI Agent Integration with UAIX Standards.md`, SHA-256 `4C546C906B4206E8672E21E01524CBB7B62EB37034E346474045446EAA9A953E`.
- Durable accepted fact: UAIX can publish standards records that combine human routes, UAI-1 transport-envelope examples, standards publication-envelope documentation, capability-ladder declarations, review receipts, public-safe audit digests, and redaction-policy records without becoming an execution runtime.
- Public outcome: standards route family, SPEC-01 through SPEC-04 pages, L0-L6 capability-ladder page, low-capability and advanced-agent guidance pages, `/schemas/index.json`, `/examples/index.json`, `/.well-known/ai-agent.json`, nine `uaix.*.v1` standards schemas/examples, invalid examples, registry and field-registry entries, docs, release notes, sitemap, llms files, fallback root assets, and `v3.57.0` WordPress upload packages.
- Durable boundary: Agent runtimes execute. UAIX records the reviewed communication, memory, trust, evidence, and handoff boundary. NeuralWikis, LocalEndpoint, Carcinus, MCP, A2A, and custom runtimes remain reference-only consumers/examples unless their own projects implement runtime behavior. UAIX.org does not claim hosted execution, runtime orchestration, repository writes, certification, endorsement, official adapters, SDK/CLI, automatic sync, or trust/crypto verification without real verifier evidence.
- Release scope: UAIX.org-only `v3.57.0` source/package work from canonical `[local path redacted]`; sibling/non-UAIX sites are intentionally out of scope for this release pass.

## 2026-05-31 Coding Standards Report Applied

- Source: `agent-file-handoff/Improvement/Coding Standards by Technology Stack.md`, SHA-256 `BA6745A46F2D8E788BE3660249AD1E56A3CA3D47291219C7B646D881191F4E0A`.
- Durable outcome as superseded by the 2026-06-06 family-aware wizard update: UAIX and LLMWikis wizard/guidance treat `.uai/coding-standards.uai` as required for project/developer packages and for non-project assistant packages that declare code, automation, executable workflow, or code-like artifacts. Code-bearing packages keep selectable stack profiles, required agent-side codebase inference when a codebase exists, DRY, once-and-only-once, SOLID, and automated testing enforcement.
- Stack-profile catalog applied from the report: PHP/WordPress, JavaScript/Node/Express, TypeScript/React, Angular, Vue, Python, Java/Spring Boot, C#/.NET, HTML/CSS, SQL, MongoDB, REST/HTTP, GraphQL, Protocol Buffers/gRPC, Cloud/Twelve-Factor, and OWASP Secure Coding.
- Original source is preserved under UAIX Agent File Handoff Archive after processing; active short-term memory carries only the brief current rule.

## 2026-05-26 Guidance Correction

- UAIX.org corrected the AI Memory Package Wizard and Project Handoff guidance so `.uai/` is the canonical local project-memory root.
- The durable rule is: current working truth goes to `.uai/short-term-memory.uai` or another typed `.uai` record; reviewed durable history goes to the long-term wiki/archive; mistaken memory folders and scattered notes are removed or clearly retired after migration.
- AIWikis should treat older records that describe legacy separate memory-folder layouts as superseded historical source evidence, not current UAIX guidance.

## 2026-06-11 Memory Maintenance And Active Instruction Anchor Correction

- Durable accepted rule: every UAIX memory package must contain `.uai/memory-maintenance.uai`; missing or invalid `.uai/memory-maintenance.uai` makes the package non-compliant.
- Universal required startup files are `.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`.
- `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/talisman.uai` are active instruction anchors. Agents must read and obey all three before broad execution.
- Changing, deleting, weakening, replacing, or reinterpreting Totem, Taboo, or Talisman requires exact human authorization naming the exact file and exact change.
- Agent-facing UAIX guidance must not use ignored-status labels. Use "Required for ..." or "Not required for ..." with the exact profile, mode, package type, capability, or boundary.
- This supersedes older UAIX rows that treated Totem/Taboo/Talisman as metadata-only files, or treated Talisman as a special profile feature. UAIX.org should distinguish required reading/obedience from protected mutation.

## 2026-06-07 Locale Router Public Recovery Retirement

- UAIX.org reviewed the `uaix-locale-router-3.76.0-marketplace-ready.zip` and hardening report from `agent-file-handoff/Improvement/` and accepted the reliable parts into source as the `v3.77.0` hardening pass.
- Durable current rule: UAIX Locale Router keeps routing diagnostics in admin/Site Health flows and must not embed public health-guard recovery endpoints, public shutdown recovery renderers, frontend loopback self-repair, active-plugin order mutation, or public `.htaccess` rewrite mutation.

## 2026-06-07 Talisman System Public Page

- Source: `agent-file-handoff/Improvement/Advanced UAIX Totem_Taboo Management.md`, SHA-256 `8A28781BF8A19886C48670D97DB4650FD8106DE5F78DFB361F75573414DE0731`; duplicate-by-text source `agent-file-handoff/Improvement/Advanced UAIX Totem_Taboo Management part 2.md`, SHA-256 `3C9FAF2FE5911466AAE471E71466F3C3AEA835EED5B305AA6268DBB8ED2A2424`.
- Historical rule, superseded 2026-06-11: this pass treated Totem/Taboo as universal required files and Talisman as profile-required for declared protected-anchor governance. Current UAIX guidance treats `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/talisman.uai` as required active instruction anchors to read and obey; exact human authorization is required only for mutation.
- Public outcome: UAIX seeds `/en-us/ai-memory/talisman-system/` as required active-instruction guidance plus advanced protected-change governance; adds an AI Memory page cross-link and chooser row; adds AI Memory Package Wizard Talisman output; adds Memory Firewall/support-panel/document-guidance links; and exposes `ai_memory_talisman_system` in the plugin artifact catalog, static well-known manifests, sitemap, route manifest, launch audits, static discovery tests, production response tests, and AI Memory regression tests.
- Durable boundary: UAIX may publish schema, package, handoff, no-op, and talk-back evidence structures for protected-anchor review. UAIX must not claim cryptographic signing, read/write interception, runtime proxy enforcement, IDE guardrails, autonomous self-protection, automatic credential validation, certification, safety proof, model training, endpoint control, AGI, consciousness, sentience, biological equivalence, or immutable enforcement unless actual implementation and release evidence exists. Teleodynamic.com remains the philosophical fulcrum for claim clarity and symbolic/teleodynamic interpretation; UAIX.org remains the interoperability, package, schema, and handoff standards layer.
- Intake disposition: apply-now-with-boundaries into public source, machine discovery, tests, docs, and memory; do not silently add `talisman.uai` to every package.

## 2026-05-26 Site Health Guard Recovery Correction (Superseded)

- UAIX.org corrected the embedded `uaix-locale-router` site-health guard so a recovery attempt for the same frontend fatal hash opens the next public frontend request instead of repeatedly serving recovery mode.
- This addresses the observed behavior where visiting `/wp-admin` could make a site appear to come back by updating non-frontend state while public traffic remained trapped behind the recovery page.
- The workspace package builder now stages `uaix-locale-router` from the canonical UAIX source for every site package that ships that plugin, including sites whose local source copy is ACL-locked.
- Superseded by the 2026-06-07 retirement above: this historical correction is no longer current packaging guidance.

## 2026-05-26 Improvement Intake Guidance Correction

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 long-term-memory 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: Long-Term Memory; 2026-06-21 Dogfooding Remediation Evidence; 2026-06-21 AI-Ready Web Program; 2026-06-02 UAIX Standards Release; 2026-05-31 Coding Standards Report Applied; 2026-05-26 Guidance Correction; 2026-06-11 Memory Maintenance And Active Instruction Anchor Correction; 2026-06-07 Locale Router Public Recovery Retirement. 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

Provenance And History

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

Machine-Readable Metadata

{
    "title":  "UAIX Long Term Memory",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/uai-long-term-memory-uai-d7d22de7/",
    "source_reference":  ".uai/long-term-memory.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:d7d22de7928a5edbc531cfefc395c5565fcb9fc88d94dd69383410a7b1408d74",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-21T20:36:12.3404100Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-1040",
    "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.
  • UAIX.org UAIX.org source-system overview for transparent AIWikis memory demonstration.
  • UAIX.org Source Memory Guide AIWikis source-governed page for durable AI memory, evidence routing, and agent-readable retrieval.
  • UAIX.org Files Site-scoped current-source file index for UAIX.org.