Private creative production
Bring the work.Enter a studio. Bring an idea—or your own work—and direct a complete creative studio around it.
Project 001 The First Mark Development motion
Your studio. Your infrastructure. Your data. No generation credits.
01 / The proposition
Creative powerown. A production operating system shaped around your direction—not a queue of disconnected generators.
RORI assembles creative departments, qualifies engines for the job, preserves authority and records how the work became the work.
Your capacity is the compute you own or dedicate. RORI does not impose a metered generation-credit allowance.
Compute, electricity, infrastructure and some model licences still carry real costs. Created and published by CDM
RORI Studios is CDM’s flagship creative-studio system: craft, production intelligence and accountable authority in one continuous operating model. Understand the CDM / RORI architecture Writing Find the story before making the frame.
Develop a premise, treatment, script or existing text into a clear creative brief. Structure, tone and language give the other departments something precise to work from.
Creative direction Keep the work recognisably yours.
Set the visual language, references, constraints and approval standard. These decisions guide each department; a change of engine does not become permission to change the idea.
Promptcraft Translate direction into instructions each engine understands.
RORI combines the brief with model-specific composition, conditioning and validated settings. The aim is to preserve intent—not send the same generic prompt to every model.
Native Visual Establish a visual world worth carrying forward.
Current covers qualified existing still-image sources and their recorded visual authorities. The private app’s source brief and review path has now produced, preserved and delivered an app-owned native development output. That result failed its requested source criteria and is not accepted as downstream conditioning, performance or final-film material. Recorded execution is not craft acceptance: reusable conditioning and complete department commissioning remain product-release requirements.
Film & motion Bring movement to an approved visual idea.
Image-to-video work tests motion, framing and continuity against selected stills. Project 001 includes Director-accepted core motion, while the complete, release-ready film remains in production.
Editorial Shape separate moments into a coherent sequence.
Editorial shapes what was made into rhythm, tension and release. Every cut is another creative decision.
Sound & music Give the work atmosphere, rhythm and a sonic identity.
Pilot for source-preserving score revision. Music-led plans can hand timed action cues to Performance through versioned cue sheets and scoped revision checks. Cue sheets do not generate acting, control motion or lock picture timing. The private Music workspace also supports optional, project-owned licence documents, documented terms, amendment history and expiry information. Rights investigation is a supporting service, not a prerequisite for creative work. Contract interpretation, signatures, payments and external licensing transactions are not qualified or enabled. Native orchestral arrangement and autonomous musical analysis remain in development. The reviewed score revision is provisional; no Project 001 scene score or final score is accepted. Sound design and contextual Foley acceptance remain separate craft requirements; isolated contributions are not a finished soundtrack.
Voice & performance Make delivery serve the character and the story.
Rehearsal and direction keep spectacle answerable to behavior, listening and emotional change.
Language & linguistics Let language carry character, culture and intention.
The local transcription and source-timing pilot connects an actual recording to reviewable dialogue cues. Listening, correction and rejection are explicit steps; estimated timings do not approve a performance. Language-specific adaptation, pronunciation, dubbing, lip-sync and final subtitles remain separately qualified work, not claims established by this pilot.
Check the production record.
03 / The RORI Review System
A studio thatargues with itself. The review protocol brings craft, realism, continuity, audience and rights into the same conversation. The work improves when objections are heard.
Enter the Review System ORIGINATING CREATOR CRAFT LEAD PRODUCTION REALIST AUDIENCE ADVOCATE AI-SCEPTIC RIGHTS · SAFETY · CULTURE WORK Human approval required
04 / You choose the authority path
Every decision.Or only the vital ones. Choose the working relationship: approval at every stage, agreed milestones or bounded delegation. Co-directed and Autopilot are pilot directions; creative and legal authority stay with you.
See the complete authority path Director Control Approve every stage Co-directed Approve defined milestones Autopilot Pilot Exceptions and authority gates 05 / How RORI works
Intent enters.Authored work leaves. Bring your own script or begin from a seed. At every stage you may approve, revise, pause, lock or delegate—with the source and decision history kept traceable.
Follow your authority path ↗ Creative authority Agree what the work must be.
The creator and Director establish the brief, source material, references and non-negotiables. These become the standard against which later decisions are reviewed.
Departments Give each craft a clear responsibility.
Writing, visual direction, Promptcraft and the relevant production departments work from the same approved brief. Each brings its own expertise while preserving the direction of the whole.
Engine expertise Choose the route for the task.
RORI uses qualified operating knowledge to select suitable engines and configurations. An engine must earn its place for the particular use case, rather than being assumed best at everything.
Promptcraft Carry the brief into the engine’s own language.
Composition, atmosphere, constraints and conditioning become model-specific instructions. Creative intent remains the reference when prompts or settings need adjustment.
Production Turn the direction into material you can judge.
Qualified routes produce candidate work and retain the production record. Bounded technical faults can be repaired without silently rewriting creative decisions; unfinished routes remain labelled in development.
Quality control Check the result, not just whether a job completed.
Review the material against the brief, technical requirements and continuity. A successful render is a candidate—not an automatic creative approval.
Director Keep acceptance a creative decision.
The Director can accept the work, request a bounded change or reject it. A production status cannot substitute for that approval, and accepted work is protected from unapproved changes.
Provenance Keep a traceable account of how the work was made.
06 / Private RORI
Your work can stayinside your world. Run RORI on customer-controlled infrastructure, with customer storage, identity, keys and network policy. Qualified local routes do not require external inference APIs.
Enter the private architecture ↗ Customer-controlled boundary Your VPC / VNet Your organisation sets the network boundary.
The BYOC pilot brings RORI into your own cloud account and private network. Your IT team controls access and outbound connections, within the infrastructure your organisation already governs.
Your model vault Keep qualified models close to the work.
Local routes bring models and validated operating knowledge into your deployment. For qualified local engines, production runs inside that environment without sending inference requests to an external service.
Your storage Keep source assets, working files and outputs under your control.
Private deployments are designed around your storage, retention and backup policies. Your organisation controls where the work lives; RORI Studios does not need access to your creative assets.
Your compute Own or dedicate the capacity that does the work.
Production is bounded by the hardware and time available, not a generation-credit allowance. GPUs, electricity, cloud charges and operations still have real costs. Larger workloads may require more capacity.
BYOC is a pilot direction. Air-gapped and sovereign profiles remain roadmap work. 08 / Ownership in practice
One studio.Multiple boundaries. From your own hardware to private cloud. Choose the boundary that fits your studio.
Compare deployment modes ↗ Customer-owned hardware Current Private Cloud / BYOC Pilot Enterprise Cluster Roadmap Customer-owned hardwareCurrent Run RORI on a validated installation you control.
Current applies to qualified internal customer-controlled installations and their recorded routes—not to arbitrary hardware. Each new installation requires its own validation and acceptance record.
Private Cloud / BYOCPilot Run inside your organisation’s cloud account.
Bring the studio to your private cloud, with networking, storage and access governed by your organisation. The pilot focuses on fitting RORI into that environment.
Studio ApplianceRoadmap A dedicated machine and qualified studio stack.
A planned RORI system that brings hardware, models and software together—built around the demands of creative production.
Dedicated ManagedRoadmap Dedicated capacity without physical hardware administration.
A planned managed-cloud option for studios that want dedicated production capacity while leaving the infrastructure operations to a managed service.
Enterprise ClusterRoadmap Coordinate capacity across teams and larger workloads.
A planned cluster deployment for sharing production capacity across studio teams, with coordinated scheduling and customer-governed access.
Sovereign StudioRoadmap Work toward a fully controlled, disconnected production environment.
Planned offline and air-gapped deployment profiles, supported by controlled updates, for organisations that need production to stay within a sovereign boundary.
RORI Studios — created and published by CDM
Create with RORI.Create through RORI. Bring your ideas, your work and your creative direction into a studio built around them.
