generation rules

Image render contract

Contract between reading result, share-card, PDF, OG preview, and asset storage.

Separate private text from public image and prevent rendering from accidentally pulling user secrets.

Where used

  • /api/visual-assets/render-plan
  • post-payment delivery
  • share-card renderer

Visual direction

  • The render plan resolves privacy first, then format, then prompt.

Technical specs

  • API returns renderPlan, redactedFields, assetPath, dimensions, alt, and QA checklist.

base prompt

Text for generation or designer

Render contract first: privacy, surface, format, dimensions, public fields, forbidden fields, prompt, negative prompt, alt, storage path

Accessibility

  • Alt is required for every public asset.

Quality checklist

  • Public format contains no private fields.
  • All filenames are deterministic.

render lab

Build image plan

vr_ece79778c5a360

Share card 1080×1080

safe
Size
1080×1080 · 1:1
Visibility
public
Path
/public/visuals/share/tarot-safe-answer-1080x1080.webp
Alt
square card: Tarot glyph: card and ray

Redacted

  • nothing

QA

  • No readable text inside the image.
  • No private question, email, birth dates, or payment id in a public asset.
  • Central safe area works for mobile crop and the HTML layer.

Prompt

OmenHall visual system, gold and deep violet, card back, sun seal, square share card background, elegant blank center, decorative oracle frame, no readable text, premium medieval oracle house, warm amber candlelight, deep violet shadows, brass and silver linework, no readable text, no horror

related doors

Where to go next