Program assembly - Contracts and edge cases

Platform spec article

Program assembly - Contracts and edge cases

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

ADRs (3)

1. 0001-feature-hub-authority Feature hub authority Accepted

   This feature hub owns normative MUST/SHOULD contract text for Program assembly.

   Context

   Sibling articles under this feature previously restated requirements in inconsistent forms.

   Decision

   This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.

   Consequences

   Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.

   Verification anchors

   • site/website/src/content/docs/platform-spec/compiler/build-pipeline/program-assembly/index.mdx
   • article bundle under the same feature directory.

   Open full ADR page

2. 0002-spec-over-implementation-notes Specification over implementation notes Accepted

   Platform-spec text supersedes informal crate comments for Program assembly.

   Context

   Implementation crates accumulated informal notes that diverged from published contracts.

   Decision

   Normative platform-spec prose and ADRs under this feature supersede informal comments in implementation crates until explicitly migrated into spec text.

   Consequences

   Engineers file spec/ADR updates when behavior changes; crate comments are non-authoritative for conformance arguments.

   Verification anchors

   • compiler/crates/beskid_analysis/

   Open full ADR page

3. 0003-primary-contract-choice Primary contract for Program assembly Accepted

   This feature hub defines how the reference compiler turns a resolved **`CompilePlan`** plus **effective (materialized-fi

   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/

   Open full ADR page

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

• Materialized-first — When PreparedProjectWorkspace exists, assembly roots must use materialized_source_root and dependency materialized_source_root entries, not pre-copy project trees.
• Lockfile fallback (LSP) — When materialization did not run, Project.lock materialized_root paths may be used when directories exist.
• max_units — Workspace scan must stop at the cap and report deterministically sorted paths.
• No diagnostic filtering — Cross-module symbols must be visible to resolution; hosts must not drop E1105/E1201/E1301 solely because a path exists on disk.
• use alias resolution — Import aliases must expand to prefetched module paths before value/type lookup; binding a use item as a callable namespace is forbidden (contract-as-namespace remains the only in-scope dotted-path fallback).
• Mod rounds — After generator output changes imports, the host may re-run assembly within maxGeneratorRounds.