VEX Lens Deployment

This guide is for operators deploying the VEX Lens consensus service into a Stella Ops estate.

Supported Scope

VEX Lens deployment follows the Stella Ops 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 VEX Lens image digest.
2. Configure VEX source paths, cache settings, and service credentials through Compose environment files or the approved host secret store.
3. Start VEX Lens through the supported Compose profile or host service manager.
4. Verify health and mapping behavior through the service endpoint and offline fixtures.
5. Record release manifest digest, VEX bundle hash, config hash, and health output in release evidence.

Unsupported Legacy Paths

Do not use Helm installs, Kubernetes scaling, Kubernetes rollouts, pods, or kubectl commands as VEX Lens deployment procedures.

See Also

• VEX Lens Offline Kit — air-gapped bundle creation, transfer, and import.
• VEX Lens architecture — service topology, storage, and consensus pipeline.
• Issuer Directory and Trust — trust configuration that VEX Lens consumes at runtime.