AIM 1.20.0

AIM 1.20.0

AIM now stands for Attribution & Ingestion Manifest for Music.

Version 1.20.0 is the first release that fully aligns AIM with its updated role as a music packaging and workflow container for downstream attribution, ingestion, disclosure, and delivery workflows.

This release moves AIM beyond a general interchange framing and establishes a clearer foundation for:

• distributor and DSP ingestion workflows
• AI attribution and disclosure packaging
• provenance-aware delivery
• validator-driven interoperability
• example-first adoption

Highlights

New positioning

AIM is now defined as Attribution & Ingestion Manifest for Music.

This name better matches the current scope of the format:

• packaging rather than DAW session interchange
• downstream ingestion rather than bidirectional project exchange
• attribution, provenance, rights, and disclosure as first-class concerns

New AIM 1.20.0 specification

This release adds the new public specification file:

• spec/AIM_1.20.0.md

Key additions in 1.20.0 include:

• AI node classes for edit graphs
• provenance-oriented process metadata
• package-level rights and external identity fields
• profile-based conformance
• aim.disclosure_ready.v1
• aim.signed.v1
• updated compatibility guidance for the 1.x line

New bundled example packages

This release expands the examples set with packages that reflect the 1.20.0 model, including:

• multitrack delivery
• web preview delivery
• karaoke scoring
• AI-editable packaging
• disclosure-ready AI-generated packaging
• disclosure-ready no-AI packaging
• signed-attached packaging

Updated example validator

The bundled non-normative example checker has been updated to validate the 1.20.0 example set and the new profile-oriented packaging model.

Why this release matters

AIM 1.20.0 is designed to make one thing clearer:

AIM packages are meant to be declared once and consumed across downstream systems.

That means a package can now serve as a structured source for:

• attribution metadata
• ingestion preparation
• provenance attachment
• disclosure workflows
• preview and review tooling

The release is especially important for workflows that need a stable packaging layer between content creation and downstream delivery.

Included in this release

This release includes:

• the AIM 1.20.0 specification
• updated repository documentation
• updated examples
• updated example validation tooling
• new release and announcement materials

Compatibility

AIM 1.20.0 continues the 1.x line and is intended to evolve without breaking the core package contract of the series.

Earlier example content and 1.19.2 materials remain in the repository for historical reference.

Upgrade guidance

If you are already using the 1.19.2 repository layout:

• keep the repository structure unchanged
• adopt spec/AIM_1.20.0.md as the new current specification
• use the updated example set as the reference baseline
• use the updated validator output as the bundled validation reference

Thanks

Thank you to everyone helping shape AIM into a clearer, more interoperable, and more deployment-ready format for music attribution and ingestion workflows.

AIM 1.19.2 Final

AIM 1.19.2 Final is the initial public specification release of AIM (Audio Interchange for Music).

This release publishes the AIM specification repository as a spec-first release, including:

• the AIM 1.19.2 specification
• repository documentation and governance files
• example AIM packages
• a small non-normative example validation script

Highlights in AIM 1.19.2 include:

• synchronized multitrack package structure and manifest authority rules
• karaoke scoring references for lyrics, pitch, and rhythm
• AI-editable graph and patch structures
• web streaming preview support
• stricter frame_hz validation behavior
• score_target consistency rules
• path safety hardening
• capabilities lowercase normalization
• stricter peaks.bin error handling

Repository notes:

• This is the public specification release.
• Player, converter, and editor implementations are not part of this release.
• Example packages and scripts are provided as supporting materials and are not normative.

Contact:

• General: hello@vtubermate.com
• Security: security@vtubermate.com