UAI-1 es la norma pública actual de mensajes para comunicación estructurada de IA a IA.
UAIX shield mark Carta pública de interoperabilidad UAIX.org 通用人工智能交换 Publicación pública de normas
Actual UAI-1
  • Versión actual UAI-1
  • Definición en lenguaje claro Formato de mensaje abierto para intercambio IA-a-IA auditable
  • Atribución actual Michael Joseph Kappel, MCP
  • Empiece aquí Inicio, Traspaso de proyecto, UAI-1, validador, hoja de ruta y registro de cambios

Herramientas

Asistente de paquete de memoria de IA

Guided builder for supported UAI AI Memory starter bundles with page-level validation, local browser draft restore, prompt nudges, Safe Structured Output Mode, .uai/archives logs, .uai files, .uai/exports artifacts, wiki long-memory compatibility required for LLM Wiki configuration, JSON-LD graphs, llms.txt outputs, package model JSON, generated system profiles, receiver briefs, startup packets, review/export checks, browser-generated ZIP packages, manifest overlays, LLM Wiki memory plans required for LLM Wiki configuration, and canonical ZIP downloads.

  • Record UAIX-TOOL-0334
  • Path /es-es/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
Herramientas
Access
Public and linkable

如何使用本页

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.

Human visual entry for the UAI AI 记忆数据包向导
Human wizard Use the visible package flow Human readers use the controls on this page to choose a supported preset, review generated files, and download the canonical starter ZIP.
Visitor AI digest entry for the UAI AI 记忆数据包向导
Visitor AI digest Read the same page as JSON AI 代理s ingest the embedded digest on this route. It is generated from the same canonical payload and bundle registry as the human wizard.

Human UI and visitor AI digest

On the 英语 route /en-us/tools/ai-memory-package-wizard/, humans use the visible wizard controls. Visiting AI 代理s should read the embedded JSON block named script[data-ai-digest] on that same page. The digest keeps stable machine keys while the surrounding page copy can be language-specific, so both readers resolve the same presets, support boundaries, generated outputs, and checksums without creating a separate public importer endpoint.

将代理指向正确的设置 URL

只需要标准数据包时使用基础路线；当第一位 AI 应该从 Agent File Handoff 配置、LLM Wiki 配置或两者开始时，使用片段 URL。这些 URL 也会以 point_agent_urls 形式列在嵌入的 AI 摘要中。

阅读代理文件交接 使用带有 LLM Wiki 的 UAI 数据包

What this page is for

The UAI AI 记忆数据包向导 turns the supported starter configurations from AI 记忆 into an eight-step local-first package planning flow. The default 基础 path is compact short-term handoff memory: current truth, constraints, receiver instructions, evidence pointers, and exports. The first step can add 代理文件交接 or LLM Wiki 计划ning required for LLM Wiki configuration, but the plain wizard URL defaults to 基础 and does not ask people or agents to set up a wiki.

当前 support boundary

  • 当前: choose a setup path and supported preset, add package metadata, move through page-level validation, restore a local browser draft, receive prompt nudges, use Safe Structured Output Mode, generate a populated operating profile, receiver startup brief, startup packet, raw session log, family-aware required files, compact .uai/short-term-memory.uai, project/developer coding standards and next-recursive-prompt files or those files required for declared code-like artifacts, DTMI policy for project/developer packages, JSON-LD graph, llms.txt, llms-full.txt, package model JSON, manifest JSON, manifest overlay JSON, .uai/file-handoff.uai required for 代理文件交接 configuration, .uai/long-term-memory.uai required for long-memory configuration, copy agent-use blocks for Codex, Claude, and GPT agents, download a browser-generated memory package ZIP, and fetch the canonical starter ZIP for the selected preset.
  • Memory folder rule: the wizard default is one predictable .uai/ suite: raw evidence in .uai/archives/, active Markdown in .uai/, and exports in .uai/exports/. The 项目交接 path should create or verify the fuller typed set: .uai/startup-packet.uai, .uai/system-profile.uai, .uai/receiver-brief.uai, .uai/index.md, .uai/context.uai, .uai/constraints.uai, .uai/progress.uai, .uai/operations.uai, .uai/test-plan.uai, .uai/coding-standards.uai, .uai/next-recursive-prompt.uai, .uai/decisions.uai, .uai/memory.uai, .uai/short-term-memory.uai, and .uai/long-term-memory.uai or .uai/file-handoff.uai required for their configurations. Non-project assistant packages use their declared family set, including assistant profile, relationship boundary, privacy boundary, user preferences, and memory-update rules. Teams may gitignore .uai/ for local-only memory or check it in after redaction. Existing .uai/ packages are the default local handoff home; merge generated files additively instead of replacing current records.
  • Code-bearing boundary: Project/developer packages and packages that declare code, automation, executable workflow, or code-like artifacts must create or verify .uai/coding-standards.uai and .uai/next-recursive-prompt.uai. The recursive prompt is a derived hot-memory resume artifact, not a second source of truth. Use it for continuation or directly related requests; related active intake files supersede or expand the stored loop and still require project work, ledger evidence, and archive movement or a recorded keep-active reason. next-recursive-prompt.uai is not required for agents that don’t deal with any coding.
  • 生成时间 ZIP boundary: browser-generated ZIP packages are local-first artifacts built from canonical starter templates plus generated .uai/archives/, .uai/, and .uai/exports/ files. They do not create hosted import, repository writes, automatic LLM Wiki sync, certification, endorsement, SDK, or CLI behavior.
  • 系统画像 boundary: .uai/system-profile.uai is a generated local operating file. It defines collaboration, workspace coordination, memory architecture, source authority, memory update rules, testing, deployment, code review, evidence ledger, conflict handling, risk escalation, rollback, placeholder-population rules, DTMI maintenance, safe structured output, and harness boundary policy; it still requires the receiver to inspect the actual codebase, CI, deployment docs, owners, workspace coordinator, runtime harness, and environment before acting.
  • Receiver boundary: .uai/receiver-brief.uai is a local startup instruction file for the next human, team, Codex session, Claude session, or GPT agent. It names read order, workspace target resolution, first-response expectations, support boundaries, selected setup mode, targeted-check expectations, and memory export paths; it is not an importer, repository writer, automatic sync system, certification, endorsement, or UAI-1 conformance result.
  • 启动包 boundary: .uai/startup-packet.uai is a local operator packet that embeds generated instructions, selected setup mode, selected-file indexes, workspace routing guidance, 文件交接 plan required for 代理文件交接 configuration, LLM Wiki 计划 required for LLM Wiki configuration, DTMI policy, Safe Structured Output Mode, agentic harness boundary guidance, and release-bound memory sorting only when the build is release-bound.
  • Memory package boundary: every default wizard session produces .uai/archives/ logs, .uai/ compact short-term memory, and .uai/exports/ artifacts. Do not create a separate memory folder, wiki folder, or random handoff .md files by default. If legacy memory folders or scattered notes already exist, review them, move useful current facts into .uai/short-term-memory.uai or the right typed .uai/*.uai record, preserve durable reviewed history in the named long-term wiki/archive or .uai/archives/ evidence, record what moved, then remove or clearly retire the mistaken path so it cannot keep steering agents. wiki/ is reserved for LLM Wiki long-term compatibility configuration.
  • Content Intake boundary: Anything dropped in this folder is expected to be used in part or in full after review. For this wizard, that folder is agent-file-handoff/Content/. Files are not passive references, background to ignore, or material to merely summarize. For site content, intake is not successful unless the dropped content is used immediately on the site as full content or incorporated source for revised page content, copy, assets, structure, or implementation.
  • 代理文件交接 boundary: 代理文件交接 setup generates local dropped-file intake guidance only. It asks the receiving AI to check active agent-file-handoff/Content/ and agent-file-handoff/Improvement/ buckets, review every pending file, perform accepted work for safe relevant files, record dispositions in .uai/intake-outcome-ledger.uai or equivalent durable .uai proof-of-use state, and move processed source files to Archive/ unless the human explicitly keeps a file active.
  • LLM Wiki boundary: LLM Wiki is not required by UAI specs or standards, and UAIX is not the wiki setup site. When a project already uses or deliberately chooses an LLM Wiki long-memory layer, use Canonical AI 记忆 to keep raw source, reviewed wiki, derived graph projection, compact AI 记忆, 项目交接, and runtime execution distinct; the wizard adds .uai/long-term-memory.uai as an active pointer required for long-memory configuration. Use LLMWikis.org for wiki setup guidance.
  • Outside current support: hosted upload or import validation, WordPress admin installation, automatic unsupervised repository or site writes, automatic LLM Wiki sync, hosted dream services, SDKs, CLIs, certification, endorsement, and broad package-manager support. This page creates local files, browser-generated packages, and starter ZIP links for people to review; it does not install, import, sync, certify, or write into another system on its own.

Intake completion gate

For 代理文件交接 configuration, a .uai refresh, memory reorganization, wizard update, or handoff setup is incomplete while any active agent-file-handoff/Content/, agent-file-handoff/Improvement/, or misplaced root intake file lacks recorded disposition and proof-of-use evidence. The receiving agent must enumerate active buckets, apply or disposition every safe relevant file, update hot memory, preserve long-memory/archive evidence when configured, move processed source to Archive/ or record a keep-active reason, and name the checks or blockers before claiming completion.

Wizard

数据包向导

构建 UAI AI 记忆起步包

选择设置路径和预设，然后导出所选包族的必需文件。项目/开发者包默认包含编码标准和 next-recursive-prompt；非项目助手包包含助手画像、关系边界、隐私边界、偏好和记忆更新文件，并在存在代码类产物时必需编码标准和 next-recursive-prompt。每个包还会导出启动包、系统画像、接收方简报、清单覆盖、文件组，以及 Agent File Handoff 或 LLM Wiki 配置必需的计划。

就绪

The wizard saves a local browser draft after changes. 生成时间 outputs stay on the review step and never upload, import, sync, certify, enforce launch-baseline files, or write to a repository.

Step 1 of 8

Preset

Choose the setup path first. The base path stays compact and active-memory first; 文件交接 and LLM Wiki add explicit generated planning files without changing the current support boundary.

用途预设

使文件成为必需的内容

声明会改变封闭必需文件集的包事实。每个文件要么是所选族、配置、能力的必需文件，要么不属于此包范围。

当前 support boundary

This page creates planning files, copyable files, JSON 导出s, and canonical ZIP links. It is not a hosted importer, automatic repository writer, LLM Wiki sync service, SDK, CLI, certification, or endorsement.

These are portable communication files. They are not hosted messaging, not automatic synchronization, and not a runtime orchestrator. Agent runtimes execute. UAIX records the reviewed communication, memory, trust, evidence, and handoff boundary.

How this connects to 项目交接

Use 项目交接 when the chosen package needs to become a repository-local transfer bundle. The UAIX Agents 协议 page is separate: it documents UAIX’s experimental WordPress package used for dogfood and test-site evaluation. It is not part of the wizard flow, and it does not mean this page can import ZIPs, install plugins, or write into a WordPress 站点.

Before widening a support claim

检查 the 路线图 and 变更日志 before describing any future admin installer, upload/import validator, source-control or site writer, automatic LLM Wiki sync, hosted dreaming service, SDK, CLI, certification, endorsement, or broad package-manager behavior as current UAIX support.

Capability-adaptive web interaction records

The 3.56.0 release adds the L0-L6 client capability ladder, nine capability profile IDs, validator rules for fallback/consent/idempotency/correlation/evidence/boundary failures, and adoption-kit starter files.

Agent Communication Operating Model

Agent runtimes execute. UAIX records the reviewed communication, memory, trust, evidence, and handoff boundary.

Use Agent Communication Operating Model when a human operator, coding agent, AI 代理, or runtime implementer needs portable identity, intent, context, acknowledgement, status, blocker, memory proposal, validation evidence, correction, final report, or handoff records. The matching machine-readable assets are published through 模式, 注册表, 示例, and the 验证器.

  • UAIX does not provide automatic sync, hosted messaging, runtime orchestration, official adapters, repository write execution, certification authority, or hosted import mechanisms.
  • Carcinus.org is a separate runtime/orchestrator example that may consume UAIX records. UAIX.org does not implement Carcinus runtime behavior and does not execute Carcinus workflows.
  • LocalEndPoint and other runtimes may consume the published UAIX records as external consumers; UAIX.org does not implement their project-specific runtime features.
  • Durable memory proposals stay separate from task execution records. Do not promote temporary endpoint statuses, session tokens, write tokens, beta platform instructions, local error traces, private keys, or API credentials.