Build1 distinct publisher3 min readUpdated
Richard Rondeau's Veridian Resonance hit its engineering targets and still read as "AI slop" to viewers, so the next chapter moves effort back to visible manual drawing.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
Richard Rondeau has published a build log for Veridian Resonance, a bilingual digital comic he treated as a production pipeline rather than an art project, and the process numbers in it are specific enough to argue with [1]. He also reports that the output landed flat with viewers, and that reception, not a technical wall, is what is pushing him back toward visible manual drawing [3].
Start with scope. The project shipped 100 panels generated and refined across 24 finished pages of published work [2], roughly four panels per page [20]. It did not begin as illustration: the world came out of a homebrew tabletop campaign, managed as interconnected markdown nodes in Obsidian and formatted through Homebrewery [4], with the stated engineering problem being how to scale dense relational text, lore, mechanics and rigid character definitions, into a 28-page visual production [5].
The style choice was made on production criteria rather than taste. Rondeau says he ran structured A/B testing across aesthetic checkpoints scored on panel consistency, manual rework required, and reproducibility at volume [6]. Grim Dark and Marvel looks were rejected because they typically needed 20 to 30 iterations per panel before post-processing to fix hatching and lighting inconsistencies [7]. The replacement was a strict cel-shaded formula, bold black outlines, flat colour, minimal ink shading, limited palette, with structural reference to Vox Machina and Avatar: The Last Airbender [8].
The headline efficiency claim comes from restriction, not better prompting. Negative prompts were tuned to block the model's pull toward generic 3D hyper-realism, producing a baseline stable enough to colour-grade against predefined palettes in Krita [9]. Combined with reference locking, that cut iteration cycles per character asset from 20-plus passes to under 5 [10], which is at least a fourfold reduction on the low end of the stated range [11].
Consistency across a sequence was the harder problem, and the first approach failed. Local models fine-tuned with LoRA held the art style but made character consistency across panels nearly impossible, a failure mode Rondeau says he later saw again in newer Midjourney versions [12]. The working system used Nano Banana 2 with character sheets and templated prompts to hold the lead character stable across the run [13], with two sheets per character, one face and one full body, which he found preserved detail better than a single reference [14]. Non-standard designs needed explicit structural commands: Krix required scale instructions to render as a short goblin instead of drifting back to a kobold archetype [15].
Around the image work, custom scripts removed an estimated 15 hours of manual file management, naming and formatting [16], and the site shipped as a bilingual EN/FR static build with no duplicated assets across language variants, swapped at build time [17].
Then the part that matters for anyone costing out a similar pipeline. Rondeau says he recognised a quality ceiling in the pure-AI approach and made a deliberate architectural pivot for Chapter 2 rather than pushing more prompts at the same problem [18]. Reception on personal and niche channels stayed muted, with much of the work read by viewers as "AI slop" regardless of the craft behind it, and that is what informed the shift toward more visible manual drawing, framed as a credibility decision as much as a quality one [3].
Worth watching: whether Chapter 2's hand-drawn content moves reception at all, whether the automation and reference discipline survive the pivot or get abandoned with the generation step, and whether the remaining four pages between 24 published and the 28-page target close under the new method [19].
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
Richard Rondeau published a dev.to article describing Veridian Resonance, a project on which his role was Technical Creator / Pipeline Architect, live at https://veridianresonance.com/
100 panels were generated and refined across 24 finished pages of published visual production.
Despite the technical and process gains, audience reception on personal and niche channels stayed muted; much of the work was read by viewers as "AI slop" regardless of craft, which directly informed a continued shift toward more visible manual drawing, both as a quality decision and a credibility one.
The project evolved from a homebrew tabletop campaign; worldbuilding was initially managed through interconnected markdown nodes in Obsidian and formatted via Homebrewery.
The stated core engineering challenge was taking dense text-based relational data, including established lore, specific game mechanics and rigid character definitions, and scaling it into a full 28-page visual production.
Rondeau ran structured A/B testing across multiple aesthetic checkpoints against production criteria: consistency across panels, manual rework required, and reproducibility at volume, not aesthetics alone.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Single first-party account, no verification
All claims trace to one dev.to post written by the project's own architect. The technique descriptions are concrete and internally consistent, but every quantitative claim — 20+ to under 5 passes, 20-30 iterations for rejected styles, 15 hours saved, 100 panels across 24 pages — is a self-estimate with no published artifacts, repository, measurement method, or third-party corroboration, and no second source exists in the cluster to confirm or contradict it.
One shipped personal project, reception muted
There is a real deployed artifact — a live bilingual site with 24 published pages and 100 panels — which is more than a proposal, but adoption stops there: one creator, one project, four pages still short of the stated 28-page target, no evidence that anyone else uses the pipeline, and the author's own report that audience reception stayed muted. No traffic, sales, engagement, or downstream-reuse figures are supplied.
Mildly overstated, partly self-corrected
The post uses heavyweight framing — 'architecture', 'constraint engineering', 'production standard' — for a single-creator comic project, and leads with unverified efficiency multipliers, which pushes the gap positive. It is pulled back toward alignment by unusual candor: the author volunteers the quality ceiling, the LoRA and Midjourney consistency failures, the 'AI slop' reception, and the fact that mainstream models now ship features that would simplify his bespoke workflow. Net: claims run modestly ahead of the evidence and adoption on hand rather than dramatically so.
Portfolio post by the project's architect
The source is a self-published dev.to piece that opens with a role title and a live project link, i.e. a credentialing and traffic-driving artifact for the author's own work; the favorable metrics are the ones a hiring or client audience would weigh. That is a strong structural incentive toward flattering self-report. It is not maximal: the author discloses reception failure, incomplete pages relative to the 28-page target, and tooling that has since been commoditized, all of which run against his promotional interest, and no sponsor, vendor, or funding relationship is disclosed anywhere in the source.
Low
Confidence is limited by single-source, single-author sourcing with no corroboration and no verifiable artifacts behind the numbers. What is reliable is the existence and shape of the project and the author's stated techniques and decisions; what is not is any magnitude claim or the generalizability of the reception finding beyond one creator's personal and niche channels.
build
Four Clocks, One Timeout: Why Long-Audio Transcription Needs a State Machine1 distinct publisher
build
Your script exited 0 because the file no longer existed: macOS evicted it to iCloud1 distinct publisher
build
The kill switch that deletes your evidence is not a kill switch1 distinct publisher
build
Force the tool call, then hand Lightsail a long-lived key1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
1 article · August 15, 2026