Why Memory Components Fail: Eight Years of License and Sustainability Events in Open-Source Data Infrastructure

LLM agent memory is now treated as a first-class architectural component in five major surveys published between January and April 2026. None of these surveys treats project governance, capital structure, or license posture as architectural variables. We argue they are. In a constructed sample of 105 production-relevant open-source data-infrastructure and AI-tooling projects, we catalogue 38 license-and-sustainability events between 2018 and May 2026. About a quarter of the sample (24 percent) experienced at least one adverse event. The conditional rates split sharply by structure: 46 percent for single-vendor venture-backed projects, 2.5 percent for foundation-governed projects funded outside the venture cycle. The headline differential -- roughly nineteen-fold -- is invariant to the most contested coding choice in the catalogue; we show the sensitivity table in Section 7. A small subset of foundation-governed projects with venture-backed corporate stewards (n=3) contains one adverse event. The cell is too small for stable estimation, but it points to a mechanism: foundation governance may block unilateral relicensing while leaving distribution decisions to the steward. Annualized incidence within the catalogue rose from 2.7 to 4.2 events per year across the window. Counterfactuals -- PostgreSQL, pgvector, SQLite, Apache Kafka, Caddy -- each show stability arising from a different structural source: distributed copyright, absence of monetisation pressure, foundation governance with non-venture stewardship. We propose a six-field decision instrument for architects choosing memory components: governance, capital structure, license, foundation membership, fork-or-migration availability, and steward concentration.