eis/doc/Binary.md

Binary program format

The current binary format is super simple, because all CPU state (registers) is part of the memory. That means you can think of it like this: There is a header (containing the registers), and a memory block. My suggestion is to just put the program instructions right after the header, and put stack and heap wherever you want (by setting the registers). Don't forget to point ip to the start of your program!

In the future, I might consider some sort of mapping format, but honestly, why make it complicated? (For ASLR, I will need to define a range or something...)