app.meeting-effect-worker

Meeting Effect Worker

Deployable worker for approved CompanyOS, Pactena, and hCircle meeting effects. It claims owner-scoped SQL outbox leases, reloads encrypted meeting state, reproves authority, rollout, approval, and artifact digests, then invokes a provider-neutral delivery port. Failed work uses the runtime's bounded retry and terminal-failure rules.

Set OPA_MEETING_EFFECT_WORKER_COMPOSITION_MODULE to an installed package in the allowlisted @lssm-tech/integration.meeting-effect-worker-* namespace. The module must export a default MeetingEffectWorkerComposition. The executable exposes /healthz, /readyz and /metrics on OPA_MEETING_EFFECT_WORKER_PORT (default 3003). /readyz answers ready, paused (operator kill switch, 200) or not-ready (503: no recent successful cycle) with cumulative totals. /metrics exposes Prometheus counters for effects by status (delivered, retrying, dead_letter, stale), errors by failure code and failed cycles. Each non-empty cycle writes one aggregate JSON log line; a failed cycle is logged by error code and retried with backoff instead of exiting.

The production image includes @lssm-tech/integration.meeting-effect-worker-postgres-http. Set the composition module to that exact package and configure its documented PostgreSQL, BYOK, authority, rollout, and HTTPS provider-delivery boundary variables.

The CompanyOS API can host the same cycle in process as the cron /api/cron/opa-meeting-effects (see the API README). Both hosts share processMeetingEffectLease from @lssm-tech/lib.organization-planning-runtime. Run exactly one host per database: when the API cron is enabled, do not deploy this worker, and vice versa.