External view:
RUN-ALL.ps1
↓
SemanticQt.module.zip
Internal view:
Qt C/C++ + PySide source/evidence
↓
license + provenance gate
↓
per-file SemanticProgram units
↓
GlobalSemanticIndex / cross-unit resolution
↓
one SemanticQt module
The module is one installable Store object, but it should not be represented as one giant Program object. A module manifest can reference thousands of independently cached Semantic units.
The current Code-Transpiler API can export individual C/C++/Python files to SemanticJSON.
A real full-Qt closure will expose unsupported C++/preprocessor/meta-object semantics.
Every failure is evidence for a universal compiler gap. Fix the UAST/primitive/lowering
once, rerun the exact same RUN-ALL.ps1, and drive the failure count to zero.