What integration package should developers request to start a reproducible pilot?

Ask for a pilot package containing a schema version, generated fixture manifest, tool contract and task entry points. JSONL can carry interaction records; Parquet can carry relational tables for inspection. The manifest should identify which files belong together and how their identifiers connect.

For an interactive environment, define what `reset` restores. It should address requests, assignments, pending events, tool side effects and agent-visible history. A reset that clears request status but leaves an earlier assignment notification can contaminate the next run.

Request explicit controls for the environment clock and any variable responses. A seed can help reproduce generated variation, but reproducibility also depends on fixed tool behaviour, scheduled events and versioned fixtures. Declare any remaining nondeterminism.

The integration package can expose a run identifier, fixture version and trace export hook so results remain attributable to the state actually used. Keep agent memory reset separate from environment reset and document both.

A useful first step is loading a fixture, executing a permitted assignment, resetting and confirming that the original state returns. This validates the integration foundation before routing performance is interpreted.