Developers

Available

Changelog

A planned changelog format for product, API, and documentation changes.

A changelog should help users understand what changed, when it changed, and whether it affects active features or planned documentation.

What this means

Changes should separate production-accepted features from local planning or documentation.
API contract changes require explicit backend/OpenAPI phases, not casual public copy changes.
Public changelogs should avoid exposing secrets, internal credentials, or private incident details.

How AINMAX supports this

Current phase reports and closeout documents already record accepted changes.
Resources content can explain how a future public changelog should behave.
Documentation updates remain separate from backend/API changes.

What is available now

Static Changelog resource content.
Phase reports in repository artifacts and documentation.
No automatic public release feed from production systems.

What is planned

Public changelog structure for product milestones.
Separate API changelog if API contracts change in accepted phases.
Release notes content batch in a future Resources phase.

Privacy / safety note

This page does not change API contracts, publish internal operational details, or expose secrets/tokens.