> For the complete documentation index, see [llms.txt](https://docs.pal.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pal.aic.io/engineering-and-delivery/release-and-support.md).

# Release and support

PAL.NET releases are tied to an upstream compatibility baseline, generated evidence, licensing, package provenance, and customer documentation.

## Release checklist

* [ ] Source revision, package version, API gateway minimum, retrieval time, and specification hash are recorded.
* [ ] Models and platform bindings were regenerated deterministically.
* [ ] Generated files compile with the supported .NET/C# settings.
* [ ] All public operations have mappings or approved documented exceptions.
* [ ] Gap report is conclusive and matches the release claim.
* [ ] Pagination, streaming, cancellation, errors, retries, scopes, and licensing evidence pass.
* [ ] Unit, architecture, integration, security, concurrency, and performance tests pass.
* [ ] Package metadata, signatures, hashes, licence configuration, and offline bundle contents are verified.
* [ ] Customer documentation, examples, migration notes, and preview-surface notes are updated.

## Versioning

Use semantic versioning for PAL.NET packages. Identify upstream baseline changes, generated contract changes, new capabilities, changed scopes, preview operations, compatibility exceptions, and migration requirements in release notes.

Generated public contracts are part of the compatibility surface. Removing or renaming a generated model, operation, property, enum member, or request builder can be a breaking change even if the HTTP route remains available.

## Preview capabilities

{% hint style="warning" %}
Preview operations must be labeled in documentation and release evidence. AIP Agent continuation currently uses a documented upstream preview operation. Do not present preview behavior as a stable long-term contract without an explicit release decision.
{% endhint %}

## Support evidence

For an upstream support case, capture:

* PAL.NET version and upstream baseline;
* operation ID and capability;
* non-secret classification and HTTP status;
* upstream diagnostic ID;
* attempt count and retry exhaustion;
* redacted request shape and relevant page/token state.

{% hint style="danger" %}
Never attach access tokens, client secrets, private keys, entitlement contents, or unredacted payloads.
{% endhint %}

## Distribution

Deliver through the authorised private feed, offline bundle, or another controlled AIC channel. Keep the package provenance, compatibility manifests, licence requirements, and migration notes alongside the release artefacts.