EXECUTABLE CONTRACT

Define what “correct” means.

NOT COMPILED

UNTESTED

No output can cross until the contract compiles and validation passes.

FAILURE LEDGER0 ERRORS

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.

NORMALIZED PARSED VALUE

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.

AI Output Gate: Circuit Breaker Validation

Your browser does not support video.

Read the explanation

Large language models produce plausible text that frequently violates type systems and schema constraints needed for reliable automation pipelines. The circuit breaker intercepts incoming payloads and evaluates each path against schema rules, tripping the relay when validation fails. Clicking load repaired supplies integer values and required properties, closing the relay contact to safely unblock downstream automation.