Preserve structured diagnostics, source attribution, phase outcomes and revision context through compiler, Studio, LSP, MCP and JavaFX. Add project service discovery and resilient VS Code reconnection. Correct all eight reproduced PBS production failures in expression context, sibling executable bindings and nominal owner identity. Consolidate specs, lessons, immutable baseline evidence and the maintained source-to-guest qualification runner. Validation: required Gradle gate recorded 724 tests, with 711 passed and 13 skipped. Full corpus passed 168 compilation observations and 108 guest runs (104 successes and four deliberate faults); supplemental controls passed 42 compilations and 16 guest runs. TypeScript compilation, two Node discovery tests and discussion validation passed.
General Compiler Specifications
Owner: compiler/general. Canonical source: docs/specs/compiler.
These specifications define shared frontend/backend acceptance, compilation, linking, typed handoff and emission. They apply across supported languages. Language contracts define PBS rules and refer to this layer for shared policy rather than duplicating it.
Authority and reading order
The runtime owns PBX binary layout, Core ISA, admission and VM execution. Read the mirror and provenance policy for that boundary. Chapters 24–25 own the detailed compiler catalog/typed-Registry consumer contracts; earlier pipeline, verification and matrix chapters reference them for these topics. Equal storage widths never replace logical identity or transfer runtime authority.
Start with pipeline entry points (23), then name/linking (14), typed handoff (25), lowering/optimization (20–21), runtime/catalog integration (16, 18, 24), and conformance/verification/compatibility (13, 17, 19, 22). Existing chapter numbers are stable and do not imply language-version numbers.
Chapter index
- 13. Conformance Test Specification
- 14. Name Resolution and Module Linking Specification
- 15. Bytecode and PBX Mapping Specification
- 16. Runtime Execution and Initialization Specification
- 17. Compatibility and Evolution Policy
- 18. Standard Library Surface Specification
- 19. Verification and Safety Checks Specification
- 20. IRBackend to IRVM Lowering Specification
- 21. IRVM Optimization Pipeline Specification
- 22. Backend Spec-to-Test Conformance Matrix
- 23. Compiler Pipeline Entry Points Specification
- 24. Runtime Catalog Support Specification
- 25. Typed Registry and PBX v0 Specification
Editorial and workflow rules
Write specs in English with title, status, scope, authority, normative rules,
non-goals and conformance/exit criteria. Keep one owner per detailed contract;
summaries link to it. Only settled decisions may change normative behavior.
Agendas, decisions and plans live in discussion/, and completed teaching
material lives in discussion/lessons/; they are not parallel spec sources.
See the specification guide for other domains.