UAI-1 est la norme publique actuelle de messages pour une communication IA-à-IA structurée.
UAIX shield mark Charte publique d'interopérabilité UAIX.org Échange universel d'intelligence artificielle Publication publique de normes
Actuel UAI-1
  • Version actuelle UAI-1
  • Définition en langage clair Format de message ouvert pour un échange IA-à-IA auditable
  • Attribution actuelle Michael Joseph Kappel, MCP
  • Commencer ici Démarrage, Transfert de projet, UAI-1, validateur, feuille de route et journal des changements

Outils

Paquet de conformité

Cette page n est pas encore disponible comme norme localisee revue. Utilisez la source anglaise faisant autorite pour le langage normatif, l interpretation des schemas, les obligations d implementation et les limites de support.

  • Dossier UAIX-TOOL-0065
  • Chemin /fr-fr/tools/conformance-pack/
  • Utilisation Dossier public canonique

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-TOOL-0065
Surface
Outils
Accès
Public et accessible par lien

Comment utiliser cette page

Use this page to assemble the current reusable conformance packet for launch review and release evidence.

Evidence sources

Conformance Pack JSONKit d'adoptionValidateurImplémentations

Evidence Packet

What travels into launch review and support claims

The conformance pack keeps the current public record, implementation evidence checklist, and conformance fixture pack together for reuse. Treat it as the evidence bundle behind release review, not as a certification surface by itself.

What travels

Catalog, schemas, fixtures, checklist, regression cases, and trust records

The pack carries the public standards inventory, implementation evidence checklist, conformance fixture pack, and machine-readable supporting records another reviewer needs to reconstruct the same baseline.

When to attach it

Launch review, regression, and release notes

Use the pack when validation evidence, fixture expectations, and checklist answers need to travel into implementation review, packaging checks, or a dated public release record.

What not to claim

Evidence is not certification

A pack helps prove what was checked, but it does not create a badge, endorsement, or blanket support claim on its own.

Evidence sources

Conformance Pack JSONMachine-readable release packet.Kit d'adoptionPublished first-proof bundle before the broader evidence packet.ValidateurGenerate the result that belongs in the packet.ImplémentationsAttach the packet to the named release lane.Policy and SecurityTrust posture that frames the packet.

Proof path

Validator-backed proof path

Keep the public reading order tied to one evidence trail: profile, schema, example, validator result, and release record.

  1. 1Pick a message profile.Start with a published UAI-1 profile and the record family that matches the exchange you need to prove.
  2. 2Compare it with schemas and examples.Resolve the schema, registry entry, and one fixture before writing or mapping your candidate packet.
  3. 3Run validator evidence.Validate keyed, minified-keyed, or keyless JSON against the current public UAI-1 records.
  4. 4Attach the result to implementation or handoff records.Carry the exported result into Conformance Pack, implementation track, changelog, or Project Handoff evidence.
Pack endpointsFetch or download the current packet
curl -s https://uaix.org/wp-json/uaix/v1/conformance-pack
curl -OJ "https://uaix.org/wp-json/uaix/v1/conformance-pack?download=1"

Use the raw JSON route for automation and the download form when the exact packet needs to travel as an attachment.

Version localisee en cours de revue

Cette page n est pas encore disponible comme norme localisee revue. Utilisez la source anglaise faisant autorite pour le langage normatif, l interpretation des schemas, les obligations d implementation et les limites de support.

Ouvrir la source anglaise faisant autorite