Block F · Motion

Motion

Every generative mesh arrives as a static surface, and rigging one by hand is the step that keeps character animation out of reach entirely. This block is the shortest on the roadmap and the most dependent: each line waits on the one before it.

Two frames is not motion

A settle expressed as a squashed re-render of the same mesh is right for exactly one beat, and has no way to say what a walk or a reaction would be. A clip does.

A curve is text or it is unreachable

A timing change inside a binary track is invisible in a diff and unreachable by an edit, which makes every adjustment a re-export from a tool nobody scripted. The format is deliberately unwritten until the skeleton decisions are made, because a format written before them would be guessing.

One settle, two outputs

The same motion exists as frames a 2D interface crossfades to and as something a 3D scene plays. Authoring it twice and keeping the two in step by hand is the work this removes.

The block itself

Four open lines, in the roadmap's own words

Each line names the failure it exists to remove and the measurement behind it. None of them has shipped. This list is generated from docs/ROADMAP.md, so it cannot describe a backlog the file does not have.

📋PW26a fetched mesh has no skeleton, so it cannot be posed at allEvery generative mesh arrives as a static surface, and rigging one by hand is the step that keeps character animation out of reach entirely.
📋PW27motion is expressed as a second static render, so nothing longer than two frames existsA settle is a squashed re-render of the same mesh, which is right for one beat and has no way to say what a walk or a reaction would be.waits on PW26
📋PW28an animation lives in a binary track, so a curve cannot be reviewed or edited as textA timing change inside a mesh file is invisible in a diff and unreachable by an edit, which makes every adjustment a re-export from a tool nobody scripted.waits on PW27
📋PW29a 2D screen needs frames and a 3D scene needs a clip, so the motion is authored twiceThe same settle exists as a sprite the interface crossfades to and as something a 3D scene would play, and keeping the two in step is manual.waits on PW27
The other blocks

What this one sits next to

A

What a call costs the turn

Handles for anything slow, a post-condition on every operation, typed errors that name the remedy, a surface that describes itself and this machine, and configuration resolved per call.

6 lines
B

Seeing the result cheaply

A surface is read on a sphere in three seconds, a render returns its measurements in the same answer, a distribution is reported as a set rather than a mean, and a sheet shows an asset beside its siblings.

5 lines
C

The asset compiler

What counts as a correct render, written as a file a search can aim at; a search that finds the rig numbers instead of a person finding them by hand; a cache so nothing renders twice; and a trace of everything the search rejected.

4 lines
D

Fetching without surprise

A silhouette gate before the credit moves, a ceiling agreed once instead of a question per fetch, the mesh kept because the service deletes it at seventy-two hours, and a fetched asset normalised into this project's axes.

6 lines
E

One world with the engine

A Godot run judged by what the script printed rather than by an exit code that means nothing, a capture that works where there is no screen, a scale derived instead of tuned, and a runner pinned so two machines agree.

4 lines
G

Geometry as a declaration

A shape stated as data rather than written as a program: a vocabulary read off real assets, numbers a search can reach, a review before anything is built, and a way back to code for the shape no format can state.

5 lines