Values shown here are placeholders. Inject credentials and license material from your secret store. Never commit real secrets.
Configuration model
Each component loads bootstrap values from its environment. The SPI, DICT Hub, COB Hub, Pix Automático API, and DICT VSync worker also consume runtime configuration from their Systemplane store after initialization. The mock provider adapter reads its configuration from the environment only and keeps its state in memory. Configure each component separately. Their ports, stores, and required dependencies differ.Shared identity and deployment
PLUGIN_AUTH_ENABLED controls inbound route authentication. PLUGIN_AUTH_HOST is the Access Manager base address used by the shared auth integration and OAuth client-credentials flows. It must be a base address only, without an OAuth path, query, fragment, or embedded credentials. Use https:// outside local development.
The mock provider adapter requires SPI_BASE_URL, PROVIDER_CLIENT_ID, and PROVIDER_CLIENT_SECRET at boot. MOCK_TEST_ENDPOINTS_ENABLED=true turns on test routes that can forge provider callbacks. The mock adapter has no route authorization: keep it unreachable from untrusted callers, whatever this switch says. Do not configure the mock adapter as a production rail.
Persistence and Valkey
Valkey behavior differs by component. SPI, DICT Hub, and COB Hub can degrade selected idempotency or cache paths when you do not configure Valkey. Some SPI, DICT, and COB mutations fail closed with
PIX-0032 when no durable replay backstop exists. DICT VSync treats Valkey as a hard dependency because it coordinates the cross-pod mutation gate. A configured but malformed REDIS_* value fails boot rather than silently selecting a different endpoint.
The Systemplane implementation does not use SYSTEMPLANE_SECRET_MASTER_KEY. Protect Systemplane database access, backups, and disk storage through the deployment environment.
Institution and service integrations
Lerian connectivity adapter
The Lerian connectivity adapter connects Pix Lerian to Lerian SPI. It runs as two components: the adapter API and its configuration writer. The adapter API serves its routes under the/lerian prefix.
The configuration writer copies its variables into the adapter’s runtime configuration store at startup. It does not overwrite a stored value that differs from the default. The adapter API reads its routing and credentials from that store.
In multi-tenant mode, the writer copies nothing. Write the values of each tenant through the writer’s admin API. These are the four callback addresses and their client credential pairs, DICT_CID_FILE_BASE_URL, and the three BRSFN_*_BASE_URL addresses. PLUGIN_AUTH_HOST, the BRSFN_SPI_CLIENT_*, BRSFN_DICT_CLIENT_*, and BRSFN_COB_CLIENT_* pairs, and the signing secrets of the event routes are not tenant values. The adapter API reads them for all tenants from the store at SYSTEMPLANE_POSTGRES_DSN.
When a Lerian SPI surface has no complete credential pair or no
PLUGIN_AUTH_HOST, the adapter does not call that surface. Each event route checks each delivery against the signing secret of its event subscription. The adapter reads these secrets from its runtime configuration, not from the environment. In single-tenant mode, when a subscription has a new signing secret, write that secret to the runtime configuration through the configuration writer’s admin API. A route with no secret refuses every delivery.
DICT VSync
The DICT VSync worker reconciles DICT state and requires its own worker configuration:VSYNC_ENABLED and VSYNC_FILE_RECON_ENABLED can be hot-reloaded through the worker’s runtime configuration. The remaining tuning values are read at boot and require a restart.
Pix Automático API
The Pix Automático API sends settlement commands to the SPI and reads these variables:Streaming and observability
The notification-outbox relay is disabled by default. To enable it, setSTREAMING_ENABLED=true and provide STREAMING_BROKERS. The shared CloudEvents source, when configured, must identify the Pix Lerian service. The component also validates the streaming broker’s TLS/SASL settings and the optional STREAMING_DATASCHEMA_BASE_URL.
Set ENABLE_TELEMETRY=true to turn on OpenTelemetry. The OTEL_* variables configure it. See BYOC configuration for shared telemetry and broker transport parameters.
Health and readiness
Probe paths and route prefixes belong to the component deployment configuration. Do not assume that every component exposes unprefixed/health or /readyz. Use the paths in the release chart and component bootstrap configuration.
