The plan for Misty is to bootstrap tools in JavaScript, leading to an x64 simple process with integers only. This leads to a single machine, multiple process implementation with tools in Misty, and ultimately a distributed implementation on the Procession Protocol.
These are steps that have been identified. Certainly, some important steps are missing.
The language has been fully specified. Some clarifications are needed.
Network Object Transfer Arrangement.
Word Object Transfer Arrangement.
This list of remaining work.
Take a source text and break it into an array of token objects.
Take an array of token objects and weave it into a parse tree.
Take a parse tree and produce mistymachine code.
Take mistymachine code and generate x64 code.
Runtime for x64 Misty programs.
Reclamation of memory.
Take a source text and break it into an array of token objects.
Take an array of token objects and weave it into a parse tree.
Optimize a parse tree by constant folding.
Take a parse tree and produce mistymachine code.
Optimize mistymachine code by shortening paths and removing unreachables.
Take mistymachine code and generate x64, Arm64, and RISC-V64 code.
Runtime for Arm64 and RISC-V64 Misty programs.
Multicore and process memory management.
Local queuing and delivery of messages.
Storage and maintenance of source code, executables, policies, and keys.
Communication with the host operating system.
Remote queuing and delivery of messages.
Message oriented debugging of distributed programs.
The Misty Operating System.