=== UAIX.org UAI Memory Management ===
Contributors: uaix
Tags: ai, memory, documentation, admin, export
Requires at least: 6.7
Tested up to: 6.9
Requires PHP: 7.4
Requires Plugins: uaix-core
Stable tag: 3.198.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Manage .uai memory, persona files, docs/wiki records, update prompts, and portable UAI memory packages from WordPress.

== Description ==

UAIX.org UAI Memory Management gives WordPress administrators a guarded place to inspect, edit, export, import, and review local AI memory records.

The Memory Explorer manages `.uai/` files, Advanced Persona records, and supported text files under existing `docs/` and `wiki/` roots. Hot memory should hold present truth, blockers, next actions, constraints, and concise pointers. Older or bulky evidence belongs in a scale-fit durable memory target.

This plugin does not call an AI model. It stores local records, validates package shape, detects nearby WordPress AI infrastructure for metadata only, and generates copyable update prompts that point agents to the UAIX.org AI Memory Package Wizard.

UAIX Core is a declared plugin dependency because it owns the Advanced Persona machine contract used by this plugin's health and readiness checks. If that contract is unavailable or invalid, Advanced Persona readiness fails closed.

== Features ==

* Dashboard, Memory Explorer, Settings, Export, Import, Validation Report, and Memory Packages screens.
* Guarded editing for supported text-oriented files in `.uai/`, existing `docs/`, and existing `wiki/` roots.
* Advanced Persona support for exactly 31 source-persona records and five evidence records, including romantic orientation without inferred private facts.
* Read-only Advanced Persona diagnostics with stable `UAI-AP-*` codes and contract-owned readiness states.
* Memory health warnings for missing launch-baseline files, oversized hot memory, date-log drift, and incomplete persona records.
* Copyable agent update prompts targeting `https://uaix.org/en-us/tools/ai-memory-package-wizard/`.
* Reviewable ZIP export/import, REST validation, and `wp uai1 export`.
* Path traversal protection, file-size limits, safe extensions, nonces, and WordPress capability checks.
* Workspace-version pointers that keep active `.uai` memory free of copied package-version ledgers.

== Installation ==

1. Install and activate the `uaix-core` dependency.
2. Upload the `uai-memory-management` folder or install its ZIP from Plugins > Add New > Upload Plugin.
3. Activate the plugin and open UAIX UAI Memory.
4. Review Memory Explorer and Settings before importing or editing records.

== Usage ==

= Memory Explorer =

Use UAIX UAI Memory > Memory Explorer to review status, copy an update prompt, and edit supported site-relative records. Executable files, unsupported roots, oversized files, path traversal, and invalid JSON saves are blocked.

= Advanced Persona diagnostics =

Memory Explorer reports affected paths and the exact computed state: `activation_ready`, `structurally_valid_scaffold`, or `activation_blocked`. It never rewrites persona source to clear a warning. Reviewed unknown, private, not-disclosed, and absent states remain activation-eligible; pending review, operative template markers, incomplete authority/integrity evidence, and blocking diagnostics do not.

Current diagnostics include `UAI-AP-FILESET-MISSING`, `UAI-AP-OMNIBUS-COLLAPSE`, `UAI-AP-PLACEHOLDER-ONLY`, `UAI-AP-EVIDENCE-REF-MISSING`, `UAI-AP-EVIDENCE-REF-UNRESOLVED`, `UAI-AP-UPDATE-ROUTE-MISSING`, `UAI-AP-UPDATE-ROUTE-MISMATCH`, `UAI-AP-SOURCE-CONSTRAINT-INJECTION`, and `UAI-AP-PROVENANCE-MISSING`. A route diagnostic means one of the 36 canonical records omits `update_route` or does not match the selected route.

= WordPress AI ecosystem =

The Dashboard detects nearby WordPress AI infrastructure for metadata only. Review memory before intentionally providing an agent with a prompt, file set, or exported ZIP. The plugin does not automatically send or synchronize memory.

= Export =

Use Export to download selected memory records and WordPress content for reviewable handoff work.

= Import =

Use Import to preview a UAI memory ZIP, choose duplicate/merge/overwrite behavior, and apply it only after human review.

= REST =

Use `POST /wp-json/uai1/v1/export/123`, `/import`, or `/validate`. Import and validation accept multipart field `package`.

= WP-CLI =

Use `wp uai1 export --id=123` or `wp uai1 export --post_type=uai_project --include_media=references`.

== Frequently Asked Questions ==

= Does this certify my package as UAIX compliant? =

No. Public conformance claims require separate published validator and release evidence.

= Does it call an AI model? =

No. Export, import, and validation run locally.

= Can it edit docs and wiki files? =

Yes, when the root already exists. Use local docs/wiki for bounded local work and shared memory with governance for cross-project or organizational knowledge.

= What does "memory out of date" mean here? =

It means current memory appears incomplete, oversized, stale, or shaped like dated history. Correct current facts and move older evidence to a scale-fit durable memory target with a concise pointer.

== Changelog ==

= 3.198.0 =

* Adds contract-owned Advanced Persona structural and activation readiness checks.
* Keeps the public readme concise and focused on current operation.

== Upgrade Notice ==

= 3.198.0 =
Adds current Advanced Persona readiness validation and concise operating guidance.
