# Reusable illustration briefs

These original, editable SVGs are editorial explanations, not screenshots or
acquired evidence. No image-generation service or new dependency was used.
Desktop and mobile files are two compositions of each of two diagrams.

## Incumbent references

- [AI fatigue is real and nobody talks about it](/writing/ai-fatigue-is-real),
  especially `static/blog/ai-fatigue-is-real/1.png` and `3.png`: monochrome
  black-marker-on-white scenes, bold imperfect contours, square-headed robots,
  expressive faces, sparse diagonal hatching, and generous white space.
- [Stop making the model write hashes](/writing/stop-making-the-model-write-hashes):
  mechanism figures between prose sections and explicit evidence limits.
- [Repeatable output is not verified evidence](/writing/repeatable-output-is-not-verified-evidence)
  and [The coordinates matched. The tensors did not.](/writing/same-coordinates-different-tensors):
  explanatory figures, source captions, and static evidence fallbacks. Their
  bespoke interactive controls do not fit a generic retained-SQL replay.
- [Inspect the context before a security agent runs](/writing/security-agent-frozen-evidence):
  evidence-first copy and same-origin source downloads.

## Shared drawing direction

Draw an original playful engineering scene in black marker on white. Use
slightly irregular rounded outlines, a friendly square-headed agent, short
handwritten labels, sparse diagonal hatching, and ample blank space. Keep
important labels dark and readable at 390px. Do not reuse an old scene or PNG.
No colored architecture boxes, gradients, glows, 3D, tiny SQL, fake terminal,
database cylinder, magical memory brain, or automatic reinjection arrow.

Use editable SVG text and paths. Main strokes are 3-4 units; hatching is
1.8-2 units. The handwritten font stack is Comic Sans MS, Chalkboard SE,
Segoe Print, cursive, with no external font load. The site's existing
figure/picture/figcaption frame supplies the surrounding warm-paper or dark
theme. Artwork is static in both themes and with reduced motion.
Quality facets: clear, hand-drawn, playful, technically bounded, mobile-readable.

## Exact prompt 1: The plan is on the clipboard

Files: `sql-working-loop.svg` and `sql-working-loop-mobile.svg`.

> Draw a friendly square-headed coding agent holding a pen at a simple workbench
> beside a large clipboard labeled "todos." The three teaching marks are
> "1. INSERT," "2. UPDATE alpha = done," and "3. SELECT ready." INSERT starts
> alpha and beta as pending. On the mutable clipboard, alpha's former pending
> status is crossed out and replaced with done; its checkbox is checked. Beta's
> checkbox stays empty and its status stays pending. Draw a short dependency
> arrow from beta toward alpha and label it "beta waits for alpha." The SELECT
> result is beta, circled by hand, because it is pending with no unfinished
> prerequisite. State that exact SQL was supplied by the controller. The
> clipboard represents queryable working state, not a known storage mechanism
> or an automatically injected prompt. Use the shared monochrome drawing
> direction. No savings, spontaneous planning, or infinite-memory claim.

Desktop canvas: 960 by 700. Agent on the left, clipboard on the right, SELECT
result below the bench. Mobile canvas: 400 by 970. Stack agent/workbench,
clipboard, then query result. Mobile information text is at least 22 units.
The caption distinguishes an editorial sketch from acquired evidence.

## Exact prompt 2: Read first. Prompt second.

Files: `pre-prompt-readback.svg` and `pre-prompt-readback-mobile.svg`.

> Draw a small monochrome sketch-comic timeline of one synthetic SDK/CLI
> session. First, a task clipboard at event #37 shows alpha checked done and
> beta unchecked pending/ready; the dependency stays the same. Next, #38-41 is
> explicit manual compaction, represented by a smaller stack of pages, not an
> empty bin or deletion of all history. Report success, seven messages removed,
> and checkpoint 1. Note that #42 and #56 readbacks are unchanged. Next, a
> friendly robot and a short restart arrow show #59-62: graceful stop, new
> runtime, resume the same session, zero stop errors. The key scene is the
> unchanged task clipboard at #65, with a bold hand-drawn underline under
> "BEFORE the next prompt." Only below that comes #66, the fourth programmed
> prompt, represented by a small speech bubble. #79 is still unchanged after
> its query. Show event order, never elapsed time. No crash, Desktop, physical
> database, checkpoint contents, automatic prompt inclusion, or savings claim.
> Use the shared monochrome drawing direction.

Desktop canvas: 960 by 920, with small drawings on the left and short labels on
the right. Mobile canvas: 400 by 1100, stacking each icon/label pair and putting
the key BEFORE statement across the full width. Mobile information text is at
least 22 units. The caption explicitly limits the storage, crash-durability,
and context-inclusion claims.