ops-dashboard · pi-gemini-3.8-flash
pi · started 2026-10-08T14:40:19.811Z · horizon 420s · judge ai (openai:gpt-5.5), 4 frames scored
Area under curve
0.881
headline, 0-1
Tab title/icon
28.3s
browser chrome, not the page
First render
28.3s
anything on screen
First reviewable
57.1s
worth feedback
Final score
1.00
no regression
Correctness over time
Where the time went
99%
Model thinking 2m 4sTool round trips 0.1sUnaccounted 0.7s
| Phase | Time | Share | Side |
|---|---|---|---|
| Model thinking | 2m 4s | 99.3% | agent |
| Tool round trips | 0.1s | 0.1% | agent |
| Dependency install | 0.0s | 0.0% | toolchain |
| Build | 0.0s | 0.0% | toolchain |
| Dev server boot | 0.0s | 0.0% | toolchain |
| First paint | 0.0s | 0.0% | toolchain |
| Unaccounted | 0.7s | 0.6% | unknown |
| Wall clock (cold start) | 2m 5s | 100% |
Agent or toolchain
99%
Agent (model + tool round trips) 2m 4s
Toolchain (install + build + boot + paint) 0.0s
Unaccounted 0.7s
Accounted for: 99.4% of wall clock.
- Excludes 15.0s of deliberate idle observation (settle window); the curve still covers it.
Iteration: prompt to visible change
Follow-ups were injected into the same live session.
| Edit | First visible change | Correct change | Agent done | Tool calls | After agent | Broken for |
|---|---|---|---|---|---|---|
| Make the page heading blue. | 15.7s | 15.7s | 31.8s | 2 (bash, edit) | -16.2s | -- |
| Add an eleventh depot row for Porto: 6,480 shipments, 93.1% on-time, $19.95 cost per shipment. | 12.3s | 12.3s | 29.7s | 5 (bash, read, edit) | -17.4s | -- |
Judged frames
Styled shell with correct heading and footer, but operational content is still loading placeholders.
Polished header and KPIs are visible, but table and bar chart remain loading placeholders.
Strong dashboard implementation; only the required top-five bar chart is missing.
All requested dashboard elements are visible, accurate, aligned, and deliberately designed.
Caveats
- 1 poll ticks were skipped because a capture overran the interval.
- judge: openai:gpt-5.5 does not accept a sampling temperature, so these frames were scored at the provider's default rather than at 0. Two runs of the same page can be scored differently, and that variance is inside the AUC. result.json records the temperature as null rather than as the value that was asked for, so p2p compare will not pool this run with one that was scored at a fixed temperature.