The infrastructure is the project. The game is the workload.
GameBoyGhost teaches a computer to play Link's Awakening.
One short stretch at a time. The game is a practice target — a test system that behaves the same way every time and can never be broken. The real work is everything around it: runs that repeat exactly, results that are checked before they count, and failures that get written up instead of hidden.
The clip that says it all
Same run, same room, same starting moment. Left: the old version — Link keeps his shield up, a bat knocks him back, the floor gives way, and he falls. Right: after the fix — shield down, he walks across and finishes the segment. Both clips are verified frame by frame against the recorded run. That loop — fail, diagnose, fix, prove — is the whole project.
The honest status
Not a trophy case.
| Segment | Result | The honest part |
|---|---|---|
| S0 — house start → sword | sealed, 96/100 | our pilot. The bar was 90%. |
| S1 | sealed, 294/294 | bar raised to 97%, and held. |
| S2 | sealed, 294/294 | 294 of 300 cases reached the start; the 6 that didn't are counted, not dropped. |
| S3 | oracle & student certified 250/250 | the student is a faithful copy of the oracle — not a new capability, stated up front. |
| S4–S18 | not started | this is where the real question — can a student exceed its teacher — begins. |
The arc is the point: we sealed the first segment at 90%, realized that wasn't strict enough, and raised our own bar to 97% before sealing the next two. Anyone can pick a number; the story is that the standard got stricter as the work went on.