A couple thoughts on the process here…

First off, Opus 5.5 built working weights and code with only two prompts:

1. Read this article and any relevant source code: https://divagr.com/blog/qwenputer. Then explore if you could emulate the chip and ram in a Nintendo Entertainment System (as people do today with FPGAs in MISTRs) using this technique. If so, what size model would you have to build and if you could use smaller faster ones, could you get it to be at the standard clockspeed.

It returned charts well illustrating any model would be _slow_. But it's still fun, so the second prompt was:

2. I think we should build it! Just for fun. It's okay if it's not fast. We want to be able to have the weights, and a cli to run them that we can point at a ROM.

Now while this was an _epic_ run by Opus (5.5 is a crazy capable model), this is a surprisingly well-structured challenge.

There is a long-lived and incredible community of classic gaming emulation work online for it to reference. And that community has created…conformance tests! Opus found them and built against one, that has >3k golden instructions: https://github.com/christopherpow/nes-test-roms/blob/master/...

Also, there is the original Qwenputer repo that Opus used to drive the weight writing. That was essential.

But this is a great example of what these models can do with proper reference materials, great specs, conformance tests, and clear direction.