What we planned at the start of the month, what actually shipped, and where RanGen Studio stands on August 31.

At the beginning of August, most of the work we were planning revolved around one idea:

Characters → Looks → Scenes.

The goal was to stop treating every generation as an isolated event. A character should have an identity that survives wardrobe changes, an approved outfit should become a Look, and that Look should carry into scenes that understand their environment and continuity.

On August 1, some of those systems were in beta, some were in testing, and a few were only plans. A month later, the codebase has moved further than the original roadmap in several places.

So this is the August 31 version. Not what we hoped to build. What actually exists now.

1. NEW CHARACTER REFERENCE SYSTEM · LIVE

Characters are now structured production objects.

At the beginning of August, the new Character Reference System was already in beta. The idea was simple: Characters needed to become structured objects instead of loose collections of reference images.

That system is now live and enforced throughout the production pipeline. RanGen maintains a canonical identity for each character and expects valid relationships to survive as references move downstream.

A character is correctly defined at the start.
Structured character IDs are preserved during AI extraction.
Unreliable fallbacks are handled defensively.

Where it is now: The system is live. Character identity is no longer just established visually; it is enforced structurally.

2. WARDROBE & OUTFIT MANAGEMENT · LIVE

Wardrobe is now fully connected to the pipeline.

At the beginning of the month, wardrobe was already moving beyond simple reference uploads. Now, an outfit belongs to a specific character. When that outfit is approved for a scene, the system validates the relationship before generation.

Character → Outfit assignments are checked.
The intended wardrobe is applied to the intended character.
Wardrobe consistency is treated as a data problem.

Where it is now: The improved wardrobe workflow is live. The structure ensures productions involving multiple characters and costumes remain consistent.

3. LOOK ROOMS & LOOK CARDS · LIVE

Approved identities and Look Cards travel downstream.

This was one of the most important bridges we wanted to build. A Character Profile defines identity, an Outfit defines wardrobe, but production needs a reusable combination: the Look.

The full progression is now functional:

Character → Outfit → Look Card

Instead of passing every raw uploaded image into generation, RanGen works from established, approved character identities and unified Look Cards.

Where it is now: Look Cards are actively part of the reference pipeline. They give both the filmmaker and the AI a clear answer to exactly what a character should look like in a scene.

4. MORE CONSISTENT SCENE GENERATION · LIVE

Character continuity now works across shots.

At the beginning of August, the connection between Character Profiles and Scene Generation was in testing. Now, character identity, approved Looks, and scene generation are part of the same continuity pipeline.

We spent a significant part of the month repairing places where that chain could break:

Fixed cases where structured character IDs disappeared during processing.
Routed Setup Masters through the self-correcting quality-control path.

Where it is now: The connection is operational. Setup Masters travel through the QC framework, and character identity survives the full path into scene generation.

5. CHARACTER–BACKGROUND COMPOSITION · IMPLEMENTED

Continuity is anchored through Setup-Based Generation.

We described this as a composition problem—better scale, placement, depth, and interaction. We originally imagined this might require explicit staging tools, but the solution that emerged was different: Setup-Based Generation.

Before every shot is treated independently, the production planner groups shots by camera position:

Setup A
Setup B
Setup C

Each setup establishes a spatial anchor. The Studio generates Setup Masters that define the environment and composition before moving into individual shots.

Where it is now: Setup-Based Generation is implemented. Related shots inherit a common visual foundation, resulting in more stable background continuity, character scale, and depth.

6. MICRODRAMA MODE · LIVE

Vertical storytelling has its own directing logic.

At the beginning of August, Microdrama Mode was in development. It is now part of RanGen's active directing system, available as a project genre with a specialized persona.

The directing logic prioritizes:

Vertical 9:16 composition
Faces and eyes dominating the frame
Faster dramatic escalation
Strong emotional readability

Where it is now: Microdrama Mode is live. It's not just a vertical export button—it's a directing mode that understands the grammar of the short-form format.

7. MULTI-PASS LOOPING EDITS · SHIPPED

Edits are decomposed into atomic, sequenced passes.

This is where the codebase moved substantially further than the roadmap. At the beginning of the month, Multi-Pass Looping Edits were planned. The system now exists.

A complex editing request can be decomposed into a sequence of smaller, controlled operations, ordered by scope:

Background → Subject → Details → Grade

Where it is now: Fully implemented and shipped. The workflow is handled in memory, exposing the passes visually in the image editor so the filmmaker can inspect the sequence pass-by-pass.

8. RANGEN MOBILE · CLOSED TESTING

The Studio is being refined for your pocket.

Mobile was simply listed as in progress at the start of August. It has now moved into closed testing. The native Android and iOS application shells are part of the active codebase.

We're deliberate about what belongs on mobile:

Reviewing work
Checking projects
Approving assets
Quick generation or review actions

Where it is now: Closed testing. The infrastructure exists, the apps are compiling, and the focus is on refining the mobile Studio experience rather than squeezing every desktop panel onto a smaller screen.

9. TEAM & ENTERPRISE ROLES · IMPLEMENTED

The foundational organization system is built.

Team & Enterprise Roles progressed significantly further than the original roadmap, moving from "in development" to a fully implemented organization and permissions system.

RanGen now has a defined role hierarchy covering:

Owner, Superadmin, Admin
Member, Reviewer, Viewer

The system also supports seat limits, organization invitations, and administrative controls.

Where it is now: Implemented across both the database and the administration UI.

So, where did August actually land?

On August 1, we published nine areas of work. On August 31, this is where they stand:

New Character Reference System — Live
Wardrobe & Outfit Management — Live
Look Rooms & Look Cards — Live
More Consistent Scene Generation — Live
Character–Background Composition — Implemented via Setup-Based Generation
Microdrama Mode — Live
Multi-Pass Looping Edits — Fully Implemented & Shipped
RanGen Mobile — Closed Testing
Team & Enterprise Roles — Implemented

A few of those moved substantially further than we expected. The biggest change is still the one we described at the beginning of the month:

Characters → Looks → Scenes

That pipeline now exists. A character can have a canonical identity, approved wardrobe, and a Look that moves into scenes. Scenes are grouped into setups, pass through continuity-aware quality control, and preserve earlier creative decisions.

What we learned in August

Consistency is an infrastructure problem.

The Studio is becoming less prompt-driven. A production has memory. Characters, wardrobe, Looks, scenes, camera setups, and editing passes exist independently of prompts. The prompt still matters, but it is becoming one instruction inside a much larger production state.

Build. Test. Learn. Improve. Repeat.

Still making. Still shipping. Keep following the build.

The August Build Log