> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peoplebot.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Releases and source identity

> Choose the right artifacts and keep documentation tied to the code you use.

These guides cover **framework release 0.1.0a3**, published as an experimental prerelease. Its distribution source commit is:

```text theme={null}
14b15c8bfb0b4ce9f0d827fe018b42af04969945
```

## Three useful identifiers

| Identifier               | What it tells you                                         |
| ------------------------ | --------------------------------------------------------- |
| Version/tag              | Which named release you intend to install                 |
| Artifact SHA-256         | Whether the downloaded bytes match the published checksum |
| Full distribution commit | Which Git source State the release identifies             |

A checksum is not a Git commit. A branch can move. A version name alone does not establish that installed driver bytes match adopted Git source. Keep all three forms of evidence when adopting a release.

## Download the complete set

The [0.1.0a3 release page](https://github.com/peoplebot-framework/peoplebot-releases/releases/tag/v0.1.0a3) provides the wheel, matching source archive, public provenance, and `SHA256SUMS`. [Installation](/guides/install) describes verification before use.

The GitHub release body confirms publication. Some files in the pinned distribution describe the earlier candidate-preparation stage. Those files are historical snapshots; their preparation-time wording does not override the later published release record. Provenance assets retain their reviewed preparation-time flags.

## Different components can have different releases

The repository also has a separately named `syslog-onboarding-v0.1.0` release. It is not a newer version of the PeopleBot Python framework. Choose a tag by component and purpose instead of assuming the most recently listed release is the framework installer.

## Documentation changes

The documentation site can change without a new framework package. Behavioral claims in these pages remain tied to 0.1.0a3 until a later public framework version is explicitly documented. An improved guide does not add a missing runtime feature to an already published wheel.

Earlier 0.1.0a1 and 0.1.0a2 distributions remain historical releases. Use the release page and its adoption notes when inspecting an older installation.