What integration agreement should precede a customer change pilot?

Before a pilot, agree where the generated package ends and the buyer's runtime begins. The package might define records, action semantics and expected transitions, while the buyer implements storage, tool routing and scheduling. A different arrangement may include an executable reference environment; that should be requested explicitly.

Specify a versioned manifest that names schemas, action contracts and policy resources. For JSONL or Parquet exports, agree how identifiers and types survive import. For MCP access, agree how tool names, arguments and error responses map to the same actions. Public editorial descriptions should not be treated as complete executable contracts.

MirrorFirm could scope generated material against this interface and provide conformance cases that exercise the mapping. A useful case sends the same change through two adapters and compares resulting business state, allowing harmless differences in transport metadata.

Reset ownership also needs a named boundary: the component that restores records must coordinate with whichever component owns queued work. Start integration by importing a snapshot, executing a specified action and checking its resulting state against the contract. Resolve mapping differences before expanding the scenario catalogue.