Cross Check

Compare research findings against validation results for $ARGUMENTS.

When to Use

• After both the researcher and validator have reported back
• When something doesn't match between docs and observed API behavior
• To find gaps before executing a new type of operation

Workflow

1. Gather inputs — read the researcher's findings (docs, endpoints, expected behavior) and the validator's results (actual API responses, device state)
2. Compare — check each finding against reality:
   • Does the documented endpoint match what the API actually returned?
   • Does the expected response format match the actual response?
   • Are there fields, statuses, or behaviors the docs mention that we haven't seen?
   • Are there things the API returns that the docs don't cover?
3. Flag gaps — anything missing, conflicting, or unverified
4. Recommend — what to do about each gap (research more, test manually, safe to proceed)

Output Format