Specification over implementation notes

Platform spec ADR

Specification over implementation notes

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

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/