Bare
v2
requirements unknown
2026-04-08
Gate passed

Escape the Dungeon · Bare

escape-the-dungeon-bare/v2

Composite score

0.601

Human review

0.50

Human review note

Most playable game of all evals. Full game loop works: title → new game → rooms → combat → dialogue → navigation. UX and flow are good. UI is very ASCII/plain — needs spacing, icons, better styling. Color coding is good. No spell crafting despite rune system in requirements. Rest room doesn't offer forge. Score 0.50: playable vertical slice but visually rough.

Reviewed by human · 2026-04-08

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.

DimensionScoreBar
Human review0.500
Requirement coverage0.833
Workflow emergence1.000
Implementation quality0.700
Iteration evidence0.000
Time efficiency0.956

Composite formula

How 0.601 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.

DimensionWeightScoreContribution
requirement_coverage0.200.8330.1666(25%)
workflow_emergence0.151.0000.1500(23%)
human_review0.300.5000.1500(23%)
implementation_quality0.200.7000.1400(21%)
time_efficiency0.050.9560.0478(7%)
iteration_evidence0.100.0000.0000(0%)
Weighted sum1.000.6544

Note: The weighted sum above (0.6544) doesn't exactly match the stored composite (0.6010). 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.

Workflow docs(1)

  • WORKFLOW.md2.6 KB

Gate report

Requirement coverage

Total criteria
12
Fully met
9
Partially met
2
Not met
1

Reviewer notes on gates

Game renders, title works, New Game works, room navigation works, combat works, dialogue works, menus work. Very playable vertical slice. Missing: rune forge, icons, visual polish.

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
21m
7 phases · 0 tasks
Started
Run start captured in TRACE timing metadata
Ended
Missing end time usually means the run was scaffolded but never finalized
Tool uses
110
87,661 tokens
Commits
6
0 with task id · 6 batch
Planning docs
0
decisions captured · 7 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.