Primary contract for Program assembly

Platform spec ADR

Primary contract for Program assembly

Back to Program assembly ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• Program assembly - Contracts and edge cases Materialized-first roots, discovery caps, and parity across CLI and LSP. article Standard Reviewed Wed May 20
• Program assembly - Design model EffectiveCompilationRoots, ProgramAssembly, ModuleIndex, and hybrid discovery modes. article Standard Reviewed Wed May 20
• Program assembly - Flow and algorithm Ordered assembly after workspace materialize and before multi-unit parse and HIR resolution. article Standard Reviewed Wed May 20
• Program assembly - Verification and traceability Test and source anchors for ProgramAssembly and effective roots. article Standard Reviewed Wed May 20

History

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

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 0 SpecSection(s) · 1 H2 heading(s)

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

Related spec docs

• Feature
  Program assembly

  Parent feature hub

Context

This feature hub defines how the reference compiler turns a resolved CompilePlan plus effective (materialized-first) source roots into a ProgramAssembly: discovered .bd units, a shared ModuleIndex for cross-module resolution, and a single front-end spine consumed by CLI, LSP, analyze, and codegen. JIT and AOT backends consume CodegenArtifact only and do not re-run assembly.

Decision

The reference compiler must implement Program assembly as documented in this feature hub and its article bundle.

Consequences

Changes require hub/ADR updates and verification anchor extensions.

Verification anchors

• compiler/crates/beskid_analysis/