Pure checks for AI Provider Boundary

Verification Boundary

The suite checks deterministic module behavior and declared configuration using local inputs.

What This Suite Proves

Only the permitted adapter crosses the provider boundary. Combined bindings require every named suite; a component assertion alone does not establish the full experiment.

What It Does Not Prove

These checks do not establish database transactions, deployed permissions, provider availability or a complete user journey.

Real Dependencies and Test Doubles

The guard reads the real tracked file list and source files in the Platform repository. Refusal samples use literal paths and text rather than extra files.

Must Not Be Doubled

Retain the function, configuration or boundary guard under test and its assertions; replacing them removes the evidence.

Show evidence (sources, provenance, origins, pinned commits)

Isolation: Literal inputs and process-local doubles, restored by the suite.
Kind: unit
Repository: services-platform
Environment: mock
Implementation state: implemented
Latest result: not-run
Conformance: not-verified

Test Files

services-platform:tests/unit/llm-provider-boundary.spec.ts

Implements

ATS-PFM-LLM-001-09

Implementation

Pure checks for AI Provider Boundary ​

Verification Boundary ​

What This Suite Proves ​

What It Does Not Prove ​

Real Dependencies and Test Doubles ​

Must Not Be Doubled ​