A picture of a mechanism is a bet that the mechanism is really there. Two projects test that bet: one on headless Blender scenes across the corpus, one on eight simulated factories.
A domestic sorting machine was supposed to show its own rotors through a cutaway wall. The "cutaway" turned out to be an opaque cube parked in front of the machine. Nothing was cut. It just looked dark enough to pass.
The batch runner used to print "renders written" even after four scripts crashed. Adding strict shell flags and a real exit code turned silence into a report you can trust.
Same principle for a cropped label hidden behind its own block: check the file, don't just re-describe the fix.
Every scene shares seed, resolution, engine, and output settings. Every scene writes a .blend and a .png. Every result ships with a small JSON sidecar of the numbers the picture is a picture of.
Proposed next: a record tying every scene to its commit, its parameters, its sidecar, and whether it actually passed its own checks. A paper trail for pictures.
Eight simulated sites, an integrated factory, ecological cycles, a paper mill, a yogurt plant, a chip fab, a recycling depot, a lab, and a kitchen, are drawn as one thing: a bounded metabolism. Stuff comes in, changes, circulates, and some of it leaves as damage nobody drew.
From pretty picture to trustworthy model:
Materials need a destination. Energy has to degrade somewhere. Water keeps a quality history. When a loop can't close, the gap should stay visible, not get cropped out of the picture.