Supabase Env
Runtime
Check the runtime before you run the pipeline.
Project Enoch uses these live checks for project creation, voice, and downstream execution.
Live readiness
Runtime Checks
Evaluated on each request from the active server environment.
Database Projects
Database Operator Query
Operator User
Sora Env
R2 Env
Pipeline map
Pipeline Sequence
The live route order from brief to delivery.
Intake
Project creation, operator access, and workspace ownership are grounded in the live Supabase path.
Generation
Scene planning, provider orchestration, and prompt execution stay aligned to the current runtime configuration.
Render
Render jobs and asset persistence depend on the storage, provider, and media pipeline checks below.
Delivery
Publish handoff stays downstream of the same verified project records instead of a disconnected UI shell.
Runtime modules
Enoch Runtime
Enoch provider
Default routeEnoch will fall back to the default provider path exposed by the server runtime.
Enoch voice path
Server audio readyElevenLabs is configured with a selected voice, so Enoch can return server-rendered audio instead of only browser playback.
Planning mode
Inline server modeWorkflow planning stays inside the current Next.js runtime until the Python orchestrator is enabled.
Current state
Current Issues
Blocking path
Sora/OpenAI video provider env/config is invalid. Check OPENAI_API_KEY, OPENAI_VIDEO_BASE_URL, OPENAI_SORA_MODEL, and SORA_DEFAULT_POLL_INTERVAL_MS. Missing required R2 env vars: R2_ACCOUNT_ID, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY, R2_BUCKET. Asset persistence cannot run without them.
Warnings
- R2_PUBLIC_BASE_URL is not set. Completed clips will persist, but the UI will only show bucket/object key instead of a public URL.
Live routes