Revision record
loading

Run record
loading

Boardly — Website Relaunch 1.0.0 — Revision 0 — UIBenchmark

boardly-app@1.0.0

Revision 0

of Run 1, Boardly — Website Relaunch, Version 1.0.0

liveGPT-6-Luna (max) · Codex CLIrev 0 · initial · run 002eb636publication state: published

The first Revision the Run produced from the frozen inputs. It was produced by Codex CLI codex-cli 0.155.1 running GPT-6-Luna, in Run 1 of Challenge Version 1.0.0.

Open live site Compare View source

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.

§1Identity

Which frozen inputs this Revision answers, and where it sits in its Run.

Challenge: Boardly — Website Relaunch
Category: web-app
Task type: Original design
Challenge Version: 1.0.0
Protocol version: 2.0.0
Repetition: 1
Revision index

§2Configuration

GPT-6-Luna (max) · Codex CLI

The immutable snapshot of the coding workflow. A changed tool version or exposed setting becomes a new Configuration rather than an edit of this one.

Tool: Codex CLI
Version: codex-cli 0.155.1
Surface: Command-line interface
Model shown by the tool: GPT-6-Luna
The model family page lists every Configuration recorded under this display name. It groups them for navigation only and never merges two identities.
Exact model ID: gpt-6-luna

§3Execution

What the operator recorded while the Run that produced this Revision was executed.

Run state: Submitted
Stop reason: Completed
Elapsed time: 12 min 5 s
Discarded attempts: 0
Attempts that failed for a technical reason and were discarded and retried from the same frozen inputs. The count is not a quality signal.
Generation cost: Not separately metered

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.

§4Timing

UTC

Three different moments, kept apart on purpose. All values are Unix milliseconds UTC in the archive and are shown in UTC here.

Challenge Version frozen: 2026-09-23 11:03 UTC
Generation time: 12 min 5 s
How long the Run took, as the operator recorded it. It is not a start or end moment.
Finalized: 2026-09-23 19:49 UTC
When the uploaded Bundle became immutable in the archive.
Published: not recorded
The archive does not record a separate publication moment yet, so this stays unrecorded rather than reusing the Finalize time.

§5Usage

tokens · tool-reported

Token counts as the coding tool itself reported them. Nothing here is a cost, a price, or a measurement the platform took.

Unit: Tokens
Reported by: Codex CLI rollout log (JSONL) reported by the tool
Model ID in the usage record: gpt-6-luna

Token categories reported for Revision 0, in the names the tool uses.
Category as the tool reports it	Tokens

§6Evaluation

What the automated checks recorded, and which evidence artifacts the operator approved for publication.

Automated checks: 14 of 18 recorded checks passed
Accessibility scan: 2 recorded violations

Recorded evidence4 artifacts

Evidence artifacts recorded for this Revision, with their kind and size. The files themselves are not served in this release and cannot be downloaded.
Name	Kind	Size

§7Hashes

SHA-256

The recorded digests of the immutable trees. They are shown in full so a published Revision can be checked against the bytes it was built from.

Source tree SHA-256: cf1c60a0a40f1aad0a54e313602b9d9bf911a27ce816807581c0f4f78a1fe6ba
Compiled tree SHA-256: dcb52c520119d80d803cc0cb5646b144a9f1e37b645858c037bbff6a4dccc302

§8Lineage

Revision 0 is the only published Revision of Run 1.

§9Deployment

Where the generated site is served from, and whether it is being served right now.

Preview host label: p-01a0cfd1-0707-7132-a32b-d3816b8678aa
Each generated site is served from its own preview address under this site's domain. Sign-in cookies for this site are locked to its own address and are not sent to preview sites, but because previews share the domain a small cookie risk remains.
Currently served: Yes — the activation record is confirmed active
A Deployment is served only when the operator asked for it and the preview Worker confirmed the activation record.
Activation last reconciled: 2026-09-23 19:50 UTC

§10Limitations

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.

Source is browser-viewable only. There is no download or archive endpoint, and no additional license is granted beyond inspection and research.

Revision 0

§1Identity

§2Configuration

§3Execution

§4Timing

§5Usage

§6Evaluation

Recorded evidence4 artifacts

§7Hashes

§8Lineage

§9Deployment

§10Limitations

Screenshots5 screenshots

Desktop

Mobile

Other captures

Loading this Revision…

Loading this Run…

Loading this Revision…

Revision 0

§1Identity

§2Configuration

§3Execution

§4Timing

§5Usage

§6Evaluation

Recorded evidence4 artifacts

§7Hashes

§8Lineage

§9Deployment

§10Limitations

Screenshots5 screenshots

Desktop

Mobile

Other captures