verify

Cross-model gate verification validates gate flows by using a reviewer from a different model family to reduce blind spots and enforce diversity. It ensures payload-driven checks are independently reviewed before releasing a final verdict.

To run a fix-and-re-view loop, execute the oracle with a composed prompt, capture findings, and update the prosecution document. Repeat this process until no LANDED findings remain to achieve a traceable verdict.

You compose the oracle prompt by extracting the protocol from the payload's SKILL.md. Select reviewers from different model families, then execute the oracle to apply cross-model verification against the in-repo payload.

Yes, cross-model verification operates without external dependencies. It applies the protocol defined internally to select reviewers, compose the oracle prompt, and generate prosecution-doc updates until no LANDED findings remain.

Using a single model family for gate review introduces blind spots and lacks diversity. Cross-model verification addresses this by enforcing reviewer pairing from different model families to close the fix-and-re-view loop before releasing a verdict.