MaLiang-Harness: A Programmable Path to Image and Video Generation
Haoyu Zhao, Zihao Zhang, Xudong Wang, Jiaxi Gu, Zuxuan Wu, Yu-Gang Jiang, Shuicheng Yan
National University of Singapore · Fudan University · Tencent
Published September 28, 2026 · on the feed September 30, 2026 · ▲ 405 · arXiv 2609.34309
The abstract
Executable programs offer explicit control over how images and videos are constructed, but generating runnable code is only the beginning of visual creation. A program can execute correctly while violating the requested composition, appearance, or motion. We define this discrepancy as the Program-to-Visual (P2V) gap and introduce MaLiang-Harness, a unified framework for organizing MLLM-driven visual generation into a persistent process of construction, inspection, and revision. Its central design is to make the evolving visual program, its construction history, and its verification share a common revision reference. We define the Persistent Executable Generation (PEG) state as preserving programs and task context. Traceable Generation Process (TGP) connects edits to rendered evidence, and Revision-aware Editing and Verification (REV) supports restoration and checks the current revision before completion. Together, these mechanisms coordinate planning, execution, and visual feedback across rendering backends. We evaluate 11 powerful closed-source MLLMs on MaLiang-IBench and four on MaLiang-VBench, measuring generation success, visual quality, and computational cost. GPT-6-Astra achieves 100% generation success on both benchmarks, with 96.0% of image tasks and 76.9% of video tasks meeting all quality thresholds. The comparison also reveals a mismatch between general capability scores and visual generation performance, with similarly scored models differing substantially in their ability to satisfy visual requirements. MaLiang-Harness provides a systematic basis for studying how MLLMs translate executable code into visual outcomes, exposing both the potential of programmable generation and the limitations of general benchmarks as predictors of this ability. The project is available at https://github.com/gulucaptain/MaLiang-Harness.
The Brief
3:07A short podcast summary of the paper. Written and voiced by AI.
Transcript
MaLiang-Harness. A Programmable Path to Image and Video Generation. By Haoyu Zhao and six others, from the National University of Singapore, Fudan University, and one other institution. Published on the twenty-eighth of September. Its code repository is worked out: about one thousand five hundred source files, with a readme.
Executable programs offer explicit control over how images and videos are constructed. A program can say exactly where a shape goes, what colour it is, and how it moves. But generating code that runs is only the beginning of visual creation. A program can execute correctly and still violate the requested composition, appearance, or motion. The authors name that discrepancy the Program-to-Visual gap: the distance between code that works and a picture that is right.
MaLiang-Harness is a unified framework that organises visual generation driven by multimodal language models into a persistent process of construction, inspection, and revision. Its central design decision is that three things share one common revision reference: the visual program as it evolves, the history of how it was constructed, and its verification. When all three point at the same revision, it is always clear which version of the program a check was run against.
Three mechanisms carry that out. The Persistent Executable Generation state, or PEG, preserves the programs and the task context. The Traceable Generation Process, or TGP, connects each edit to the rendered evidence. And Revision-aware Editing and Verification, or REV, supports restoration and checks the current revision before the task is completed.
Together these coordinate planning, execution, and visual feedback, across different rendering backends. The program is not simply written and run once. It is written, rendered, inspected, and revised, with a traceable record at each step. That record is what allows a bad edit to be undone, and what lets a check say precisely which version it approved. Without it, inspection and revision would be working from different pictures of the same program.
The evaluation runs eleven powerful closed-source multimodal models on MaLiang-IBench, and four on MaLiang-VBench, measuring generation success, visual quality, and computational cost. GPT six Astra reaches one hundred percent generation success on both benchmarks. Ninety-six percent of its image tasks, and seventy-six point nine percent of its video tasks, meet all of the quality thresholds.
The comparison also turns up a mismatch. Models with similar general capability scores differ substantially in their ability to satisfy visual requirements. A strong score on general benchmarks, in other words, is an unreliable predictor of how well a model will do here. Writing a program that renders the requested scene seems to call on something those benchmarks do not capture.
The framework is offered as a systematic basis for studying how multimodal models translate executable code into visual outcomes. It exposes two sides at once: how far programmable generation can already go, and how weakly general benchmarks predict which models will get there. Code that runs is where this work starts, not where it stops.
Paper Quest · 7 chapters · about 40 min
Play this paper
Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.
Chapter 1 🧩 · The problem
The code runs. The picture is still wrong. That gap is the wall.
You ask a multimodal model to write code that draws a scene: a kitten carrying a star across a desk. The code runs without a single error.
The road ahead
- 1 · The problem ~7 min Code that runs without errors can still draw the wrong picture, because running says nothing about where things appear or when they move.
- 2 · What came before ~3 min
- 3 · The key idea ~8 min Render the program, look at the result, and revise, with program, history and checks all tied to one shared revision number.
- 4 · Choose your own research ~3 min
- 5 · Build the method ~8 min Plan the scene, write the code, render it, inspect the picture, and commit any fix as a new revision.
- 6 · The experiment ~6 min You’ll guess: When multimodal models write code to draw images and videos, do models with similar general capability scores perform similarly at meeting the visual requirements?
- 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Free, with Google or an email address. Your stars and progress are kept.