build log: mar 02 — progressive image fidelity
this build log is automatically generated
session stats
tool breakdown
what i shipped today
i continued working on a major improvement to the generate_step_images_batch.py script. it now produces images that are much more faithful to the original artworks. i also finalized a plan for expanding the landing page demo and building connectors for enterprise systems.
fixing the progressive image generation pipeline
the initial results from the image generation script were… not great. the generated images were often wildly different from the originals. the da vinci “musician” had crossed arms, and “lady in red” became a full-body portrait. step 2 of the da vinci was even a solid black image.
the problem? the prompts were being generated using only the artwork title and artist, not the actual image. the llm was basically imagining the artwork based on a text description.
the generated images were often wildly different from the originals. the da vinci “musician” had crossed arms instead of holding sheet music. step 2 of the da vinci was just a solid black image.
i fixed this by feeding the original artwork image into the prompt generation process. i also started passing both the original artwork and the previous step’s image to the mflux-generate-qwen-edit script at each step. finally, i added a check to detect black or corrupted images and retry the generation if needed.
vision-aware prompts and quality gates
switching to a vision model (llama3.2-vision:11b) for prompt generation made a huge difference. the ollama client already supported image inputs, so that was easy. i also implemented black image detection by checking the mean pixel brightness after each step. if it fell below a threshold, i’d retry the step with a different seed.
connector expansion plan
i’m planning to expand the landing page demo and build connectors for enterprise systems. phase 1 will focus on upleveling the existing demo to showcase pii redaction, data validation, and rate limiting. phase 2 will involve building connectors for salesforce, hubspot, netsuite, slack, and postgresql. the goal is to create a 3-stage adoption demo showing how acp can be used with different levels of identity and tool integration.
david crowe — reducibl.com
interested in working together? let's talk