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

AI Memory

changelog.uai

Records dated package-memory changes, version-affecting edits, public-surface changes, and reviewer-relevant deltas. Required for project/developer packages and release-bound packages.

  • Record UAIX-MEMR-2329
  • Path /en-us/ai-memory/uai-files/changelog-uai/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-MEMR-2329
Surface
AI Memory
Access
Public and linkable

How to use this page

Use this page as the canonical public reference for changelog.uai 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.

Records dated package-memory changes, version-affecting edits, public-surface changes, and reviewer-relevant deltas.

changelog.uai
File.uai/archives/changelog.uai
CategoryEvidence and audit files
Required statusRequired for project/developer packages and release-bound packages
Main readerReceiving AI, release reviewer, owner
Update frequencyWhenever package memory, release posture, public routes, generated exports, or significant source behavior changes.
Human review requirementRequired before release-bound work relies on the changelog.
No-op trigger typeUnrecorded source change, missing date, version mismatch, or release evidence without matching change trail.

What this file is

changelog.uai is a bounded UAIX memory record. It is meant to be read before action, compared against related package files, and updated only through a reviewed package-memory change.

Why necessary

The file keeps this class of knowledge explicit instead of burying it in chat history, private assumptions, or stale generated summaries.

When required

Required for project/developer packages and release-bound packages.

What belongs

  • Accepted current facts for the declared package scope.
  • Source, owner, reviewer, or evidence pointers needed to verify the record.
  • No-op or escalation triggers that protect the package boundary.
  • Compact instructions the next reader can act on without guessing.

What does not belong

  • Raw chat dumps, unresolved brainstorming, or unreviewed generated summaries.
  • Secrets, private credentials, personal data beyond the declared minimum, or unsupported public claims.
  • Rules that belong in a more specific file such as constraints.uai, test-plan.uai, or deployment-memory-and-test-report.uai.
  • Historical notes that should live in archives until reviewed and promoted.

How receiving AI should use it

  • Read memory-maintenance.uai first, then this file when it is in the declared package scope.
  • Compare it with identity.uai, world-context.uai, startup-packet.uai, progress.uai, and the manifest before trusting it as current.
  • Use the no-op trigger as a stop point when the file is missing, stale, contradictory, or outside the declared package profile.
  • Record any update in the right typed `.uai` record and the package changelog when the change affects future agents.

How human reviewer should use it

  • Confirm the file states a concrete required scope rather than a softer invitation to read it.
  • Check that current facts have an owner, evidence path, or review source.
  • Confirm outdated material was moved to archives or replaced with a dated current record.
  • Reject vague language that lets agents ignore package-critical material.

Scenario examples

  • A receiving agent opens a Project Handoff package and uses this record to decide whether work may proceed.
  • A reviewer sees a contradiction between files and uses the no-op trigger to require clarification before release.
  • A maintenance pass promotes a reviewed fact into this file and retires the stale note from active memory.

No-op and human-review triggers

  • Missing file for its declared required scope.
  • Conflict with universal launch-baseline files.
  • Current package work depends on an unreviewed fact.
  • The file claims authority beyond its declared profile, mode, package type, or capability.

Update and maintenance rules

  • Keep entries short enough to be read at startup.
  • Date meaningful updates and record why the change happened.
  • Move stale detail to archives after accepted current facts are captured.
  • Align generated exports and human-facing memory after changes.

Relationship to other .uai files

  • identity.uai names the package and owner.
  • world-context.uai locates the operating environment.
  • memory-maintenance.uai governs lifecycle, required active instruction anchors, validation behavior, and memory write safety.
  • totem.uai and taboo.uai are default guardrails to read and obey; modifications require exact human artifact-and-operation authorization.
  • totem.uai, taboo.uai, and talisman.uai are default active instructions; mutation requires exact human artifact-and-operation authorization.
  • startup-packet.uai points to the active `.uai/` read order, and progress.uai carries reviewed current status.

Minimal example

Code example
# changelog.uai
file: .uai/archives/changelog.uai
required_status: Required for project/developer packages and release-bound packages
owner: human-reviewed owner or steward
current_state: accepted current record for this package scope
no_op_trigger: Unrecorded source change, missing date, version mismatch, or release evidence without matching change trail.
evidence: link or local pointer to reviewed source
review_status: current until superseded by owner review

Completeness checklist

  • Required status names the exact scope.
  • Owner or reviewer is clear.
  • Current facts match related .uai files.
  • No-op triggers are concrete.
  • Stale material has an archive or replacement path.

Common mistakes

  • Using softer language that agents treat as ignorable.
  • Mixing current truth with raw source intake.
  • Letting the file contradict another required record.
  • Leaving no review path for high-impact changes.

Machine-readable digest

Agents should treat this digest as page-orientation evidence, not runtime authority.