Prompt Kit: The Conway Leak — Platform Risk, Lock-In, and Agent Architecture

The Conway leak revealed more than code — it revealed that always-on agents are about to create a new category of vendor lock-in built on behavioral context, not just data. This kit gives you three prompts to evaluate platform risk before you commit, negotiate portability before you deploy, and decide where your agent's memory should live.

How to use this kit

These three prompts serve different needs but share a common thread: making smart decisions before an always-on agent platform makes them for you.

Prompt 1 (Platform Risk Assessment) works for anyone — enterprise buyer, developer, or enthusiast. Use it before committing to any agent infrastructure. It maps your dependencies and surfaces the risks you haven't thought about.
Prompt 2 (Vendor Lock-In Evaluation) is for enterprise leaders and procurement teams. Use it before signing a contract with any agent platform provider. It produces the actual clauses and questions you need.
Prompt 3 (Agent Architecture Decision Framework) is for developers and technical leaders. Use it when choosing between a convenient provider-hosted agent (like Conway) and a portable self-owned memory architecture (like Open Brain).

Each prompt works independently. If you're an enterprise CTO, you might run all three in sequence. Run these in any capable AI assistant — ChatGPT, Claude, Gemini, or similar.

Prompt 1: Platform Risk Assessment

Job: Maps your dependencies on an agent platform and surfaces the risk you're actually taking — across data, behavioral context, integrations, and exit cost.

When to use: Before committing your team or organization to any always-on agent platform. Also useful if you're already on one and want to understand your exposure.

What you'll get: A dependency map, a risk matrix covering five categories of lock-in (data, behavioral context, integrations, extensions, billing), an exit cost estimate, and specific mitigation steps ranked by urgency.

What the AI will ask you: Your role, what agent platform you're evaluating or already using, what tools and data the agent connects to, how long you've been using it (or plan to), and what your alternatives look like.

Prompt 2: Vendor Lock-In Evaluation for Enterprise

Job: Produces a negotiation playbook for enterprise teams deploying an always-on agent platform — specific contract clauses to demand, questions to ask vendors, red flags in their responses, and a framework for ongoing evaluation.

When to use: Before signing or renewing a contract with any AI agent platform provider, especially one that will accumulate behavioral context about your organization over time.

What you'll get: A list of contract clauses covering behavioral context portability, data export rights, pricing protection, and termination terms. A vendor questionnaire with acceptable and unacceptable answers. A 90-day evaluation framework. And a red-flag checklist for ongoing monitoring.

What the AI will ask you: Your organization type and size, what agent platform you're evaluating, what the agent will access, your existing data governance posture, and your procurement timeline.

Prompt 3: Agent Architecture Decision Framework

Job: Helps developers and technical leaders decide whether their agent's memory should live with a model provider (convenient, single-provider lock-in) or in infrastructure they own (portable, higher setup cost).

When to use: When you're choosing the architecture for an agent system — whether for yourself, your team, or a product you're building for others. Especially relevant if you're weighing something like Conway against a self-owned memory layer exposed through MCP.

What you'll get: A structured comparison of provider-hosted vs. self-owned memory architecture, a decision matrix weighted to your specific constraints, an honest trade-off analysis, and an implementation recommendation with next steps.

What the AI will ask you: What you're building, your team's technical capability, your tolerance for setup complexity vs. lock-in risk, your timeline, whether you're building for yourself or for customers, and your current infrastructure.