EXECUTABLE CONTRACT
Define what “correct” means.
UNTESTED
No output can cross until the contract compiles and validation passes.
Run the bundled sample to see exact instance paths, schema paths, keywords, and repair parameters.
Boundary: PASS proves declared JSON structure, not factual truth, authorization, or safe autonomous action.
CANDIDATE AI OUTPUT
Never wire plausible JSON directly.
Nothing parsed yet.
SCHEMA PARSEWAITING
OUTPUT PARSEWAITING
REQUIRED COVERAGE—
DOWNSTREAM RELAYOPEN / BLOCKED
Validity is a boundary, not a feeling.
Valid JSON only means the text parsed. A compiled contract adds required fields, types, allowed values, ranges, patterns, and forbidden extras. Passing those checks still does not prove the world agrees with the payload.
Why fail on extra properties?
Unexpected fields can leak private notes or trigger downstream code that was never part of the contract. Strict schemas make additions explicit.
Why keep exact paths?
An error at /items/0/quantity is reproducible and repairable. “The output looks wrong” is not.
What remains after PASS?
Independent fact checks, authorization, rate limits, human review for consequential actions, and real service permissions still matter.