Architecture Direction

cREXX uses a toolchain architecture because explicit stages make the system easier to inspect, test, package, and evolve.

At the vision level, the important ideas are:

• source code should have a clear route through compiler, assembler, linker, and runtime stages
• bytecode should remain inspectable enough to support diagnostics and tooling
• libraries and tools should become more self-describing over time
• host integration should be deliberate rather than a pile of special cases
• implementation layers should be separable enough that one area can improve without rewriting the whole project

This wiki does not describe current file formats, opcodes, AST structures, or API details. Those are implementation facts and belong in the repository docs.

Current Technical References

• Architecture notes
• Assembler notes
• Linker notes
• Interpreter notes