> ## 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 *** ### [Access Manager SSO preflight and fixed-organization setup](/en/news/2026/august/access-manager-sso-preflight-static-organization) **What changed** Access Manager documentation now covers non-mutating SSO provider preflight validation and `PLUGIN_AUTH_SSO_STATIC_ORGANIZATION` for a fixed-organization single-tenant BYOC deployment. Do not set the variable with `MULTI_TENANT_ENABLED=true`. **Who is affected** Teams that configure Access Manager SSO, especially single-tenant BYOC deployments. **What you need to do** Use preflight before saving an SSO provider. Evaluate the static-organization option only for a fixed-organization single-tenant deployment. ### [Flowker workflow execution and observability model](/en/news/2026/august/flowker-workflow-execution-observability) **What changed** Flowker documentation now distinguishes workflow-graph execution, recorded processing nodes, and opt-in telemetry. Trigger nodes do not create step records, and the documentation no longer claims a Console execution dashboard. **Who is affected** Teams that operate workflows or consume Flowker execution history and telemetry. **What you need to do** Review runbooks and execution-history consumers. Enable and connect a telemetry backend if you need OpenTelemetry data. ### [Tracer rule-engine performance claim removed](/en/news/2026/august/tracer-rule-engine-performance-contract) **What changed** Tracer documentation no longer presents an unverified guarantee that compiled CEL expressions evaluate in under one millisecond. **Who is affected** Teams that used the prior statement for Tracer performance planning or commitments. **What you need to do** Review sizing and latency commitments. Measure rule evaluation under your own rule sets and load. ### [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. ### [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. ### [Double-entry consistency guidance](/en/news/2026/august/double-entry-consistency-guidance) **What changed** The double-entry guide now states that matching the source total, destination total, and sent value in Midaz is an amount-consistency control. It does not itself prove authorization, classification, or completeness. The debit/source and credit/destination explanation applies to the illustrated transfer, not every account type. **Who is affected** Teams using the guide for Midaz control design, audit evidence, or training. **What you need to do** Review material that treated double-entry balancing as proof that other financial controls passed, and keep those controls separate. ## Action required *** ### [Lender Consignado API and event contract](/en/news/2026/august/lender-consignado-api-and-event-contract) **What changed** The Consignado API replaces `PUT /v1/credentials/dataprev/taxa-mensal` with `PUT /v1/credentials/dataprev/portal-base-url`. The Lender reference adds nine Consignado contract-divergence and compensating-adjustment operations, documents `lender.loan_account.debt_balance_changed`, and corrects guarantee recovery to `lender.guarantee_recovery_cash.allocated`. `CONSIGNADO_ENABLED` now documents its remaining legacy rejected-averbação handling only. **Who is affected** Teams integrating with the Lender Consignado API, consuming its events, or operating the Consignado configuration. **What you need to do** Replace calls to the retired monthly-rate endpoint, validate portal URLs before sending them, update guarantee-recovery subscriptions, and review `CONSIGNADO_ENABLED` runbooks before the next deployment. ### [Matcher activation and fee-conflict contract](/en/news/2026/august/matcher-activation-and-fee-conflict-contract) **What changed** Setup progress now exposes `context.activation.requirement.*` values in `readiness.missing` and `next.requirementId`. An unready activation returns `409` with `MTCH-0103` and those identifiers. Fee-schedule deletion conflicts use `MTCH-0108` and include blocking contexts at `errors.fee-schedule.delete.blocking-contexts`. **Who is affected** Teams that build Matcher setup flows or handle fee-schedule deletion conflicts. **What you need to do** Update client handling to use the public requirement identifiers, `MTCH-0103` problem details, and the documented `MTCH-0108` blocking-context field. ### [CADOC 4111 Reporter template contract](/en/news/2026/august/reporter-cadoc-4111-template-contract) **What changed** The CADOC 4111 guide now matches the tested `registros/registro` XML layout, `YYYY/MM/dd` date format, and balance selection from the latest operation for each account-and-route pair. **Who is affected** Teams using the Reporter CADOC 4111 template or a custom template derived from the previous guide. **What you need to do** Update and validate the template before your next CADOC 4111 submission. Do not sum every historical operation. ### [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. ### [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. ### [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. ## Product index *** | Product area | August updates | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Access Manager** | SSO provider preflight validates configuration without mutation. `PLUGIN_AUTH_SSO_STATIC_ORGANIZATION` is for fixed-organization single-tenant BYOC only and must not be set with multi-tenancy. Documentation update; no runtime change announced. | | **Midaz** | Double-entry balancing validates recorded amount consistency; it is not proof of authorization, classification, or completeness. The debit/source and credit/destination wording is scoped to the illustrated transfer. Documentation correction only. | | **Reporter** | CADOC 4111 now documents the tested `registros/registro` layout, `YYYY/MM/dd` date format, and latest-operation-per-account-and-route balance selection. Update custom templates before the next submission. Documentation correction only. | | **Tracer** | The unverified sub-millisecond CEL evaluation claim was removed. Do not treat the prior statement as an SLA or capacity guarantee. Documentation correction only. | | **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. Setup progress exposes public activation-requirement identifiers and blocked activation returns `MTCH-0103` with those identifiers. Fee-schedule deletion conflicts return `MTCH-0108` with blocking contexts at `errors.fee-schedule.delete.blocking-contexts`. Update client handling before the next integration release. Documentation update; no runtime release announced. | | **Flowker** | Workflow execution follows a graph of nodes and edges. Executed processing nodes create records; trigger nodes do not. Telemetry is opt-in, and the documentation does not claim a Console execution dashboard. Documentation correction only — runtime behavior did not change. Scheduler Redis isolation remains an operator configuration requirement: use a dedicated Redis instance or a logical database index separate from tenant lifecycle events. | | **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. | | **Lender** | Consignado now documents nine contract-divergence and compensating-adjustment operations. Replace the retired monthly-rate endpoint with the HTTPS worker-portal URL endpoint, update guarantee-recovery subscriptions to `lender.guarantee_recovery_cash.allocated`, and review the narrowed `CONSIGNADO_ENABLED` gate. Documentation update; no runtime release announced. |