# Regulatory Tracking, Platform Changelog & API Versioning Policy

Tracking continuous platform enhancements, international regulatory framework updates, and audit capabilities.

## API Versioning and Deprecation Policy
- **Versioning Scheme**: Stable REST endpoints use major-version URL path prefixes (e.g. `/api/v1`). Breaking changes require a new major version path (`/api/v2`).
- **RFC 9745 Deprecation Headers**: Deprecated endpoints emit `Deprecation: @<timestamp>` and `Sunset: <date>` HTTP response headers and a `Link: <...>; rel="deprecation"` header.
- **Advance Sunset Window**: A minimum notice period of 180 days is provided prior to retiring any deprecated endpoint or breaking change.
- **Current Version**: v2.0.0 (Stable). No endpoints are scheduled for deprecation or sunset through at least December 31, 2028.

## Release History
- **v2026.3 (October 2026)**: Global Multi-Jurisdiction Engine & Model Context Protocol (MCP) edge deployment at `/mcp`, multi-tenement spatial density screening, and digital elevation terrain hazard modeling.
- **v2026.2 (August 2026)**: Environmental baseline and protected habitat verification suite (national parks, marine reserves, Natura 2000, sensitive wetlands).
- **v2026.1 (June 2026)**: Foundation pre-submission clearance audit engine, multi-document cross-reconciliation, and predictive review simulation.