Skip to content

Known Gaps

Last refreshed: 2026-07-27

Documentation

  • Previous docs are under docs/_stale and may conflict with current code.
  • 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.
  • PresentationConfig v2 compilation, immutable revision storage, and immutable package assembly are implemented. ANU-14 now adds exact editor embedding, manual/autosave revision append, durable conflict recovery, packaged Signal/Paper templates, structured AI surface edits, and a coordinated three-surface saved-revision Web preview.
  • Simple Scene Editor recompilation is currently blocked while local scene edits are pending before Bento opens. A richer warning/confirmation flow for recompiling an already editor-authored accepted revision remains a UX hardening opportunity.
  • CMS consumer fixtures are verified locally. Python and Unity consumption of the exact package remains owned by their repository-specific follow-up work.

Anuva Upgrade

  • Workflow-support contracts, stage gate helpers, source adapters, and repository/orchestration scaffolding exist. The active compiled output is PresentationConfig v2.
  • 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

  • The Compose stack covers the CMS web app, Postgres/pgvector, pgAdmin, and the RAG and presentation workers; S3, providers, Python, Unity, and the upgrade-path Anuva worker remain external or manual dependencies.
  • Worker scripts poll queues in-process. There is no separate durable queue service documented in current code.
  • The accepted ANU-7 local cutover is machine-local and depends on ignored .env.compose state plus the persistent named volume. It is not a production migration or a substitute for repeating parity after future source refreshes.
  • 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.