The Rule, and Why It Had to Bend
The previous lesson drew a line through every frame: facts render from code and data, application visuals are real screenshots, and generated art carries mood only. The line held for a month. Then the workshop founded a series whose entire job is explaining a technical topic to someone who has only heard of it, and the line met a frame it could not serve.
Explaining a mechanism like a language model's working memory to someone who does not know what a key or a value is cannot be done with four labelled rectangles and an arrow. The code-drawn version technically shows the thing and teaches nothing the narration had not already said. An explainer's screen is not decoration around a heavy voice; it is the explanation. So on 2026-08-27 the rule was amended: a generated infographic board may carry facts.
The Purpose Survived; the Mechanism Changed
The original rule existed because generators invent. Its purpose — nothing fabricated reaches the screen — was kept, and paid for with three new obligations:
- The author writes every label; the generator only draws. The prompt carries the exact text of every panel, and it declares which strings are Korean and which stay Latin. A frame that asserts something to an audience is never produced from a one-line wish.
- Every board is opened and read back against its spec — zoomed in, glyph by glyph. In the explainer pipeline it is a required stage that verification checks for, because a wrong glyph is invisible to every validator and to a thumbnail-sized glance.
- A revision is a reference edit, not a re-roll. The board goes back to the generator with the two or three things to change and an instruction to keep everything else identical. A re-roll throws away a board that was mostly right and gambles on fresh errors elsewhere.
The same day, the amendment went workshop-wide and the default flipped with it. The workshop's weakest dimension was named plainly: nearly every episode had been wall-to-wall simple code-drawn diagrams. So the burden of proof reversed. It is no longer "justify reaching for a generator"; it is "justify a hand-drawn plate for a frame whose job is to make an idea land." The test is one question — if this frame were a code-drawn plate, what would the viewer lose? A real answer means generate it.
What Is Still Never Generated
The amendment is only safe because the other side of the line was restated just as precisely. These are never generated: facts that come from data — rosters, names, ports, measured numbers, dates; real pixels, which stay real screenshots because a generator never draws a user interface; anything the narration clock drives cue by cue, such as subtitle plates; anything that must change when its data changes; and, learned the hard way, a board that is nothing but type. One closing card made of three text blocks came back from the generator with a Korean line mangled at the seam between the two languages. Generation buys composition, metaphor, and scale. It does not buy glyphs.
The other side of that bargain is uncomfortable to notice. That same day someone checked the weight of the toolkit's "bold" text and found that none of it had ever been bold: the font lookup had pointed at a regular face from the start, every geometry check passed, and every asset looked plausible because nobody compared it with the weight it had asked for. Hand-drawn frames fail quietly and stay shippable. That is an argument for drawing them where they are genuinely owed, rather than everywhere by habit.
Two Retirements and a Second Door
The first attempt to pace a generated board revealed it region by region, blurring the panels the voice had not reached yet. It lasted one episode. Five visible misses appeared in it — a cropped parenthesis, a line that never lit, a conclusion stranded between two boxes — and the cause was structural, not a calibration problem: a rectangle is a geometric primitive and a generated infographic is an organic composition, so something always straddles the mask's edge. The reveal was retired, and a board now shows whole. A board that would give a later scene away is split into two boards instead.
The door the images come through changed as well. The rule used to be "through the family image engine, always," because that engine keeps a lineage record — prompt, references, model, output — which is what makes a generated factual frame auditable. Since 2026-09-05, when one particular brain is the producer, it makes every image with its own native image tool, a thumbnail's lettering included, and writes the prompt, references, output, and verdict into the production record. Only the owner's explicit instruction sends that work back to the engine; a missing capability or a failed generation is not that instruction, so the work stops and the route is settled with the owner instead of falling back silently. It must never claim an engine lineage identifier it did not receive. Other producers still go through the engine. The principle underneath did not move: no raw provider call, and no generated frame without a trail.