Pure checks for Validate Catalog Declarations

Verification Boundary

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

What This Suite Proves

Invalid catalog publication is atomic. 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 validator and published declarations are real. Refusal cases alter copies of those declarations.

Must Not Be Doubled

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