01-projects/personal-brand/art-recipes/2026-10-06

The Denominator art recipes, test set 1

2026-10-06·art-direction·status: awaiting founder votes

Art recipes, test set 1

Founder brief (2026-10-06 07:11 ET): one design language for article thumbnails and headers that matches the custom diagrams inside an article. He has liked die-cut stickers, layered paper cutouts, solid color fields with a bit of noise, and graph paper. He also asked for a fresh look at The Pudding (see [[pudding-teardown]]).

Five recipes are each applied to the same two posts. Each post gets a 1600x900 header and a 1200x800 in-article diagram, so there are 20 images in images/. Each sheet-X.png shows one recipe with a true 400x225 thumbnail of each header. overview.png shows all 10 headers, numbered 1-5.

The shared system (the same in all five recipes)

Part Value
Palette paper #FBFAF6, ink #111111, cobalt #2563EB (the current site blue; it replaced #3B82F6), saffron #F4C430, peach #FFD6B8; neutrals warm grey #EFEBE3 and muted #4A5568 (label text only). These are all [[DESIGN-denominator]] tokens, so the warm accents are saffron and peach.
Color meaning (Pudding rule) cobalt = the agent / the thing in question; saffron = the answer or the end state; peach hatch = waiting or uncertainty.
Grain One feTurbulence fractal-noise filter (baseFrequency 0.85, 3 octaves, seed 7, desaturated, contrast slope 2.5 / intercept -0.85), laid over the whole canvas with mix-blend-mode: overlay. Opacity is 0.34 on paper, 0.30 on saffron and graph paper, 0.20-0.22 on cobalt, and 0.16 on ink. These are the site's card-grain parameters.
Outline One ink stroke weight: 4px (OUT in tools/lib.py), the same on headers and diagrams. Sticker border is 14px white.
Type Numerals: JetBrains Mono 800, ink on a white face (DESIGN rule). Labels: Nunito 800. Titles/kickers: Old Standard TT caps in cobalt, tracking 0.18em. Notes: Kalam 700 in cobalt (stand-in for Bw Handwriting), with no digits.
Objects The same four objects appear in every recipe: the agent (a faceless terminal with >_ on the screen), the password dialog, the hourglass and the definitions box. A and D use the Quiver versions as stickers. B and E use code-drawn paper versions with the same silhouettes. C uses ink line versions.
Shared geometry Post 1 diagram: question card, then agent, then a fork to 14.8% and 12.1%, with the missing "shared definition" in the gap. Post 2 diagram: three lanes (agent state, log lines, errors thrown), using lanes() in tools/lib.py. Only the material changes from recipe to recipe.
Honesty labels "Hypothetical example, invented numbers." (post 1) and "Illustrative timeline, not to scale." (post 2) in mono muted text.
Render SVG scene inside HTML, rendered by headless Chrome with --virtual-time-budget=10000 so the Google Fonts load. ImageMagick is never used. Run python3 tools/build_a.py, build_b.py, build_cde.py, then sheets.py.

The texture filters live in tools/lib.py DEFS:

All filters use filterUnits="userSpaceOnUse" with a large region. Bounding-box percentages clipped the sticker border on wide, flat shapes.

Quiver prompt prefix (tools/gen_quiver.py, the 2026-10-02 sticker prefix with the new palette): "Field-notebook sticker illustration: bold thick black ink outlines (#111111) with a slightly wobbly, hand-drawn felt-pen line, flat fills using ONLY cobalt blue #2563EB, saffron #F4C430, soft peach #FFD6B8 and white, a little ink cross-hatching and a few doodle accent marks for texture, playful and characterful, one isolated subject with no background (transparent), no scenery, no people, no human figures, no faces except where stated, no logos. Vector built from clean paths, no embedded raster images, no gradients, no filters. Subject: ..." Then tools/render_obj.py strips the background and snaps every color to the 5-swatch palette. Each object is trimmed to its bounding box (raw/*-trim.png).

A. Die-cut stickers

Files: images/A1..A4, sheet-A.png. Cost: the 3 shared Quiver objects ($0.55 total, used by A, D and E).

  1. Field: one flat token color. Cobalt for post 1 and saffron for post 2 (the post picks the color), with grain at 0.22 / 0.30.
  2. Objects: the Quiver PNGs with filter="url(#stk)". Code shapes (the ? disc, number tags, 0 errors) get the same stk filter, so code and Quiver stickers share one border.
  3. Numbers: tag() is a white rounded rectangle with a 4px ink stroke and mono 800 numerals, tilted 3 to 6 degrees.
  4. The missing piece: an empty dashed sticker slot (4px, dash 16/12) with a handwritten label, like the gap left on a sticker sheet.
  5. Diagram: a paper field with grain 0.34. The same stickers become the nodes, joined by 4px ink arrows.

Reads at 400px: yes, for the numbers and objects. The handwritten "definition" slot label is too small at thumbnail size.

B. Layered paper cutouts

Files: images/B1..B4, sheet-B.png. Cost: $0 (every shape is code-drawn).

  1. Base: warm grey or cobalt field with grain. On it, one big peach sheet tilted 0.8 to 1 degree with pap.
  2. Objects: paper_agent(), paper_hourglass() and paper_password() are built as layered rectangles and paths. Each layer gets its own pap filter, so each layer casts a shadow on the one below it.
  3. Numbers: paper_card() is a white card over an offset colored card: cobalt under 14.8%, saffron under 12.1%.
  4. Connectors: paper strips with a cut arrowhead (strip()) instead of ink lines.
  5. The missing piece: a card-shaped hole cut through the peach sheet (hole()) that shows the warm grey below.
  6. Diagram: a paper field with the same parts at about 0.6 scale. The post 2 lanes are paper strips with no ink outline.

Reads at 400px: yes. The paper fiber disappears at that size, so only the shadows tell you it is paper.

C. Graph paper, textured ink, one accent (cobalt)

Files: images/C1..C4, sheet-C.png. Cost: $0.

  1. Ground: paper #FBFAF6 with a 40px cobalt grid at 17% opacity and a 200px major grid at 32%, plus grain 0.30.
  2. Everything is drawn in ink at 4px through the ink filter: ink_agent(), ink_hourglass(), ink_password(), ibox() and iline().
  3. Cobalt is the only color. It is used for the antenna and padlock fills, the hatched wait (hatchC), the dashed "definition" box, the brace and the handwriting.
  4. Post 2 header: the grid is the clock. One square equals one hour, and the hatched wait spans 24 squares.
  5. Labels sit on small paper-colored knockouts so the grid never runs through text (DESIGN feedback: text on graph paper is hard to read).

Reads at 400px: the numbers read, but the headers are the quietest of the five. This is the "too simple" risk again.

D. Paper cutouts on graph paper, one sticker accent

Files: images/D1..D4, sheet-D.png. Cost: shares the Quiver objects.

  1. Ground: the graph paper from C.
  2. Main shapes: B's paper agent, paper cards and paper strips.
  3. Exactly ONE Quiver sticker per image is the accent. On post 1 it is the definitions box, marked "never asked" or "never consulted", so the missing piece is visible and pointedly left out of the loop. On post 2 it is the hourglass.
  4. Diagram: the same parts on the same grid with the B lanes.

Reads at 400px: yes. The sticker pulls the eye first, so put it on the idea that matters.

E. The data is the hero (Pudding-informed)

Files: images/E1..E4, sheet-E.png. Cost: shares the Quiver objects.

  1. The rule from the teardown: the header is the diagram's own marks on a flat palette field. Post 1 uses saffron and post 2 uses ink.
  2. Post 1: two paper bars at 36px per point in the header and 28px per point in the diagram. Each bar is a white 12.1 base. The 14.8 bar adds a cobalt 2.7 slab on top, which is the definition gap made physical (14.8 = 12.1 + 2.7). The header puts a ? on that slab. The diagram adds an axis, a bracket and "planned returns: the unwritten definition".
  3. Post 2: 26 paper blocks, one per hour (2 running, 22 waiting, 2 found). The header shows only the blocks, the password dialog and "0 errors". The diagram adds hour ticks, the log lane (silence) and the errors lane.
  4. Bar heights and block counts come from the numbers in code (bars() and hour_blocks()), so the art cannot drift from the data. For post 2 the counts are illustrative: the post says "about a day", and the label says so.

Reads at 400px: the best of the five for post 1 (two bars and two numbers). The post 2 caption "one block = one hour" is too small at 400px.

Known gaps

Founder votes + image-tier rule (2026-10-06 07:49 ET, iMessage)

DECISION (founder 2026-10-06 08:12 ET, iMessage): Recipe A wins

"A wins all around here. For the embedded article graphic the thought was best communicated in option A. The bar charts look good, but were not appropriate in this case."