Skip to content

Latest commit

 

History

History
42 lines (35 loc) · 2.62 KB

README.md

File metadata and controls

42 lines (35 loc) · 2.62 KB

Adapter contracts

AISim exposes separate boundaries for execution, configuration, output and native Replay composition. An adapter's support at one boundary does not establish support at the others. This directory is an ABI reference; usage of the existing Dynamo integration is documented with Replay.

Boundary Owns Discovery / version
Runner Execute one resolved ReplaySpec and report capabilities/metrics aisim.runner_factories; Python replay-spec API 1
Simulation configuration Compile prediction, search plan and candidate hooks aisim.config_adapters; config API 3
SDK sweep provider SDK search-space preparation and materialization aisim.sweep_config_providers; provider API 1
Recommendation output Optional live callbacks and additional final artifacts aisim.output_adapters; output API 1
Native composition Placement and optional scaling in Rust Replayer Rust traits in aisim_core::replay; crate-version compatibility

Here ABI means the versioned cross-package data/interface contract. These Python protocols and Rust traits are not a stable C binary ABI. Check the installed package/crate pair rather than inferring compatibility from a shared method name. Explicit version checks fail instead of silently translating an unsupported contract.

AISim owns traffic, engine schemas, optimization, process supervision and canonical output. Config adapters return data and hooks; a runner combines them and starts execution once. The native composition depends on AISim's neutral types, while AISim core does not import Dynamo's Router/Planner. Output adapters do not influence simulation or ranking.

Discovery imports selected plugins only. Configuration/output names must be unique and match their declared names. Built-in runner names take precedence; for an optional stack, duplicate installed entry points fail. Zero-argument constructors or preconstructed values are accepted where the resolver permits. Provider objects stay in the coordinator process; replay workers receive a serializable factory and data-only ReplaySpec, not a pickled provider.

The legacy recipe configuration importer converts external recipes to AIC requests. It is neither SimulationConfigAdapter nor SweepConfigProvider and does not add a replay framework.