Start with one tool, not a platform migration.

Bring one internal MCP tool, such as a refund tool, a deploy trigger, or a payout call, with a retry or audit concern. Send the scenario by email for a written answer on fit; if it fits, I walk the action through the full loop.

What the pilot includes

• One partner owned agent, one staging MCP tool, one consequential action, one named partner engineer.
• A staging environment on synthetic or redacted data, with a written scope and end date.
• An acceptance flow: a retry with the same key returns the original receipt instead of dispatching again. Verify the receipt offline.

Five things for your email

1. The tool or action. What the agent calls and what changes, for example a refund tool, a deploy trigger, or a payout call.
2. What goes wrong on retry.
3. How you check it happened. How you check whether the action ran, and ran once.
4. What one duplicate or unproven call costs. Lost money, recovery hours, or a concrete customer consequence. Unknown is an acceptable answer.
5. Who owns the budget and when they decide.

Use synthetic or redacted examples only. Never send production secrets, credentials, or customer data.

One tool, one operator, one action. Clone the public source repository to run make prove-trust-plane locally without live API credentials.