This case focuses on productizing a SaaS-to-Agent migration: keeping the original project intact while turning existing video-generation source into Reallier-owned private comic-video production control plane with a real automated demo flow.
FrameForge decomposes the original video SaaS into script understanding, storyboard planning, asset memory, provider runtime, review gates, cost guardrails, and acceptance demos, with the harness owning state, tools, retries, and human checkpoints.
The issue was not a missing page. The legacy SaaS was tied to provider calls, had weak information architecture, limited auditability, and a demo flow that could look fake. FrameForge turns it into a private, reviewable production control plane.
The delivery includes the FrameForge brand, narrow icon rail, unified login, operations home, automated demo flow, provider key management, cost and review pages, and an independent test deployment boundary.
FrameForge is not another chat box. It decomposes comic-video production into inspectable, replayable, retryable modules with human checkpoints.
Starts Agent Runs from script text and stores run name, input text, and storyboard context.
Turns scripts into shots, characters, scenes, and props instead of a single generate button.
Characters, scenes, props, and reusable media become searchable memory for episode continuity.
Image, video, TTS, and LLM calls are routed through Provider Runtime and Runtime Keys.
Reviewer lanes handle character conflicts, scene continuity, budget requests, and human checkpoints.
Run budget, provider credit, and episode guardrails organize cost control and approvals.
The original script2video-ai runtime remains separate while the new product moves into frameforge with its own git baseline.
The product becomes FrameForge, and the first screen becomes a runtime console instead of a welcome page.
Login, icon rail, hover hints, subpage structure, and internal surfaces are unified.
Playwright drives a real UI journey across page transitions, project generation, assets, review, cost, and Runtime Keys.
The test stack uses independent containers, port, and database instead of reusing the original project gateway.
Scripts, storyboards, asset review, and provider routing live in one auditable production surface.
The key is not copying the old pages. Start by isolating the original project, then define the new product boundary, Agent workflow, Provider Runtime, demo journey, and private deployment acceptance criteria.
