How metedinler/uxbasic works
The README describes a Python runner that executes 45 modular test sources through three output lanes: JSON/log, x64, and web. The JSON/log lane covers tokens, preprocessing, AST, semantics, MIR, and interpreter output; the other lanes produce native and browser artifacts. The runner and its referenced test and report paths do not appear in the supplied tree, so those components have no source path. Relationships shown below reflect README documentation only; no runner implementation was inspected.
Components 13
Pipeline orchestration
- 45 test sources
- Pipeline runner
- uxb executable
- Run reports
JSON/log lane
- Front end stages
- Interpreter run
- JSON/log artifacts
x64 lane
- x64 generation
- x64 build attempt
- x64 artifacts
Web lane
- Web generation
- Browser artifacts
Other components
- Engineer
Connections 12
- Engineer → Pipeline runner: runs
- 45 test sources → Pipeline runner: provides tests
- Pipeline runner → uxb executable: invokes
- Pipeline runner → Front end stages: runs lane
- Front end stages → Interpreter run: feeds
- Interpreter run → JSON/log artifacts: produces
- Pipeline runner → x64 generation: runs lane
- x64 generation → x64 build attempt: generates for
- x64 build attempt → x64 artifacts: produces
- Pipeline runner → Web generation: runs lane
- Web generation → Browser artifacts: produces
- Pipeline runner → Run reports: writes reports