Escape the Dungeon · Bare
escape-the-dungeon-bare/v4
Composite score
0.000
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=45. Shared rate bucket with parallel GAD + Emergent runs.
Full round 4 partial-results finding →Human review note
RATE LIMITED before completion. 6 source files written, vite build succeeds manually (54 KB bundle). worklog.md shows 10-step plan covering all 4 gates. Implementation depth: step 1 of 10 complete. DO NOT include in cross-round comparisons against completed runs.
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 |
|---|---|---|
| Requirement coverage | 0.125 | |
| Planning quality | 0.100 | |
| 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-bare/gad.json. Contribution = score × weight; dimensions sorted by contribution so you can see what actually moved the needle.
| Dimension | Weight | Score | Contribution |
|---|---|---|---|
| time_efficiency | 0.05 | 0.533 | 0.0267(52%) |
| requirement_coverage | 0.20 | 0.125 | 0.0250(48%) |
| 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%) |
| human_review | 0.30 | 0.000 | 0.0000(0%) |
| Weighted sum | 1.00 | 0.0517 |
Note: The weighted sum above (0.0517) 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.
Skills written(2)
create-skill.md4.9 KBfind-sprites.md5.9 KB
Planning notes(1)
worklog.md745 B
Gate report
Requirement coverage
Reviewer notes on gates
G1 partial (scaffold only). G2/G3/G4 NOT MET. RATE LIMITED before any gate could be verified. Vite build succeeds manually (54 KB, 18 modules) but game loop is not wired end-to-end.
Process metrics