versioning.

Version records define which binaries, contracts, interfaces and services are intended to work together and how upgrades affect integrators and operators.

release identity

Qualified releases should identify the software or protocol version, supported network, deployment or activation point, and any related contract or schema revisions.

compatibility

Reference entries should state whether a release is backward compatible, requires client changes, introduces a migration or changes an interface relied on by applications.

breaking changes

Breaking changes should be called out explicitly with affected interfaces, migration guidance and the last compatible release where applicable.

history

Superseded releases remain documented so historical transactions, events and application behavior can be interpreted using the rules active at that time.