Integration keeps Evals’ contracts stable while an application supplies the target, model client, process, or qualification rollup. Choose the narrowest adapter that can produce a validated Observation, then reuse the same cases, evaluators, gates, and report format.

Connect a target

Integration need	Continue with	Boundary
Call an Inference client and project typed evidence	Composition and testing	`target/inference.NewTarget` owns request projection and subject identity.
Add capability-aware tables and scorecards	Pluto qualification tooling	Pluto plans tables, executes Evals runs, and derives dispositions.
Choose the model request first	Inference model selection	The caller owns provider and model identity before composing the target.

Deterministic scripted targets and fake clients should carry the contract tests. Credential-gated provider tests then verify the live adapter seam without making the qualification suite depend on network timing.

Source

The public target seam is declared in target.go, with the Inference adapter in target/inference/target.go.

Proof

The live adapter boundary is covered by target_integration_test.go, and deterministic test presentation by evaltest/run.go.