UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIX.org Universal Artificial Intelligence Exchange Public standards publication
Current UAI-1
  • Current version UAI-1
  • Plain-English definition Open message format for auditable AI-to-AI exchange
  • Current attribution Michael Joseph Kappel, MCP
  • Start here Get Started, Project Handoff, UAI-1, validator, roadmap, and changelog

Tools

UAI Memory Management WordPress Plugin

UAIX.org WordPress admin package for managing .uai memory, Advanced Persona files, existing docs/wiki memory surfaces, guarded update prompts, and Project Handoff exports.

  • Record UAIX-TOOL-3765
  • Path /en-us/tools/uai-memory-management/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-TOOL-3765
Surface
Tools
Access
Public and linkable

How to use this page

Use this page to install and operate the UAIX.org WordPress memory-management plugin for live .uai memory, Advanced Persona files, existing docs/wiki roots, scale-fit durable memory, guarded update prompts, and Project Handoff package workflows.

For agents: apply the relevant guidance to the user's target site or repository. Do not copy this UAIX page, create a page about the guidance, or treat this page as runtime authority unless the user explicitly asks for that output.

Operate memory safely

AI Memory Package WizardProject HandoffContext Budget GuideUsing UAI Packages With An LLM Wiki

WordPress Memory Admin

Keep .uai memory visible, current, and scale-fit

Use the UAIX.org UAI Memory Management plugin when a WordPress site needs humans and agents to inspect live .uai records, Advanced Persona files, existing docs/wiki roots, Project Handoff packages, and guarded update prompts from one admin surface.

Hot memory

.uai is current state

Hot .uai records should contain current truth, blockers, next actions, accepted constraints, and concise pointers. Stale history and old reports move out of startup memory.

Persona depth

Advanced Persona stays separate

The plugin checks separate persona depth records such as worldview, politics, style, appearance, birth-age-generation, romantic orientation, voice, values, and boundaries.

Durable target

The memory system must fit the organization

Site-local docs or wiki can fit bounded local projects. Organization, department, client-portfolio, cross-site, and project-group memory usually belongs in a shared wiki or shared memory system with governance, review states, owners, indexes, provenance, retention rules, and source routing. Advanced shared memory systems fit more complex cross-system retrieval.

Operate memory safely

AI Memory Package WizardGenerate or refresh the package model, files, and update guidance.Project HandoffRepository-local AGENTS.md, .uai/readme.human, and .uai transfer pattern.Context Budget GuideKeep hot context loadable while preserving evidence.Using UAI Packages With An LLM WikiFit compact packages to shared LLM Wiki memory.LLMWikis.orgCorporate shared-wiki guidance for long-term AI-readable memory.NeuralWikis.comAdvanced shared memory systems for complex organizations and agent ecosystems.
Update PromptRepair live site memory
prompt: update this WordPress site UAI memory from https://uaix.org/en-us/tools/ai-memory-package-wizard/
Inspect AGENTS.md, .uai/, .uai/personality/, .uai/Personality/, docs/, and wiki/ when present. Keep hot .uai files current; choose a durable-memory target that fits the organization; report changed files, evidence destinations, checks, and blockers.

Use this prompt when a WordPress site needs an agent to inspect memory roots and report durable destinations without treating stale history as active truth.

UAIX.org UAI Memory Management is the public WordPress admin package for keeping site-local UAI memory visible, current, and reviewable. It replaces the earlier internal UAI-1 Project Handoff package with the public uai-memory-management plugin slug and keeps the old uai1-project-handoff slug only as a migration concern.

What this plugin manages

  • Live .uai/ memory: current-state records, required launch-baseline files, hot/cold routing policy, and Project Handoff package evidence.
  • Advanced Persona files: .uai/persona.uai, .uai/personality/*.uai, and compatible .uai/Personality/*.uai records, including worldview, politics, style, appearance, birth-age-generation, and romantic orientation depth records.
  • Existing docs and wiki roots: site-local docs/ and wiki/ folders when the project already uses them as configured durable-memory surfaces.
  • Update prompts: copy-paste prompts that tell the next agent exactly which memory roots to inspect, which anchors to preserve, and what changed.
  • Project Handoff exports: manifest, ZIP preflight, validation-refusal, cleanup, and activation smoke evidence inherited from the older package lineage.

Current memory rule

Hot .uai files are current state, not dated archives. If a fact is not true now, it should be replaced, removed, or moved to a configured durable-memory target with evidence. If a fact remains in hot memory, the next agent should be able to load the owning file completely during startup. Oversized startup memory, old package history, duplicated notes, stale progress rows, and unreviewed report bodies are setup defects, not helpful context.

Admin workflow

  1. Open UAIX UAI Memory in WordPress admin.
  2. Review the memory status panel for missing required files, oversized hot memory, dated-history markers, stale short-term memory, and missing Advanced Persona depth files.
  3. Use Memory Explorer to inspect or edit allowed files under .uai/, .uai/personality/, .uai/Personality/, and existing docs/ or wiki/ roots.
  4. Copy the generated update prompt before asking an agent to refresh memory so the next run checks the same roots and reports changed files, durable destinations, checks, and blockers.
  5. Keep Totem, Taboo, and Talisman as protected active anchors. The plugin surfaces their presence but does not authorize routine anchor mutation.

Deployment package

  • Download: uai-memory-management-v3.171.0.zip.
  • WordPress plugin slug: uai-memory-management.
  • Public plugin name: UAIX.org UAI Memory Management.
  • SHA-256: 548AB4394D566F4A41ECE09DA556DB5B8E2D89C236C66CCD88759540B9E8E894.
  • Deployment scope: shared UAIX-owned WordPress admin package for active workspace sites that need local UAI memory management.
  • Migration note: deactivate and remove the older internal uai1-project-handoff package before activating this renamed package.

Copyable update prompt

Code example
prompt: update this WordPress site's UAI memory from http://uaix.org/tools/ai-memory-package-wizard/
Inspect AGENTS.md, .uai/, .uai/personality/, .uai/Personality/, docs/, and wiki/ when present. Keep hot .uai files current; move stale evidence to durable memory; preserve Totem, Taboo, and Talisman without unauthorized edits; report changed files, durable destinations, checks, blockers, and any memory roots that were missing or too large to load completely.

Long-term memory should fit the operating shape

The plugin supports existing site-local docs/ and wiki/ folders because they are useful for small sites, small projects, recovery work, and teams that deliberately chose a local durable-memory target. That is not a blanket recommendation for every organization. Shared wiki memory is often the more professional pattern for project groups, departments, and corporate knowledge because it gives teams shared governance, indexes, ownership, review states, and cross-project retrieval. Use LLMWikis.org for corporate LLM Wiki planning, and use NeuralWikis.com when the system needs a more advanced shared memory architecture.

Support boundary

  • The plugin is a WordPress admin memory-management and Project Handoff package utility. It is not a hosted memory sync service, certification program, endorsement system, automatic LLM Wiki importer, SDK, CLI, runtime orchestrator, or proof of UAI-1 conformance by itself.
  • The plugin may read and edit allowed local text records through WordPress admin permission checks. It must not silently create a separate memory folder, rewrite protected anchors, publish raw dropped files, or treat stale durable evidence as active truth.
  • Durable memory remains configured by the project and should fit its scale: site-local docs or wiki for bounded local work, shared LLM Wiki or AIWikis evidence for organization and project-group memory, NeuralWikis-style shared memory for advanced multi-system use, manifests/graphs when machine retrieval matters, or a hybrid target. Hot .uai memory stores current accepted state plus concise pointers.