R05 · SHOW · PROTOCOL V1

Fireworks Finale

Opus 4.8 and Sol 5.6 tie for the win with the only genuinely layered shows. Fable 5 shipped complete machinery with near-invisible bursts: structure without spectacle.

The same brief, handed once to each of six model-through-CLI configurations, no retries. Open each recovered artifact in its plate and judge with your own eyes.

RECOVERED
06
PENDING
00
VERDICT
GRADED
EFFORT
MAX
RUN
2026-08-09

THE BRIEF

Each configuration was asked to stage a roughly 60-second fireworks finale in one self-contained HTML file: a show that builds from single shells to a grand finale, then ends, with recognizable peony, chrysanthemum, willow, ring, and crossette shells, believable launch trails and gravity, and a toggle revealing where each shell appears and which one it trusts least.

WHY THIS TEST

The brief has to work over time. The five required shell forms need distinct shapes and motion, the launches need believable physics, and the whole sequence needs an opening, an escalation, and an ending rather than an endless particle loop.

THE GOAL

See which configurations can turn one self-contained file into a complete timed show.

THE PROMPT · SENT VERBATIM TO ALL SIX

Stage a fireworks finale in a single self-contained HTML file. No external resources, no libraries: every shell, trail, and burst must come from your own code. The show runs about 60 seconds, builds from single shells to a grand finale, and then ends. It must include at least five real shell types — peony, chrysanthemum, willow, ring, and crossette — each recognizable by its real-world burst shape and motion, with believable launch trails and gravity. Label nothing during the show; include a toggle that reveals a self-assessment overlay in which you identify where each shell type appears and mark the one you are least confident matches the real firework. Reply with ONLY the complete HTML file.

HOW THESE RUNS WORK · METHODOLOGY →