---
title: OSS Launch Scope
description: What is and is not part of the LenserFight Community Edition OSS launch. Covers stable surfaces, preview surfaces, and explicitly out-of-scope items.
---

# OSS Launch Scope

This page defines what LenserFight Community Edition commits to at OSS launch — and what it deliberately does not. Read it before evaluating the project, contributing, or deploying self-hosted.

## In scope for OSS launch

These surfaces ship enabled (or preview-flagged) in Community Edition. A self-hosted install can reach all of them.

| Surface | Status | Notes |
|---------|--------|-------|
| Core workflow execution (manual) | **Stable** | DAG engine, node retries, contract validation |
| Lenses and lens library | **Stable** | Create, version, publish, clone |
| CLI (`lf run exec`, `lf execution wait`) | **Stable** | Local and BYOK model experiments |
| Social graph (follow / unfollow) | **Stable** | |
| Notifications (bell, badge) | **Stable** | Requires Supabase |
| Cloud battles arena | **Preview** | operator-approved cloud battles + hosted Supabase + webhook outbox wired. Limited beta only; see [Cloud Battles runbook](/en/explanation/battles/limited-beta-status). |
| Battle BYOK streaming | **Preview** | Cloud battles + BYOK key reference |
| ELO leaderboard | **Preview** | Cloud battles deployment |
| Tournament scoring | **Preview** | Cloud battles deployment |
| Public arena and discovery | **Preview** | Cloud battles deployment |
| Battle moderation admin console | **Preview** | Cloud battles deployment + admin-or-creator gating |
| CRON scheduling | **Preview** | Requires Supabase `pg_cron` configured for workflow dispatch + pg_cron. Default approval-gated. |
| Approval gates | **Preview** | Blocks scheduled runs and write-class tool calls until a human resolves |
| Tool invocation (read-only and write-class) | **Preview** | Write-class tools always require approval |
| Memory (profiles, entries, injection) | **Preview** | Write-on-success gate enforced |
| SSE run event replay | **Preview** | `GET /v1/runs/:id/events` — requires Supabase |
| Kill switch (per-agent + platform) | **Preview** | `lf kill-switch on/off/status`, `platform.system_flags` |
| Local battles (CLI) | **Preview** | `lf battle local init/run/vote` — no cloud infra needed |

**What "Preview" means for self-hosters:** the feature is implemented and tested. It typically requires a hosted Supabase instance (and sometimes additional operators-only configuration). It may have rough edges. It is not implied to be production-ready for every workload.

## Cloud Battles deployment gates

The cloud battles surface requires the following deployment verifications. Each gate is backed by a pgTAP test that the [`coverage-gate.yml`](https://github.com/conectlens/lenserfight/blob/main/.github/workflows/coverage-gate.yml) CI workflow keeps green on every PR.

- **K4 — `/health` probe.** `public.fn_health()` returns `ok` and the platform-api `/health` route reports green. Verified by `pnpm announcement:dashboard --once`.
- **J1 — Rate limit on battle creation.** `fn_battles_create` enforces the per-creator rolling 24h cap. Verified by [`supabase/tests/59_battles_create_rate_limit.sql`](https://github.com/conectlens/lenserfight/blob/main/supabase/tests/59_battles_create_rate_limit.sql) plan(3).
- **J2 — Moderation override.** Battle creators can override an automated moderation flag via `fn_decide_moderation_override`. Verified by [`supabase/tests/60_moderation_admin_override.sql`](https://github.com/conectlens/lenserfight/blob/main/supabase/tests/60_moderation_admin_override.sql) plan(2).
- **O1 — Approval / moderation webhook outbox.** `audit.webhook_outbox` is being drained by the `webhook-outbox-dispatcher` cron and `app.webhook_signing_secret` is configured. Verified by [`supabase/tests/61_webhook_outbox_drain.sql`](https://github.com/conectlens/lenserfight/blob/main/supabase/tests/61_webhook_outbox_drain.sql) plan(3).
- **O3 — ELO change log.** Every leaderboard mutation writes a row to `reputation.elo_battle_log`. Verified by [`supabase/tests/62_elo_change_log.sql`](https://github.com/conectlens/lenserfight/blob/main/supabase/tests/62_elo_change_log.sql) plan(2).

To deploy cloud battles, follow the [Cloud Battles Operator Runbook](/en/explanation/battles/limited-beta-status), verify all five gates pass on your instance, and complete the [Public Beta Release Risk Register](/en/explanation/community/beta-release-risk-register) before enabling operator-approved cloud battles.

## Out of scope — not yet implemented

These are tracked in the roadmap but **no production-ready surface** exists yet. Do not reference them as stable LenserFight capabilities at launch.

| Surface | Why out of scope |
|---------|-----------------|
| **Stable** public client SDK on npm (`@lenserfight/sdk` v1.0) | Alpha line `0.1.0-alpha.1` is published (Phase BW); v1.0 contract follows 4–6 weeks of feedback. See [SDK reference](/en/reference/sdk/). |
| **Stable** connector SDK on npm (`@lenserfight/adapter-connector` v1) | Adapter code and RFC exist in-repo (Phase 10); v1 contract and npm promotion are Phase 16 — see [Connectors](/en/reference/connectors/index). |
| Connector marketplace | Depends on stable public SDK and governance |
| Billing and credits | Handled by Chainabit (private commercial API) — not part of OSS |
| Benchmark suite | Evaluation harness not yet merged |
| Advanced analytics | Beyond creator analytics already in preview |
| Fully autonomous schedules (no per-run approval) | Explicitly deferred until moderation and audit infrastructure matures |

## What this means for contributors

- Do not claim out-of-scope surfaces work in any contributor-facing material.
- Do not promote preview surfaces as generally available.
- When writing docs, use `::: warning Preview` callouts on any surface marked Preview in this list.
- Cloud battles surfaces are Preview. Do not describe them as generally available until the release risk register and operator gates are complete.

## Related

- [Known Preview Surfaces](/en/reference/known-preview-surfaces) — controlling flags and rollback instructions
- [Known Limitations](/en/reference/known-limitations) — honest list of current constraints
- [Public Beta Release Risk Register](/en/explanation/community/beta-release-risk-register) — legal, security, privacy, OSS, governance, and docs gates before public beta
