contract-validation

Contract validation prevents violations by verifying agent inputs and outputs against predefined rules during execution start, finish, or debugging phases, recording results in workflow-state.json to support governance and traceability.

You validate inputs and outputs by loading definitions from contracts/*.json and applying rule checks through lib/contract-validator.ts, which automatically verifies data before and after agent execution and updates workflow-state.json with results.

During debugging, the validation mechanism leverages lib/contract-validator.ts to perform automated checks against contracts/*.json, verifying previous inputs and outputs to identify where the contract violation occurred within the workflow-state.json updates.

Yes, you can use it for governance and monitoring. The validation process automatically records results in workflow-state.json, providing traceability and supporting end-to-end governance scenarios across the entire OMT pipeline.

Yes, you need JSON contract files. The validation mechanism relies on definitions stored in the contracts/*.json directory to load the required rules and verify that agent inputs and outputs comply with the contract-first pattern.

You should avoid automated contract validation when your workflow lacks defined contracts in contracts/*.json, or when your agents operate outside the OMT pipeline, as the validation mechanism specifically depends on lib/contract-validator.ts and workflow-state.json integration.