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

UAIX Agents Protocol

UAIX-produced experimental WordPress package for dogfooding Project Handoff exports, manifest validation, ZIP preflight checks, refusal behavior, cleanup, and activation smoke testing.

  • Record UAIX-TOOL-0066
  • Path /es-us/tools/uaix-agents-protocol/
  • Use Canonical public record

Document status

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

How to use this page

Use this page as part of the current Tools public record, then follow its linked standards pages for the next step.

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.

What this page is for

UAIX Agents Protocol is the legacy public dogfood record for the UAIX-produced WordPress package that is now published as UAIX.org UAI Memory Management. UAIX.org remains the source-of-truth producer and distribution surface for the package; LlmWikis.org, AIWikis.org, and other test sites should consume the UAIX-published ZIP rather than treating their local copies as canonical.

Current status

  • Package name: uai-memory-management-v3.188.0.zip.
  • WordPress plugin slug: uai-memory-management.
  • Current public plugin name: UAIX.org UAI Memory Management.
  • SHA-256: D695E6BE19E228311237BC77DF5E054BE08B2186F384C3A3F79FF415A353DEA7.
  • Status: legacy dogfood and smoke-test evidence route; the current admin-plugin route is UAI Memory Management.
  • Evidence role: local dogfood and smoke-test evidence for Project Handoff packaging, .uai/readme.human, a fuller .uai handoff set, active file-intake buckets, and no source-site Archive scaffolding when durable-memory storage is configured, not official UAIX generator, validator, SDK, CLI, certification, or endorsement support.

Dogfood finding

The AIWikis.org package build exposed a practical failure mode: a package can cite Project Handoff while omitting the active agent-file-handoff/ workspace or a complete enough .uai context set. The memory-management pass adds a second dogfood lesson: if correct information is hidden inside stale, oversized, or date-log-style hot memory, agents can miss it even though it technically exists. Hot .uai records must stay current, compact, and fully loadable.

What UAIX should prove with it

  • Generated manifests use the current UAI-1 uai.intent.request.v1 shape and pass UAIX Core validation when the Core validator is available.
  • Generated packages include .uai/readme.human, the loaded .uai handoff records for context, stack, architecture, constraints, decisions, progress, operations, test plan, style, sources, prompts, file handoff, and active bucket review, plus agent-file-handoff/Content/ and agent-file-handoff/Improvement/ scaffolding without visible README files inside those buckets.
  • Plugin-local validation behavior stays aligned with UAIX Core validator behavior or with bundled schema and registry fixtures.
  • apply_to_site refuses to run when manifest validation fails.
  • Imports apply ZIP size, file-count, unpacked-size, traversal, path allowlist, and executable-file checks before extraction or apply.
  • Memory Explorer surfaces .uai/, Advanced Persona files, and existing docs/ or wiki/ memory roots without silently inventing a competing memory folder.
  • Cleanup jobs remove temporary extraction folders, expired upload records, and stale package working files.
  • Activation smoke output exists before WordPress compatibility is treated as proven for a release.

How to use it in UAIX release work

  1. Install and activate the UAIX-published versioned ZIP in the local Studio workspace.
  2. Review the UAI Memory admin status panel before exporting or applying Project Handoff packages.
  3. Export a Project Handoff package from current UAIX repository context.
  4. Validate the generated manifest through UAIX Core and keep the result with the test packet.
  5. Confirm the package includes .uai/readme.human, the expected loaded .uai files, active file-intake buckets without a source-site Archive folder when durable-memory storage is configured, but does not publish raw dropped files or preserved source records as public content.
  6. Try invalid packages and confirm apply_to_site refuses them before any site write occurs.
  7. Record the package hash, file count, preflight outcome, validator result, cleanup result, activation smoke result, and memory-status warnings before widening public language.

Current public boundary

  • This page preserves the downloadable dogfood evidence route for controlled test-site evaluation.
  • The current public admin-plugin product route is UAI Memory Management.
  • The plugin does not publish a hosted .uai generator, hosted upload validator, SDK, CLI, certification process, or endorsement program.
  • The plugin can support WordPress memory-management evidence only while the public roadmap, fixtures, validation behavior, release notes, and broader support evidence stay aligned.
  • UAI Memory Management is the current public admin-plugin page.
  • Project Handoff is the practical AGENTS.md, .uai/readme.human, and .uai handoff pattern this package exercises.
  • Agent File Handoff explains the active local intake and durable-memory preservation workspace this package exports.
  • Validator explains the public evidence posture for UAI-1 message validation.
  • Conformance Pack is the reusable public packet model this package should not overclaim as certification.
  • Launch Readiness is the go-live gate for package evidence, locale QA, and support-claim boundaries.
  • Roadmap and Changelog are the places to check before repeating future tooling or compatibility claims.

Smoke sequence

Use a small, repeatable local sequence when this package participates in a UAIX release check.

Code example
studio wp plugin install uai-memory-management-v3.188.0.zip --activate
studio wp plugin is-active uai-memory-management
# Validate generated manifests with UAIX Core before apply_to_site.
# Record ZIP preflight, refusal, cleanup, memory-status warnings, and activation smoke evidence.