<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Interoperability on Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/tags/interoperability/</link><description>Recent content in Interoperability on Control Plane by Karl McGuinness</description><generator>Hugo</generator><language>en-us</language><managingEditor>public@karlmcguinness.com (Karl McGuinness)</managingEditor><webMaster>public@karlmcguinness.com (Karl McGuinness)</webMaster><lastBuildDate>Mon, 06 Jul 2026 12:00:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/tags/interoperability/index.xml" rel="self" type="application/rss+xml"/><item><title>Reachability Is the New Lock-In</title><link>https://notes.karlmcguinness.com/notes/reachability-is-the-new-lock-in/</link><pubDate>Mon, 06 Jul 2026 12:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/reachability-is-the-new-lock-in/</guid><description>Egress policy used to be plumbing. For agents it is authorization. An agent discovers the systems it needs at runtime, so the allowlist that decides where it may go also decides what it may do. That makes reachability a control point, and control points become competitive. Identity portability created competition among identity providers. Agent portability will create competition among agent providers, but only if an agent can reach any system the enterprise authorizes, regardless of who built the agent. Restricting runtime connectivity is the quiet way to prevent that, and it turns an enterprise into a captive client. The fix is portable, policy-governed connectivity, the same move every open ecosystem eventually makes.</description></item></channel></rss>