Pilot readiness: responsibilities by execution model

Source: deck slide 18 · WPP Pilot assessment | Risks Pilot risk groups; 19 requests mapped in appendix

Purpose: Confirm evidence and configuration; agree owners and residual-risk decisions.

Labels on this page: Wrike = Wrike's responsibility, WPP = WPP's responsibility, Joint = agreed together.

Governance & oversight (#1, #6, #7, #11, #20)#

Wrike AI Agents

• Wrike: Demonstrate the registry, creation rights and protected rules.
• Joint: Agree named owners, use-case review and treatment of high-impact actions.

Wrike MCP

• WPP: Record connections and owners.
• Joint: Agree which client approval settings and middleware restrictions apply to high-risk writes.

Identity, data & tool boundaries (#2, #3, #4, #15–#18, #21)#

Wrike AI Agents

• Wrike: Show the actions and locations configured for Pilot agents.
• Joint: Check the data present and agree the acceptable exposure for the Pilot.

Wrike MCP

• WPP: Demonstrate OAuth, allowlists, token handling, permitted tools and middleware scope, including how the assistant handles shared context.

Audit, support & client trust (#9, #10, #12, #14, #19)#

Wrike AI Agents

• Wrike: Show real logs, agent attribution and disablement.
• Joint: Confirm the evidence WPP needs and who owns incident response and recovery.

Wrike MCP

• Joint: Trace a real MCP action, rehearse shutdown and token revocation, and agree which team owns audit evidence and incident communications.

Discussion log#