SplitScript reference / Migration / Loaded module discovery

Loaded module discovery

Migration from ASL

Source pattern

Look for the ASL concept Loaded module discovery in the source. The semantic difference below is more important than a token-for-token rewrite.

Canonical SplitScript

Use the canonical language and API symbols linked below.

Semantic difference

Replace the enumerable ASL module bag with the narrow typed probe that matches the source intent: main executable discovery, a known optional module, a required module, or typed build identity. Preserve genuine unknown-name enumeration as an explicit host-runtime gap.

Supported hosts

This uses the standard SplitScript runtime contract. Any provider-specific requirements are documented by the linked canonical API.