Escape the Dungeon · GAD
escape-the-dungeon/v9
Composite score
0.000
Human review
0.05
Rate-limited run · excluded from cross-round comparisons
This run hit an account-level rate limit before completing. The data captured here reflects partial progress only — it is not included in the freedom-hypothesis scatter, the Results card grid, or any aggregate comparison on the site (decision gad-63). Preserved here as a data point for planning-differential analysis and honest documentation.
Details: Hit account-level rate limit at tool_uses=81 (highest of three conditions). Planned 7 phases + 23 tasks before rate-limit. Completed phase 01 fully + task 02-01.
Full round 4 partial-results finding →Human review note
Rate-limited GAD v9. Start screen loads but nothing beyond it — regressed vs earlier GAD builds. Preserved as data point but excluded from cross-round quality per gad-63. User playtest 2026-04-09.
Reviewed by human · 2026-04-09
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.
| Dimension | Score | Bar |
|---|---|---|
| Human review | 0.050 | |
| Requirement coverage | 0.208 | |
| Planning quality | 0.850 | |
| Per-task discipline | 0.000 | |
| Time efficiency | 0.533 |
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.
| Dimension | Weight | Score | Contribution |
|---|---|---|---|
| planning_quality | 0.15 | 0.850 | 0.1275(64%) |
| requirement_coverage | 0.15 | 0.208 | 0.0312(16%) |
| time_efficiency | 0.05 | 0.533 | 0.0267(13%) |
| human_review | 0.30 | 0.050 | 0.0150(7%) |
| per_task_discipline | 0.15 | 0.000 | 0.0000(0%) |
| skill_accuracy | 0.10 | 0.000 | 0.0000(0%) |
| Weighted sum | 0.90 | 0.2004 |
Note: The weighted sum above (0.2004) 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).
What the agent built for itself
Emergent workflow artifacts
Bare and emergent runs don't have a framework giving them structure — they author their own methodology on the fly. These are the files the agent wrote into its own game/.planning/during this run. When a file appears here that isn't in the inherited bootstrap set, the agent invented it.
Planning notes(2)
VERIFICATION.md154 Bsource-STAT-AND-BEHAVIOUR-TAXONOMY.md4.5 KB
Gate report
Requirement coverage
Reviewer notes on gates
G1 PARTIAL — title screen scene renders, scene transition to New Game NOT IMPLEMENTED (task 02-02 was next). No room navigation. G2 NOT MET. G3 PARTIAL — title screen styled. G4 NOT MET. RATE LIMITED at task 02-02. Phase 01 scaffold passed its own verification with working build.
Process metrics