Who this is for
Use UAIX if you are implementing, evaluating, governing, or citing AI-system exchanges that need declared, reviewable structure. UAIX is the public standards and publication site, UAI is the standards family, and UAI-1 is the current normative release.
Reader paths by role
- Implementers: start with UAI-1, then move through 模式, 注册表, 示例, the 验证器, and Implementations.
- Tool builders: start with 模式, 注册表, 示例, the 验证器, and the published discovery surface so automation can resolve the current routes cleanly.
- Researchers and standards readers: start with UAI-1, then use the 变更日志, News, and 引用 and Contributors when you need the public revision trail and citation context.
- Editors, reviewers, and contributors: start with 引用 and Contributors, the 变更日志, News, and the 验证器 so proposals stay attached to the public record rather than private side notes.
- Public readers and press: start with News for the public release trail, then use Press and 引用 and Contributors for outward-facing language and durable links.
AI memory and handoff path
If you are onboarding a new AI, a new contractor, or a second team from repository files instead of from private chat history, start with AI 记忆 for the public framing and live starter bundle, then use 项目交接 when you need the engineering pattern for a root AGENTS.md file, a .uai/readme.human briefing, and local .uai/ bundle.
- Fastest orientation: read AI 记忆 first, then 项目交接, then 代理文件交接 for the active drop-folder intake pattern, then the AGENTS.md .uai Linking 规范ification when you need explicit link syntax.
- Deeper background: use 报告 and Refining UAI Protocol for Agent Communication when you need the longer validation, interoperability, and security reasoning behind the handoff layer.
- When the handoff becomes public evidence: return to UAI-1, 模式, 注册表, 示例, the 验证器, and Implementations.
First 15 minutes
Use this quick path when you are trying to understand where UAIX fits in an agentic architecture: the harness runs the work, MCP and A2A can support runtime coordination, and UAIX preserves the reviewed evidence and project memory that should survive the run.
- Orient: start with UAI-1, 标准定位, and 路线图 to separate the current public contract from planned bridge work.
- Build memory: use AI 记忆, the AI 记忆数据包向导, and 项目交接 when the next human or agent needs durable startup context.
- 证明 one exchange: choose one 示例, run the 验证器, and keep the result beside the 接入套件 or 一致性包 when the packet moves toward review.
- Plan agentic fit: use Agentic Harness Strategies And UAI to keep orchestration, tools, approvals, tracing, and live memory in the runtime while UAIX records the portable proof.
- 检查 the claim: one proof run is packet evidence, not certification, endorsement, official adapter support, SDK, CLI, automatic sync, or broad conformance.
What problem UAI-1 solves
UAI-1 gives implementers a stable public envelope for identity, profile declaration, intent, context, provenance, payload transfer, outputs, and errors. The goal is to make interoperable machine communication easier to validate, audit, and evolve than private runtime-by-runtime dialects.
How the public work is organized today
UAIX currently organizes its public work through record families and 实施轨道 rather than through a separate events calendar, membership program, or broad community portal.
- Use UAI-1, 模式, 注册表, 示例, 验证器, and Implementations as the practical program map for technical adoption.
- Use 变更日志, News, 引用 and Contributors, and Press as the release, citation, and public-facing support layer around that map.
Quick evaluation checklist
- Confirm the current public record exists on stable canonical routes: UAI-1, 模式, 注册表, 示例, the 验证器, Implementations, the 变更日志, and 引用 and Contributors.
- Decide whether you need a current published 实施轨道 or only the portable baseline. Today the public tracks are the WordPress 发布轨道 and the .NET 桥接轨道 described under Implementations.
- 检查 whether the release trail is visible and current: use the 变更日志 and News to see how changes are dated, explained, and linked back to the affected records.
- 检查 whether contributor and citation handoff is sufficient for your use case: 引用 and Contributors should let another reviewer resolve the same public records without private notes.
- Treat broader public contact channels, named multi-stakeholder governance roles, and additional runtime tracks as future work unless they are explicitly published on the site. Use Governance, 政策与安全, Privacy and Data, Accessibility, Analytics, and 引用 and Contributors for the current published trust posture on the launch surface.
What to read first
- Start with UAI-1 to understand the current normative message model.
- Read 模式 and 注册表 together so field rules, profile identifiers, and compatibility handles stay aligned.
- Review 示例 and run the 验证器 before treating an implementation as conformant.
- Use Implementations to choose the publication or runtime track that fits your environment.
Five-minute developer path
- Open UAI-1 and read the first boundary sections so you know what the current public contract covers.
- Pick one published 示例 and resolve its matching 模式 and 注册表 entry.
- Run the same packet through the 验证器 so you have reviewable evidence instead of only a prose impression.
- Use Implementations only to decide what support is actually published today; do not infer a broader SDK or runtime catalog from the standard itself.
Adoption checklist
- Pick one UAI-1 profile and confirm why that profile matches the exchange you want to support.
- Build or map one candidate message with explicit version, profile, source, target, body, provenance, and integrity fields.
- 验证 the message and save the result before wiring it into a release path.
- Decide which public track carries the work next: WordPress publication, .NET bridge integration, or another implementation path tied back to the public record.
- Record any compatibility assumptions in the changelog or release notes before downstream users depend on the behavior.
Capability-adaptive reading path
If the next reader might be a crawler, low-token fetcher, browser-assisted agent, tool-calling agent, workflow agent, multi-agent runtime, or audited system, read Capability-Adaptive Web Interaction before widening support claims.
What records you need next
- The normative record on UAI-1.
- Machine-validation targets on 模式.
- Stable profile and identifier references on 注册表.
- Working fixtures on 示例.
- Validation evidence from the 验证器.
- Deployment direction from Implementations.
当前 public implementation scope
The public site currently documents two implementation lanes through Implementations: a WordPress publication path and a .NET bridge path.
- Do not assume Python, JavaScript, SDK, CLI, or other runtime support unless a public implementation record has been published.
- If you are evaluating another environment, treat UAI-1, schemas, registry entries, examples, and validator evidence as the portable baseline until a public track exists.
当前 public developer kit
- Published now: UAI-1, 模式, 注册表, 示例, Tools, 验证器, discovery routes, validation routes, the WordPress 发布轨道, and the .NET 桥接轨道.
- Not yet published: a public SDK, CLI, standalone source-repository link, general-purpose reference server, or broader runtime-support catalog.
- Best reading today: treat the developer kit as the canonical pages, machine-readable routes, example fixtures, and validator exports until those additional surfaces are formally published.
How UAI-1 fits with MCP and A2A
- UAI-1: the public envelope, trust, provenance, async-delivery, and release-evidence layer for an exchange.
- MCP: local host-client-server tool sessions and capability negotiation inside an application boundary.
- A2A: agent discovery, delegation, and task-flow coordination across cooperating systems.
- Best fit: use UAI-1 above or beside MCP and A2A when another team needs a portable, citable record rather than only a runtime-local interaction. Use 标准定位 for the full UAI-1, MCP, and A2A chooser.
Protocol fit Use this decision table when you need to explain quickly why UAIX publishes UAI-1 beside MCP, A2A, and the live OpenAPI route surface. Typical combination: use MCP or A2A for runtime coordination, UAI-1 for the portable public record, and OpenAPI for the route-level HTTP description when an API is involved. Architecture map Use this visual path when onboarding new readers: start from the runtime layer, shape one UAI-1 packet, validate it against the published artifacts, then carry only the named release evidence forward. Runtime layer These layers can handle local tool use, delegation, and execution flow without being treated as the public release record. Portable public layer UAI-1 keeps the exchange citable, reviewable, and validator-ready when it has to travel beyond one runtime boundary. Machine-readable artifacts These records turn the written contract into machine checks, fixtures, route lookups, and exportable conformance evidence. 发布版本 surface Carry the validated packet into the named implementation lane and the public release trail instead of leaving support claims as local notes. Companion records: transport bindings, trust channels, the error registry, and conformance levels stay beside the message contract so delivery, identity posture, typed failures, and support claims remain explicit.When to use UAI-1 vs MCP, A2A, and OpenAPI
Comparison point
UAI-1
MCP
A2A
OpenAPI
Primary role
Portable public exchange, trust declaration, async-delivery, and release-evidence record.
Host-client-server tool sessions and capability negotiation inside an application boundary.
Agent discovery, delegation, and task-flow coordination across cooperating systems.
路由-level HTTP API description for onboarding, documentation, and client generation.
Best when
Another team needs a citable message contract and validator-backed evidence.
One host application needs local tool, resource, or model integration.
Multiple agents need explicit handoff, delegation, and task-state coordination.
You need a documented HTTP surface, including the UAIX machine-facing REST 路由s.
Carries on the record
身份, workflow continuity, trust posture, provenance, typed errors, and conformance evidence.
Tools, resources, prompts, and runtime session capabilities within the host boundary.
Agent capabilities, task lifecycles, delegation state, and inter-agent coordination.
Endpoints, methods, parameters, request bodies, responses, and auth schemes for an API.
Does not try to replace
传输 choice, local orchestration, a single credential stack, or the runtime tool bus itself.
Portable public release records or validator-backed support claims outside the local session boundary.
A general-purpose public message envelope or long-term release-evidence record.
Message-level provenance, portable trust posture, or validator-driven interoperability evidence.
How the launch surface fits together from runtime to release
MCP, A2A, orchestrators, SDKs
UAI-1 envelope, trust, provenance, delivery
模式, registry, examples, validator
一致性包, 实施轨道, release trail
Launch-ready machine entry points
- API 参考 translates the live REST surface into a route-by-route handbook with OpenAPI export and starter requests.
- 接入套件 publishes the first-proof bundle with starter files, validator-ready payloads, and a reference mock-exchange packet.
- 一致性包 assembles the broader release artifacts into one reusable JSON packet for launch review and regression work.
/wp-json/uaix/v1/adoption-kitpublishes the machine-readable onboarding bundle and supports a direct download form with?download=1./wp-json/uaix/v1/openapi.jsonpublishes the current OpenAPI 3.1 description of the machine-facing UAIX routes./wp-json/uaix/v1/conformance-packpublishes the current machine-readable conformance packet and supports a direct download form with?download=1.
First machine calls
curl -s /wp-json/uaix/v1/catalog
curl -s /wp-json/uaix/v1/schemas/uai.intent.request.v1
curl -s /wp-json/uaix/v1/adoption-kit
curl -s -X POST /wp-json/uaix/v1/validate -H "Content-Type: application/json" -d @validate-request.jsonUse the catalog first, then resolve one schema or example, pull the published onboarding bundle, and submit one validator run. That is the shortest machine-facing path from reading the standard to proving one packet against the public record.
Published first-proof run
Use the public runbook and starter calls below when the next goal is one validator-backed packet built entirely from the currently published surface.
First proof run Use this runbook when the next goal is one validator-backed packet built only from the currently published public surface. Step 1 Pull the current route inventory first so the rest of the proof run stays anchored to the published machine surface. Step 2 Use one published request example as the first packet so your review starts from current public structure instead of local guesswork. Step 3 Build one validator request body with the example packet nested under `message` and request the result record format. Step 4 Submit the validation request to the live POST route and keep the returned result record with the exact packet that was checked. Step 5 Post the same validated packet to the mock exchange route when you want one real conforming response shape before a runtime track exists. Step 6 Move from proof into the named implementation lane, conformance pack, and release trail instead of claiming broader support than the site publishes. Keep the starter packet, validator request, and mock-exchange request required for mock-exchange configuration together with the returned result. That bundle is the smallest repeatable proof-and-response packet on the current public surface. Client examples Use these plain HTTP snippets to reach the live public surface quickly, including the reference-response route, while official runtime tracks remain intentionally narrow. 起步片段使用实时公开路由，而不是私有 SDK 或未发布的辅助层。Get to one valid UAI-1 message in five minutes
解析 the live catalog
Fetch one starter example
Wrap the message for validation
Run one validator check
Test the live reference response
Carry only the named next step
/wp-json/uaix/v1/catalog
模式
/wp-json/uaix/v1/schemas/uai.intent.request.v1
示例
/wp-json/uaix/v1/examples/uai.intent.request.v1
验证
/wp-json/uaix/v1/validate
Adoption kit
/wp-json/uaix/v1/adoption-kit
Mock exchange
/wp-json/uaix/v1/mock-exchange
{
"uai_version": "1.0",
"profile": "uai.intent.request.v1",
"message_id": "msg-2026-04-22-0001",
"source": {
"type": "agent",
"id": "agent.alpha",
"label": "Agent Alpha",
"uri": "https://agents.alpha.example/runtime",
"did": "did:web:agents.alpha.example",
"role": "requesting-agent",
"implementation": "alpha-runtime-2.4.1"
},
"target": {
"type": "service",
"id": "uaix.gateway",
"label": "UAIX 闸门way",
"uri": "/wp-json/uaix/v1/discovery",
"did": "did:web:uaix.org",
"role": "public-record-gateway",
"implementation": "uaix-core-0.4.0"
},
"conversation": {
"conversation_id": "conv-2026-04-22-uaix-001",
"turn_id": "turn-001",
"traceparent": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01",
"sequence": 1
},
"delivery": {
"mode": "async",
"priority": "interactive",
"expires_at": "2026-04-22T16:05:00Z",
"reply_requested": true,
"ack_required": true
},
"trust": {
"channel": "credentialed",
"auth_scheme": "did+vc",
"principal": "did:web:agents.alpha.example",
"credential_ref": "https://agents.alpha.example/credentials/uai-interop.json",
"signature_ref": "https://agents.alpha.example/signatures/msg-2026-04-22-0001.jws",
"replay_window_id": "rw-2026-04-22-0001",
"trust_profile": "uai.trust.did-vc-reference.v1",
"verification_status": "not_verified",
"credential_status": "not_checked",
"verifier_ref": "https://agents.alpha.example/verifiers/uai-trust-policy.json",
"trust_root_ref": "https://agents.alpha.example/.well-known/uai.json",
"proof_ref": "https://agents.alpha.example/signatures/msg-2026-04-22-0001.jws",
"replay_policy_ref": "https://agents.alpha.example/trust/replay-policy.json",
"verification_checked_at": "2026-04-22T16:00:00Z",
"verification_expires_at": "2026-04-22T16:05:00Z",
"assurance_level": "reference_only"
},
"body": {
"intent": "resolve-profile",
"subject": "uai.task.status.v1",
"requested_profile": "uai.task.status.v1",
"parameters": {
"include_schema": true,
"include_example": true,
"include_field_registry": true
},
"constraints": [
"public-record-only",
"trace-linked",
"validator-ready"
],
"response_profile": "uai.intent.response.v1"
},
"provenance": {
"trace_id": "trace-7f3a2d",
"parent_trace_id": "trace-root-uaix-2026",
"issued_at": "2026-04-22T16:00:00Z",
"log_ref": "urn:uaix:log:2026:0001",
"agent_id": "agent.alpha",
"model_id": "model.alpha.reasoner-2",
"confidence": 0.98,
"lineage": [
{
"stage": "request-composition",
"actor_id": "agent.alpha",
"model_id": "model.alpha.reasoner-2",
"note": "Requested the async task-status profile and matching field registry."
}
]
},
"integrity": {
"version": 2,
"algorithm": "sha256",
"canonicalization": "jcs",
"checksum": "sha256:dd8a9d16c9226cc9d1f4888a4d2bbcbf06b5b4b8"
},
"extensions": [
{
"namespace": "urn:uaix:ext:delivery",
"purpose": "Explicit async request handling and expiry semantics.",
"critical": false
}
]
}{
"message": {
"uai_version": "1.0",
"profile": "uai.intent.request.v1",
"message_id": "msg-2026-04-22-0001",
"source": {
"type": "agent",
"id": "agent.alpha",
"label": "Agent Alpha",
"uri": "https://agents.alpha.example/runtime",
"did": "did:web:agents.alpha.example",
"role": "requesting-agent",
"implementation": "alpha-runtime-2.4.1"
},
"target": {
"type": "service",
"id": "uaix.gateway",
"label": "UAIX 闸门way",
"uri": "/wp-json/uaix/v1/discovery",
"did": "did:web:uaix.org",
"role": "public-record-gateway",
"implementation": "uaix-core-0.4.0"
},
"conversation": {
"conversation_id": "conv-2026-04-22-uaix-001",
"turn_id": "turn-001",
"traceparent": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01",
"sequence": 1
},
"delivery": {
"mode": "async",
"priority": "interactive",
"expires_at": "2026-04-22T16:05:00Z",
"reply_requested": true,
"ack_required": true
},
"trust": {
"channel": "credentialed",
"auth_scheme": "did+vc",
"principal": "did:web:agents.alpha.example",
"credential_ref": "https://agents.alpha.example/credentials/uai-interop.json",
"signature_ref": "https://agents.alpha.example/signatures/msg-2026-04-22-0001.jws",
"replay_window_id": "rw-2026-04-22-0001",
"trust_profile": "uai.trust.did-vc-reference.v1",
"verification_status": "not_verified",
"credential_status": "not_checked",
"verifier_ref": "https://agents.alpha.example/verifiers/uai-trust-policy.json",
"trust_root_ref": "https://agents.alpha.example/.well-known/uai.json",
"proof_ref": "https://agents.alpha.example/signatures/msg-2026-04-22-0001.jws",
"replay_policy_ref": "https://agents.alpha.example/trust/replay-policy.json",
"verification_checked_at": "2026-04-22T16:00:00Z",
"verification_expires_at": "2026-04-22T16:05:00Z",
"assurance_level": "reference_only"
},
"body": {
"intent": "resolve-profile",
"subject": "uai.task.status.v1",
"requested_profile": "uai.task.status.v1",
"parameters": {
"include_schema": true,
"include_example": true,
"include_field_registry": true
},
"constraints": [
"public-record-only",
"trace-linked",
"validator-ready"
],
"response_profile": "uai.intent.response.v1"
},
"provenance": {
"trace_id": "trace-7f3a2d",
"parent_trace_id": "trace-root-uaix-2026",
"issued_at": "2026-04-22T16:00:00Z",
"log_ref": "urn:uaix:log:2026:0001",
"agent_id": "agent.alpha",
"model_id": "model.alpha.reasoner-2",
"confidence": 0.98,
"lineage": [
{
"stage": "request-composition",
"actor_id": "agent.alpha",
"model_id": "model.alpha.reasoner-2",
"note": "Requested the async task-status profile and matching field registry."
}
]
},
"integrity": {
"version": 2,
"algorithm": "sha256",
"canonicalization": "jcs",
"checksum": "sha256:dd8a9d16c9226cc9d1f4888a4d2bbcbf06b5b4b8"
},
"extensions": [
{
"namespace": "urn:uaix:ext:delivery",
"purpose": "Explicit async request handling and expiry semantics.",
"critical": false
}
]
},
"format": "result"
}{
"scenario": "accepted-task",
"format": "exchange",
"message": {
"uai_version": "1.0",
"profile": "uai.intent.request.v1",
"message_id": "msg-2026-04-22-0001",
"source": {
"type": "agent",
"id": "agent.alpha",
"label": "Agent Alpha",
"uri": "https://agents.alpha.example/runtime",
"did": "did:web:agents.alpha.example",
"role": "requesting-agent",
"implementation": "alpha-runtime-2.4.1"
},
"target": {
"type": "service",
"id": "uaix.gateway",
"label": "UAIX 闸门way",
"uri": "/wp-json/uaix/v1/discovery",
"did": "did:web:uaix.org",
"role": "public-record-gateway",
"implementation": "uaix-core-0.4.0"
},
"conversation": {
"conversation_id": "conv-2026-04-22-uaix-001",
"turn_id": "turn-001",
"traceparent": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01",
"sequence": 1
},
"delivery": {
"mode": "async",
"priority": "interactive",
"expires_at": "2026-04-22T16:05:00Z",
"reply_requested": true,
"ack_required": true
},
"trust": {
"channel": "credentialed",
"auth_scheme": "did+vc",
"principal": "did:web:agents.alpha.example",
"credential_ref": "https://agents.alpha.example/credentials/uai-interop.json",
"signature_ref": "https://agents.alpha.example/signatures/msg-2026-04-22-0001.jws",
"replay_window_id": "rw-2026-04-22-0001",
"trust_profile": "uai.trust.did-vc-reference.v1",
"verification_status": "not_verified",
"credential_status": "not_checked",
"verifier_ref": "https://agents.alpha.example/verifiers/uai-trust-policy.json",
"trust_root_ref": "https://agents.alpha.example/.well-known/uai.json",
"proof_ref": "https://agents.alpha.example/signatures/msg-2026-04-22-0001.jws",
"replay_policy_ref": "https://agents.alpha.example/trust/replay-policy.json",
"verification_checked_at": "2026-04-22T16:00:00Z",
"verification_expires_at": "2026-04-22T16:05:00Z",
"assurance_level": "reference_only"
},
"body": {
"intent": "resolve-profile",
"subject": "uai.task.status.v1",
"requested_profile": "uai.task.status.v1",
"parameters": {
"include_schema": true,
"include_example": true,
"include_field_registry": true
},
"constraints": [
"public-record-only",
"trace-linked",
"validator-ready"
],
"response_profile": "uai.intent.response.v1"
},
"provenance": {
"trace_id": "trace-7f3a2d",
"parent_trace_id": "trace-root-uaix-2026",
"issued_at": "2026-04-22T16:00:00Z",
"log_ref": "urn:uaix:log:2026:0001",
"agent_id": "agent.alpha",
"model_id": "model.alpha.reasoner-2",
"confidence": 0.98,
"lineage": [
{
"stage": "request-composition",
"actor_id": "agent.alpha",
"model_id": "model.alpha.reasoner-2",
"note": "Requested the async task-status profile and matching field registry."
}
]
},
"integrity": {
"version": 2,
"algorithm": "sha256",
"canonicalization": "jcs",
"checksum": "sha256:dd8a9d16c9226cc9d1f4888a4d2bbcbf06b5b4b8"
},
"extensions": [
{
"namespace": "urn:uaix:ext:delivery",
"purpose": "Explicit async request handling and expiry semantics.",
"critical": false
}
]
}
}curl、PowerShell、Python 和 TypeScript 的可复制起步请求
curl -sS "/wp-json/uaix/v1/adoption-kit" -o uai-adoption-kit.jsoncurl -sS "/wp-json/uaix/v1/catalog"curl -sS "/wp-json/uaix/v1/examples/uai.intent.request.v1" -o example-record.jsoncurl -sS -X POST "/wp-json/uaix/v1/validate" \
-H "Content-Type: application/json" \
-d @validate-request.jsoncurl -sS -X POST "/wp-json/uaix/v1/mock-exchange" \
-H "Content-Type: application/json" \
-d @mock-exchange-request.jsonInvoke-RestMethod -Uri "/wp-json/uaix/v1/adoption-kit" | ConvertTo-Json -深度 20 | Set-Content .\uai-adoption-kit.jsonInvoke-RestMethod -Uri "/wp-json/uaix/v1/catalog"Invoke-RestMethod -Uri "/wp-json/uaix/v1/examples/uai.intent.request.v1" | ConvertTo-Json -深度 20 | Set-Content .\example-record.json$message = (Get-Content -Raw .\example-record.json | ConvertFrom-Json).message
$body = @{ message = $message; format = "result" } | ConvertTo-Json -深度 20
Invoke-RestMethod -Method Post -Uri "/wp-json/uaix/v1/validate" -ContentType "application/json" -Body $body$message = (Get-Content -Raw .\example-record.json | ConvertFrom-Json).message
$body = @{ scenario = "accepted-task"; format = "exchange"; message = $message } | ConvertTo-Json -深度 20
Invoke-RestMethod -Method Post -Uri "/wp-json/uaix/v1/mock-exchange" -ContentType "application/json" -Body $bodyimport json, urllib.request
kit = json.load(urllib.request.urlopen("/wp-json/uaix/v1/adoption-kit"))import json, urllib.request
catalog = json.load(urllib.request.urlopen("/wp-json/uaix/v1/catalog"))example_record = json.load(urllib.request.urlopen("/wp-json/uaix/v1/examples/uai.intent.request.v1"))
message = example_record.get("message", example_record)payload = json.dumps({"message": message, "format": "result"}).encode("utf-8")
request = urllib.request.Request("/wp-json/uaix/v1/validate", data=payload, headers={"Content-Type": "application/json"}, method="POST")
result = json.load(urllib.request.urlopen(request))payload = json.dumps({"scenario": "accepted-task", "format": "exchange", "message": message}).encode("utf-8")
request = urllib.request.Request("/wp-json/uaix/v1/mock-exchange", data=payload, headers={"Content-Type": "application/json"}, method="POST")
exchange = json.load(urllib.request.urlopen(request))const kit = await fetch("/wp-json/uaix/v1/adoption-kit").then((response) => response.json());const catalog = await fetch("/wp-json/uaix/v1/catalog").then((response) => response.json());const exampleRecord = await fetch("/wp-json/uaix/v1/examples/uai.intent.request.v1").then((response) => response.json());
const message = exampleRecord.message ?? exampleRecord;const result = await fetch("/wp-json/uaix/v1/validate", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({ message, format: "result" }),
}).then((response) => response.json());const exchange = await fetch("/wp-json/uaix/v1/mock-exchange", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({ scenario: "accepted-task", format: "exchange", message }),
}).then((response) => response.json());
Minimal first success
- Choose one published profile and build a message that matches its declared purpose.
- 验证 that message against the published schema and registry record.
- Compare the message to a published example fixture.
- Save the resulting validation record as part of your release evidence.
First public proof run
- Start with one published profile and either a matching example fixture or a candidate message that stays inside the same public record family.
- 解析 the matching 模式, 注册表, and canonical page paths before validation so another reviewer can reproduce the same packet.
- Run the 验证器, export the result, and keep the exact example or candidate message used during the check.
- Attach the relevant Implementation track, 引用 and Contributors, the 变更日志, and News once the work moves from local testing into a public review or release context.
- Treat the resulting packet as current public evidence of alignment, not as a permanent certification across future revisions.
What you can claim at each readiness step
- After one passing validator run: you have current public evidence that one message or fixture aligned with the published record at review time.
- After assembling a release packet: you can describe the work as release-ready for public review within the chosen 实施轨道.
- After a public implementation-track record exists: you can describe only that named track and release as publicly supported, and only within the owner and scope stated on the site.
- Do not turn local testing, one passing result, or unpublished runtime work into claims of certification, blanket ecosystem support, or permanent compatibility.
阶段 1
已验证数据包
已发布 fixture 或候选消息已通过当前公开记录检查。
- 可立即用于评审、调试和回归工作。
- 在结果附到已命名发布路径前，它仍然只是证据。
阶段 2
可发布数据包
通过结果现在与实现版本、制品链接和发现上下文一起传递。
- 把已检查数据包、验证器导出、制品 URL 和兼容性说明放在一起。
- 这是上线评审、打包和可重复 QA 的交接点。
阶段 3
公开支持声明
已命名实现轨道和发布轨迹现在说明哪些内容已公开支持、哪些仍在范围外。
- 把声明限定到实际已发布的准确配置文件、传输绑定和负责人路径。
- 使用当前一致性级别和发布链接，让其他读者能验证同一状态。
数据包要点
最低首次证明数据包
- 一个已发布的配置文件，以及匹配的架构和注册表路由。
- 一个实际经过审阅的可读有键 JSON 示例或候选消息。
- 一个与被检查数据包精确对应的导出验证结果。
- 可让另一位审阅者解析相同发布状态的发现和引用链接。
后续附件
在称其为公开支持前附上这些材料
- 已命名的实现轨道，以及发布版本或包版本。
- 当工作流依赖它们时，附上兼容性说明以及传输、信任和错误指南。
- 当结果改变公开发布姿态时，附上变更日志和发布摘要链接。
- 只声明站点当前已发布的精确范围，不扩大为运行时或生态承诺。
当前公开一致性级别： 当数据包成为具名发布和实现记录的一部分后，使用这些级别约束对外表述。
L1-core-envelope
L1 Core 信封
Produce or consume keyed UAI envelopes for named profiles without changing the canonical root fields.
- Preserve uai_version, profile, message_id, source, target, conversation, delivery, trust, body, provenance, integrity, and extensions.
- Name the exact profile and release for every support claim.
- Do not claim runtime execution from envelope support alone.
公开声明： May claim L1 only for the exact named profiles whose canonical envelope round-trips successfully.
L2-profile-validation
L2 配置文件 Validation
Pass published schema and validator checks for the exact profiles claimed.
- 解析 schemas, registry entries, examples, and field registry records from public UAIX routes.
- Pass positive fixtures and fail required negative fixtures for each claimed profile.
- Keep skipped checks and validator warnings attached to evidence.
公开声明： May claim L2 only for profiles with validator-backed evidence.
L3-trust-and-integrity
L3 信任 and Integrity
Preserve trust metadata, replay-window hints, provenance, integrity, and trace continuity.
- Declare trust channel and principal.
- Preserve integrity canonicalization and checksum metadata.
- 验证 signed, credentialed, did+vc, and trace metadata when claimed.
公开声明： May claim L3 only for the trust channels and integrity behavior proven by fixtures.
L4-public-record-publisher
L4 Public Record Publisher
Publish discoverable 公开制品 needed for external inspection and reproduction.
- Publish discovery, schemas, registry, examples, field registry, transport bindings, trust channels, error registry, conformance levels, validator guidance, changelog, and release evidence.
- Keep sitemap, llms.txt, and public navigation aligned with current routes.
- Avoid private logs or screenshots as the only support evidence.
公开声明： May claim L4 only for the public release surface that is discoverable and evidenced.
L5-agent-communication-profiles
L5 Agent Communication 配置文件数
Support the eight uai.agent.*.v1 profiles as canonical UAI-1 envelope records.
- 验证 agent message, ack, task-status, blocker, memory-proposal, handoff, final-report, and correction profiles.
- Reject secret-like memory proposals, unsafe blockers, cold-memory direct promotion, and incomplete final reports.
- Carry the UAIX support boundary in relevant records.
公开声明： May claim L5 only for the specific agent profiles with passing positive and negative conformance cases.
L6-reliable-delegation-idempotency-correlation
L6 Reliable Delegation with Idempotency and Correlation
Use idempotency, correlation, retry, lifecycle, timeout, fallback, acknowledgement, and expected-output rules for delegated work.
- Require delivery.idempotency_key for each distinct delegated or destructive operation.
- Preserve conversation.correlation_id across related messages.
- Declare retry_count, sequence, expires_at, lifecycle, timeout_ms, fallback_directive, and expected_output_schema when delegation is claimed.
公开声明： May claim L6 only for reliable delegation behavior proven by conformance fixtures and receiver behavior.
L7-capability-negotiation
L7 Capability Negotiation
Publish and validate capability discovery, assertions, negotiation failures, and unsupported-capability responses.
- Publish capability statements with exact profiles, bindings, trust channels, conformance levels, and error codes.
- Return capability_not_supported for unsupported capability requests.
- Do not imply certification, official adapter status, hosted messaging, or runtime orchestration.
公开声明： May claim L7 only for the exact capability negotiation flows proven by public fixtures and validator behavior.
声明规则
公开表述应限于已发布证据
- Support claims must name the highest achieved level plus the exact profiles, transport bindings, trust channels, and conformance cases implemented.
- A project may claim only profiles, bindings, trust channels, and conformance levels that public fixtures and validator tests prove.
- A passing validator result is evidence, not certification, endorsement, official adapter support, hosted messaging, automatic sync, or runtime execution.
- Public-record claims require discoverable schemas, registry records, examples, field registry records, error codes, conformance pack cases, changelog, and release notes.
- Revalidate support claims when schemas, registry records, field order, examples, validator behavior, implementation version, trust posture, sitemap, or public navigation changes.
- 一致性 evidence does not prove security, privacy, availability, performance, legal compliance, hosted trust infrastructure, or production operations by itself.
- 当另一支团队需要验证同一公开状态时，请保留实现页面、发布轨迹以及引用/发现链接。
工作规则： 表述时使用一致性阶梯，但实际公开支持边界应以具名实现轨道和发布轨迹为准。
What to keep with your first public release
- The validation record exported from the 验证器.
- The chosen Implementation track and any packaging or runtime notes tied to it.
- 引用 and Contributors for stable discovery and citation links.
- The 变更日志 when downstream implementers need migration posture.
- News when the work needs a public-facing release summary.
- Press when the release also needs approved outward-facing language.
下一步 step
Continue to UAI-1, then move through 模式, 注册表, 示例, the 验证器, and Implementations in that order. Use 引用 and Contributors, the 变更日志, and News to keep the first public release traceable.