Build pipeline

Platform spec area

Build pipeline

Back to Compiler ◎ Open in platform map

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs

No architecture decision records under adr/ for this feature yet. Standard features must publish at least one ADR or keep a ## Decisions summary on the hub.

Articles

• No directly attached article pages for this node. Nested descendants exist deeper in this subtree.

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Architecture

Reference build pipeline

Implementation-facing stages from project resolution through lowering to JIT or AOT backends, aligned with the Beskid compiler workspace layout.

Completeness

OKarea · 3 SpecSection(s) · 0 H2 heading(s)

Section id	Required	Found
scope	yes	yes
features	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Domain
  Compiler

  Parent domain hub

• Domain
  Language meta

  User-visible semantics live here; this area covers implementation phases

Scope

This area specifies the reference compiler workspace (compiler/ in the Beskid repository): which stages exist, their ordering, observable CLI behaviour, and where JIT and AOT diverge. It does not redefine language semantics; those remain in Language meta.

Execution host details (runtime ABI chapters, long-form IR narrative) continue to live under Execution where noted; this area links to them from backend features.

Pipeline overview

The diagram below mirrors the primary data flow: project resolution (optional) supplies source_path and source text; lowering (beskid_codegen::lower_source) performs parse, semantic rules (when enabled), HIR, resolution, typing, and Cranelift lowering into a CodegenArtifact; JIT (beskid_engine::run_entrypoint) or AOT (beskid_aot::build) consumes that artifact.

flowchart TB
  resolve[Project resolution]
  assemble[program.assemble]
  parse[Parse and syntax diagnostics]
  mods[Mod host optional]
  semantic[Semantic rules and composition.resolve]
  hir[HIR resolve and type-check]
  lower[lower_program to CodegenArtifact]
  jit[JIT run_entrypoint]
  aot[AOT build and link]
  resolve --> assemble --> parse --> mods --> semantic --> hir --> lower
  lower --> jit
  lower --> aot

Subtree summary

• 58 page(s) under this subtree
• 6 direct child path segment(s)

Child entries

• Backends (JIT and AOT)
• Build and run orchestration
• Dependency workspace and lockfile
• Diagnostics parity (CLI and LSP)
• Program assembly
• Stage ordering and lowering

Feature index

Use the tiles below for normative feature contracts (each page declares status and owner metadata).

Features

• Backends (JIT and AOT)Contracts for JIT execution and AOT object/link flows that consume a shared lowering artifact.
• Build and run orchestrationFeature hub for the build and run orchestration in the reference compiler.
• Dependency workspace and lockfileCanonical compiler contract for compile plans, workspace materialization, lockfile policy, and dependency source trees.
• Diagnostics parity (CLI and LSP)Contracts for diagnostic provenance and parity across CLI parse, lowering, and LSP analysis paths.
• Program assemblyMulti-module program composition from CompilePlan and materialized source roots, shared by analyze, lowering, LSP, and backend-agnostic front-end paths.
• Stage ordering and loweringCanonical ordering from resolved source through lowering into a backend-ready CodegenArtifact.