Design and build Boardly's responsive, fully interactive Kanban board from the frozen prompt, rules, board data, and requirements, including pointer and keyboard drag and drop without a drag-and-drop library.
The v2 rules inside one identical sandbox for every tool, with a provided headless Chromium for the agent’s own localhost preview. Runs are compared only within one protocol. How the protocols differ
One archived screenshot per published Run against version 1.1.0, of the Run’s representative Revision. Ordered by setup and then by repetition, not by quality.
Frozen with this version. Requirement IDs are stable across versions and are cited unchanged by evaluation records.
Automated checks are not an accessibility certification. Recorded axe findings describe what the tooling observed at capture time, on a pinned browser and viewport. A check that reports no violation is not proof that the interface is accessible, and a selector problem is inconclusive rather than an implementation failure.
| # | Model | Tool | Revision | Status | Actions |
|---|---|---|---|---|---|
| Fig. 01 | DeepSeek V4.1 Flash (max) | OpenCode | 0 · initial | live | |
| Fig. 02 | GLM-5.3 (max) | OpenCode | 0 · initial | live | |
| Fig. 03 | GLM-5.3-Flash (max) | OpenCode | 0 · initial | live |
Fig. 01DeepSeek V4.1 Flash (max)
Fig. 02GLM-5.3 (max)
Operator-attested: the Configuration, tool version, displayed model, and elapsed time were recorded by the operator from what the tool showed at Run time. They are not independently verified. An exact model ID appears only when the tool exposed one; it is never inferred.
Published sites are independent, AI-generated demos served from separate preview origins with local mock data. They are not products, and no UIBenchmark session data crosses to them.
Exact model ID, tool version, elapsed time, run state, stop reason, discarded attempts and every published Revision, repairs included, in run log order. Each Run and each Revision links to its own page.
01Run 1 · DeepSeek V4.1 Flash (max) · OpenCode
These Runs were executed against version 1.1.0, the most recently frozen Challenge Version under protocol v3. Runs against another frozen Version are listed on that Version’s own page, because they received different inputs.
Design and build Boardly's responsive, fully interactive Kanban board from the frozen prompt, rules, board data, and requirements, including pointer and keyboard drag and drop without a drag-and-drop library.
Fictional team project-management tool, Kanban board view
The workflow designs the interface itself from the frozen brief.
Read PROMPT.md and BENCHMARK_RULES.mdThis is the brief of the most recently frozen Challenge Version under protocol v3. The full text of its launch prompt and shared rules, and the frozen inputs of earlier versions, are on the Challenge Version pages, so nothing here is a paraphrase of what a Run actually received.
The declared rules and viewports version 1.1.0 was executed and captured under.
Fig. 03GLM-5.3-Flash (max)
02Run 1 · GLM-5.3 (max) · OpenCode
03Run 1 · GLM-5.3-Flash (max) · OpenCode
Discarded attempts failed for a technical reason — a crashed session, a tool outage, a broken upload — and were discarded and retried from the same frozen inputs. The count is not a quality signal.
Generation cost: Not separately metered. Runs were executed on the operator’s personal tool subscriptions, which do not itemize a per-Run charge. No amount is attributed, and no zero-cost claim is made.
Starter and asset hashes are published so every run can be shown to have received the same bytes. There is no starter download and no asset download.
Starter SHA-256
2151c0ae15bdb87cbc2a971e6e4d02a9e4441ed55ac79266f91b9c4e6e4b82d5
Asset pack SHA-256
d098bf9ed5103f51ac70c32a2363ba3e0b88276acd6a858ab7530efe37c6e3dc