User Stories¶
Script to Assets¶
A creative lead begins development on a feature film project titled “Revenge of the Roombas.” The story takes place in a near-future world where common household and service robots rebel against their human masters.
The lead starts on the Concept page, outlining the premise as a darkly comedic look at humanity’s dependence on automation and defining tone, genre, and key themes. They move into Characters, creating entries for “Living Room Roomba” (a loyal cleaning bot turned revolutionary) and The Master Server (the networked intelligence coordinating the rebellion).
Next, the lead opens the Scriptwriting section and begins drafting the film script. As they write, new entities such as the Drone Patrols (character) and the Human Safe Zone (environment) are automatically registered in Storycraft through the script breakdown process. When the draft is complete, the Chat Assistant highlights that these new entities lack descriptions and offers to guide the user through expanding them and/or to generate starter text based on the script context.
After filling in missing creative details (either manually, automatically, or somewhere in between), linked Asset tasks are automatically created for visual development of these entities. Each task now displays an Open incomplete task. Clicking either task opens the same task window shown in the Asset screen for tracking and review.
Later, when the final Drone Patrols design is approved, the completed concept art appears automatically in Storycraft under that entity’s media frame. The creative lead can review the approved asset in context and use the assistant to identify any remaining incomplete entries before moving on.
Throughout this process, the user(s) move naturally between defining the world, writing the script, and refining the entities generated by that writing. Storycraft and the Asset windows stay synchronized, providing a continuous creative-to-production loop that evolves as the story does, and automatically/continuously highlights any new tasks that appear as a result of creative changes so nothing slips through the cracks.
Sequence Diagram¶
Shots¶
A shot artist begins work on “Revenge of the Roombas”, Episode 1. After completing the script in Storycraft, the system automatically generates a sequence of shots, each linked to its script context.
In the Shots View, the user opens S01_E01_010: Roomba Unit 9 Awakens. The shot card lists the set (INT. HUMAN APARTMENT), lighting (Night), characters (Roomba Unit 9, The Overseer), and dialogue. The Chat Assistant displays a summary and prompts the user to generate the first frame.
Within the Image Workspace, the assistant automatically loads the relevant memory assets from Storycraft, including the apartment environment and character references. The artist types, “Make the camera lower, as if the Roomba is waking up on the floor.” The system regenerates several versions using these parameters.
The artist favorites a few outputs along the way, and finally selects one for Review using the right-side Output frame to easily jump between them for comparison. The creative director sees that the shot status has changed to “In Review” and opens it up to take a look. She selects her preferred frame in the Review Tab, approves it, and the system automatically creates a linked Video Task using that first frame as input. In the Video Workspace, the same context is carried over. The user simply confirms generation, reviews the output, and approves it.
Once complete, the shot state changes to Approved. The assistant summarizes the remaining incomplete shots in the sequence and offers to open the next one.
Sequence Diagram¶
Editorial¶
After assembling Episode 1 of “Revenge of the Roombas,” the user opens the timeline and sees approved videos alongside first frames where finals are not yet ready. Scene 2 has two variants; the user swaps between them in place to test pacing. The Craftology Assistant suggests inserting a short cutaway before Scene 3 to smooth the transition and creates a placeholder shot linked to a task in Shots, while updating the Shot Breakdown.
The user trims two clips, adds a one-second crossfade, and previews the full sequence. Time-stamped comments are added for a slower moment in Scene 1. Later, when Scene 3’s final video is approved, the timeline replaces the first frame automatically and records the change in history. The user exports an MP4 preview for internal review and an EDL for external finishing, then marks the episode as locked for Publishing.
Sequence Diagram¶
Quality Control¶
As “Revenge of the Roombas” approaches release, the user runs a full QC scan for the Episode 1 cut. The system analyzes all visual, audio, and metadata components against the project’s configuration, which targets global streaming release on multiple platforms.
The QC dashboard highlights the following issues:
- A shot output from Scene 5 contains a background advertisement resembling a real-world brand, triggering an IP warning.
- A line of dialogue exceeds the PG-13 threshold for language under the U.S. content guidelines.
- The runtime exceeds the configured platform limit for episodic short content.
- The use of the brand name “Roomba” in the title violates the brand name IP of the Roomba product.
Each issue is displayed in context.
- Clicking the flagged shot opens the frame with an overlay showing the logo in question. The assistant suggests regenerating the shot with adjusted composition and offers to create a linked Art task for the replacement.
- For the flagged dialogue, the assistant highlights the script line in Storycraft and proposes an alternate phrasing.
- The runtime issue includes an auto-generated note recommending which transitional shots could be trimmed to meet the limit.
- Finally, and most unfortunately, the title of the production and all visual and linguistic references to Roomba must be replaced, causing about 85% of the entire film to have to be recreated.
The production team reworks the production under the new IP-safe title.
After resolving all issues, the user re-runs the scan. The QC dashboard updates, showing zero unresolved issues and marking the episode as Ready to Publish under the new title “Revenge of the Robotic Vacuums.”
Sequence Diagram¶
Publishing¶
After finalizing Episode 1 of “Revenge of the Robotic Vacuums,” the user opens the Publishing dashboard. The system automatically imports the approved version from Editorial and verifies that it has passed all QC checks.
The user connects their YouTube, TikTok, and Disney+ creator accounts, each authenticated through the integrated platform APIs. Craftology pulls in the current channel data, thumbnails, and audience demographics. The assistant generates suggested metadata based on Storycraft context, proposing a title (“Revenge of the Robotic Vacuums – Episode 1: Uprising”), a short description, and tags derived from the project’s themes and characters.
The user reviews and edits the metadata, adjusts the release times for each region, and sets the video to premiere simultaneously across all platforms. Once published, the system begins tracking analytics automatically. The Performance Dashboard shows cumulative engagement across platforms, highlighting strong performance in Southeast Asia and lower-than-expected completion rates in the U.S. The assistant summarizes this in a daily report and suggests shortening the intro sequence for future episodes to improve retention.
Sequence Diagram¶
Settings¶
A production lead opens the Settings page to standardize configurations across several active projects. Under Organization Settings, they define a default naming convention and restrict universe creation to producers. They connect the company’s YouTube and TikTok accounts under Integrations for shared publishing access.
An artist opens the same page under their user account to adjust personal preferences, enabling dark mode and limiting notifications to assigned tasks. The Craftology Assistant acknowledges the changes, ensuring that future interactions and alerts follow the updated settings.