The Lab

What it does

Start from a prototype built for your show — Newsroom, Late show, Explainer, Podcast, Sports desk, Town hall and more — or from nothing, and edit on a canvas that moves: drag a block, resize it, snap it to a zone, watch the band cycle its messages and the ticker crawl.

Or ask the director: pick a skeleton, say what you want in your own words, hand over a clip or a picture you admire, and the look lands on the canvas for you to change.

Make it, and the render plane draws every frame: a looping plate (MP4), the rig as an overlay with transparency (WebM), a preview anyone can play, and a poster. Use them in an episode, on a live channel, on the stage of a live room — or download them for OBS and the rest.

Share a look and every creator on Rookery can start from it, in their own colours, with their own logo and handles.

The standard behind it

• One recipe, three readers: the studio's canvas, the stage page and the render plane place every element by the same rule from the same seeds, and a test runs the Python against the TypeScript over the same inputs.
• A loop is seamless by construction: every motion is a function of the loop's phase with a whole number of cycles, so the first frame and the last are the same picture — a test says so for every plate kind.
• The clock is never burned into a file. A rendered loop plays for hours and a burned time is wrong within a minute; the stage draws the time live and a file leaves the slot empty.
• A recipe carries no storage key. Pictures are asset ids the API resolves under row security; the render plane checks every key against the job's own workspace before it reads it.