What technical sample should a builder request before committing to a larger environment?

Ask for a sample that exercises your loader as well as your agent. The request can specify a schema document, representative fixture files and a manifest listing file roles, encoding, schema versions and content checksums. Choose JSONL or Parquet according to your existing ingestion path rather than assuming both are necessary.

Define identifier handling before import. Fields such as `request_id` and `queue_id` should remain stable within the package, while your application can map them to internal identifiers. Agree how timestamps, enumerations, absent values and explicit nulls are represented; these details can change tool behaviour after conversion.

A compatibility check can load the sample into an empty namespace, validate references and execute a declared routing action. It can then export the resulting records and confirm that policy-relevant fields survive the round trip. Unknown required fields should produce a clear import failure rather than being silently discarded.

MirrorFirm could scope this sample around the buyer’s adapter requirements. Request documentation of supported assumptions and unresolved format differences, without assuming an existing connector. The useful first result is evidence that generated world state can enter and leave your simulator with its meaning intact.