Package-level declarations

On-disk cache of lazily-extracted ksl.simulation.ModelDescriptor JSON for bundles that were not pre-enriched by kslpkg enrich. Entries are keyed by the SHA-256 of the bundle's source JAR so replacing the JAR automatically invalidates the cache.

The well-known in-JAR paths that make up a KSL bundle. This object is the authoritative spec for the bundle JAR layout; the kslpkg CLI tool, the runtime loader, and any tests must reference these constants rather than hard-coding paths in multiple places.

Entry point for discovering and loading KSLModelBundle instances.

Adapter that exposes one or more LoadedBundles through the existing ksl.simulation.ModelProviderIfc contract used by KSLAppSession. This lets callers that today take a ModelProviderIfc (such as the four reference Swing apps) consume bundle-supplied models without any change to the interaction-layer API.

Identifies the configuration shape of a KSLConfigRecipe shipped inside a bundle.

Identifies a KSL application workflow that a bundled model can claim to support.

One model packaged inside a KSLModelBundle.

An author-curated configuration shipped inside a bundle JAR for one of the bundle's models. A recipe is a pre-filled set of inputs (a RunConfiguration, a scenario batch, a designed-experiment spec, or an optimization run spec) that an end user can load in a GUI, inspect, tweak, and run.

The service-provider interface for a self-describing KSL model bundle.

Runtime-managed wrapper around one discovered KSLModelBundle. Holds the bundle's classloader and (when applicable) its source JAR and content hash, and provides on-demand access to each model's ksl.simulation.ModelDescriptor with a three-tier resolution strategy.

The source a loaded bundle came from: its JAR file name, or "classpath" for a classpath-discovered bundle. The human-facing disambiguator shown in pickers, the Loaded Bundles dialog, and newest-wins dedup disclosure when several sources carry the same bundleId.