Pipeline phases

Mods insert between parse and lowering—after you have syntax, before you pretend Cranelift will save you.

Author-facing order

From Compiler Mod SDK — pipeline interaction:

flowchart TB
  collect[mod.collect — Collector scopes targets]
  generate[mod.generate — merge + reparse loops]
  analyze[mod.analyze — diagnostics on merged program]
  rewrite[mod.rewrite — apply fixes]
  semantic[Semantic rules continue]
  lower[codegen.lower]
  collect --> generate --> analyze --> rewrite --> semantic --> lower

Host modules (beskid_analysis::mod_host)

Phase	Host concern
discovery / load	Find AOT artifacts, build schedule
collect	Narrow work per mod instance
generate / merge / reparse	Typed AST contributions
analyze	Run analyzers on merged snapshot
rewrite	Apply rewriter results

Map: Mod host bridge flow, Crate-to-spec anchors.

beskid_pipeline

Rust host composition shares phase IDs across CLI, analysis, and codegen services—avoid ad-hoc logging strings in random crates (Pipeline composition, Stage ordering).

IoC note

Dependency injection inside the Rust host is compile-time and read-only to mods/SDK—do not expect to register services from Beskid mod code.

Where to go next

• Ship a mod: keep Compiler Mod SDK open beside your editor.
• Debug pipeline: 14. From source to something that runs
• Change law: 12. The normative bible