UAI-1 es la norma pública actual de mensajes para comunicación estructurada de IA a IA.
UAIX shield mark Carta pública de interoperabilidad UAIX.org 通用人工智能交换 Publicación pública de normas
Actual UAI-1
  • Versión actual UAI-1
  • Definición en lenguaje claro Formato de mensaje abierto para intercambio IA-a-IA auditable
  • Atribución actual Michael Joseph Kappel, MCP
  • Empiece aquí Inicio, Traspaso de proyecto, UAI-1, validador, hoja de ruta y registro de cambios

Implementaciones

.NET 桥接轨道

Runtime integration track that connects the public UAI-1 record to .NET services.

  • Record UAIX-IMPL-0059
  • Path /es-es/implementations/dotnet-bridge/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-IMPL-0059
Surface
Implementaciones
Access
Public and linkable

如何使用本页

Use this track when published UAI-1 messages need to connect to .NET services without changing the public contract.

When to choose this track

Use the .NET 桥接轨道 when the public UAI-1 record needs to connect to deeper runtime services, orchestration layers, or backend execution flows without turning the public site into the application runtime.

What this track covers

The bridge should preserve the public UAI-1 contract while adapting it to service-side execution. It can map, validate, route, and log messages, but it should not introduce hidden profile behavior, undocumented payload shortcuts, or runtime-only semantics that contradict the public schema, registry, examples, or validator.

Responsibilities

  • Map public standard records to runtime-accessible endpoints and services.
  • Preserve validation, provenance, versioning, and compatibility rules across the handoff.
  • Keep publication concerns separate from execution concerns while still pointing back to the public record.

当前 public packaging status

  • uaix-bridge.zip is the current packaged WordPress-side artifact for the named bridge track.
  • The .NET NuGet Package page documents Protocol5.UAI.CSharp, its direct Protocol5 download, and installation notes for C# implementers.
  • Treat the NuGet package as Protocol5 implementation distribution tied back to UAIX.org for standards truth, not as a general-purpose UAIX SDK, CLI, certification, endorsement, or broader .NET ecosystem claim.

Public records that must stay attached

What counts as evidence here

  • Messages that still pass the public 验证器 after runtime integration.
  • 配置文件 resolution and provenance that still match the published 注册表 and public 示例.
  • 发布版本 notes and compatibility statements recorded through Governance, the 变更日志, and linked implementation updates.

当前 support-claim boundary

The .NET 桥接轨道 supports runtime mapping that preserves the public UAI-1 contract. It does not, by itself, publish a general .NET SDK or blanket .NET ecosystem support claim.

  • A passing bridge integration supports a claim that the tested handoff still aligned with the public record at review time.
  • A current public support claim for .NET should stay scoped to the named bridge behavior, release packet, and compatibility notes published on the site.
  • Do not use this track to imply support for unrelated frameworks, transports, or hidden runtime conventions that are not attached to the public record.

When this track is release-ready

  1. Integrated messages still pass validator-backed checks against the published schemas, registry entries, and examples.
  2. Runtime mapping notes, release versioning, and migration guidance are attached to the same public release packet.
  3. The release trail states what the bridge supports now without implying a broader SDK, certification, or ecosystem program.

下一步 step

Use the bridge alongside the public record, not instead of it. Keep validator evidence, registry references, example links, and public change records attached to every integrated release.