Skip to main content
Lerian SLC is the Lerian-owned settlement rail that clears and settles over Núclea’s SLC across the RSFN. You set these variables at deploy time. A service restart applies them. Every Lerian Go service shares a universal backbone — server, datastores, multi-tenancy, telemetry, plugin authentication, and licensing. BYOC configuration essentials documents that backbone once. This page covers only the variables distinctive to Lerian SLC. In the tables below, the Default / Required column shows the default value. A bold qualifier (e.g. Required, Required in production) marks a variable you must set. means no default. A variable marked Sensitive carries credential or key material. Inject it from your secret manager at deploy time. Never commit a value.

Service and runtime

Lerian SLC exposes /health (liveness) and /readyz (readiness) on the main port, plus /version and /metrics. When you enable multi-tenancy, it also exposes GET /readyz/tenant/{id}. See Health and readiness for the probe contract.

Núclea REST transport

This channel submits to Núclea online over mutual TLS. Leave NUCLEA_REST_BASE_URL empty to keep the transport unwired.

RSFN inbound consumer

This channel receives inbound RSFN messages. It also observes XSD conformance.

SFN inbound bus

The SFN bus relays SILOC messages. This path ingests them. The whole family stays inert unless you set SFN_INGEST_ENABLED=true.

Signing sidecar

Lerian SLC signs the SPB security envelope through a stateless signing sidecar. The private key never enters the service process. You select the custody backend per deployment.

Settlement schedule

Lerian SLC gates dispatch to Núclea’s settlement windows and runs a per-tenant schedule worker.
You must declare both credit-window variables, even when you use the standing schedule. The service refuses to start if either value is omitted or blank; it never assumes a credit grade from a default.
Lerian SLC ships a family of per-driver runtime toggles. Each toggle opts one flow into the schedule worker: credit and debit dispatch and forward, anticipation, cancellation, status relay, D+1 confirmation, and stuck-operation alerts. Each is a SCHEDULE_*_ENABLED switch that defaults to false. You opt each one in during homologation, once the per-tenant Núclea material is ready. The cadence and batch knobs follow the *_INTERVAL_SEC / *_BATCH_SIZE / *_PAGE_SIZE pattern.

Webhooks

Lerian SLC can deliver settlement events to a subscriber endpoint. In BYOC the client supplies the credential material through their own Kubernetes secret.