A line of inquiry
Below the abstraction.
Emulation makes the details matter: state, timing, instructions, and the gap between a model and a machine.
Why emulation?
An emulator is a model of behavior. That makes it a rich place to ask precise questions: what is observable, which details matter, and how can an implementation be checked against evidence?
Questions for the notebook
- How can instruction behavior be expressed and tested clearly?
- What does timing change when a functional model seems correct?
- How do small test programs expose a hidden assumption?
Evidence before conclusions
No emulator results or compatibility claims are published here yet. When there is an experiment to share, it should include its scope, sources, test conditions, and limitations.
Explore the field notes ↗