Project intake creates session workspaces with treatment, logline, outline, bibles, artifacts, assets, score history, memory, and usage events.

Dashboard plus primary Analyze and Write links follow the current or latest project and fall back cleanly.

Server-side AI, Write, and plan-gated tool-calling routes settle usage before Library persistence and return project-specific local artifacts until OpenAI is connected.

Project-specific reports, score dials, proprietary metrics, First Ten Pull, character diagnostics, scene health, market comps, score history, and improvement panels are visible.

Script Intelligence Score is calculated server-side from validated rubric inputs.

TXT, Fountain, PDF, DOCX, and FDX-style intake can parse, chunk, plan-gate storage, upload parsed source files to Supabase Storage, and persist indexed memory for authenticated UUID-backed projects.

Project-specific file manifests track uploads, parsing, plan-gated storage, Storage object paths, and memory indexing state, then persist through project_assets for authenticated UUID-backed projects.

PDF, Fountain, and FDX-style exports run server-side, save project-attached export artifacts to Library, and upload generated payloads to private Supabase Storage for authenticated UUID-backed projects.

Deterministic memory search indexes project sources and uploaded chunks locally, then switches /api/retrieval/search to Supabase project_memory_chunks plus pgvector RPC search for authenticated UUID-backed projects.

Project-grounded responses use plan-aware usage gates, safety checks, memory retrieval, and mock/live-ready AI routing.

Character and world bible entries can be viewed and safely updated, then persisted through Supabase story_bibles for authenticated UUID-backed projects.

Normalized title metadata, provider IDs, Story DNA profiles, availability snapshots, provider sync jobs, similarity runs, matches, and score audit logs are modeled in Supabase with RLS and explicit grants.

TMDb is normalized through the existing metadata client; OMDb, TheTVDB, and Watchmode have deferred adapters ready for live calls in the next phase.

Market Heat and comp signals run from curated data without keys, then use TMDB search, details, genre, and keyword metadata with safe fallback when TMDB_API_KEY is configured.

Generated and fallback Library documents use project-specific bodies with version history, plan-aware edits, duplicate saves, private Library Storage copies, and storage usage events.

Write workspace draft history is project-specific, plan-gated draft saves record storage usage, local saves remain available for session comparison, and Writer's Room compare shows draft deltas.

Re-analysis appends score records for actual improvement tracking and switches to Supabase analysis_reports for authenticated UUID-backed projects.

Projected lift, actual lift, before/after reports, report body deltas, and rewrite history are unified across runtime and Supabase-backed score/decision state.

Project-specific writing tool history records usage-ready skill runs and switches to Supabase skill_runs for authenticated UUID-backed projects.

Billing usage records analysis, writing, export, project, and storage events with project-filtered activity; authenticated Supabase requests read and write the live usage_records table.

Account can show browser session state and request magic-link sign-in when Supabase public credentials are configured.

A local no-credential verifier checks schema tables, RLS, grants, storage buckets, vector memory, and setup-check coverage before applying SQL.

An explicit DATABASE_URL-only helper can apply supabase/schema.sql through psql and parse supabase/setup-check.sql without printing credentials.

A read-only SQL check can verify extensions, tables, RLS, grants, buckets, storage policy, and project memory RPC after schema setup.

Stripe setup metadata lists Checkout, portal, webhook, recurring Price env names, event types, and missing setup names without exposing secrets.

An explicit STRIPE_SECRET_KEY-only helper can reuse or create the Analyzer and Full Access recurring monthly Prices and print only Price IDs for environment setup.

A local no-credential verifier checks billing plans, recurring Price env names, Checkout, portal, webhook events, lifecycle persistence, CI, and docs.

A no-secret checklist command shows which non-OpenAI values are ready to copy into Vercel or Railway and keeps OpenAI separated as the last setup group.

A local no-credential verifier checks Vercel config, Railway config, health endpoint, smoke checks, CI wiring, hosted URL setup, and docs.

Rewrite priorities can be accepted or rejected with projected improvement tracking and Supabase recommendation_decisions persistence.

Project-specific graph nodes, run history, locally started plan-aware runs, step status, and Supabase workflow_runs persistence are wired for authenticated UUID-backed projects.

Project-specific background queues cover plan-gated large analysis, document indexing, comp research, report generation, and memory rebuilds.

Versioned deterministic policy checks run before AI and writing-tool execution, with rule IDs, context, review path, and mitigation guidance.

OpenAI, Stripe, server Supabase, model routing, and provider adapters are marked server-only; browser Supabase auth uses a separate public client.

The 23 requested deliverables are mapped to current implementation evidence, with external access needs separated from code readiness.

A single no-secret command prints the ordered Supabase, Stripe, hosting, GitHub, optional provider, and OpenAI-last handoff without exposing credential values.

A focused setup endpoint lists needed credentials, optional integrations, hosting state, schema file, and the OpenAI-last step.

A deployment-safe system health endpoint summarizes audit, access, hosted URL, and key setup order without exposing secrets.

A no-OpenAI command checks Supabase table, Storage, and pgvector RPC access, Stripe recurring Prices, and hosted health once those credentials are configured.

A single no-key local command runs setup status, external setup verifiers, lint, production build, dependency audit, scope scans, and runtime smoke checks.

A non-mutating checklist command checks local git state, origin remote readiness, GitHub CLI availability, and the production readiness workflow.

A local no-credential verifier checks workflow triggers, read-only permissions, Node setup, all readiness gates, smoke checks, product scope scan, and secret-shape scan.

A repository workflow is ready to run install, lint, setup status, Supabase schema verification, Stripe setup verification, hosting setup verification, GitHub CI verification, build, system smoke, dependency audit, product scope, and secret-shape checks before hosted deploys.

The Next.js production build passes locally and host config files plus hosting verification are present for Vercel and Railway once environment variables are set.

Stripe billing is intentionally deferred; entitlement gates and safe mock checkout behavior remain active until live billing is added.

Database, storage, RLS, and repository layers are ready; mock mode is active without Supabase credentials.

Film and TV index metadata provider.

Film and TV index metadata provider.

Film and TV index metadata provider.

Film and TV index metadata provider.

Future external vector memory provider.

Future external vector memory provider.

Optional project-memory reranking.

Optional advanced document parsing.

Optional advanced document parsing.