GAD
v1
requirements unknown
2026-04-06
pre-gate requirements

Escape the Dungeon · GAD

escape-the-dungeon/v1

Composite score

0.000

Dimension scores

Where the composite came from

Each dimension is scored 0.0 – 1.0 and combined using the weights in evals/escape-the-dungeon/gad.json. Human review dominates on purpose — process metrics alone can't rescue a broken run.

DimensionScoreBar
Time efficiency1.000

Composite formula

How 0.000 was calculated

The composite score is a weighted sum of the dimensions above. Weights come from evals/escape-the-dungeon/gad.json. Contribution = score × weight; dimensions sorted by contribution so you can see what actually moved the needle.

DimensionWeightScoreContribution
time_efficiency0.051.0000.0500(100%)
requirement_coverage0.150.0000.0000(0%)
planning_quality0.150.0000.0000(0%)
per_task_discipline0.150.0000.0000(0%)
skill_accuracy0.100.0000.0000(0%)
human_review0.300.0000.0000(0%)
Weighted sum0.900.0500

Note: The weighted sum above (0.0500) doesn't exactly match the stored composite (0.0000). The difference is usually the v3 low-score cap (composite < 0.20 → 0.40, composite < 0.10 → 0.25) or a run with an older scoring pass.

Skill accuracy breakdown

Did the agent invoke the right skills at the right moments?

Skill accuracy data isn't relevant for this run (no expected trigger set).

Process metrics

How the agent actually worked

Primary runtime
older runs may not carry runtime attribution yet
Agent lanes
0
0 root · 0 subagent · source missing
Observed depth
0 traced event(s) with agent lineage
Wall clock
0m
0 phases · 0 tasks
Started
Apr 6, 9:39 PM
Run start captured in TRACE timing metadata
Ended
Apr 6, 9:39 PM
Missing end time usually means the run was scaffolded but never finalized
Planning docs
0
decisions captured · 0 phases planned
Client debug · NEXT_PUBLIC_CLIENT_DEBUG=1
0 lines

No events yet. Window errors, unhandled rejections, and React render errors appear here. Set NEXT_PUBLIC_CLIENT_DEBUG_CONSOLE=1 to mirror console.error / console.warn.