Methodology
Same prompt. Same rules. Public receipts.
Every benchmark version preserves its prompt, tool policy, execution route, run date, model release date, model metadata, artifacts, and notes. Manual/native website runs are labeled separately from API runs.
Active Prompts
| Version | Tool policy | Prompt |
|---|---|---|
| svg-v1-no-web | no web | Create a standalone SVG portrait of Gary Busey's face. Output only valid SVG markup. Do not wrap the SVG in Markdown fences. Do not use external images, links, scripts, CSS imports, or remote assets. Make the portrait recognizable as Gary Busey using vector shapes only. Include face shape, hair, eyes, eyebrows, nose, mouth, teeth, and expressive features. Use a 1024 by 1024 viewBox. Use detailed SVG-native vector techniques: layered paths, gradients, masks, clipping paths, shadows, highlights, blur filters, opacity, and fine strokes. The portrait should be as recognizable and detailed as possible. |
| image-v1 | manual unknown | A recognizable editorial portrait of actor Gary Busey, centered face, expressive eyes, broad smile, detailed hair, neutral studio background, high detail, square composition. Do not include text, logos, watermarks, or extra people. |
No Numerical Scoring
BuseyBench does not assign numerical grades. The point is visual comparison over time: how model releases improve, degrade, or simply get stranger under the same prompt. Notes can describe context, failures, or manual-run caveats, but the gallery avoids pretending subjective likeness is an objective leaderboard.
What To Compare
| Model release date | Newest and oldest model sorting uses the model release date, not the date the prompt was run. |
|---|---|
| Prompt version | Runs are only apples-to-apples when they use the same prompt version and tool policy. |
| Execution route | OpenRouter, direct API, native website, and manual uploads are labeled because those surfaces can behave differently. |
| Artifact source | SVG runs expose stored source so the output can be inspected beyond the rendered preview. |
Safety Handling
Model SVG output is treated as untrusted code. The app extracts SVG markup, rejects scripts, event handlers, remote assets, and embedded objects, then stores the sanitized artifact for review before publication.