mod host bridge - FAQ and troubleshooting

Platform spec article

mod host bridge - FAQ and troubleshooting

Back to Mod host bridge ◎ 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 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

• Feature
  mod host bridge

  Parent feature hub

This article collects FAQ entries for mod host bridge.

Why separate language-meta and compiler pages?

Language-meta defines Beskid-side mod contracts; this compiler area defines how the Rust host executes them safely and incrementally.

Can meta call arbitrary FFI?

No — unless explicitly granted by platform policy and declared in compilation capabilities. Default contracts deny ambient FFI.

Authoritative split: FFI and extern (language Extern contracts), Interop.Contracts (abstract primitives), C ABI profile / Rust ABI profile (concrete profiles). Meta does not implicitly satisfy any of these without host-granted capabilities.

Where do Roslyn/KSP parallels apply?

Only as rationale for incremental caches and typed models; Beskid contracts are authoritative here, not foreign tool behavior.