Skip to Content
LYNKORIADocs

Remaining tasks

Engineering work that is not done, in priority order, with next steps and dependencies.

Last updated: 2026-11-13. Items that wait on something outside the repository are in blockers. IDs match the tracker.

P0: before production traffic

IDTaskNext stepsDepends on
SEC-07Apply runtime-role timeoutsApplied automatically by OpenTofu on each environment's first deploy; confirm SHOW statement_timeout as lynkoria_appDatabase access
SEC-02Confirm the client-IP header cannot be spoofedOn staging, send a request with a fake DO-Connecting-IP; the console sign-in audit row must show the real IPStaging
LOAD-01, OPS-01Staging load, restore and rollback drillsSee blockersStaging

P1: launch quality

IDTaskNext stepsDepends on
SEC-06Confirm the scanner image passes the CI Trivy gatePush; fix any fixable high/critical findings in the scanner base like the API's zlib pinCI
TEST-01Clean-project installsInstall each npm package, the Maven artifacts and the Swift package into fresh sample projects and run the quickstartBuilt artifacts
NAT-01..03Native SDKsCompile and test once toolchains exist; add Android instrumentation tests and React Native native-module testsBlockers
DocsKeep docs currentUpdate this tracker, platform status and the changelog with every changenone

P2: improvements

IDTaskNext stepsDepends on
SEC-08Pin the ClamAV image digestReview clamav/clamav:1.4, record its digest in both Compose filesOperator review
SEC-11Tighten console CSPTemplate connect-src with the API origin at build time or per Pages projectnone
FEAT-01Waiting roomsIf a product needs admission control: add a waiting participant state, a host approval endpoint and a socket event; until then, product backends gate join-token issuanceProduct requirement
FEAT-02Offline send queuePersist unsent messages in the client SDK (IndexedDB / platform storage) and replay on reconnect with the same clientMessageIdProduct requirement
ARCH-02HLS/CDN for large audiencesEgress HLS to the bucket, short-lived signed CDN URLs, viewer analyticsREC-01
DEP-01Single-host Compose deploymentProduction-shaped Compose (API, migrate job, scanner, clamd, Caddy) for hosts outside DigitalOcean, with external PostgreSQL/Redis/S3/LiveKit; validate with docker compose config and a TLS staging runDecision that a second deployment target is supported
TEST-02Local Egress testAdd livekit/egress to the local Compose profile and an integration test that records a short room into local storagenone
LoadMore scenariosPresence churn, group-call media, network interruption, scanner and push throughput (load testing)Staging for meaningful numbers

AR effects

Filters, masks and beauty effects are client-side processing of the local camera track before it is published; the server only forwards tracks. The supported approach (ADR 017): web apps attach a LiveKit track processor (@livekit/track-processors for background blur/replacement, or a MediaPipe-based processor for face effects) to the camera track from session.room.localParticipant; native apps use the platform equivalents in the LiveKit Android/iOS SDKs. Lynkoria adds no server component, and effects work with E2EE. A first-class session.setVideoProcessor() wrapper is worth adding only when a product commits to effects.

On this page