◆ FORGE · forge.alakazam.gg
The forge takes a robot dataset you already have and gives you back a bigger,
verified one. It runs the same world-model engines that power Alakazam’s
interactive worlds, pointed at your episodes instead of ours.
There are two ways in, and they work on the same campaigns:
Dataset Workbench
The pipeline. Upload or open a dataset, check its health, sample sources,
plan transforms, run gated renders, and deliver an augmented dataset you can
train on. Six legible steps, every one inspectable.
Playground
One episode at a time. Scrub a real recorded episode fullscreen, describe a
change in words, or splice a precise counterfactual, surgical augmentation
with a verification verdict on every version.
The spine
A campaign walks six steps. You can stop, inspect, and re-enter anywhere; the pipeline never advances on your behalf.The engines
Two model families, two different jobs:- New trajectories (workbench runs, and both playground verbs) use the campaign’s action-conditioned render engine: a fine-tune of the Cosmos world-model line that actually obeys spliced or edited action streams. The base model doesn’t; the fine-tune is why the forge can change what the robot does and keep the video honest.
- Object swap and environment restyle (workbench transforms) use general video-to-video transfer models, change what the scene looks like, keep the demonstrated motion. Their backends connect per deployment; the Transform step shows exact readiness.