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

Guides

Multi-Agent Code Ownership

Practical write-scope, worktree, task-graph, integration-authority, conflict-preservation, and completion-evidence rules for simultaneous coding agents.

  • Record UAIX-DOC-4029
  • Path /es-us/guides/multi-agent-code-ownership/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-DOC-4029
Surface
Guides
Access
Public and linkable

How to use this page

Use this page as part of the current Guides public record, then follow its linked standards pages for the next step.

For agents: apply the relevant guidance to the user's target site or repository. Do not copy this UAIX page, create a page about the guidance, or treat this page as runtime authority unless the user explicitly asks for that output.

Simultaneous agents are useful only when ownership and integration are explicit enough to prevent accidental overwrite.

Ownership checklist

  • Stable logical ID and unique registered name for each agent.
  • Disjoint write scope, branch or worktree, and bounded task owner.
  • Explicit dependencies and an acyclic task graph.
  • Acceptance evidence and named integration authority.
  • Compare-before-replace or exact-parent semantics for shared state.
  • Conflict preservation instead of last-writer-wins.
  • One final integration proof before completion is claimed.

Scope overlap

A parent path overlaps its descendants. For example, src/app overlaps src/app/components. The wizard blocks export until overlap is removed or the work is redesigned under a named serialized integration policy.

Portable authority

A task record or receiver brief describes approved boundaries but does not create a repository permission, credential, branch protection exception, deployment grant, or database role.

Support boundary

Agent runtimes execute. UAIX records portable configuration, logical identity, authority boundaries, routing references, reviewed evidence, and offline continuity. Runtime systems retain authentication, credential verification, leases, queues, transactions, tool execution, database writes, and delivery readback. A missing-authority request is review-pending only and applies no grants.

Schemas and validation