Findings Ledger Deployment

Audience: DevOps operators deploying and upgrading the Findings Ledger service. Purpose: Define the supported, non-Kubernetes deployment model for Findings Ledger and the checklist for capturing release evidence.

Supported scope

Findings Ledger deployment follows the StellaOps non-Kubernetes release model: Docker Compose, the Offline Kit, signed release manifests, and host / service-manager operations.

Kubernetes and Helm deployment instructions are retired.

Deployment checklist

  1. Verify the signed release manifest and image digests. Deploy by digest, not by tag.
  2. Configure Findings Ledger storage, tenant isolation, and service credentials through Compose environment files or the approved host secret store.
  3. Start the service through the supported Compose profile or host service manager.
  4. Run health checks and ledger migration checks.
  5. Record the release manifest digest, config hash, migration result, and health output in release evidence.

Row-Level Security: Tenant isolation is enforced in the database via RLS. When deploying or upgrading, apply the RLS migration as described in the RLS migration guide.

Unsupported legacy paths

Do not create Kubernetes Secrets, run Helm upgrades, inspect pods with kubectl, or publish Kubernetes manifests as Findings Ledger deployment artifacts.