sketch-conceptlisted

# sketch-concept Make an abstract technical mechanism feel like a small physical world. The illustration should communicate one insight at a glance, not attempt to be a complete architecture diagram. ## Visual language - Use thick, slightly wobbly black outlines, flat colors, generous whitespace, and a handwritten font resembling Virgil or Patrick Hand. - Use a soft paper-colored or saturated single-color background. Keep the palette to 4–5 colors: sky blue, pale lemon, ochre, coral, lavender, plus black. - Reuse one visual identity for like things: people for requests/tenants, small packages for chunks/messages, a warehouse for remote storage, a cabinet for cache, a ticket booth or tent for admission control. - Turn each important system component into a friendly physical metaphor. Make the metaphor support the actual behavior rather than decorate it. - Use direct arrows for the happy path. Reserve a large curved arrow for retry, queueing, timeout, or feedback loops. - Put the conclusion in the composition itself (color, position, missing item) and reinforce it with one short caption. Avoid dashboards, gradients, glossy vector UI, generic cloud-service logos, dense boxes, and more than one central claim. ## Choose the story Before generating, express the picture as: `actor → decision or absence → visible consequence` Examples: - A file read → one chunk is missing → fetch only that chunk. - Requests arrive → capacity runs out → the newest request is served first. - W