Kinetic Painter: getting latency out of the way
A conversation with Jev has me thinking about returning to Kinetic Painter.
Lynn Cole / Laboratory
Experiments, research notes, mad science, and things in progress.
A conversation with Jev has me thinking about returning to Kinetic Painter.
A small Qwen training run tests whether play, critique and revision can change engineering taste while preserving correctness. The results guide the next replication run.
Building a play-training dataset takes longer than the neat plan suggested. These are the challenge counts, solution trajectories and training signals so far.
Hubnot adds issue structure, explicit revision history, retry handling and stale-update checks while keeping assignment separate from execution authority.
Nano-Kitty combines Spec Kitty’s planning with a long-running agent harness, aiming to carry complex work beyond any single session.
Nano-Kitty isolates parallel worktrees and processes while building toward a model-agnostic, long-horizon agent system.
A planned self-play experiment uses compiler verification and multiple reviewers to turn a small Qwen model into a stronger Go developer.
A video-generation experiment organizes work around deliverables rather than isolated renders, while optimization exposes the shape of the model pipeline.
Putting Glamin into a local inference stack turns vector-space state changes into a possible interface for tools, memory and small applications.
A coding-workflow comparison of Agents A1 and Qwen finds different failure modes across Go, Zig and Next.js, and a useful response to QA feedback.
A deliberately vague Zig assignment pushes Qwen through planning, implementation and the complexity wall. The failure is part of the evaluation.
AI upscaling can improve archival footage while making clean video look waxy. The next experiment deliberately degrades the source before restoration.