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

AI Memory Package Wizard

Guided builder for supported UAI AI Memory starter bundles, package model JSON, generated system profiles with source-authority and evidence protocols, receiver briefs, startup packets, copy-paste file decks, manifest overlays, optional LLM Wiki memory plans, readiness checks, and canonical ZIP downloads.

  • Record UAIX-TOOL-0334
  • Path /en-us/tools/ai-memory-package-wizard/
  • Use Canonical public record

Document status

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

How to use this page

Use this page to configure a supported UAI AI Memory starter bundle, export a package model, copy files, and download the matching canonical ZIP without treating it as a general hosted generator.

What this page is for

The UAI AI Memory Package Wizard turns the supported starter configurations from AI Memory into a guided package planning surface. It uses the same canonical template registry, generated manifest, and deterministic ZIP download routes already used by the public starter bundle page.

Current support boundary

  • Current: choose a supported preset, add package metadata, generate a populated operating profile, generate a receiver startup brief, generate a one-file startup packet, optionally answer whether the project uses an LLM Wiki, set advanced audience, sensitivity, deck-scope, review gates, collaboration model, UAI-only or UAI plus Wiki architecture, unit and integration test posture, test timing, deployment posture, code review strategy, release gate, source-authority policy, memory-update policy, evidence ledger path, conflict-resolution policy, change-risk level, and rollback strategy, inspect a readiness checklist, copy individual files, download a package model JSON, download a manifest overlay JSON, download UAI_MEMORY_SYSTEM_PROFILE.md, download UAI_MEMORY_RECEIVER_BRIEF.md, download UAI_MEMORY_STARTUP_PACKET.md, download the optional LLM_WIKI_MEMORY_PLAN.md file, and fetch the canonical starter ZIP for the selected preset.
  • Current ZIP boundary: ZIP files are generated from canonical starter templates. Wizard metadata, system profiles, receiver briefs, startup packets, overlays, and generated plan files travel beside them as JSON or Markdown so the page does not pretend to be a general hosted repository writer.
  • System profile boundary: UAI_MEMORY_SYSTEM_PROFILE.md is a generated local operating file. It defines collaboration, memory architecture, source authority, memory update rules, testing, deployment, code review, evidence ledger, conflict handling, risk escalation, rollback, and placeholder-population rules for the receiver; it still requires the receiver to inspect the actual codebase, CI, deployment docs, owners, and environment before acting.
  • Receiver boundary: UAI_MEMORY_RECEIVER_BRIEF.md is a local startup instruction file for the next human, team, or AI. It names read order, first-response expectations, support boundaries, and targeted-check expectations; it is not an importer, repository writer, automatic sync system, certification, endorsement, or UAI-1 conformance result.
  • Startup packet boundary: UAI_MEMORY_STARTUP_PACKET.md is a local operator packet that embeds generated instructions and selected-file indexes for easier handoff. It is still not a hosted importer, automatic repository writer, automatic wiki sync, SDK, CLI, certification, endorsement, or UAI-1 conformance result.
  • LLM Wiki boundary: LLM Wiki is not required by UAI specs or standards. When a project also uses an LLM Wiki long-memory layer, the wizard can add an exact-root LLM_WIKI_MEMORY_PLAN.md planning file. That file explains what gets saved along the way, when to update long-term memory, which source-authority and conflict rules apply, which archive-transfer evidence to record, which promotion gates apply, and why wiki memory remains background until promoted into project truth. Use Using UAI Packages With An LLM Wiki for the practical package/wikimemory operating path, and use LLMWikis.org-style guidance for the deeper wiki layer rather than treating UAIX.org as the wiki host. Learn more at LLMWikis.org.
  • Not current: hosted upload or import validation, WordPress admin installation, automatic site writes, automatic LLM Wiki writes or bidirectional sync, SDKs, CLIs, certification, endorsement, or broad package-manager support.

Wizard

Package Wizard

Build a UAI AI Memory starter package

Start with a supported preset and leave with a one-file startup packet, system profile, receiver brief, populated operating protocols, manifest overlay, copyable file deck, optional LLM Wiki plan, and canonical starter ZIP link.

Ready
1Pick a pathChoose the reader goal before tuning files.
2Review boundariesAudience, sensitivity, owners, and redaction stay explicit.
3Define operationsTesting, deployment, review, and collaboration choices populate the system profile.
4Set protocolsSource authority, evidence, conflict, risk, and rollback rules are populated.
5Brief the receiverGenerate the first-read and first-response instructions.
6Add wiki planOptional LLM Wiki instructions travel as a generated file.
7Copy or downloadExport JSON, inspect files, copy the startup packet, or fetch the canonical ZIP.

1. Choose preset

2. Package metadata

3. Operating strategy

These choices populate UAI_MEMORY_SYSTEM_PROFILE.md with the collaboration model, UAI versus UAI plus Wiki architecture, unit and integration test rules, deployment posture, code review strategy, and placeholders the receiver must fill from the real system.

4. Protocol and evidence rules

These choices tell the generated system profile how the receiving project decides source authority, when memory updates, where evidence is recorded, how conflicts are resolved, which risks escalate, and how rollback is handled.

5. Receiver startup packet

The wizard generates UAI_MEMORY_STARTUP_PACKET.md, UAI_MEMORY_SYSTEM_PROFILE.md, and UAI_MEMORY_RECEIVER_BRIEF.md so the next human, team, or AI has one first file, a populated operating profile, and a standalone brief for read order, support boundaries, and targeted-check expectations.

6. Optional: Are you using an LLM Wiki?

LLM Wiki is not required by UAI specs or standards. Use this only when deep internal documentation, source summaries, research trails, or archive memory already affect how the portable package should be shaped.

Use UAI packages with an LLM Wiki Learn more at LLMWikis.org

7. Choose output mode

Advanced options Audience, sensitivity, review gates, and deck scope

Audience and scope

Trust and review gates

Review package model

Download canonical ZIP

Live build preview

Watch the generated memory files update as each choice changes. This preview is local to the page and does not upload, import, sync, certify, or write to a repository.

UAI_MEMORY_STARTUP_PACKET.md
Code example

Manifest overlay preview

This local overlay records the wizard choices that travel beside the canonical ZIP; it is not an upload, import, certification, or endorsement result.

Code example

Copy-paste file deck

How this connects to Project Handoff

Use Project Handoff when the chosen package needs to become a repository-local AGENTS.md, readme.human, and .uai transfer bundle. Use the UAIX Agents Protocol page only for the experimental WordPress package dogfood record; it does not widen the wizard into a public plugin importer.

Before widening a support claim

Check the Roadmap and Changelog before describing any future admin plugin, upload validator, source-control writer, automatic LLM Wiki sync, SDK, CLI, certification, or endorsement behavior as current UAIX support.