Reusable HTML Spec

THUMBNAIL PIPELINE v1.0

A deterministic generation spec for center-band, 16:9-safe, high-urgency thumbnails using a fixed template workflow. Written to be reusable, shareable, and revised over time.

Core Objective

Generate maximum-impact thumbnails that place all meaningful content inside a true 16:9 horizontal band, leaving all outer vertical space disposable. Output must be visually dense, emotionally urgent, and directly compatible with a fixed magenta-band template.

Single message only Band constrained No wasted vertical dependency Template-first layout Readable at small scale

Non-Negotiable Rules

1. ALL meaningful pixels must exist inside the center band.
2. NO critical text or objects may cross the band edge.
3. TOP and BOTTOM zones are dead space.
4. NEVER generate multiple thumbnails in one image.
5. EXACTLY one message per thumbnail.
6. Text must be readable at 10% scale.
7. Composition must be horizontally compressed.
8. Output must align with the template without manual repositioning.

Template Geometry Model

Canvas Height = H
Canvas Width  = W

Band Height = user template center band
Band Width  = full template width used by composition

Active zone:
Y in [band_top, band_bottom]
X in [safe_left, safe_right]

Everything outside active zone = ignorable / black / empty

Default Message Rotation

1. BILLIONAIRES OWN YOUR DATA?
2. YOUR DATA. THEIR POWER.
3. WHO TOOK YOUR DATA?
4. THIS IS NOT OK
Selection rule: use one message per image. Do not combine. Do not stack unrelated claims into a collage. Rotate sequentially unless the user explicitly overrides the message.

Text Rendering Spec

Typeface style: heavy sans / condensed / bold
Case: ALL CAPS

Primary line:
- Max width fit inside band
- Color: #FFD400 or #FFFFFF
- Stroke: dark, strong
- Glow: subtle

Secondary line:
- 60% to 75% of primary size
- White or yellow only

Alignment:
- left or center
- never right if it risks clipping

Line count:
- max 2 lines
- prefer 1 if message permits

Visual Subject Library

- generic silhouettes of power figures
- data streams / binary fields
- server racks / glowing networks
- locks / broken encryption motifs
- warning panels / cracked interfaces
- city grids / transmission overlays
- glowing cubes / data cores / folders
- money stacks only when visually useful

Composition Rules

  1. Primary subject must sit entirely inside the horizontal band.
  2. Fill the band with horizontal energy, not vertical stacking.
  3. Foreground object + midground tension + background system layer.
  4. Do not place empty dead space inside the band if text can be enlarged.
  5. Do not split the image into four panels, side-by-side concepts, or storyboard fragments.
  6. Maintain high contrast and emotional immediacy.

Color System

Primary palette:
- Red     #FF2A2A
- Orange  #FF7A00
- Yellow  #FFD400

Secondary palette:
- Deep blue  #0A1A3A
- Black      #000000
- White      #FFFFFF

Rule:
Warm = threat / urgency / power
Cool = data / systems / surveillance
Contrast must remain high

Validation Checklist

Before returning final output:

[ ] Single message only
[ ] No multi-panel layout
[ ] All text fully inside band
[ ] Main subject fully inside band
[ ] No dependency on top/bottom zones
[ ] Readable at thumbnail scale
[ ] Visually dense and emotionally clear

If any item fails: regenerate

Execution Logic

INPUT:
- Template image
- Optional headline override

PROCESS:
1. Read template geometry from uploaded reference.
2. Detect exact center band position and usable width.
3. Select one headline.
4. Build a single-scene composition constrained to the band.
5. Keep top/bottom visually empty or discardable.
6. Place and scale text for 10% readability.
7. Validate against checklist.
8. Return only if fully compliant.

OUTPUT:
- One thumbnail image
- Compatible with the fixed template workflow
- No composite sheets, no concept boards, no collages

Revision Protocol

Revise this file over time as a living spec. Keep the structure stable and append observations after testing.

Revision log template:

Date:
Test input:
Output result:
What failed:
What succeeded:
Rule update:
Next version:
Failure pattern to avoid: returning concept sheets, collages, or multiple thumbnail ideas in a single image. The pipeline is successful only when it returns one band-compliant asset at a time.