Files
prometeu-studio/docs/specs/compiler
bquarkz 71fb80efc3
Test / Tests and coverage occurred while executing withChecks step.
Intrepid/Prometeu/Studio/pipeline/head There was a failure building this commit
feat(studio): ship JavaFX 2 Play and delegate integration tooling
Launch the JavaFX 2 project shell on Java 25 with an interactive viewport,
managed Play lifecycle and project mutation guards. Preserve headless/MCP and
save compatibility, and qualify exact runtime executable bundles.
Separate unit JaCoCo gates from opt-in integration suites and use the internal
Pong fixture for the headless visual pilot.
Move maintenance and native conformance tools into tooling; retain the VS Code
extension and update current navigation links.

Validation: tooling make verify passed, including 1064 Studio unit tests,
JaCoCo thresholds and 22 headless integration tests.
2026-11-19 17:32:03 +00:00
..

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

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. Engineering discussions, decisions and plans live in the enclosing workspace's AI Engineering project. Published teaching material remains in discussion/lessons/; neither is a parallel spec source.

See the specification guide for other domains.