Kuts Studio · Editing brain
Kuts Brain, algo at the core.
Kuts isn’t a cloud export tool. It’s WorldVelopers’ agentic video analysis, reasoning and editing engine — musical drama, rush casting, Gold judgment.
WorldVelopers ecosystem
Where does the Kuts algo live?
WorldVelopers = studio + AI stack in production. Kuts is the editing product. CRM feeds its Gold brain. Aldo runs ops. Business SaaS stay separate.
Kuts Studio
Editing brain
Rush + music analysis → Drama Graph → grid → cast → EditPlan. Live: kuts.studio
CRM Hub
Business + Gold corpus
Upload / review Gold cuts → DA StyleProfiles injected into Architect
Aldo
Ops / agency agent
Chat, quotes, monitoring — not the cut engine; orchestrates around it
Business SaaS
MenuSoft, Lyaly, Tap-Share…
Client products — Kuts doesn’t replace them
Signal flow
CRM Gold → StyleProfile DA → Kuts Architect ← Drama Graph ← Music
· Rushes → Cast roles → EditPlan → kuts.studio
Doctrine
5 engines = product force
01
Analysis
Rushes (quality, motion, shot) + music (drama graph, hits, energy).
02
Reasoning
DA intent, zone policy, shot casting.
03
Edit
Variable slots, drop/hit/off-beat sync, living rhythm.
04
Judgment
Gold + Quality corpora — score like an editor, not a metronome.
05
Improvement
Gold feedback → StyleProfile → Architect briefs.
Generation pipeline
From rush to plan.
Deterministic logic locks time. The LLM picks content.
- 01Music analysisBeatServiceBPM, beats, drums, energy → Drama Graph
- 02Rush analysisGemini + FFmpeg + Macenergy, shot, motion, blur/shake
- 03Zone policydrama_policysoft intro → hard drop → soft outro
- 04Slot plannerbeat_gridhits > onsets > beats; densify on drop
- 05Cast + rankcast_rolesestablishment / detail / impact / emotion
- 06Architect LLMslot pickerfills slots — never invents timeline
- 07Validatetimeline_validatorkeeps musical lock
Architect v2 invariant: the grid locks timeline_in/out. The model doesn’t move cuts — it casts rushes.
Music Drama Graph
Not a metronome, a dramaturgy.
The algo follows the musical arc. Beat is a secondary constraint — sometimes intentionally broken outside climax.
Intro
Long holds, establishment, soft snap
Buildup
Rising density, off-beat allowed
Drop
Hard anchor, hits, impact climax
Outro
Breath, emotion, holds
Stored on MusicTrack (sections type drama_graph). Edit window centered ~58% on the drop.
Cut policy
Behavior by zone
| Zone | Cuts | Snap | Role | Behavior |
|---|---|---|---|---|
| intro | long (2–6s) | soft 40ms | establishment | wide OK, low energy |
| buildup | tightening | 80ms | detail | close/motion, off-beat OK |
| drop | short + anchor | hard 120ms | impact | peak + beat_sync |
| outro | long | soft 40ms | emotion | tenderness / triumph |
Rush matcher
Cast roles on the grid
Each slot has a role. The scorer pushes the right shot type — before the LLM.
wide / establishing
peak energy, action, beat_sync
close-up, medium-fast motion
strong emotion, not chaotic
neutral / transition
Gold loop
Judgment sharpens the brain
CRM Hub → reference cuts → grades → DA StyleProfile → Architect brief.
01
CRM upload
Gold Corpus Hub sends the cut to Studio
02
Gemini + zones
global beat_sync + musical_zones (intro/buildup/drop/outro)
03
Judge
excellent | good | avoid — intentional off-beat ≠ defect
04
DA StyleProfile
averages + avoid_patterns + zone_directives
05
Architect
build_gold_da_brief injected into prompts
See Kuts in production
The product runs at kuts.studio. This page documents the brain — not product marketing.