# Versioning

# Versioning Policy

AIEP is intended to be stable. The web is built on interfaces that persist. AIEP therefore treats versioning as a core discipline.

## What gets versioned

AIEP versions:
- schemas
- policy documents
- registry surfaces where applicable
- canon rules

## Compatibility

AIEP aims to be backward compatible where possible. Breaking changes should be introduced as new versions rather than silent mutations.

A practical rule is simple:
- publish new endpoints for new versions
- keep old endpoints accessible or redirected
- never change the meaning of an existing version silently

## Why this matters for AI

AI systems need stable retrieval behaviour. Versioning allows retrieval tools to remain deterministic even as the ecosystem evolves.