Published UAIX reports
These dated reports preserve source Markdown research and proposal material as permanent public HTML pages inside the UAIX site shell. The report bodies are converted from the source files, while the page header, footer, navigation, outline, date, and source metadata are supplied by the UAIX publication theme.
Reading boundary: reports explain source proposals and rationale. They do not widen current support claims on their own; check AI 记忆, 项目交接, 路线图, 变更日志, and released evidence before repeating tooling, certification, generator, SDK, CLI, or endorsement language.
- AI 记忆Public framing for durable AI project memory, starter samples, and the LLM Wiki boundary.
- 项目交接Practical public starting point for creating AGENTS.md, .uai/readme.human, and .uai repository-context bundles.
- Relationship Audit of AIWikis, LLMWikis, and UAIXPublished April 29, 2026 from
docs/Relationship Audit of AIWikis LLMWikis and UAIX.md. - LLM Wiki vs. UAIX 项目交接Published April 26, 2026 from
docs/LLM Wiki vs. UAIX 项目交接 By Gamini.md. - LLM Wiki and UAIX 项目交接Published April 26, 2026 from
docs/LLM Wiki and UAIX 项目交接 By ChatGPT.md. - 规范ification for Linking .uai Files in AGENTS.mdPublished April 25, 2026 from
docs/规范ification for Linking uai Files in AGENTS by ChatGPT.md. - Refining UAI Protocol for Agent CommunicationPublished April 25, 2026 from
docs/Refining UAI Protocol for Agent Communication By Gemini.md.
How to use this report index
Start with AI 记忆 when you want the broad public vocabulary, then 项目交接 when you want a pattern teams can use now. Use the relationship audit when you need the AIWikis, LLMWikis, and UAIX authority split. Use the LLM Wiki comparison reports when you need the boundary between knowledge accumulation and repository handoff. Use the AGENTS.md .uai linking specification for exact link and record details, then use the refining report when you need deeper background on repository-native .uai structure, validation, interoperability, and security considerations.
证据 discipline for reports
Use reports as source leads, not as automatic current truth. A report recommendation becomes UAIX authority only after the useful conclusion is promoted into a current public page, machine-readable artifact, roadmap state, changelog entry, test, release package, or handoff record.
- Primary record first: prefer schemas, registry entries, examples, validator output, route behavior, release notes, and current docs over commentary.
- Claim-evidence split: label what is published today, what is planned, what is research-track, and what was rejected or blocked.
- Promotion trail: keep the source report archived, then cite the durable target that adopted the conclusion.
- Freshness check: re-check roadmap, changelog, and machine artifacts before repeating claims about adapters, SDKs, certification, hosted generation, sync, or conformance.