# Match the guide to your code.

> Use a reproducible source snapshot for these guides and the matching published reference for crate dependencies.

- Canonical page: https://www.poulpy.dev/docs/versions/
- Poulpy version: 0.9.0
- Source revision: [`7dd13e6aa9808982f5355fb6acb70ca434de4e35`](https://github.com/poulpy-fhe/poulpy/tree/7dd13e6aa9808982f5355fb6acb70ca434de4e35)
- Documentation reviewed: 2026-10-08
- Audience: For application developers

## Two references

The website documents Poulpy version **0.9.0** at source revision [`7dd13e6`](https://github.com/poulpy-fhe/poulpy/tree/7dd13e6aa9808982f5355fb6acb70ca434de4e35), the 0.9.0 release revision dated 8 October 2026. The guides, downloadable examples, and linked source use this same baseline.

```sh
git clone https://github.com/poulpy-fhe/poulpy.git
cd poulpy
git checkout 7dd13e6aa9808982f5355fb6acb70ca434de4e35
```

The snapshot pins `nightly-2026-05-14` in `rust-toolchain.toml`. Run commands from the repository root. `--locked` keeps the checked-in dependency resolution.

## Published API documentation

[API reference](https://www.poulpy.dev/docs/api-reference/) links target 0.9.0. For the source snapshot, generate the matching documentation:

```sh
cargo doc --locked --no-deps -p poulpy-hal -p poulpy-core -p poulpy-cpu-portable -p poulpy-ckks -p poulpy-bin-fhe --features poulpy-cpu-portable/enable-ckks --open
```

## Published documentation checks

These observations record gaps between the source and published rustdoc.

| Surface | Last checked | How to proceed |
| --- | --- | --- |
| AVX2 crate reference | 10 September 2026: docs.rs reports a failed 0.8.3 build; not yet rechecked for 0.9.0 | Use the pinned source and the local documentation command on [API reference](https://www.poulpy.dev/docs/api-reference/#backend-apis) |

## Updating an application

Keep the Cargo lockfile and the source revision or exact dependency versions with your application. Re-run its correctness checks, parameter analysis, and benchmarks when updating. Do not assume prepared backend layouts or serialized application envelopes are compatible across revisions without an explicit contract.