Skip to content

Known Gaps

Last refreshed: 2026-05-21

Documentation

  • Previous docs are under docs/_stale and may conflict with current code.
  • .env.example does not currently list all active provider and runtime keys observed in .env.
  • Upgrade target docs were moved to stale; current upgrade intent should now be represented through docs/core, docs/state, code, and new change folders.
flowchart TD
  gaps["Known gaps"] --> docs["📚 Documentation drift"]
  gaps --> presentation["🎬 Presentation generation"]
  gaps --> upgrade["🧬 Anuva upgrade"]
  gaps --> rag["🔎 RAG/source model"]
  gaps --> billing["💳 Billing semantics"]
  gaps --> infra["⚙️ Infrastructure assumptions"]

Presentation Generation

  • Legacy UI-bound generation logic remains large and central in src/app/(frontend)/app/presentation/actions.ts.
  • The current create UI uses presentationVideoWorkflow, and prompt text has moved out of Payload prompt records into code-owned Mastra builders. Some compatibility action code remains until the old direct generation path can be retired.
  • Scene visuals now start from persisted Image Gen prompts and asynchronous worker jobs. Uploaded visuals are manual Scene Editor replacements rather than automatic scene assignments.
  • Render/final video readiness depends on multiple persisted state fields; stale-state regressions are a high-risk area.

Anuva Upgrade

  • v1 contracts, stage gate helpers, source adapters, and repository/orchestration scaffolding exist.
  • Payload V1 upgrade collections have been removed; durable persistence for AnuvaRepository is deferred and needs a repository storage design before upgrade runtime state can survive process restarts.
  • Full A0-A8 agent and W0-W8 workflow target coverage should be verified before being described as complete.
  • RSS and source adapter support exists at lower layers, but product UI coverage may be narrower.

RAG

  • Product RAG source types and Anuva v1 source adapter types are not the same abstraction.
  • Web source normalization exists and is tested, but source-specific policies and product UI affordances should be checked before expanding.

Billing

  • Gold Coin metering is implemented for AI interactions.
  • Silver Coin behavior appears plan-level in current code; broader wallet semantics should not be assumed.
  • Zoho webhook idempotency is tested, but live provider behavior still depends on configured webhook secrets and payload shapes.

Infrastructure

  • Local services are not guaranteed by Docker config. Active .env points at hosted services.
  • Worker scripts poll queues in-process. There is no separate durable queue service documented in current code.
  • Because the active environment uses a Supabase pooler connection, Payload schema push is disabled and schema drift must be resolved with explicit migrations. Skipping pnpm payload migrate after collection changes can break admin/runtime reads even when generated types are current.
  • External render-worker upload and download presigning currently assumes path-style S3-compatible object URLs that match the configured bucket prefixes. Revalidate this against production object storage before treating it as fully hardened.