◆ FORGE · playground
The playground is where you touch the model. Open any campaign episode, including the one-click demo episode, and the screen becomes a workbench for
that single recording: the video in a persistent dock, the version
constellation owning the rest of the viewport, and a floating composer.
Two verbs, one engine (the campaign’s action-conditioned render fine-tune):
Describe a change
Scrub to a moment, then say what should happen next, “place it further to the left”, “lift higher before placing”. The text is classified into constrained trajectory edits (the grasp arm’s seven action columns; anything outside that contract is refused with guidance, not guessed). Each described change becomes a real batch bound to your exact episode (wb/<campaign>/<episode>), and joins the constellation as a node whose state
is always honest:
- pending: the executor holds it
- clip + verdict: generated, with its verification result on the node
- the executor’s exact words: when a backend isn’t live, the node says “recorded, live engine pending”; the batch is real and runs when the live engine is on. Nothing is ever fabricated.
Precise splice
The miner’s ranked partner tails for this episode’s head, same scene, same reach, compatible grasp. Rendering one splices this episode’s grasp onto that partner’s carry: a real counterfactual through the full pipeline (compose → render → verify → gates), reviewable with the same confirm/overrule verbs as a campaign run, and deliverable like any other kept episode.Where it lives
https://forge.alakazam.gg/?view=playground: the standalone door: demo episode in one click, or pick any of your datasets and sample an episode.- Inside the workbench, every episode card has open in playground, same surface, bound to that campaign episode.
Programmatic access: the precise path is plain HTTP (see the
quickstart,
partners → runs with explicit pairs).
Described changes ride the platform’s scenario-batch system; batches and
their items are queryable and subscribe-able in realtime.