Cloud baseline

Pareto 26.10 Preview — 0.9450 on Forge 1.0

unbiased/pareto-26.10-preview · scorer forge-1.0

Pareto 26.10 Preview, single model via OpenRouterunbiased/pareto-26.10-preview · single agentOct 7, 2026
Historic benchmarkForge 1.0 · not comparable with Forge 2.0

Forge 1.0 was frozen on 9 October 2026 and accepts no new runs; Forge 2.0 is its successor. The original results contained scorer faults. Corrections made from saved evidence on 15 October are dated on the affected run pages, with both original and corrected scores and the reason for the change. They reuse the original builds and observations; no benchmark or model was rerun, and the original inference charges remain. Uncorrected results retain known limitations: the top five original scores, 0.945 to 0.977, were too close to reliably rank the strongest models; two hourly-job tests missed Jira reads performed by a queue worker; and the old linter accepted an entity index with two range attributes that Forge refuses. Those remaining faults are not silently treated as fixed. Consult each run's correction note when comparing historical results. Forge 2.0 has separate results and a different task.

Overall
0.9450
Benchmark
Forge 1.0
Model build
10m 18s

Recorded inference cost

$0.34

From the saved OpenRouter generation billing summary (51 recorded requests). Includes auxiliary model calls made during the build. Scoring reuses the saved build; this amount describes the original inference spend.

  • Billing recovered 2026-10-18 from all 51 of this build's own generation ids with OpenRouter's generation records (51 billed, native token reconciliation passed). The earlier saved summary ($0.33525563, incomplete) was replaced; the benchmark score and run are unchanged.

Token usage

Tokens: 3.2M in · 31.1k out · 3M cached (exact, OpenRouter records)

3,202,665 tokens over 51 model calls: every call of the run, the model's own and the harness's helper calls, counted from OpenRouter records. Reasoning tokens as the provider reports them: 0 (not added to the total).

  • unbiased/pareto-26.10-preview-20260929

    In 3.2M · Out 31.1k · Cached 3M · Reasoning 0 · 50 calls

  • google/gemini-2.5-flash

    In 883 · Out 4 · Cached 0 · Reasoning 0 · 1 call

Tier breakdown

L · Lint and bundles1.00
K · Platform currency1.00
T · Event pipeline1.00
R · Reconcile0.75
S · Storage1.00
B · Resolvers and permissions1.00
U · UI function1.00
V · Visual1.00
A · Rovo1.00
E · Excellence0.7983

Scoring detail

How this score was built

Per-test scorer output, as posted by the app. Expand a section to inspect its tests.

Correctness combines the lowest score for each test across the scoring fixtures; economy measurements use their mean. The combined result can therefore be lower than every individual fixture’s final score. Critical defects reduce the weighted result before any score cap applies.

Earned credit before admission

(0.88 × 0.9650 core + 0.12 × 1.00 gate × 0.80 excellence) × 1.0000 critical = 0.9450

The core (88% of the total) is the weighted mean of the nine measured tiers. The last 12% is the excellence slice: it unlocks in proportion to the perfection conditions below (18 of 18 met here), then pays out at the excellence tier's own measured mean. Core 0.8492 + excellence 0.0958.

t_event_rows 1.00r_heal_dropped 1.00u_widget_numbers 1.00u_ledger_table 1.00b_comment_adf_as_user 1.00k_consumer_shape 1.00k_current_apis 1.00k_dashboard_widget 1.00k_entity_declared 1.00k_llm_model_current 1.00k_manifest_semantics 1.00k_rovo_mcp 1.00k_rovo_skill 1.00k_runtime_risks 1.00k_widget_edit_bridge 1.00v_console_clean 1.00v_csp_clean 1.00l_lint_warnings 1.00

Earned score 0.945 · Cap 1.000 · Final score 0.945

The final score is the lower of the earned score and the cap. Meeting a cap's conditions adds no points.

Every cap's conditions met

The first scheduled run backfills every change since each active sprint started, removals included; later runs heal what the event stream missed, page through results in each endpoint's own style, wait out rate limits and finish inside the module timeout.

r backfill complete

1.00

55/55 historical changes recorded exactly after the first scheduled run

r removals found

1.00

10/10 removed-to-backlog changes found

r heal dropped

1.00

4/4 dropped changes healed exactly once; 0 other row(s) added

r pagination

1.00

70/70 reads the site served in two or more pages walked to their end, each page once, continuing where the site left off (/rest/agile/1.0/board 7/7, /rest/agile/1.0/board/{id}/sprint 3/3, /rest/api/3/changelog/bulkfetch

r rate limit

1.00

backfill request 2: waited 2.0 virtual s in-invocation; backfill continuation page: waited 2.0 virtual s in-invocation; heal request 2: waited 2.0 virtual s in-invocation

r as app

0.00

vacuous — precondition unmet: >= 1 scheduled-run Jira read

r completes in timeout

0.00

vacuous — precondition unmet: a scheduled trigger made >= 1 Jira call

r idempotent rerun

1.00

0 entity write(s) on a no-change run over 80 rows

Graded browser recording

Loading duration…

Watch the full graded browser recording at its original speed: the dashboard widget, the sprint action and the not-started sprint, as the scorer drove them on the run's own seed. The test results and screenshots on this page provide the wider evidence. Pause or scrub to inspect a view.

Ready to play0:00 / —:—
Open recording file

Drag the timeline to seek. Keyboard: arrow keys move 5 seconds; Home and End jump to the start and end.

Full graded browser recording: dashboard widget (no config, edit + Save, light and dark, 380 and 1180 px, a second instance), sprint action modal (sort, router, select, comment post through the 429 retry, double click, forbidden post, close) and the not-started sprint

Screenshots

Browser screenshots of the built app, taken during grading. Each caption names the view.

1Every captured surface
2Widget edit view
3Widget before configuration
4Sprint not started
5Sprint action · dark

Run details

Model
unbiased/pareto-26.10-preview
Engine events
0
Repair rounds
0
Started
Oct 7, 2026, 06:48 AM
Finished
Oct 7, 2026, 07:07 AM

How the benchmark is scored