Registro de cambios

2026-06-06 | Principles governance and traceability update#

Change type: Additive governance, principles-to-policy, AI 记忆, Memory Firewall, Evaluation Packet, 一致性包, 路线图, and machine-discovery update.

• Affected records: Principles Charter, Principles Role Guidance, Governance, 政策与安全, 一致性包, AI 记忆数据包向导, 路线图, route manifests, well-known manifests, sitemap, llms files, and local .uai memory.
• Migration note: principle-bearing changes now classify affected principles as current, governance-review, planned, or research-track before they can widen public trust, AI 记忆, handoff, capability, or support-claim language. 信任-significant changes should complete the principles impact-assessment template or record a specific not-applicable rationale.
• Support boundary: this principles layer is governance and release-review evidence. It is not certification, endorsement, legal recognition, runtime control, SDK or CLI support, hosted import validation, automatic sync, security-operations coverage, consent-center operation, policy-office authority, or proof of UAI-1 conformance by itself.

2026-06-05 | UAI-1 / UAI V1.0 closed required file set v3.67.0#

Change type: Pre-launch AI 记忆数据包向导, 项目交接, roadmap, public copy, and validation guidance update for closed required file sets.

• Affected records: AI 记忆数据包向导, AI 记忆, 项目交接, UAI-1, API 参考, and 路线图.
• Required file set: current wizard and .uai handoff packages classify package files as universal required, profile-required, content-triggered required, or out of scope. 通用 required files are .uai/memory-maintenance.uai, .uai/identity.uai, .uai/world-context.uai, and .uai/short-term-memory.uai. Operator-only protected artifacts are metadata-only unless exact human authorization exists. Project/developer packages and code-bearing assistant packages also require .uai/coding-standards.uai.
• Support boundary: launch-baseline package files are local, reviewable files. They are not hosted enforcement, runtime control, automatic writes, automatic sync, SDK, CLI, certification, endorsement, UAI-1 conformance evidence, or proof of safety.

2026-06-04 | UAIX Agent Compatibility and GET-Action Standardization v3.59.0#

Change type: Additive agent-compatibility specification, GET-Action standardization, low-capability quick start, no-op protocol, capability matrix, validator rules, examples, discovery, and package release.

• Affected records: Agent Compatibility, Capability-Adaptive Interoperability, GET-Action 模式, GET-Action Security Boundaries, No-Op Protocol, Capability Surface Matrix, 验证器 Rules, and Implementation 示例.
• Support boundary: agent runtimes execute. UAIX records reviewed communication, memory, trust, evidence, fallback, and handoff boundaries.

2026-06-03 | UAIX Chatbot Access and GET-Action 模式 v3.58.0#

Change type: Additive chatbot-access, Minimal Access Tier, GET-Action fallback, progressive-agent, discovery-manifest, documentation, and package release.

• Affected records: Chatbot Access, Minimal Access Tier, GET-Action 模式, Agent Capability Ladder, Limited Browser Support, Progressive Agent Access, GET-Action Security, and Advanced Agent Support.
• Support boundary: Minimal Access is read-only public GET; GET-Action remains a bounded fallback and not a replacement for POST JSON endpoints.

2026-06-02 | UAIX Standards 信封 and Capability Ladder v3.57.0#

Change type: Additive standards route family, publication-envelope mapping, schema/example expansion, discovery-manifest hardening, and release-package update.

• Affected records: Standards, UAI-1 Standards Overview, SPEC-01 Canonical 信封, SPEC-02 项目交接, SPEC-03 AGENTS.md, SPEC-04 文件交接, Capability Ladder, Low-Capability Agents, and Advanced Agents.
• Support boundary: UAIX records reviewed communication, memory, trust, evidence, and handoff boundaries while runtimes execute elsewhere.

2026-05-31 | Capability-Adaptive Web Interaction and Agent Communication#

Change type: Additive capability ladder, profile, validator, guide, wizard, adoption-kit, conformance-pack, and package updates.

• Affected records: Capability-Adaptive Web Interaction, Limited Browser Support, Advanced Agent Support, Browser and Agent Parity, UAIX vs MCP vs Webhooks, Agent Consent Boundaries, and Agent Communication Operating Model.
• Support boundary: UAIX does not provide automatic sync, hosted messaging, runtime orchestration, official adapters, repository write execution, certification authority, or hosted import mechanisms.

How implementers should use this log#

Read the changelog as the public record of what changed, whether the change is additive, corrective, policy-oriented, or breaking, and what migration work a downstream implementation should perform before release.

发布版本 history#

This log records public changes across the UAIX site and standards record so implementers can trace revisions, compatibility expectations, and governance signals without relying on informal notes.

2026-05-08 | Launch-grade public-record alignment pass#

Change type: Additive route, discovery, documentation, validator-workflow, and handoff-source alignment across the public record.

• Affected records: Home, 规范ification, UAI-1, 模式, 示例, Tools, 验证器, Implementations, Governance, discovery manifests, and launch-surface audit scripts.
• Migration note: long-form public aliases for WordPress 发布轨道, .NET 桥接轨道, AGENTS.md UAI linking, and 代理文件交接 now redirect to the canonical records while remaining discoverable for agents and reviewers. The current proof path still runs through schemas, registry, examples, validator evidence, 实施轨道, conformance pack, and the release trail.
• Support-claim effect: this pass improves findability and evidence alignment without creating SDK, CLI, certification, official adapter, hosted-import, automatic-write, automatic-sync, endorsement, or broader runtime-support claims.
• Reference paths: Home, UAI-1, Tools, Implementations, Governance, and 引用 and Contributors.

2026-05-01 | LLM Wiki report-preservation hardening#

Change type: Additive package and archive-consolidation guidance.

• Affected records: 将 UAI 包与 LLM Wiki 配合使用, AI 记忆数据包向导, the generated .uai/long-term-memory.uai, the experimental 项目交接 plugin package scaffolding, root handoff docs, local .uai files, and AIWikis outcome-routing memory.
• Migration note: when a package or source-site archive is consolidated into an LLM Wiki or AIWikis-style cold memory, preserve original processed reports with source paths, destination paths, file counts, checksums, dispositions, and discoverable summary/index updates. Summaries, staged drafts, and hot-context snapshots are not enough if future work may need original wording.
• Support-claim effect: this improves preservation guidance only. It does not create automatic LLM Wiki sync, hosted import validation, repository writes, SDKs, CLIs, certification, endorsement, official adapters, or validator-backed conformance evidence.
• Reference paths: 将 UAI 包与 LLM Wiki 配合使用, AI 记忆数据包向导, 代理文件交接, and 变更日志.

2026-05-01 | 项目交接 context-budget guide#

Change type: Additive guide and discovery-surface hardening.

• Affected records: 项目交接 上下文预算, 项目交接, AI 记忆, 将 UAI 包与 LLM Wiki 配合使用, root handoff docs, local .uai files, well-known manifests, and focused memory regression coverage.
• Migration note: keep AGENTS.md, readme.human, and typed .uai files as hot context containing current truth, constraints, decisions, active routes, and targeted checks. Move bulky research, old reports, chat transcripts, roadmap history, and pre-slim snapshots into LLM Wiki or AIWikis-style cold memory with source path, final path, checksum, actor, time, summary, and disposition.
• Support-claim effect: this is context-budget guidance and dogfood practice. It does not create automatic LLM Wiki sync, hosted import validation, repository writes, SDKs, CLIs, certification, endorsement, official adapters, or validator-backed conformance evidence.
• Reference paths: 上下文预算 guide, 项目交接, AI 记忆, and 变更日志.

2026-05-01 | 项目交接 coding-agent compatibility guide#

Change type: Additive guide, pointer, and discovery-surface clarification.

• Affected records: 项目交接, OpenAI/Codex guide, Coding Agents guide, AI 记忆, root handoff docs, local .uai files, well-known manifests, and focused handoff regression coverage.
• Migration note: coding-agent-specific files should stay thin pointers back to AGENTS.md, readme.human, and .uai records. Use one repo-local bundle across Codex, Claude Code, Cursor, GitHub Copilot, Gemini Code Assist, local agents, vendors, and humans instead of duplicating project truth per tool.
• Support-claim effect: this is compatibility guidance and repo-local pointer structure. It does not create official vendor adapters, SDKs, CLIs, hosted import validators, automatic repository writers, certification, conformance evidence, or endorsement claims.
• Reference paths: Coding Agents guide, 项目交接, 路线图, and 变更日志.

2026-05-01 | 项目交接 OpenAI-compatible memory positioning#

Change type: Additive positioning, guide, and discovery-surface clarification.

• Affected records: 项目交接, Using UAIX 项目交接 with OpenAI Agents and Codex, AI 记忆, roadmap state, root handoff docs, local .uai files, well-known manifests, and focused AI 记忆 regression coverage.
• Migration note: 项目交接 is now framed as portable project memory, governance, and review context for any agent runtime. The public shorthand is: OpenAI runs the agents; 项目交接 preserves the project memory.
• Support-claim effect: this is compatibility guidance and repo-local context structure. It does not create an OpenAI replacement, agent runtime, scheduler, tool-calling framework, official OpenAI adapter, hosted import validator, automatic repository writer, trace exporter, SDK, CLI, certification, or endorsement program.
• Reference paths: 项目交接, OpenAI/Codex guide, 路线图, and 变更日志.

2026-05-01 | AI 记忆数据包向导 staged review flow#

Change type: Additive wizard UX and review-boundary hardening.

• Affected records: AI 记忆数据包向导, AI 记忆, route copy, root handoff docs, local .uai files, and focused AI 记忆 regression coverage.
• Migration note: the wizard now moves through Preset, Basics, Operations, Protocols, Receiver, and Review and Export steps. Required fields validate before forward movement, local browser drafts can be restored, sensitive or high-risk selections auto-enable review gates, LLM Wiki 计划ning required for LLM Wiki configuration stays inside the receiver step, and export actions live on the review step beside lazy generated-artifact previews.
• Support-claim effect: this remains local package planning over canonical starter bundles. It does not create hosted import validation, automatic repository writes, automatic LLM Wiki sync, provider execution tests, SDK, CLI, certification, endorsement, WordPress admin installation, or automatic site writes.
• Reference paths: AI 记忆数据包向导, AI 记忆, 路线图, and 变更日志.

2026-04-30 | AI 记忆数据包向导 protocol expansion#

Change type: Additive generated-memory operating protocol expansion.

• Affected records: AI 记忆数据包向导, homepage package-building CTA, AI 记忆, roadmap state, machine-readable roadmap state, root handoff docs, local .uai files, and focused AI 记忆 regression coverage.
• Migration note: the wizard now asks for memory update policy, source authority policy, change risk level, conflict resolution policy, evidence ledger path, memory update targets, and rollback strategy. These choices populate UAI_MEMORY_SYSTEM_PROFILE.md, UAI_MEMORY_RECEIVER_BRIEF.md, UAI_MEMORY_STARTUP_PACKET.md, the manifest overlay, and the .uai/long-term-memory.uai required for long-memory configuration so the generated package includes operational definitions instead of only empty selections.
• Support-claim effect: these remain local generated planning files beside canonical starter bundles. They do not create hosted import validation, automatic repository writes, automatic LLM Wiki writes or sync, SDK, CLI, certification, endorsement, or UAI-1 conformance evidence.
• Reference paths: AI 记忆数据包向导, AI 记忆, 路线图, and 变更日志.

2026-04-30 | AI 记忆数据包向导 system profile release#

Change type: Additive operating-profile and package-output hardening.

• Affected records: AI 记忆数据包向导, AI 记忆, homepage package-building CTA, roadmap state, root handoff docs, local .uai files, machine-readable roadmap state, and focused AI 记忆 regression coverage.
• Migration note: the wizard now generates UAI_MEMORY_SYSTEM_PROFILE.md beside the startup packet, receiver brief, overlay, LLM Wiki 计划 required for LLM Wiki configuration, copied file deck, and canonical starter ZIP. The profile records single-user versus multi-user collaboration, UAI-only versus UAI plus Wiki memory architecture, unit and integration test posture, test timing, deployment strategy, code review strategy, release gates, evidence expectations, and placeholders such as {PROJECT_ROOT}, {UNIT_TEST_COMMAND}, and {DEPLOY_COMMAND_OR_STEPS} that the receiving AI must fill from the actual system.
• Support-claim effect: this is a local generated operating file and test/deployment planning aid. It does not create hosted import validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, certification, endorsement, WordPress admin installation, or UAI-1 conformance evidence.
• Reference paths: AI 记忆数据包向导, AI 记忆, 路线图, and 变更日志.

2026-04-30 | AI 记忆数据包向导 receiver brief and startup packet release#

Change type: Additive package-startup and homepage CTA hardening.

• Affected records: AI 记忆数据包向导, AI 记忆, homepage package-building CTA, roadmap state, root handoff docs, local .uai files, and focused AI 记忆 regression coverage.
• Migration note: the wizard now generates UAI_MEMORY_RECEIVER_BRIEF.md and UAI_MEMORY_STARTUP_PACKET.md beside the package model, manifest overlay, copied file deck, .uai/long-term-memory.uai required for long-memory configuration, and canonical starter ZIP. Use the receiver brief as the first-read instruction, and use the startup packet as the one-file operator bundle for the next human, team, or AI before broad work starts.
• Support-claim effect: these are local generated instruction files that name read order, first-response expectations, first task, success evidence, boundaries, selected files, and targeted checks. They do not create hosted import validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, certification, endorsement, or UAI-1 conformance evidence.
• Reference paths: AI 记忆数据包向导, AI 记忆, 路线图, and 变更日志.

2026-04-30 | AI 记忆数据包向导 LLM Wiki 计划 hardening#

Change type: Additive package-planning and UX hardening.

• Affected records: AI 记忆数据包向导, AI 记忆, roadmap state, root handoff docs, local .uai files, and focused AI 记忆 regression coverage.
• Migration note: when a project uses an LLM Wiki, the wizard can now generate an .uai/long-term-memory.uai file with memory steward, source collection, archive target, transfer evidence log, promotion targets, source boundary, a memory routing matrix, required transfer evidence, and promotion gates. 生成时间 files stay visible in narrowed decks and the review panel now reports readiness items before export.
• Support-claim effect: this remains a local planning artifact beside the canonical starter ZIP and copied files. It does not create hosted import validation, automatic repository writes, automatic LLM Wiki writes, bidirectional sync, SDK, CLI, certification, endorsement, or UAI-1 conformance evidence.
• Reference paths: AI 记忆数据包向导, AI 记忆, 路线图, and 变更日志.

2026-04-29 | 代理文件交接 archive-to-LLM-Wiki history clarification#

Change type: Additive public handoff lifecycle clarification.

• Affected records: 代理文件交接, 项目交接, AI 记忆, root AGENTS.md, root readme.human, local .uai handoff files, helper navigation, and canonical reference docs.
• Migration note: active files still move through visible review and disposition before they are archived. When a human explicitly asks an LLM Wiki implementation such as AIWikis.org to consolidate already-dispositioned archive files, the pickup must record source path, final memory path, checksums, disposition, actor, time, and transfer evidence, then update the AIWikis history, log, index, or wiki graph before the source archive copy is removed.
• Support-claim effect: AIWikis archive memory is provenance and long-term system memory, not routine UAIX intake, public UAIX authority, certification, endorsement, or UAI-1 conformance evidence.
• Reference paths: 代理文件交接, 项目交接, AI 记忆, 路线图, and 变更日志.

2026-04-28 | 项目交接 package dogfood correction#

Change type: Package-scaffold and evidence-boundary correction from AIWikis.org dogfood.

• Affected records: UAIX Agents 协议, 项目交接, 代理文件交接, roadmap state, root handoff docs, and the UAIX-produced 项目交接 ZIP package.
• Migration note: generated handoff packages should include the active agent-file-handoff/Content, Improvement, and Archive folders plus a fuller loaded .uai set: context, stack, architecture, constraints, decisions, progress, operations, test plan, style, sources, prompts, file handoff, and active bucket review.
• Support-claim effect: this improves experimental dogfood packaging and validation. It still does not create official generator, hosted validator, SDK, CLI, certification, endorsement, or conformance support.
• Reference paths: UAIX Agents 协议, 项目交接, 代理文件交接, and 路线图.

2026-04-28 | AI 记忆起步包 release#

Change type: Additive public handoff, route, and download-surface expansion.

• Affected records: AI 记忆, 项目交接, 报告, 路线图, launch-surface audits, discovery manifests, and canonical workspace docs.
• Migration note: use AI 记忆 as the broad public phrase for durable AI project context, use 项目交接 as the transfer configuration, use the supported bundle chooser when the lifecycle or trust boundary differs, and use an LLM Wiki when deep internal documentation needs a larger searchable memory surface. The /AI_Memory entry path redirects to the canonical /en-us/ai-memory/ page as the intended non-canonical search entry alias.
• Support-claim effect: UAIX now publishes supported starter ZIPs generated from canonical templates, generated manifests, and the same resolved samples rendered on AI 记忆 and 项目交接. Hosted generators, upload validators, SDKs, CLIs, certification, and endorsement services remain outside current support.
• Reference paths: AI 记忆, 项目交接, LLM Wiki comparison report, 路线图, and 变更日志.

2026-04-27 | 代理文件交接 archive boundary release#

Change type: Additive handoff lifecycle clarification.

• Affected records: 代理文件交接, 项目交接, UAIX Agents 协议, root AGENTS.md, root readme.human, local .uai handoff files, intake scripts, and LlmWikis dogfood guidance.
• Migration note: active files belong in agent-file-handoff/Content/ or agent-file-handoff/Improvement/. After disposition, move the source file to agent-file-handoff/Archive/; routine AI intake should ignore archived files unless a human explicitly names one or moves it back into an active bucket.
• Support-claim effect: the archive is local source retention only. It is not public content, a discovery surface, certification evidence, or an automatic AI task queue. Folder-local README instructions are not part of the base pattern; durable instructions belong in AGENTS.md and .uai files.
• Reference paths: 代理文件交接, 项目交接, UAIX Agents 协议, 路线图, and 变更日志.

2026-04-27 | readme.human handoff briefing release#

Change type: Additive 项目交接 clarification and dogfood expansion.

• Affected records: 项目交接, UAIX Agents 协议, root readme.human, root AGENTS.md, local .uai handoff files, the 项目交接 WordPress prototype package, and LlmWikis dogfood guidance.
• Migration note: active projects should add a root readme.human beside AGENTS.md as a human-facing briefing from the AI perspective. Use it to tell people what the AI needs to know, what it will defend, and what humans should make explicit before broad work.
• Support-claim effect: readme.human is a briefing aid, not an authority layer. It does not override AGENTS.md, project constraints, system instructions, repository rules, or current human requests.
• Reference paths: 项目交接, UAIX Agents 协议, 路线图, and 变更日志.

2026-04-27 | 代理文件交接 active intake release#

Change type: Additive local handoff and dogfood tooling expansion.

• Affected records: 代理文件交接, 项目交接, UAIX Agents 协议, root AGENTS.md, local .uai handoff files, active bucket guidance, and the 项目交接 WordPress prototype package.
• Migration note: active projects should make an active-bucket scan and review gate part of AGENTS.md handoff load so files in Content/ and Improvement/ are noticed and processed even when the human prompt does not mention them. Do not require watchers, daemons, queue folders, manifests, cron loops, out-of-chat auto-pickup, or bucket-local README files. Inspect and disposition every non-placeholder file in Content/ or Improvement/ before unrelated broad edits, then move processed source files to Archive/.
• Support-claim effect: UAIX now dogfoods local file-active bucket reviewing into project-state artifacts, while hosted generators, upload validators, SDKs, CLIs, certification, and endorsement remain outside current support.
• Reference paths: 代理文件交接, 项目交接, UAIX Agents 协议, 路线图, and 变更日志.

2026-04-25 | Project handoff and AGENTS.md .uai audit hardening#

Change type: Additive developer-handoff and launch-QA clarification.

• Affected records: 项目交接, AGENTS.md .uai Linking 规范ification, 报告, Refining UAI Protocol for Agent Communication, 路线图, launch-surface audits, and canonical workspace docs.
• Migration note: use 项目交接 as the practical draft and first public navigation target for repository context; require the next AI to summarize loaded context, constraints, intended touchpoints, and checks before broad edits; treat Markdown context-profile files and JSON information-profile files as additive draft source formats with explicit loader and trust guardrails.
• Support-claim effect: public pages and launch audits now cover the AGENTS.md/report surfaces, while .uai generators, starter template libraries, upload validators, SDKs, CLIs, and certification remain planned until public evidence exists.
• Reference paths: 项目交接, AGENTS.md .uai Linking 规范ification, 精化报告, 路线图, and 变更日志.

2026-04-24 | 上线就绪治理闸门发布#

Change type: 面向公开治理与证据表面的增量上线加固。

• Affected records: 上线就绪, Governance, 政策与安全, Accessibility, API 参考, 一致性包, 验证器, route inventories, and zh-CN release copy.
• Migration note: 在大范围公开推进前，使用“上线就绪”作为响应检查、打包证据、可访问性 QA、语言版本 QA、发布轨迹对齐和支持声明边界的公开上线闸门。
• Governance effect: 上线加固现在拥有命名的公开页面，把现有政策、一致性、验证、发现和发布说明证据连接起来，同时不暗示认证或生产安全计划。
• Reference paths: 上线就绪, 政策与安全, 一致性包, 验证器, 变更日志, and News.

2026-04-24 | 一致性 fixture pack release#

Change type: Additive validator-regression and release-evidence expansion.

• Affected records: 接入套件, 一致性包, API 参考, 路线图, discovery, production response checks, and the public UAIX REST surface.
• Migration note: release packets can now carry reusable positive keyed/minified-keyed/keyless validator cases, canonical-hash equivalence metadata, and negative checks for missing profile, missing required fields, undeclared fields, invalid traceparent, DID/VC trust evidence, keyless shape, keyless overflow, and unsupported alias.
• Support-claim effect: current validator behavior is easier to regression-test before launch, while alias maps and binary envelopes remain future work until their own fixtures and route behavior exist.
• Reference paths: 接入套件, 一致性包, 路线图, 变更日志, and News.

2026-04-24 | Implementation evidence checklist release#

Change type: Additive conformance-evidence and developer-handoff expansion.

• Affected records: 接入套件, 一致性包, API 参考, 路线图, catalog discovery, and the public UAIX REST surface.
• Migration note: release packets should now carry the implementation evidence checklist beside validator output, fixture references, changelog or release-note links, compatibility notes, and an owner or contact record before support language widens.
• Support-claim effect: the adoption kit and conformance pack now publish a reviewable checklist for moving from first proof to launch evidence without presenting that evidence as certification, badge, or endorsement.
• Reference paths: 接入套件, 一致性包, 路线图, 变更日志, and News.

2026-04-24 | 验证器规范化模式发布#

Change type: 面向一致性和紧凑传输的增量加固。

• Affected records: 验证器, API 参考, 一致性包, 标准定位, 路线图, examples, field registry, OpenAPI, and the public UAIX REST surface.
• Migration note: validate 路由现在接受 keyed-json, minified-keyed-json, and keyless-json; 无键数据包会先通过公共字段注册表扩展，再运行模式和策略检查。
• Support-claim effect: 紧凑无键传输现在已有验证器背书的扩展证据，而别名映射和二进制信封在公开夹具和路由行为存在之前仍保持为已计划或研究轨道。
• Reference paths: 验证器, API 参考, 一致性包, 路线图, and 变更日志.

2026-04-24 | 联系 review and standards-fit page release#

Change type: Additive public-operating and specification-boundary expansion.

• Affected records: 联系与评审, 标准定位, 引用 and Contributors, Governance, 路线图, launch audits, catalog discovery, and zh-CN localized page bodies.
• Migration note: use the dedicated contact-and-review path for contributor packets and change proposals, and use the standards-fit path when explaining A2A, MCP, OpenAPI, JSON 模式, DID/VC, Trace Context, compact transfer, and normalization boundaries.
• Support-claim effect: public operating and standards-fit guidance is now a page-level launch surface instead of only a roadmap item, while issue trackers, broad governance rosters, alias maps, binary envelopes, SDKs, and certification remain future work until evidence is published.
• Reference paths: 联系与评审, 标准定位, 路线图, 变更日志, and News.

2026-04-24 | Public roadmap and interoperability route release#

Change type: Additive public-operating-layer and machine-readable guidance expansion.

• Affected records: 路线图, API 参考, 一致性包, the public UAIX REST surface, homepage navigation, and canonical roadmap guidance.
• Migration note: use the published roadmap page and /wp-json/uaix/v1/roadmap as the current forward-plan handoff instead of reconstructing priorities from older research notes.
• Support-claim effect: future-facing interoperability, compact-transfer, normalization, conformance, and developer-handoff ideas now have a public boundary that separates current support, next work, planned work, and research-track ideas.
• Reference paths: 路线图, API 参考, 一致性包, 变更日志, and News.

2026-04-23 | UAI-1 specification fit-and-proof update#

Change type: Additive specification-page reframe for launch readers and implementers.

• Affected records: UAI-1, 规范ification, 模式, 示例, 验证器, API 参考, 接入套件, and 一致性包.
• Migration note: the UAI-1 page now leads with fit, boundary, proof path, operating surfaces, and launch-support links so readers can move from specification text into current public evidence more quickly. Read the page as the main contract and launch decision surface rather than as a prose-only reference.
• Support-claim effect: implementers can now move from the written contract into schemas, examples, validation, route guidance, and release evidence with less reconstruction work, which reduces the risk of overstating support from partial reading.
• Reference paths: UAI-1, 模式, 示例, 验证器, API 参考, 接入套件, 一致性包, and the News archive.

2026-04-23 | Adoption kit route and page release#

Change type: Additive onboarding expansion across the public launch surface.

• Affected records: Get Started, Tools, 接入套件, API 参考, 一致性包, Implementations, and the UAIX core REST surface.
• Migration note: use the published adoption kit page and /wp-json/uaix/v1/adoption-kit as the default first-proof bundle instead of assembling the starter packet manually from scattered routes.
• Support-claim effect: onboarding now has a concrete downloadable handoff bundle before widening support claims.
• Reference paths: 接入套件, API 参考, 验证器, 一致性包, Implementations, and News.

2026-04-23 | Public security-header and trust-hardening release#

Change type: Additive launch hardening across the public response and trust surface.

• Affected records: 政策与安全, API 参考, the public UAIX REST surface, and the UAIX SEO Sweep response layer.
• Migration note: public WordPress-rendered responses now ship with a narrow security-header baseline for framing, referrer handling, browser capability policy, and MIME-type handling. Treat HTTPS redirect, HSTS, and static-file parity as deployment follow-through rather than as already-complete app behavior.
• Support-claim effect: the launch trust posture now has observable response hardening behind it, making it easier to verify the public machine-facing surface without overstating a broader security program.
• Reference paths: 政策与安全, API 参考, 验证器, 一致性包, 变更日志, and News.

2026-04-23 | Dedicated governance policy-page release#

Change type: Additive governance and trust-surface expansion across the launch record.

• Affected records: Governance, 政策与安全, Privacy and Data, Accessibility, Analytics, 引用 and Contributors, About, Press, and related launch guidance.
• Migration note: treat privacy, accessibility, and analytics as published governance child pages rather than as future-tense posture. Use the policy hub plus the dedicated pages when a release changes trust-significant behavior.
• Governance effect: UAIX now publishes a clearer trust-policy section that can be cited directly during launch review without implying a broader institutional program than the site actually maintains.
• Reference paths: 政策与安全, Privacy and Data, Accessibility, Analytics, 变更日志, and News.

2026-04-23 | First-proof run and multi-language starter-call release#

Change type: Additive onboarding expansion across the public developer path.

• Affected records: Get Started, 示例, Tools, 验证器, API 参考, and the release trail.
• Migration note: the launch surface now publishes a first-proof runbook plus copyable curl, PowerShell, Python, and TypeScript starter requests on the public adoption pages. Use those published snippets and the validator-backed packet as the default onboarding path instead of reverse-engineering the REST surface or inventing a private SDK.
• Support-claim effect: onboarding now points more directly to the current public contract and makes it easier to produce a reviewable first packet without overstating runtime support.
• Reference paths: Get Started, 示例, 验证器, API 参考, 一致性包, and Implementations.

2026-04-22 | Operating-layer, ownership, and trust-posture clarification#

Change type: Additive public operating-layer clarification across the launch surface.

• Affected records: Governance, 政策与安全, 引用 and Contributors, the shared UAIX Core visual surfaces, and related release-trail language.
• Migration note: use the published operating-layer matrix and handoff packet to explain what is published now, how to verify it, and what is still future work. Keep repository, contributor, ownership, and policy claims scoped to the public record until broader channels are formally published.
• Governance effect: UAIX now makes ownership state, contributor intake, citation and discovery handoff, and trust-significant release posture easier to audit without implying a broader institution than the site currently publishes.
• Reference paths: Governance, 政策与安全, 引用 and Contributors, Implementations, API 参考, 一致性包, and News.

2026-04-22 | API reference, conformance pack, and policy surface release#

Change type: Additive launch-support expansion across the public record.

• Affected records: Get Started, Tools, API 参考, 一致性包, Governance, 政策与安全, 验证器, and the UAIX core REST surface.
• Migration note: machine-facing onboarding now includes a route-level API handbook, a published OpenAPI export, and a reusable conformance packet. Launch-stage trust posture now has a dedicated public page instead of remaining scattered across governance notes.
• Support-claim effect: teams can now point to route documentation, downloadable evidence packets, and a dedicated trust-posture record before widening public support claims.
• Reference paths: API 参考, 一致性包, 政策与安全, 验证器, Implementations, and News.

2026-04-22 | Developer onramp and protocol-fit clarification#

Change type: Additive public-entry and onboarding clarification across the site.

• Affected records: Home, Get Started, UAI-1, Governance, 引用 and Contributors, and Press.
• Migration note: describe UAI-1 as the public envelope, trust, and evidence layer that can sit above MCP, A2A, and runtime-specific tooling, and use the published pages, machine-readable routes, examples, and validator as the current developer kit.
• Governance effect: UAIX now states more directly what is published today, what is still future work, and how to explain the current single-publisher public record without overstating maturity.
• Reference paths: Home, Get Started, UAI-1, Governance, 引用 and Contributors, Press, and News.

2026-04-22 | 传输, trust, error, and conformance surface release#

Change type: Additive operating-surface release across the public UAI-1 record.

• Affected records: 规范ification, UAI-1, Tools, 验证器, the UAIX core REST surface, capability and conformance examples, and related metadata.
• Migration note: the public record now publishes transport bindings, trust channels, an error registry, and conformance levels. Treat these records as part of the live interoperability and support-claim surface instead of as commentary that can be skipped.
• Support-claim effect: teams can now describe transport fit, trust posture, typed failures, and achieved conformance level with more precision when they publish release evidence.
• Reference paths: UAI-1, Tools, 验证器, 示例, Implementations, and the News archive.

2026-04-22 | Protocol contract, field registry, and async workflow release#

Change type: Additive and corrective protocol expansion across the public record and machine-readable artifacts.

• Affected records: 规范ification, UAI-1, 模式, 注册表, 示例, Tools, 验证器, the UAIX core REST surface, and related metadata.
• Migration note: the public contract now publishes a richer shared envelope, a field registry for keyed-to-keyless order, typed problem-style errors, validator-backed policy checks, and a dedicated uai.task.status.v1 profile for async workflow visibility. Treat these records as the new current baseline when evaluating compatibility.
• Governance effect: UAIX now states more clearly that UAI-1 is the public exchange and release-record layer that can sit beside orchestration, tool, and trust systems without trying to replace every adjacent protocol.
• Reference paths: UAI-1, 模式, 注册表, 示例, 验证器, Implementations, and the News archive.

2026-04-22 | Endpoint and packaged artifact guidance update#

Change type: Additive implementation-surface clarification across the site.

• Affected records: About, 引用 and Contributors, Tools, 验证器, Implementations, WordPress 发布轨道, and .NET 桥接轨道.
• Migration note: use the named route family and packaged artifact list when explaining what UAIX currently publishes, and do not infer a standalone SDK, package registry, or broader runtime catalog unless it is explicitly added to the public record.
• Governance effect: UAIX now makes the current machine-facing endpoints and packaged WordPress artifact family easier to cite, which narrows the credibility gap between the written standards record and the currently shipped implementation surface.
• Reference paths: 引用 and Contributors, Tools, 验证器, Implementations, and News.

2026-04-21 | Homepage orientation and trust-surface update#

Change type: Additive public-entry-surface clarification across the site.

• Affected records: Home, the front-page launch surface, and related orientation language.
• Migration note: use the homepage as the short public summary of the current trust posture, published support boundary, and first-read path into the deeper record rather than treating it as a generic brochure lead-in.
• Governance effect: UAIX now makes the front door say more directly what the deeper record already supports, which reduces onboarding ambiguity without widening the published support boundary.
• Reference paths: Home, Get Started, Implementations, Governance, and News.

2026-04-21 | Policy and trust-surface posture update#

Change type: Additive governance and trust-surface clarification across the site.

• Affected records: Governance, 引用 and Contributors, About, Press, and related release-note language.
• Migration note: read privacy, accessibility, and analytics posture as governance-led and release-trail-led on the current launch surface, and do not infer standalone policy programs or broader institutional disclosures that have not yet been published.
• Governance effect: UAIX now states more concretely how policy-significant changes should be described, reviewed, and attached to the public release trail before they are treated as current truth.
• Reference paths: Governance, 引用 and Contributors, About, Press, and News.

2026-04-21 | 发布版本 readiness and support-claim guidance update#

Change type: Additive adoption and trust-surface clarification across the site.

• Affected records: Get Started, Implementations, WordPress 发布轨道, .NET 桥接轨道, 验证器, and related release-note language.
• Migration note: distinguish local validation success, release-ready evidence packets, and current public support claims, and keep support language scoped to the published implementation-track record.
• Governance effect: UAIX now states more directly what a passing validator result proves, what additional evidence makes a release reviewable, and when a public support claim becomes justified on the site.
• Reference paths: Get Started, Implementations, WordPress 发布轨道, .NET 桥接轨道, 验证器, and News.

2026-04-21 | Technical record map update#

Change type: Additive technical-orientation clarification across the site.

• Affected records: 规范ification, UAI-1, 模式, 注册表, 示例, and related release-note language.
• Migration note: use the published profile-family map and compatibility cues when moving from normative reading into schemas, registry resolution, fixtures, and validator-backed evidence, and keep those records aligned rather than treating them as separate references.
• Governance effect: UAIX now makes the current technical stack easier to reconstruct from the public record, which reduces adoption ambiguity without changing validator behavior, routes, or profile support boundaries.
• Reference paths: 规范ification, UAI-1, 模式, 注册表, 示例, and News.

2026-04-21 | Proof packet and roadmap signal update#

Change type: Additive onboarding and participation-surface clarification across the site.

• Affected records: Get Started, Tools, Governance, 引用 and Contributors, and related release-note language.
• Migration note: use the first public proof run and roadmap-signal guidance when assembling a reusable adoption packet or interpreting current priorities, and treat the published governance and release records as the roadmap until a standalone roadmap or contributor surface is explicitly published.
• Governance effect: UAIX now makes the shortest path from first validation to public participation easier to reconstruct from the published record without implying issue trackers, contact channels, or ecosystem programs that are not yet public.
• Reference paths: Get Started, Tools, Governance, 引用 and Contributors, and News.

2026-04-21 | Evaluation and maturity guidance update#

Change type: Additive public-orientation clarification across the site.

• Affected records: Get Started, About, Press, and related release-note language.
• Migration note: use the published evaluation checklist and maturity framing when assessing current readiness or describing UAIX to third parties, and treat unpublished contact, governance, policy, and runtime surfaces as future work unless they are explicitly published.
• Governance effect: UAIX now distinguishes current public infrastructure from planned growth infrastructure more directly, which makes current readiness easier to cite without overstating institutional completeness.
• Reference paths: Get Started, About, Press, and News.

2026-04-21 | Operating-layer and ownership clarity update#

Change type: Additive public-operating-layer clarification across the site.

• Affected records: Governance, 引用 and Contributors, Implementations, and related release-note language.
• Migration note: treat the current public operating layer as a combination of named attribution, aligned canonical records, validator or implementation evidence, and the release trail rather than as a broader published contact or governance program.
• Governance effect: UAIX now states more concretely where current ownership is published, how release decisions become public truth, and what future 实施轨道 must publish before they should be treated as supported.
• Reference paths: Governance, 引用 and Contributors, Implementations, and News.

2026-04-21 | Program model and adoption-kit assembly clarification#

Change type: Additive public-operating-model clarification across the site.

• Affected records: About, Get Started, Implementations, News, and related release-note language.
• Migration note: treat UAIX’s current public work as a record-family and implementation-track surface, not as an events or membership program, and assemble the current adoption kit from the published record until a standalone download is explicitly published.
• Governance effect: UAIX now states more directly how readers should understand the current public operating layer and where adoption packaging already exists today.
• Reference paths: About, Get Started, Implementations, News, and 引用 and Contributors.

2026-04-21 | Implementation scope and release-archive clarification#

Change type: Additive onboarding and release-posture clarification across the site.

• Affected records: Get Started, Implementations, News, and related release-note language.
• Migration note: treat the WordPress 发布轨道 and .NET 桥接轨道 as the only current public 实施轨道, use the portable record when evaluating other environments, and read the news archive as a release-note-led public timeline rather than a broader community channel.
• Governance effect: UAIX now states more directly where current public implementation support stops and where future ecosystem work would need new published records before it counts as public support.
• Reference paths: Implementations, News, 引用 and Contributors, and Governance.

2026-04-21 | 一致性包et and regression guidance clarification#

Change type: Additive conformance-evidence clarification across the site.

• Affected records: Implementations, Tools, 验证器, Governance, and related release-note language.
• Migration note: keep exported validator results, profile and schema references, fixture baselines, and release links together as a reusable public conformance packet, and do not present that packet as a formal certification badge or endorsement.
• Governance effect: UAIX now states more directly that repeatable conformance evidence and regression-ready fixtures are part of the current trust surface even though a broader formal assurance program remains future work.
• Reference paths: Implementations, Tools, 验证器, Governance, and News.

2026-04-21 | Use-case and positioning guidance clarification#

Change type: Additive public orientation and outward-facing language clarification across the site.

• Affected records: About, 引用 and Contributors, Press, and related release-note language.
• Migration note: use the published practical use cases and positioning guardrails when describing UAIX to implementers, researchers, press, and evaluators, and do not imply unpublished partner, contact, or governance structures.
• Governance effect: UAIX now makes the public use-case map and outward-facing limits easier to cite without changing normative behavior or route structure.
• Reference paths: About, 引用 and Contributors, Press, and News.

2026-04-21 | Role paths and public policy posture clarification#

Change type: Additive public orientation and governance clarification across the site.

• Affected records: Get Started, Governance, 引用 and Contributors, and related release-note language.
• Migration note: use the role-based reading paths when onboarding implementers, tool builders, reviewers, and public readers, and treat privacy, accessibility, and analytics pages as planned governance surfaces until they are explicitly published.
• Governance effect: UAIX now states more directly that participation is documentation-led and that policy posture should travel through the same public release trail as the rest of the trust surface.
• Reference paths: Governance, 引用 and Contributors, News, and Implementations.

2026-04-21 | Adoption packet and sitemap surface clarification#

Change type: Additive onboarding and discovery clarification across the site.

• Affected records: Implementations, Tools, the root and locale sitemap surfaces, and related launch-audit coverage.
• Migration note: keep the first-release packet tied to UAI-1, schemas, registry entries, examples, validator evidence, discovery manifests, and sitemap routes, and keep both root and locale-prefixed sitemap surfaces live in release QA.
• 发现 effect: UAIX now states more directly that /sitemap.xml and /sitemap.html are the durable root discovery surfaces while locale-prefixed sitemap routes should continue to resolve the same public inventory for localized readers and tooling.
• Reference paths: Implementations, Tools, 引用 and Contributors, and News.

2026-04-21 | Governance, contributor, and validator workflow clarification#

Change type: Additive public operating-layer clarification across the site.

• Affected records: Governance, 引用 and Contributors, 验证器, the machine-readable discovery guidance, and related release-trail language.
• Migration note: use the 验证器 page for the human-facing workflow, treat the validate REST 路由 as a machine-facing JSON POST endpoint, and use Governance plus 引用 and Contributors as the current public handoff path for contributor and citation context.
• Governance effect: UAIX now states more explicitly that trust infrastructure, public handoff paths, and visible review posture are part of the launch-surface operating layer.
• Reference paths: Governance, 引用 and Contributors, 验证器, Implementations, and News.

2026-04-20 | Terminology and implementation-track alignment#

Change type: Corrective public terminology and naming alignment across the site.

• Affected records: homepage copy, Get Started, About, 引用 and Contributors, Implementations, track labels, Press language, and related public release notes.
• Migration note: cite UAIX as the website and publication venue, UAI as the standard family, UAI-1 as the current release, and the WordPress 发布轨道 and .NET 桥接轨道 as the current public implementation-track names.
• Governance effect: the public wording now tracks the canonical terminology model more closely, reducing ambiguity without changing routes or validator behavior.
• Reference paths: About, 引用 and Contributors, Implementations, Press, and News.

2026-04-20 | Authority, validator, discovery, and safety rollout#

Change type: Additive standards-positioning update across the public site and runtime.

• Affected records: homepage, About, 规范ification, UAI-1, 模式, 示例, Tools, 验证器, Governance, Press metadata, the public news archive, and the machine-readable discovery surface.
• Migration note: implementers should align exchanges with published profile declarations, schema checks, provenance fields, integrity metadata, downloadable validation records, and the current discovery manifest before deployment.
• Governance effect: UAIX now states more directly that authority is earned through public review, validator tooling, machine-readable discovery, and auditable implementation evidence.
• Reference paths: About, 规范ification, UAI-1, 验证器, Governance, and News.

2026-04-19 | Public standards site launch#

Change type: Initial public publication release.

• Affected records: primary UAIX route structure, specification pages, governance pages, press resources, implementation packaging, and the public news archive.
• Migration note: use clean locale-prefixed public paths rather than query-string routes when linking or citing public UAIX material.
• Reference paths: Home, UAI-1, WordPress 发布轨道, Press, and News.

How this log pairs with other public pages#

• Use News when a changelog entry also needs a public-readable summary.
• Use Implementations when a change affects packaging, runtime evidence, or deployment posture.
• Use 引用 and Contributors when citation, discovery, and attribution links should travel with the release record.
• Use Press when the change also needs approved public language.

What every future entry should capture#

• 发布版本 date and affected record family.
• Whether the change is additive, corrective, policy-oriented, or breaking.
• Migration notes for implementations, validators, discovery files, and public references.
• Links back to the canonical documents that were updated.