Escape the Dungeon · Bare
escape-the-dungeon-bare/v6
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-bare/gad.json. Human review dominates on purpose — process metrics alone can't rescue a broken run.
| Dimension | Score | Bar |
|---|
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-bare/gad.json. Contribution = score × weight; dimensions sorted by contribution so you can see what actually moved the needle.
| Dimension | Weight | Score | Contribution |
|---|---|---|---|
| requirement_coverage | 0.20 | 0.000 | 0.0000(0%) |
| implementation_quality | 0.20 | 0.000 | 0.0000(0%) |
| workflow_emergence | 0.15 | 0.000 | 0.0000(0%) |
| iteration_evidence | 0.10 | 0.000 | 0.0000(0%) |
| time_efficiency | 0.05 | 0.000 | 0.0000(0%) |
| human_review | 0.30 | 0.000 | 0.0000(0%) |
| Weighted sum | 1.00 | 0.0000 |
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.
Skills written(2)
create-skill.md4.9 KBfind-sprites.md5.9 KB
Planning notes(1)
progress.md2.5 KB
Process metrics