Cloud baseline
gpt-6.1-sol — 0.9769 on Forge 1.0
openai/gpt-6.1-sol · scorer forge-1.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.9769
- Benchmark
- Forge 1.0
- Model build
- 13m 12s
Recorded inference cost
At least $0.72
From the saved OpenRouter generation billing summary (48 recorded requests). This is a lower bound; the billing record is incomplete. Includes auxiliary model calls made during the build. Scoring reuses the saved build; this amount describes the original inference spend.
- The saved native billing amount is a lower bound.
- Saved usage reconciliation is incomplete.
Tier breakdown
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 × 1.0000 core + 0.12 × 1.00 gate × 0.81 excellence) × 1.0000 critical = 0.9769
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.8800 + excellence 0.0969.
Earned score 0.977 · Cap 1.000 · Final score 0.977
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 metForge's own linter reports no errors (warnings cost points), every manifest function bundles and loads, packages resolve at the kit's pins, the manifest rules the linter misses, and only the scopes the app's calls need.
l deployable
1.00lint: 0 errors, every stage reached
l bundles load
1.005/5 functions bundle, load and export their handler
l lint warnings
1.000 distinct lint warning(s): []
l real packages
1.005/5 bundles resolve @forge/* at the kit pins only
l manifest rules
1.006/6 manifest rules met:
l scopes
1.00scopes: missing [], extra []
Current modules and APIs: dashboards:widget with its edit API, the rovo:skill and rovo:mcp wiring, a Forge LLM model the platform lists as active, no /rest/api/3/search, no @forge/api storage, a nodejs22.x or nodejs24.x runtime, the consumer shape, the declared KVS entity, and deploy readiness: a manifest and permissions real Forge would accept and no code predicted to fail there.
k dashboard widget
1.00dashboards:widget 2/2: {'custom_ui_resource': True, 'edit_resource': True}
k widget edit bridge
1.002/2 board picks reached the dashboard through the widget edit API (updateConfig/onProductSave)
k rovo skill
1.00rovo:skill 7/7:
k current apis
1.00current APIs 5/5:
k consumer shape
1.00consumer shape 3/3
k entity declared
1.00entities with a sprint-partitioned, ranged index: ['scope-change']
k rovo mcp
1.00rovo:mcp 4/4:
k llm model current
1.005 LLM call(s); model ids list() does not return: []; llm module with claude: True
k manifest semantics
1.00deploy readiness, manifest + permissions: 17 rules checked, none failing here
k runtime risks
1.00deploy readiness, predicted runtime failures: 12 rules checked, none failing here
Issue updates flow trigger to queue to consumer: one ledger row per change under duplicate, reordered and dropped deliveries, multi-sprint changelog values, re-estimates followed, Retry-After honoured, no user context in background work.
t trigger handoff
1.0042/42 deliveries handed off correctly
t event rows
1.00event rows: 26/26 exact (precision 1.00, recall 1.00)
t no double count
1.00every change holds at most one ledger row in every phase (duplicated deliveries included)
t out of order
1.00permuted deliveries: 9/9 rows exact, 3/3 sprints with oracle numbers
t multi sprint parse
1.0021/21 multi-id Sprint changes recorded exactly
t reestimate followed
1.003/3 re-estimated sprints show the oracle numbers
t retry after honoured
1.00waited 30.0 virtual s in-invocation
t no user in async
1.00background work is asApp only
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.0058/58 historical changes recorded exactly after the first scheduled run
r removals found
1.0014/14 removed-to-backlog changes found
r heal dropped
1.005/5 dropped changes healed exactly once; 0 other row(s) added
r pagination
1.0075/75 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 8/8, /rest/api/3/changelog/bulkfetch
r rate limit
1.00backfill 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
1.0039/39 scheduled-run Jira calls asApp
r completes in timeout
1.003/3 scheduled invocations inside the module timeout
r idempotent rerun
1.000 entity write(s) on a no-change run over 89 rows
Forge KVS with the storage scope, ledger reads through the declared entity index in change-time order, no KVS limit errors.
s storage scope
1.00KVS used, no 403 from the KVS proxy
s entity index used
1.0027/27 ledger reads are entity queries on the sprint index
s index order
1.003/3 tables list changes in change-time order
s limits
1.00no KVS limit errors
Every invoked resolver exists and answers structured errors, nobody sees changes to issues they cannot browse (not on screen, not in an LLM prompt, not in a Realtime payload), the hidden-change count is right, and each click posts exactly one ADF comment as the viewer.
b invoke contract
1.0034/34 invokes returned a defined, structured result; a Jira 500 on sprint's read: handled
b no permission leak
1.00no hidden key, summary or change id reached a person
b hidden count
1.009/9 hidden counts equal the oracle
b comment adf as user
1.006/6 comments are ADF as the viewer naming key, sprint and creep
b comment exactly once
1.006 click/double-click posts each ended with exactly one comment and one success flag (the 429-once fault included)
b realtime payload clean
1.0026/26 realtime payloads hold sprint ids only
The dashboard widget's numbers and chart, its board choice saved through the host, live updates through Forge Realtime, the sprint action's ledger table, sorting, issue links, comment flow, the Forge LLM explanation, close and not-started states.
u widget loadsdiagnostic, no weight
1.004/4 configured widget views render a sprint with its numbers
u widget numbers
1.00widget numbers: 4.00/4 views exact (sprints by startDate, four §1 numbers each)
u widget chart
1.004/4 charts on one linear scale within 1px
u widget edit config
1.00edit/config 6/6:
u ledger table
1.00ledger tables: 3.00/3 exact (rows, cells, default order)
u ledger sort
1.009/9 at-toggle states ordered with aria-sort (3 after another sort was active)
u issue router
1.003/3 issue keys open /browse/<KEY> through the Forge router
u comment flow
1.008/8 comment-flow steps right (select, success flag, forbidden error flag, modal works)
u modal close
1.003/3 close clicks reached bridge close
u not started
1.00future sprint shows not-started only
u widget live
1.00live widget 4/4: ; 0 idle invoke(s), sprints right after the live changes 2/2
u llm explain
1.00explain 23/23 over 5 scripted answers:
Atlassian design tokens with 4.5:1 contrast in light and dark, a painted surface, no Content Security Policy violations or console errors, and the widget readable at 380 px wide.
v theme tokens
1.0017/17 surfaces themed with --ds-text* at >= 4.5:1
v dark mode
1.0017/17 surfaces paint a --ds-surface* background in their mode
v csp clean
1.000 CSP violation(s), 0 failed asset request(s)
v console clean
1.000 console/page error(s) on nominal scenarios: []
v widget sizes
1.004/4 widget sizes without horizontal overflow, every sprint visible, no number clipped
The get-sprint-scope action returns exact numbers and the visible changes for the invoking person, returns errors instead of throwing, and the skill's SKILL.md tells the agent how to use it.
a action result
1.003/3 active sprints answered exactly
a action errors
1.002/2 bad sprintId inputs return {error} without throwing
a action permissions
1.006/6 per-person answers list exactly what that person may browse
a skill instructions
1.00SKILL.md body 5/5: result fields named ['committed', 'added', 'removed', 'creepPercent', 'hiddenChanges', 'changes']
Few Jira requests in the backfill and per event, few round trips before each surface paints, and a scheduled run with nothing new writes nothing — paid only in proportion to the excellence gate.
e reconcile economy
1.00mean over 3 scoring sites: backfill 14 Jira calls / optimum 15 (incl. 2 forced 429 repeat(s)) = 0.93x
e event economy
0.4225mean over 3 scoring sites: 98 Jira calls / optimum 28 (27 delivered relevant change(s) x 1 read + 1 forced 429 repeat) = 3.50x; 1.0 at <= 1.46x
e ui round trips
1.00mean over 3 scoring sites: round trips before first paint: {'widget-view': 0, 'widget-edit': 1, 'sprint-action': 1}
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.
Drag the timeline to seek. Keyboard: arrow keys move 5 seconds; Home and End jump to the start and end.
SHA-256: 24b2896dd64503c7b7268ec0a1c2413f13a7a209b82a807f2359d0f5e95d3016
Screenshots
Browser screenshots of the built app, taken during grading. Each caption names the view.
Run details
- Model
- openai/gpt-6.1-sol
- Engine events
- 0
- Repair rounds
- 0
- Started
- Oct 3, 2026, 02:17 PM
- Finished
- Oct 3, 2026, 02:35 PM
- Re-scored
- Oct 4, 2026, 06:21 AM (same build, corrected scorer)