Docs / Concepts
Concepts
What moxzi is made of, and the ideas the rest of the documentation assumes.
| Page | Question it answers |
|---|---|
| Architecture | What are the moving parts, and how does a program get from .mo to running actor? |
| Byte-identical output | What does "byte-identical to moc" mean, what does it buy you, and how is it verified? |
| Self-hosting and fixed points | Why does moxzi compile itself, what is a C2==C3 fixed point, and why is it the real correctness gate? |
| The compile pipeline | Which stage owns which part of the work, and which stage produced my error? |
| Resumability | Why is every stage checkpointed, and why is on-chain compile time message count rather than instructions? |
| Trust model | What does each of the four front ends require you to trust? |
If you only read one page, read Architecture.