Files
prometeu-studio/docs/specs/compiler
bquarkz 1471b427f1
Test / Tests and coverage occurred while executing withChecks step.
Intrepid/Prometeu/Studio/pipeline/pr-master There was a failure building this commit
feat(studio): deliver asset authoring and automation workflows
Add shared human/task asset batches with reviewed atomic publication, explicit
reference rebinds, ownership inspection and qualified glyph/scene budgets.
Expose the same authoring and capacity results through Assets and MCP.

Deliver isolated guest test targets, retained visual evidence and immutable
runtime lifecycle/control observations. Preserve provider qualification and
installed authoring examples alongside the completed discussion lessons.

Close AGD-106 coordination and the delivered discussion workflows through
housekeeping, updating lesson references and preserving qualification limits.
Sound remains outside the asset delivery wave.

Validation: 579 module tests and 31 additional desktop, process and installed
checks passed; native glyph/scene 16/17 boundaries qualified. Discussion
validation passed after housekeeping.
2026-11-11 01:21:25 +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. 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.