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

## Read verified changes

Release notes give you a dated, focused view of changes that have been checked for this public page. Each entry names what changed, where it applies, and which visible result supports the description.

## Read the scope

An entry may describe a product surface, documentation area, version, audience, or observed behavior. Read that scope before applying the note to another part of Lithi. A change to one page is not a statement about every page.

Dates belong to the change being described. When more than one date matters, the entry labels the relevant event. A missing or conflicting date should remain visible rather than being replaced with today’s date.

## Keep evidence in context

Entries distinguish a reviewed source change, a successful check, a named release, and an observed result. These stages answer different questions. A checked change is not automatically available everywhere, and an observed result does not broaden the entry’s stated scope.

When no verified entries are available, the page says so. It does not invent a feature, borrow a date, or turn an expected change into an announcement.

For installation and identity guidance, [read how to install and verify Lithi for Mac](/docs/it-deployment/install).