API stability

Software, dataset and schema are separately versioned using semantic versions. v0.x contracts may evolve, but stable public IDs should remain stable. Display wording may change without renaming an ID. Deprecate a record or field with explanation and migration guidance before removal; preserve historical release artifacts.

New breaking API contracts should use a new route version. Pin dataset versions/digests in reproducible research and record API/software versions. Compare release notes for new entities, changed relationships, evidence revisions, deprecated fields and breaking changes. Hosted service availability is separate from the perpetual availability of a downloaded, licensed release.