What integration contract should be agreed before connecting a pilot to an agent harness?

Ask for a release manifest that identifies the dataset version, schema version, policy bundle and supported task interface. A buyer can also request file checksums and a declared compatibility policy so an updated export cannot silently replace the material used in an earlier evaluation.

Define how generated records map into the harness. Fields such as `case_id`, `subject_ref` and `policy_ref` should have agreed types and resolution rules. Specify whether absent fields mean unknown, inapplicable or omitted, because adapters often turn those distinctions into misleading defaults.

For tool-based tasks, document the mapping between simulated actions and the harness's callable functions. Include argument validation, error payloads and the boundary between agent-visible observations and evaluator-only artifacts. A successful connection should not depend on undocumented field names or hidden transformations.

MirrorFirm could scope this contract as part of a pilot handoff. The first integration check can load a declared release, resolve its references and execute a permitted action through the adapter. Record the release and adapter versions with the run so later differences can be traced to their actual source.