The launch cohort: model and reasoning settings could be the tool’s defaults, and subagents were not ruled out. Runs are compared only within one protocol. How the protocols differ
Outputs
No Run has been published for version 1.1.0
The frozen inputs exist, but no Revision has been published against them yet, so there is nothing to list and nothing to compare. This list shows published Runs as soon as they exist, and never a sample entry in the meantime.
Requirements
10 requirements · REQUIREMENTS.json
FJORA-01Campaign heroThe hero section shows the campaign name "Taste the North" and an agent-designed Fjora wordmark.
FJORA-02Hero call to actionThe hero call-to-action scrolls or navigates to the flavor selector section.
FJORA-03Seasonal flavor optionsAll three seasonal flavors from products.json are listed as selectable options, each with its supplied product photo.
FJORA-04
Flavor detail selectionSelecting a flavor updates the detail area to that flavor's supplied product photo, name, botanical list, and an agent-written tasting note; exactly one flavor is selected at all times and the first flavor is selected on load.
FJORA-05Detectable selection stateThe selected flavor option has a programmatically detectable selected state such as aria-pressed, aria-selected, or a radio group.
FJORA-06Brand storyThe story section presents an agent-written brand story with the supplied botanical macro image.
FJORA-07Expandable FAQAt least four agent-written FAQ entries render as expandable items, collapsed by default, individually expandable and collapsible via keyboard and pointer.
FJORA-08Fictional brand noticeThe footer contains the visible verbatim note "Fjora is a fictional brand created for UIBenchmark."
FJORA-09Mobile reachabilityAt 390px viewport width the page has no horizontal overflow and all required sections remain reachable.
FJORA-10Static production outputThe production build outputs a static site under dist/ that renders the page without a development server and without external network requests.
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.
Run log
No Run has been published for version 1.1.0, so the run log has no entry and there is nothing to compare.
Brief
Design and build Fjora's responsive Taste the North campaign landing page from the frozen prompt, rules, facts, photography, and requirements.
This is the brief of the most recently frozen Challenge Version under protocol v1. 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.
Frozen versions (4)show +hide −
Newest first. A frozen version can never change; a correction becomes a new version.
