Mod host bridge

Platform spec feature

Mod host bridge

Back to Compiler Mods ◎ Open 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 Mod host bridge.

   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/compiler-mods/mod-host-bridge/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 Mod host bridge.

   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/
   • compiler/crates/beskid_codegen/
   • compiler/crates/beskid_analysis/src/services.rs

   Open full ADR page

3. 0003-mod-aot-only-registration Mod host AOT-only with descriptor registration Accepted

   Mods previously risked manifest attach lists for discovery.

   Context

   Mod packages must export public Beskid types implementing SDK contracts; host loads AOT artifacts and mod.descriptor.json registrations—not manifest attach metadata.

   Decision

   Contract discovery uses (contractId, typeId, entrySymbol) tuples; failures emit E1821–E1870 before mod.collect.

   Consequences

   JIT mod execution is not normative; rebuild uses beskid mod rebuild.

   Verification anchors

   • compiler/crates/beskid_analysis/
   • mod artifact store paths in analysis services.

   Open full ADR page

Articles

• Mod host bridge - AOT artifact contract On-disk mod artifact layout, cache keys, export descriptor schema, and load-failure diagnostics. article Standard Reviewed Wed May 20
• mod host bridge - Contracts and edge cases Reference compiler-owned execution, capability policy, and communication with compile-time Beskid modules. article Standard Reviewed Thu Apr 30
• mod host bridge - Design model Rust-side mod host execution, AOT artifact lifecycle, capability policy, and typed merge. article Standard Reviewed Wed May 20
• mod host bridge - Examples Reference compiler-owned execution, capability policy, and communication with compile-time Beskid modules. article Standard Reviewed Thu Apr 30
• mod host bridge - FAQ and troubleshooting Reference compiler-owned execution, capability policy, and communication with compile-time Beskid modules. article Standard Reviewed Thu Apr 30
• mod host bridge - Flow and algorithm Reference compiler-owned execution, capability policy, and communication with compile-time Beskid modules. article Standard Reviewed Thu Apr 30
• mod host bridge - Verification and traceability Reference compiler-owned execution, capability policy, and communication with compile-time Beskid modules. article Standard Reviewed Thu Apr 30

History

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

Open full history on GitHub

No commits recorded for this path.

Architecture

Compile-time mod execution flow

Reference ordering from parse through mod collection, generation, semantic analysis, rewrite, and lowering.

Completeness

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

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

Related spec docs

• Area
  Compiler Mods

  Parent area

• Domain
  Compiler

  Parent domain hub

• Area
  Metaprogramming (language meta)

  Beskid-side compiler mod SDK contracts

• Feature
  Compiler Mod SDK

  Beskid contracts consumed by this host

• Feature
  Project manifest contract

  Mod project type and package wiring

• Feature
  Incremental scheduling and determinism

  Invalidation contract for host-recorded work

This feature hub defines Rust-side mod-host execution: Mod project registration, contract discovery, AOT artifact lifecycle, compilation-event orchestration, and capability policy.

Language alignment

Implements language-meta compiler-mod contracts (Collector, Generator, Analyzer, Rewriter, AttributeGenerator) for manifest-driven Mod orchestration.

Implementation anchors

• compiler/crates/beskid_analysis/src/mod_host/ — mod discovery, registration validation, contract dispatch through ContractInvoker, typed merge / reparse, analyze / rewrite orchestration.
• compiler/crates/beskid_analysis/src/mod_host/invoker.rs — ContractInvoker trait with StubContractInvoker / ScriptedContractInvoker for host bring-up and tests.
• compiler/crates/beskid_analysis/src/mod_host/validate.rs — pre-mod.collect cross-artifact validation that short-circuits scheduling on E1828, E1829, E1851, E1852, E1853, E1854, E1855.
• compiler/crates/beskid_codegen/src/services.rs — lowering boundaries after typed mod contributions.
• compiler/crates/beskid_engine/tests/mod_host.rs — engine integration test driving the full pipeline through Engine::compile_artifact.

Decisions

No open decisions. Closed choices are normative ADRs under adr/ (D-COMP-MODS-0010 … D-COMP-MODS-0012); use the reader ADRs tab for expandable detail.

• Design model
• AOT artifact contract
• Flow and algorithm
• Contracts and edge cases
• Examples
• Verification and traceability
• FAQ and troubleshooting