I'll echo everyone's sentiment that this is massively ambitious and impressive, not just to make a full simulated CPU and assembler for a 48 hour game jam, but to get as far as implementing a sequence of tutorial levels and documentation pages for it. Very cool.
However, I'll also echo the sentiment that even with assembly programming experience, I was unable to make any headway in this game. Basic things like what base the arguments should be provided in, which direction bits and bytes are counted from, etc. were not clear. I also had the bug where the computer's power light doesn't show up, and there's no reticle in mouse capture mode so I couldn't even tell if I had turned the computer on or not.
I know you wanted the game to be about discovering how to use the computer, but for as complex as a CPU architecture can be, it's hard to expect people to try to comprehend the documentation and work it out by trial and error (not to criticize your documentation, but anything produced in a 48 hour sleep deprived state is going to be a little all over the place).
For example, in the blinkenlights tutorial the hint merely says "you pretty much NEED to start off with a DATAC or SET operation" but it's unclear to me why that is. Shouldn't this command
SETDATA 0 0 0100000000000000000000
accomplish the correct thing? From my reading it should shift the argument into the correct place to be read by the monitor, but it doesn't work and I don't know why.
I think it's awesome you made this, and I think there's a lot of places you could go with it. I'm a big fan of Zachtronics' assembly puzzle games, and I've even shown the game Human Resource Machine to non-programmers and had them enjoy it a lot, so I think this is an idea worth pursuing as long as it could be made less opaque.