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

# August 2026

> Documentation updates published in August 2026 for Matcher, Flowker, Pix, Lerian Console, and Platform, grouped by required customer action.

Updates are grouped by required customer action. Product filters show only the areas that affect your integration. See [News](/en/news/news) for impact definitions.

## Review recommended

***

<Update label="August 10th, 2026" tags={["Lerian Console"]}>
  ### [Lerian Console deletion contract](/en/news/2026/august/console-deletion-contract)

  **What changed**

  The documentation now correctly states that deleting a Console user or application permanently removes it and cannot be undone. Application details show the name, description, ClientId, and ClientSecret; they do not show scopes or redirect URIs.

  **Who is affected**

  Teams that administer users or applications in Lerian Console.

  **What you need to do**

  Review access-management runbooks before your next deletion. Do not rely on application details as a source of scope or redirect URI data.
</Update>

<Update label="August 10th, 2026" tags={["Platform"]}>
  ### [Helm chart coverage for BYOC deployments](/en/news/2026/august/helm-chart-coverage)

  **What changed**

  Deployment documentation now correctly states that official Helm charts are available for the products and platform components supported through Lerian’s Helm repository; it no longer states that every product has an official chart.

  **Who is affected**

  Teams planning or operating BYOC deployments with Helm.

  **What you need to do**

  Confirm chart availability for your target product or platform component before planning a BYOC deployment.
</Update>

## Action required

***

<Update label="August 10th, 2026" tags={["Matcher"]}>
  ### [Matcher error and idempotency contract](/en/news/2026/august/matcher-error-and-idempotency-contract)

  **What changed**

  The documentation now correctly describes Matcher’s RFC 9457 error envelope and idempotency-key constraints and retry behavior. Runtime behavior did not change.

  **Who is affected**

  Teams integrating with the Matcher API.

  **What you need to do**

  Align error parsing and generated idempotency keys with the documented contract before your next client release.
</Update>

<Update label="August 10th, 2026" tags={["Pix"]}>
  ### [SPI operations PII startup configuration](/en/news/2026/august/spi-operations-pii-startup-configuration)

  **What changed**

  The documentation now correctly states that the SPI service requires `SPI_OPERATIONS_PII_ENCRYPTION_KEY` to be a valid AES-256 key and `SPI_OPERATIONS_BLIND_INDEX_PEPPER` to contain at least 32 characters in every environment. Missing, malformed, or too-short values prevent the service from starting.

  **Who is affected**

  Teams deploying or operating the SPI service for Pix operations.

  **What you need to do**

  Before the next SPI start or redeployment, verify that both values are supplied through your secret manager and meet the documented requirements. Do not commit or log either value.
</Update>

<Update label="August 10th, 2026" tags={["Flowker"]}>
  ### [Flowker scheduler Redis isolation configuration](/en/news/2026/august/flowker-scheduler-redis-isolation)

  **What changed**

  The documentation now correctly states that the Flowker scheduler has its own Redis configuration, but startup does not enforce isolation from the Redis used for tenant lifecycle events. Operators must provide a dedicated Redis instance or, when sharing an instance, a different logical database index.

  **Who is affected**

  Teams running Flowker workers with scheduled workflows enabled.

  **What you need to do**

  Verify the scheduler Redis settings before enabling or continuing to run scheduled workflows. Point the scheduler to a dedicated Redis instance, or configure a logical database index that tenant lifecycle events do not use.
</Update>

## Product index

***

| Product area       | August updates                                                                                                                                                                                                                         |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Matcher**        | The error reference now correctly documents the RFC 9457 envelope (`title`, `status`, `detail`, `code`, and optional `errors`) and idempotency-key constraints and retry behavior. Runtime behavior did not change.                    |
| **Flowker**        | Scheduler Redis isolation is an operator configuration requirement: use a dedicated Redis instance or a logical database index separate from tenant lifecycle events. Documentation correction only — runtime behavior did not change. |
| **Pix**            | SPI operations PII requires a valid AES-256 key and a blind-index pepper with at least 32 characters in every environment; missing or invalid values prevent startup. Documentation correction only — runtime behavior did not change. |
| **Lerian Console** | User and application deletion is permanent and irreversible; application details show name, description, ClientId, and ClientSecret, not scopes or redirect URIs. Documentation correction only.                                       |
| **Platform**       | Official Helm charts cover products and platform components supported through Lerian’s Helm repository, not every product. Documentation correction only.                                                                              |