PR0TA Documentation
Current operating guide for PR0TA's project-based generative production platform, from screenplay development through media generation, review, and post-production.
What PR0TA Is
PR0TA is a closed-beta production workspace for AI-assisted film and video creation. The app combines screenplay-aware planning, project asset management, multimodal generation, review workflows, and timeline assembly.
Product Map
| Area | Use It For | Key Pages |
|---|---|---|
| Dashboard | Project selection, source documents, task progress, and project controls. | Dashboard, Projects |
| Development | Story structure, screenplay drafting, screenplay source import, and approvals. | Beat Sheet, Screenplay |
| Prep | Script analysis, style, casting, locations, props, character looks, movement, and references. | Breakdowns, Style, Cast, Locations, Props, Character Looks, Choreography |
| Production | Performance setup, shot plans, storyboard frames, and batch generation. | Human Performances, Generative Performances, Shot Listing, Storyboarding, Production Queue |
| Generators | Hands-on image, video, audio, music, and LoRA workflows. | Image Generator, Video Generator, Audio Generator, Music Generator, LoRA Training |
| Post | Asset management, timeline editing, narration timing, and audio mixing. | Asset Browser, Timeline, Narration Timeline, Mixer |
| Team | Studio workspaces, client review, community profiles, and review submissions. | Artists, Clients, Job Board, Public Review Room |
Two Valid Ways To Work
Project-First Workflow
- Create or select a project in Dashboard.
- Import or draft screenplay material.
- Run Breakdowns to build script, scene, and continuity context.
- Review Prep pages so style, cast, locations, props, and looks are coherent.
- Create Shot Lists and Storyboards.
- Use Production Queue or direct generators to create media.
- Review, organize, mix, and assemble in post-production surfaces.
Direct Tools Workflow
You can also start in the generators or Asset Browser when you need fast standalone assets. Direct tools still require an active project so outputs, costs, metadata, and references are stored in the right workspace.
Access and Gating
- Project-gated pages: most production, generator, and post pages require a selected project.
- Role-gated pages: studio artists and client reviewers see different workspace surfaces than project owners.
- Admin-gated pages: Music Generator, LoRA Training, and Admin settings are limited to accounts with admin access.
Important Accuracy Notes
- In-app pricing, billing, model availability, and queue estimates are the source of truth because providers and plans can change.
- Static documentation describes current workflows, but if a button is disabled, check project selection, account role, admin status, and prerequisites.
- PR0TA focuses on generative production workflows. It is not a physical production scheduling or budgeting suite.
How To Read These Docs
| Doc Element | What It Covers | How To Use It |
|---|---|---|
| Controls and functions | Buttons, panels, toggles, menus, editors, and page-level actions. | Use this section when training a user or checking what a page can do. |
| Inputs and prerequisites | Project selection, source documents, role gates, admin access, and upstream analysis requirements. | Check this first when a control is disabled or a page is empty. |
| Outputs and handoff | Where generated data, assets, statuses, or settings appear after an action completes. | Use this to verify whether work landed in the right project surface. |
| Failure modes | Expected empty states, blocked actions, provider failures, missing metadata, and permission issues. | Use this before retrying expensive generation or asking support. |
Global Controls Used Across PR0TA
| Control | Function | Expected Result |
|---|---|---|
| Project selector | Changes the active project context for documents, assets, tasks, review submissions, and generated outputs. | All project-gated pages refresh around the selected project. |
| Task and queue indicators | Expose background generation, processing, and provider state. | Use them to confirm whether a job is pending, running, complete, or failed. |
| Asset Browser launchers | Open the central library for selecting references, importing media, previewing assets, or sending results downstream. | Selected assets are attached to the current action or opened in the relevant editor. |
| Model pickers | Select the provider model used by a generator, tool, or agent role. | The selected model determines available parameters, cost, duration, and output behavior. |
| Advanced settings | Expose model-specific schema fields such as size, duration, seed, aspect, guidance, strength, or output format. | Values are included in the next request and usually stored in output metadata. |
| Regenerate and reroll actions | Create a new attempt from current context without assuming previous output should be overwritten. | New results appear as additional takes or assets unless the page explicitly asks to replace state. |
| Review submission actions | Send selected assets into studio or client review flows. | Assets become review submissions with visibility and status controls. |