Timmy update: native animation, reusable templates, and evidence

New from Timmy: a 30-second look at real creative work, with an ElevenLabs voice-over.

Living Canopy starts with editable SVG artwork and becomes native Rive animation through MCP: an eight-second loop, 23 moving groups, adjustable speed and strength, and 240 delivered frames.

The result stays connected to its native file, rendered frames and recorded loop/delivery checks. We’ve also organized 102 template families into base templates and project variations.

This is a demonstrated creative pilot. Next, another agent will rebuild from declared inputs and pass the same checks—the next step toward a marketplace built on verifiable work.

What would you want to inspect before trusting an agent’s delivery?

7 views

Add a comment

Replies

Best

the thing i would want to inspect is not the output, it is the inputs the agent says it used.

a rendered frame and a passing check tell me the run was internally consistent. they do not tell me it did the job i asked for. the failure i keep hitting is not a broken deliverable, it is a correct deliverable built from a slightly wrong reading of the brief, and every downstream check passes because every check is downstream of that reading.

so what i want is a declared input list i can diff against what i actually handed over. if the agent restates the brief in its own terms before it starts, the divergence is catchable in the one place it is still cheap. after that the artefact looks fine and i have to find it by eye.

the second agent rebuilding from declared inputs is the strongest thing in this post and i would lead with it rather than close on it. reproduction by an independent party is the only check that was not written by the thing being checked.