Role of the 实施轨道
The implementation section explains how UAIX turns UAI-1 from a published standard into deployable software and release evidence. The goal is not just to describe the standard, but to show where publication, validation, packaging, runtime integration, and release records actually happen.
当前 tracks
- WordPress 发布轨道 for publication, distribution, package release, discovery alignment, and public documentation.
- .NET 桥接轨道 for runtime and service-side integration beyond the public website.
- .NET NuGet Package documents the Protocol5-distributed C# package, direct download, install commands, and authority boundary for .NET implementers.
- Portable modules and supporting packages where shared features need a stable implementation home.
当前 published package family
uaix-authority-theme-v2.8.0.zipis the active public launch theme and carries the current front-door publication surface.uaix-theme-v2.8.0.zipremains packaged and smoke-tested as an installable compatibility theme, but it is not the current public launch surface.uaix-core-v2.8.0.zipcarries the core standards runtime and REST record surface.uaix-modules-v2.8.0.zipcarries the redistributable module pack used by UAIX implementations.uaix-bridge-v2.8.0.zipcarries the WordPress-to-.NET reference bridge for the named bridge track.Protocol5.UAI.CSharpis the current Protocol5-hosted .NET package distribution page; use it as implementation support, not as UAI-1 standards authority.uaix-locale-router-v3.0.0.zipcarries locale-prefixed routing so the public launch paths stay on clean/en-us/...routes.uaix-seo-sweep-v2.8.0.zipcarries canonical SEO, query-string cleanup, sitemap generation, robots output, and the root discovery manifest surface.
当前 public implementation scope
The current public implementation story is intentionally narrow and explicit. The published tracks are WordPress 发布轨道 and .NET 桥接轨道.
- Do not imply Python, JavaScript, SDK, CLI, or other runtime support unless a public implementation page, validator-backed evidence, and release-trail entry have been published.
- Use UAI-1, schemas, registry entries, examples, and validator evidence as the portable baseline when evaluating an environment that does not yet have a published track.
Supporting public records
- 引用 and Contributors for discovery links, attribution, and citation guidance.
- The 变更日志 and News archive for migration notes, release summaries, and implementation updates.
- Press when implementation work needs approved public language for directories, partner notes, or standards coverage.
What counts as credible implementation evidence
- Use of published profiles, schemas, registry identifiers, and 示例 rather than private substitutes.
- Validation output from the 验证器 or an equivalent conformant check.
- Fixtures, compatibility notes, packaging results, and release records that make changes reviewable after deployment.
- Links back to the current public changelog and canonical records so readers can trace what shipped.
当前 evidence ladder
- Choose the published profile and canonical records that define the behavior you intend to support.
- 验证 a candidate message or fixture and export the result record.
- Bind that result to the implementation version, release date, and track that carried the work.
- Attach the matching changelog, news, and discovery links so outside readers can verify the same public state.
当前 support-claim ladder
- 验证d candidate: one or more messages or fixtures pass against the current public record.
- 可发布数据包: the validation record, implementation version, discovery links, and compatibility notes are attached to a releasable package or runtime build.
- 当前 public support claim: a published implementation-track record and release-trail entry state what is supported now, who owns it, and what remains experimental.
UAIX currently treats only the third level as a public support claim. The first two levels are necessary evidence, but they are not the same as published support.
发布版本 readiness
How implementation evidence becomes a public support claim
Use this map when a WordPress or .NET track run is ready to move from local validation into a named public release lane.
阶段 1
已验证数据包
已发布 fixture 或候选消息已通过当前公开记录检查。
- 可立即用于评审、调试和回归工作。
- 在结果附到已命名发布路径前，它仍然只是证据。
阶段 2
可发布数据包
通过结果现在与实现版本、制品链接和发现上下文一起传递。
- 把已检查数据包、验证器导出、制品 URL 和兼容性说明放在一起。
- 这是上线评审、打包和可重复 QA 的交接点。
阶段 3
公开支持声明
已命名实现轨道和发布轨迹现在说明哪些内容已公开支持、哪些仍在范围外。
- 把声明限定到实际已发布的准确配置文件、传输绑定和负责人路径。
- 使用当前一致性级别和发布链接，让其他读者能验证同一状态。
发布版本 packet
What should ship with the implementation evidence
- Implementation-track name plus package, runtime, or deployment version.
- 验证d profile IDs, the checked packet, and the exact validator export used during review.
- 模式, registry, example, and discovery routes that reproduce the same public baseline.
- Compatibility notes, release date, and any affected launch-support surfaces.
Public support boundary
What must exist before a support claim belongs on the site
- A named implementation page that states owner, scope, and what remains experimental.
- 变更日志 and news entries that explain what changed and why another team should trust it.
- Only the highest achieved conformance level plus the exact profiles and transport bindings implemented.
- Citation and discovery links that make the claim reviewable after deployment.
当前公开一致性级别： 当数据包成为具名发布和实现记录的一部分后，使用这些级别约束对外表述。
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.
- 当另一支团队需要验证同一公开状态时，请保留实现页面、发布轨迹以及引用/发现链接。
工作规则： 表述时使用一致性阶梯，但实际公开支持边界应以具名实现轨道和发布轨迹为准。
发布证据 packet
A release-ready implementation should keep the public standard record and the software evidence together rather than scattering proof across private build logs.
- Include the package or runtime version, the validated profile IDs, and the schema and registry routes used during the check.
- Attach exported validator results, fixture references, and any compatibility notes that affect downstream adopters.
- Point readers to the relevant changelog entry, news summary, and citation links before calling the implementation release-ready.
当前 public conformance packet
UAIX currently treats a conformance packet as reviewable evidence attached to a release, not as a standalone certification surface.
- Keep the exported validator result, validated profile IDs, schema and registry routes, and the example or candidate fixture used during review together.
- Attach the implementation version, release date, and the matching changelog or news references so outside readers can trace what actually passed.
- Rebuild the packet whenever schemas, fixtures, validator behavior, or runtime mappings change.
- Do not present a passing packet as a certification badge, partner endorsement, or permanent guarantee across future releases.
Track admission checklist for future public support
- A public implementation page that states the owner, support boundary, and relationship to the normative UAI-1 record.
- 验证器-backed evidence or equivalent conformance proof tied to published profiles, schemas, registry entries, and examples.
- A release-trail entry that states what is supported now, what remains experimental, and what downstream readers need to migrate.
- 发现, citation, and implementation links that let outside readers resolve the same track without private notes or screenshots.
Starter adoption packet
Teams evaluating UAIX should be able to assemble a minimal public packet from the current record without private notes, unpublished routes, or internal screenshots.
- UAI-1, 模式, 注册表, and 示例 as the normative and machine-readable baseline.
- 验证器-backed evidence from the 验证器 for at least one candidate message or published fixture.
- 引用 and Contributors, the
/.well-known/uaix.jsonmanifest, and the published sitemap surfaces as the discovery and citation layer. - The 变更日志 and News entries that explain the current migration and release posture.
当前 adoption-kit path
UAIX now publishes the first-proof bundle directly through the 接入套件 page and the /wp-json/uaix/v1/adoption-kit route.
- Start there when a team needs starter files, validator-ready payloads, a reference mock exchange response, and implementation next steps in one reusable packet.
- Keep UAI-1, 模式, 注册表, and 示例 as the deeper technical baseline behind the bundle.
- Attach exported validator evidence, the relevant implementation-track record, and the matching 变更日志 and News entries when the packet moves into release review.
How to use this section
Choose the 实施轨道 that matches your responsibility, then carry validator evidence, fixture references, changelog discipline, and public-link context with that implementation rather than treating them as separate documentation chores.
下一步 step
Use the WordPress 发布轨道 if you need the publication, packaging, and release-record path. Use the .NET 桥接轨道 if you need deeper runtime integration behind the public record, then keep both tied to the 变更日志 and News.