UAIX guides turn the public records into practical adoption paths. Use these pages when the specification is not enough by itself and a team needs a concrete setup, operating sequence, or integration model.
Recommended reading paths
- Agentic Harness Strategies And UAISeparate runtime harness strategy from the portable evidence, handoff, and conformance records UAI should preserve.
- Agentic systems and public evidenceUse Standards Fit to decide what the runtime owns, what MCP or A2A owns, and what UAIX should preserve as a portable public record.
- Using Project Handoff With OpenAI Agents And CodexUse OpenAI to run the agents while Project Handoff preserves the repo-local project memory.
- Using Project Handoff With Coding AgentsUse one local handoff bundle across Codex, Claude Code, Cursor, Copilot, and Gemini Code Assist.
- Project Handoff Context BudgetPrevent AGENTS.md, readme.human, and .uai files from becoming oversized archives.
- Project HandoffCreate the durable AGENTS.md, readme.human, and .uai bundle.
- AI MemoryStart with the broader portable memory framing and starter bundles.
- RoadmapCheck current versus planned tooling before making support claims.
Agentic system evidence path
For agentic systems, start by separating the live control plane from the durable record. Runtimes, workflow engines, tool protocols, guardrails, and observability systems run the work. UAIX records the part that another team, release, auditor, customer, or future agent needs to validate and carry forward.
| Layer | Usually owns it | What UAIX should preserve |
|---|---|---|
| Execution and control flow | Agent runtime or workflow harness | Reviewed request, outcome, task status, handoff summary, and release evidence. |
| Tools and resources | MCP, API clients, local integrations, or runtime adapters | Portable request/result evidence when the interaction crosses a team, vendor, audit, or release boundary. |
| Agent coordination | A2A or runtime-native handoff | Capability statements, task-state records, and validator-ready public exchange packets. |
| Project memory | AI Memory and Project Handoff after human review | Current constraints, decisions, owners, evidence paths, checks, and receiver briefs that survive the run. |
| Trace and approval history | Runtime trace, approval, and observability systems | Only the reviewed, redacted identifiers and summaries needed to reproduce or cite the public record. |
Boundary: this path does not create SDKs, CLIs, official adapters, certification, endorsement, hosted import validation, automatic repository writes, or automatic LLM Wiki sync. Use the Roadmap before repeating those ideas as current support.