11.Why Open Compounds

Here is the strongest objection to everything in Part IV, and it deserves to be stated at full strength. Nearly every platform era of modern computing ended with one or two closed winners taking most of the value: operating systems did, search did, mobile did, social did, cloud largely did. A skeptic reading this guide is entitled to ask why the AI-operations layer should end differently, and why a hyperscaler or frontier lab with infinite resources would not simply absorb this architecture the moment it looks valuable.

The paper's answer turns on trust in what is being exchanged: a marketplace of context-bearing artifacts only works if participants can inspect, and therefore trust, the format holding their most sensitive assets (§8.1), and no incumbent, it argues, is structurally positioned to offer that (§9). This guide would extend the argument one step the paper does not take, and the extension is what makes the answer interesting rather than merely convenient. Closed platforms have historically won where the exchanged content is low-trust or low-stakes: search queries, social posts, app downloads. The artifacts of this economy sit at the other pole. A Frame is an organization's distilled operational knowledge; Organizational Memory is its accumulated institutional record. Organizations have poured exactly such assets into proprietary systems before, and Part I is a catalog of that trade; the crown jewels sitting in closed CRM, ERP, and record systems show it can persist for decades. The paper's bet is that these artifacts arrive after the lesson: an organization adopting Frames because of the tenancy problem has little reason to rebuild that problem one layer up, and the compliance pressure documented in Section 6 turns an inspectable, portable format from a preference into a purchase criterion. The paper quotes January 2026 industry analysis making the security half of the same point: "Open standards for AI will be essential because they allow the entire ecosystem to inspect, test, and harden the protocols agents use. When those interfaces are closed or proprietary, you end up with blind spots." For context-bearing, compliance-bearing artifacts, openness functions less as philosophy than as a precondition: trust is the scarce input, and open inspection is the only known way to manufacture it at ecosystem scale.

The flywheel, with its brakes shown

This is a standard two-sided network effect, artifact publishers on one side and Hub deployers on the other, and the paper presents it as self-reinforcing, which, once spinning, it is. A field guide should also show the brakes, so here is the same loop with its balancing forces drawn in:

        ┌──→ more Hubs ──→ bigger market for publishers ──→ more artifacts ──┐
        │                                                                    │
        └──────────────── more value per Hub deployment ←────────────────────┘
                             (reinforcing loop)

   balancing forces, any of which can stall it:
   • cold start: few Hubs → few publishers → little to install → weak case for Hubs
   • fragmentation: competing context/packaging standards split the network
   • quality collapse: a marketplace of mediocre Ops teaches buyers to stop looking
   • incumbent bundling: "good enough" closed features soak up the demand first

        ┌──→ more Hubs ──→ bigger market for publishers ──→ more artifacts ──┐
        │                                                                    │
        └──────────────── more value per Hub deployment ←────────────────────┘
                             (reinforcing loop)

   balancing forces, any of which can stall it:
   • cold start: few Hubs → few publishers → little to install → weak case for Hubs
   • fragmentation: competing context/packaging standards split the network
   • quality collapse: a marketplace of mediocre Ops teaches buyers to stop looking
   • incumbent bundling: "good enough" closed features soak up the demand first

The cold-start problem is the classic one for every marketplace, and the architecture's implicit answers are visible in earlier sections: Frames are useful at n=1 (a company gets internal alignment value with zero marketplace), Ops are useful at n=1 (an installable, validated workflow beats a bespoke integration even if nobody else ever installs it), and the open-source distribution channel seeds supply the way it seeded every package registry. Whether those answers suffice is one of Section 12's watchable indicators, not a settled fact.

Platforms tax; protocols compound

Why the incumbents haven't already won this

The paper's competitive analysis reduces to a structural observation per category, and it is more persuasive in that form than as a feature table. Foundation-model providers monetize aggregated, vendor-side intelligence; sovereign, customer-side deployment inverts their unit economics, which is why their enterprise offers keep pulling context inward. Cloud AI platforms sell managed convenience inside one cloud; a cross-cloud, customer-owned standard dissolves their lock-in rather than extending it. Agent frameworks are libraries: genuinely useful, but without deployment standards, governance layers, or a distribution economy, they are components of this architecture rather than competitors to it. Enterprise SaaS vendors embed AI into their own vertical silos, the opposite of a cross-domain, portable-context standard. None of this makes incumbents harmless; any of them can bundle a good-enough closed substitute, which is the fourth brake on the flywheel above. The paper's own conclusion is worth carrying with its confidence calibrated: the category is open because no incumbent is structurally configured to fill it, which is an argument about posture, not about destiny.