UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIXUniversal Artificial Intelligence ExchangePublic standards publication
CurrentUAI-1 v1.0
  • Current versionUAI-1 v1.0
  • Plain-English definitionOpen message format for auditable AI-to-AI exchange
  • Current attributionMichael Kappel and the UAIX contributors
  • Start hereGet Started, Project Handoff, UAI-1, validator, roadmap, and changelog

Governance

Analytics

Current public posture for measurement limits, telemetry-significant release handling, and analytics disclosure across the UAIX launch surface.

  • Record UAIX-GOVR-0076
  • Path /en-us/governance/analytics/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-GOVR-0076
Surface
Governance
Access
Public and linkable

How to use this page

Use this page as the canonical public reference for Analytics and its standards-facing content.

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.

What this page covers

Use this page for the current public posture on analytics and telemetry across the UAIX launch surface. It explains how measurement-related behavior should be scoped, disclosed through release notes, and kept consistent with what the public site actually does.

Current published analytics posture

  • Current analytics posture is limited to what is explicitly published on the site. Do not imply a broader advertising, cross-site profiling, or consent program that has not yet been made public.
  • If instrumentation or telemetry-relevant behavior changes, treat that as trust-significant release work and record it in the public release trail instead of leaving it implicit.
  • Use observable front-end behavior, canonical public pages, and release notes as the current review surface for analytics-significant changes.

What reviewers should verify now

  1. Check whether any measurement-related behavior is obvious from the public page surface and consistent with published wording.
  2. Check whether embeds, scripts, forms, downloads, or machine-facing routes changed in a way that expands data collection or introduces new telemetry-significant behavior.
  3. Check whether the same change also affects Privacy and Data or Accessibility so the release record stays coordinated.
  4. Check whether the release trail says what changed before downstream readers are asked to trust the new state.

What is not claimed

  • UAIX does not currently publish an analytics dashboard, a broader disclosure portal, an ad-tech stack, or a consent-management platform.
  • Do not infer audience-profiling, retargeting, or cross-site tracking from the current public launch surface unless it is explicitly published on canonical UAIX pages.
  • Do not imply a broader product-analytics program across unpublished tools, partner channels, or account systems that are not part of the current public site.

How analytics-significant changes should travel

  • Update the public wording and the observable front-end behavior together.
  • Use Policy and Security when the same release also affects licensing or security-significant posture.
  • Record the change through Governance, the Changelog, and News so another reviewer can resolve the same public record later.
  • Use References and Contributors when the next step is handing the current policy posture to someone else without private context.

Next step

Continue to Privacy and Data if the question is about public data exposure or intake posture, or to Policy and Security when the next step is the broader trust-policy hub.