<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:media="http://search.yahoo.com/mrss/">
<channel>
<title><![CDATA[ Invest in Open Infrastructure ]]></title>
<description><![CDATA[ Helping you invest in the open technology that research relies on. ]]></description>
<link>https://investinopen.org</link>
<image>
    <url>https://investinopen.org/favicon.png</url>
    <title>Invest in Open Infrastructure</title>
    <link>https://investinopen.org</link>
</image>
<lastBuildDate>Thu, 01 Oct 2026 16:59:25 +0000</lastBuildDate>
<atom:link href="https://investinopen.org/rss/" rel="self" type="application/rss+xml"/>
<ttl>60</ttl>

    <item>
        <title><![CDATA[ Where the money goes ]]></title>
        <description><![CDATA[ Funding insights at a level no single funder can see from inside its own portfolio.


Grant funding flows are one signal of how the research ecosystem values and takes responsibility for the infrastructure it shares.


The data and analyses we published in 2024 and 2025 primarily focused on better understanding ]]></description>
        <link>https://investinopen.org/state-of-open-infrastructure-2026/sooi-where-the-money-goes-2026/</link>
        <guid isPermaLink="false">6abe8ab319ee5f000115d8ec</guid>
        <category><![CDATA[ SOOI-2026 ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Thu, 01 Oct 2026 16:57:24 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ 
<!--kg-card-begin: html-->
<!-- ============================================================
SoOI 2026 · Section 1 (Where the money goes) · v10 · CMS embed
Source text: "State of Open Infrastructure 2026 (Milestone 2)" PDF.
Paste into an HTML block/card. Self-contained & scoped: all styles
apply only inside .sooi-s1 and cannot leak into site styles.
Fonts: loads Inter from Google Fonts; BW Gradual (headings) inherits from the site.
If the site already loads these (check site <head>), delete the
<link> line to avoid a duplicate request.
Page title + subtitle are owned by the CMS template (not in this block).
v10 = nav anchors: #what-does-the-money-support, #how-concentrated-are-the-sources,
#data-and-software-availability-statement.
NEW vs sooi-s1-embed-v6 (pending Jerry's CMS review): pull quote; figure labels/notes;
leverage figure stack + Efficiency/Fragility pair; 3-up stat row (.eco-3); country symbol
lists (replace schematic SVG maps, per final Figs 6–7); links are now real <a> tags with reset.
HELD/FLAG comments inline mark passages that contradict cards.csv — search "HELD" / "FLAG".
============================================================= -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<!-- BW Gradual (headings) is loaded by the site; the embed inherits it. -->
<style>
/* ================= BRAND TOKENS =================
   Copied verbatim from sooi-s1-embed.html. Edit ONLY this block to re-theme.
   ================================================= */
.sooi-s1{--bg:transparent;--text:#000000;--text-secondary:#262626;--text-tertiary:#6f6f6f;
    --border:#e6e4df;--border-light:#f0efec;
    /* IOI brand. Blue is FILL-ONLY (2.1:1 on white as text); numbers & links are black, per site. */
    --accent:#000000;--accent-light:#d9f0fc;
    --brand-yellow:#ffde17;--brand-mint:#83fed1;--brand-blue:#69b3f2;--brand-peach:#ffbea1;
    --card-bg:#ffffff;--highlight:#fdf6e3;
    /* No red in IOI palette: risk maps to peach backgrounds with black text. */
    --risk-critical:#000000;--risk-critical-bg:#fff1e6;--risk-high:#262626;--risk-high-bg:#ffe9d6;--risk-low:#262626;--risk-low-bg:#dcfbee;
    --direct:#69b3f2;--adjacent:#9aeef7;--adoption:#b6fcdf;--unknown:#e6e4df;
    --ops:#ffbea1;--rnd:#69b3f2;--other:#e6e4df;--land:#ecebe7}
.sooi-s1 *{margin:0;padding:0;box-sizing:border-box}
.sooi-s1{font-family:'Inter',var(--site-body-font,sans-serif);color:var(--text);line-height:1.6;-webkit-font-smoothing:antialiased;max-width:1080px;margin:0 auto;padding:8px 0 40px}
.sooi-s1 .lede{font-size:16px;color:var(--text-secondary);max-width:760px;line-height:1.7}
.sooi-s1 .lede + .lede{margin-top:14px}
.sooi-s1 .cut{border-top:1px solid var(--border-light);margin-top:52px;padding-top:38px}
.sooi-s1 .cut-num{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;letter-spacing:2px;color:var(--text-tertiary);text-transform:uppercase;margin-bottom:6px}
.sooi-s1 .cut-intro{font-size:15px;color:var(--text-secondary);max-width:740px;margin-bottom:22px}
.sooi-s1 .caveat{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);background:#fff;border:1px dashed var(--border);border-radius:6px;padding:8px 12px;margin-top:14px;line-height:1.5}
.sooi-s1 .door{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--accent);margin-top:18px;display:flex;align-items:center;gap:8px}
.sooi-s1 .door::before{content:'→'}
/* spacing after bare headings: styles the following element, never the heading */
.sooi-s1 h2 + p,.sooi-s1 h2 + div,.sooi-s1 h3 + p,.sooi-s1 h3 + div{margin-top:10px}
.sooi-s1 .subhead{margin-top:44px;margin-bottom:0}
/* figure labels + notes (new, minor) */
.sooi-s1 .fig{margin-top:30px}
.sooi-s1 .fig-title{font-size:15px;font-weight:600;color:var(--text);margin-bottom:12px}
.sooi-s1 .fig-note{font-size:12px;color:var(--text-tertiary);line-height:1.5;margin-top:12px;max-width:820px}
/* pull quote (new component) */
.sooi-s1 .pullquote{margin:44px 0;max-width:640px}
.sooi-s1 .pullquote .marks{display:flex;gap:6px;margin-bottom:14px}
.sooi-s1 .pullquote .marks span{display:block;height:10px;border-radius:5px}
.sooi-s1 .pullquote .marks .m1{width:32px;background:#000}
.sooi-s1 .pullquote .marks .m2{width:18px;background:var(--brand-yellow)}
.sooi-s1 .pullquote .marks .m3{width:10px;background:var(--adjacent)}
.sooi-s1 .pullquote p{font-size:22px;font-weight:700;line-height:1.3;color:var(--text)}
/* ---- defensive reset: site link styles ---- */
.sooi-s1 a{color:var(--text) !important;font-weight:inherit !important;background:transparent !important;border:0 !important;box-shadow:none !important;
  text-decoration:underline !important;text-decoration-color:var(--brand-yellow) !important;text-decoration-thickness:2px !important;text-underline-offset:3px;overflow-wrap:anywhere}
.sooi-s1 a:hover{text-decoration-color:var(--text) !important}
.sooi-s1 sup{font-size:.7em;line-height:0;vertical-align:super}
.sooi-s1 sup a{text-decoration:none !important}
.sooi-s1 .footnotes{list-style:none !important;margin-top:28px !important;border-top:1px solid var(--border-light) !important;padding-top:12px !important;font-size:12px !important;color:var(--text-tertiary) !important}
.sooi-s1 .footnotes li{margin-bottom:4px !important}
/* ---- defensive reset: site list styles (ol/ul/li) bleed into references & lists ---- */
.sooi-s1 ol,.sooi-s1 ul{list-style:none !important;margin:0 !important;padding:0 !important;background:transparent !important;border:0 !important;box-shadow:none !important;counter-reset:none !important}
.sooi-s1 li{list-style:none !important;margin:0 !important;padding:0 !important;background:transparent !important;border:0 !important;box-shadow:none !important;text-indent:0 !important;font-size:inherit !important;line-height:inherit !important;color:inherit !important}
.sooi-s1 li::marker{content:none !important}
.sooi-s1 li::before,.sooi-s1 li::after{content:none !important;display:none !important}
.sooi-s1 .eco{display:grid;grid-template-columns:repeat(4,1fr);gap:1px;background:var(--border);border:1px solid var(--border);border-radius:12px;overflow:hidden;margin:0 0 4px}
.sooi-s1 .eco.eco-3{grid-template-columns:repeat(3,1fr);margin-top:24px}
.sooi-s1 .eco-card{background:var(--card-bg);padding:24px 20px;text-align:center}
.sooi-s1 .eco-card .n{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:34px;font-weight:700;color:var(--accent);line-height:1;margin-bottom:6px}
.sooi-s1 .eco-card .l{font-size:12px;color:var(--text-secondary);line-height:1.3}
.sooi-s1 .eco-card .s{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:10px;color:var(--text-tertiary);margin-top:4px}
.sooi-s1 .split-bar{display:flex;height:44px;border-radius:8px;overflow:hidden;margin:6px 0}
.sooi-s1 .seg{display:flex;align-items:center;justify-content:center;color:#000;font-size:12px;font-weight:600;min-width:0}
.sooi-s1 .seg.d{background:var(--direct)}
.sooi-s1 .seg.a{background:var(--adjacent)}
.sooi-s1 .seg.ad{background:var(--adoption);color:var(--text-secondary)}
.sooi-s1 .seg.u{background:var(--unknown);color:var(--text-secondary)}
.sooi-s1 .split-legend{display:flex;gap:20px;flex-wrap:wrap;font-size:12px;color:var(--text-secondary);margin-top:10px}
.sooi-s1 .split-legend b{color:var(--text)}
.sooi-s1 .dot{width:10px;height:10px;border-radius:3px;display:inline-block;margin-right:6px;vertical-align:middle}
.sooi-s1 .leverage{background:#000;color:#fff;border-radius:12px;padding:30px 32px;display:flex;gap:32px;align-items:center;flex-wrap:wrap;margin-top:24px}
.sooi-s1 .leverage .big{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:56px;font-weight:700;line-height:1;white-space:nowrap;color:var(--brand-yellow)}
.sooi-s1 .leverage p{font-size:15px;line-height:1.6;opacity:.94;flex:1;min-width:300px}
.sooi-s1 .leverage strong{color:#fff}
/* leverage: figure stack + efficiency/fragility pair (new sub-components) */
.sooi-s1 .leverage .lev-fig{min-width:150px}
.sooi-s1 .leverage .lev-one{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:28px;font-weight:700;line-height:1;color:#fff;margin-top:14px;padding-top:12px;border-top:1px solid rgba(255,255,255,.35)}
.sooi-s1 .leverage .lev-lab{font-size:11px;letter-spacing:1px;text-transform:uppercase;color:#fff;opacity:.8;margin-top:6px}
.sooi-s1 .leverage .lev-body{flex:1;min-width:280px}
.sooi-s1 .leverage .lev-body p{min-width:0}
.sooi-s1 .leverage .lev-pair{display:grid;grid-template-columns:1fr 1fr;gap:20px;margin-top:18px}
.sooi-s1 .leverage .lev-pair > div{border-top:2px solid var(--brand-yellow);padding-top:10px}
.sooi-s1 .leverage .lev-k{font-size:15px;font-weight:700;color:var(--brand-yellow);margin-bottom:4px}
.sooi-s1 .leverage .lev-pair p{font-size:13px;min-width:0;opacity:.94}
.sooi-s1 .ratio-wrap{margin-top:6px}
.sooi-s1 .ratio-row{display:grid;grid-template-columns:220px 1fr 150px;align-items:center;gap:12px;margin-bottom:7px}
.sooi-s1 .ratio-name{font-size:13px;text-align:right;color:var(--text-secondary)}
.sooi-s1 .ratio-track{height:24px;background:var(--border-light);border-radius:4px;overflow:hidden}
.sooi-s1 .ratio-fill{height:100%;background:var(--adjacent);border-radius:4px;display:flex;align-items:center;justify-content:flex-end;padding-right:8px;color:#000;font-size:11px;font-weight:600}
.sooi-s1 .ratio-amt{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);line-height:1.35}
.sooi-s1 .donut-wrap{display:flex;gap:36px;align-items:center;flex-wrap:wrap}
.sooi-s1 .donut{flex-shrink:0}
.sooi-s1 .donut-legend{flex:1;min-width:260px}
.sooi-s1 .dl-row{display:flex;align-items:center;gap:10px;padding:8px 0;border-bottom:1px solid var(--border-light);font-size:14px;flex-wrap:wrap}
.sooi-s1 .dl-row:last-child{border:none}
.sooi-s1 .dl-row .sw{width:14px;height:14px;border-radius:3px;flex-shrink:0}
.sooi-s1 .dl-row .name{flex:1}
.sooi-s1 .dl-row .val{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:13px;color:var(--text-secondary)}
.sooi-s1 .dl-row .desc{font-size:12px;color:var(--text-tertiary);width:100%;padding-left:24px}
.sooi-s1 .conc-grid{display:grid;grid-template-columns:1fr 1fr;gap:16px;margin-top:24px}
.sooi-s1 .conc-card{background:var(--card-bg);border:1px solid var(--border);border-radius:10px;padding:22px 24px}
.sooi-s1 .conc-card .big{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:40px;font-weight:700;color:var(--accent);line-height:1;margin-bottom:6px}
.sooi-s1 .conc-card h3{font-size:15px;font-weight:600;margin-bottom:6px}
.sooi-s1 .conc-card p{font-size:13px;color:var(--text-secondary);line-height:1.55}
.sooi-s1 .br-row{display:grid;grid-template-columns:280px 1fr 42px;align-items:center;gap:12px;margin-bottom:6px}
.sooi-s1 .br-name{font-size:13px;text-align:right;color:var(--text-secondary)}
.sooi-s1 .br-track{height:22px;background:var(--border-light);border-radius:4px;overflow:hidden}
.sooi-s1 .br-fill{height:100%;background:var(--brand-blue);border-radius:4px}
.sooi-s1 .br-val{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--text-tertiary)}
.sooi-s1 .maps{display:grid;grid-template-columns:1fr 1fr;gap:16px;margin-top:6px}
.sooi-s1 .mapcard{background:var(--card-bg);border:1px solid var(--border);border-radius:10px;padding:18px 18px 14px}
.sooi-s1 .mapcard .oi{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;background:var(--accent-light);color:var(--accent);padding:2px 8px;border-radius:3px;display:inline-block;margin-bottom:10px}
/* country symbol list (new component; replaces schematic SVG maps to match final Figures 6–7) */
.sooi-s1 .cl-row{display:grid;grid-template-columns:36px 1fr;align-items:center;gap:10px;padding:3px 0;font-size:13px;color:var(--text-secondary)}
.sooi-s1 .cl-sym{display:flex;align-items:center;justify-content:center}
.sooi-s1 .cl-sym span{display:block;border-radius:50%}
.sooi-s1 .cl-row.dir{color:var(--text);font-weight:600}
.sooi-s1 .fed{background:var(--risk-critical-bg);border:1px solid var(--brand-peach);border-radius:10px;padding:24px;margin-top:20px}
.sooi-s1 .fed-head{display:flex;gap:24px;align-items:center;flex-wrap:wrap;margin-bottom:18px}
.sooi-s1 .fed-head .big{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:38px;font-weight:700;color:var(--risk-critical);line-height:1;white-space:nowrap}
.sooi-s1 .fed-head .fed-lab{font-size:12px;font-weight:600;color:var(--text);margin-top:6px;max-width:190px;line-height:1.35}
.sooi-s1 .fed-head p{font-size:14px;color:var(--text-secondary);line-height:1.55;flex:1;min-width:280px}
.sooi-s1 .fed .cut-num{margin-top:4px}
/* ---- defensive reset: site table styles bleed into .fed-table (yellow bands) ---- */
.sooi-s1 .fed-table,.sooi-s1 .fed-table thead,.sooi-s1 .fed-table tbody,
.sooi-s1 .fed-table tr,.sooi-s1 .fed-table th,.sooi-s1 .fed-table td{
  background:transparent !important;border:0 !important;box-shadow:none !important}
.sooi-s1 .fed-table{border-collapse:collapse !important;width:100% !important;margin:0 !important;font-size:13px !important}
.sooi-s1 .fed-table th{font-size:10px !important;letter-spacing:1px !important;text-transform:uppercase !important;
  color:var(--text-tertiary) !important;text-align:left !important;padding:6px 10px !important;font-weight:500 !important;
  border-bottom:2px solid var(--brand-peach) !important}
.sooi-s1 .fed-table td{padding:8px 10px !important;border-bottom:1px solid #ffe4d2 !important;color:var(--text) !important}
.sooi-s1 .fed-table td.amt,.sooi-s1 .fed-table th.amt{text-align:right !important}
.sooi-s1 .fed-table td.amt{font-weight:600 !important;color:var(--text) !important;font-family:'Inter',var(--site-mono-font,sans-serif)}
.sooi-s1 .fed-table td.muted{color:var(--text-tertiary) !important}
.sooi-s1 .fed-table tr:last-child td{border-bottom:0 !important;border-top:2px solid var(--brand-peach) !important}
/* nav anchors: invisible jump targets for the report navigation */
.sooi-s1 .nav-anchor{display:block;height:0;scroll-margin-top:90px}
.sooi-s1 [id]{scroll-margin-top:90px}

/* ---- responsive ---- */
@media (max-width: 900px){
  .sooi-s1 .maps{grid-template-columns:1fr}
  .sooi-s1 .conc-grid{grid-template-columns:1fr}
  .sooi-s1 .donut-wrap{flex-direction:column;align-items:flex-start}
}
@media (max-width: 640px){
  .sooi-s1 .pullquote p{font-size:18px}
  .sooi-s1 .eco{grid-template-columns:1fr 1fr}
  .sooi-s1 .eco.eco-3{grid-template-columns:1fr}
  .sooi-s1 .ratio-row{grid-template-columns:110px 1fr 96px;gap:8px}
  .sooi-s1 .ratio-name{font-size:11px}
  .sooi-s1 .br-row{grid-template-columns:140px 1fr 34px;gap:8px}
  .sooi-s1 .br-name{font-size:11px}
  .sooi-s1 .leverage{padding:22px 20px;gap:18px}
  .sooi-s1 .leverage .big{font-size:42px;color:var(--brand-yellow)}
  .sooi-s1 .leverage .lev-pair{grid-template-columns:1fr}
  .sooi-s1 .fed-head .big{font-size:30px}
  .sooi-s1 .split-legend{gap:10px;font-size:11px}
  .sooi-s1 .fed-table{font-size:12px !important}
  .sooi-s1 .fed-table th,.sooi-s1 .fed-table td{padding:6px 6px !important}
}
@media (max-width: 420px){
  .sooi-s1 .eco{grid-template-columns:1fr}
  .sooi-s1 .ratio-row{grid-template-columns:90px 1fr;gap:6px}
  .sooi-s1 .ratio-amt{display:none}
}
</style>
<div class="sooi-s1">
<h2>Funding insights at a level no single funder can see from inside its own portfolio.</h2>
  <p class="lede">Grant funding flows are one signal of how the research ecosystem values and takes responsibility for the infrastructure it shares.</p>
  <p class="lede">The data and analyses we published in 2024 and 2025 primarily focused on better understanding the amount, impact, and limitations of grant funding to Open Infrastructures (OIs). In 2026, we are looking more closely at a related factor: how much funding is supporting infrastructure elements directly versus how much funding is supporting research that leans on and invokes infrastructure, but doesn’t contribute to it financially.</p>
  <p class="lede">This section maps the funding dependencies for infrastructure and how narrowly the sustaining funding is sourced. We hope our analysis offers funders, institutions, and infrastructure providers a shared, independent picture of patterns that none of them created alone, and that none can address alone.</p>
  <p class="lede">Our full data collection and preparation methods are described in detail in the documentation that accompanies the raw data — this is available for download.<sup><a href="#sooi-s1-fn1">1</a></sup> We encourage readers to explore the full documentation for additional information on how we processed the data, as well as key assumptions and their likely trade offs. The funding described in this report is limited to grants we were able to identify through public sources and does not include other sources of revenue or funding for these infrastructures.</p>

  <div class="fig">
    <div class="cut-num">Figure 1</div>
    <div class="fig-title">Ecosystem analysis overview</div>
    <div class="eco">
      <div class="eco-card"><div class="n">$663M</div><div class="l">Total tracked funding</div><div class="s">2001–2026</div></div>
      <div class="eco-card"><div class="n">1,065</div><div class="l">Awards analysed</div><div class="s">965 dollar-bearing</div></div>
      <div class="eco-card"><div class="n">47</div><div class="l">Funders</div><div class="s">canonical, ROR-resolved</div></div>
      <div class="eco-card"><div class="n">94</div><div class="l">Open infrastructures</div><div class="s">Infra Finder catalogue</div></div>
    </div>
    <p class="fig-note">All financial data in the report is quoted in US dollars.</p>
  </div>

  <div class="fig">
    <div class="cut-num">Figure 2</div>
    <div class="fig-title">What the tracked funding pays for</div>
    <div class="split-bar">
      <div class="seg d" style="width:29%">$192M</div>
      <div class="seg a" style="width:62%">$411M</div>
      <div class="seg ad" style="width:3.4%"></div>
      <div class="seg u" style="width:5.6%"></div>
    </div>
    <div class="split-legend">
      <span><span class="dot" style="background:var(--direct)"></span><b>$192M direct</b> — funds an OI</span>
      <span><span class="dot" style="background:var(--adjacent)"></span><b>$411M adjacent</b> — funds work that depends on an OI</span>
      <span><span class="dot" style="background:var(--adoption)"></span><b>$23M</b> adoption</span>
      <span><span class="dot" style="background:var(--unknown)"></span><b>$37M</b> unknown</span>
    </div>
    <p class="fig-note">Shares are of $663M across 965 dollar-bearing award clusters, out of 1,065 clusters in total. The remaining 100 carry no allocatable dollar figure and are counted by presence only.</p>
  </div>

  <div class="pullquote"><div class="marks"><span class="m1"></span><span class="m2"></span><span class="m3"></span></div><p>Grant funding flows are one signal of how the research ecosystem values and takes responsibility for the infrastructure it shares.</p></div>

  <!-- ============ Q1 ============ -->
  <div class="cut">
    <div class="nav-anchor" id="what-does-the-money-support"></div>
    <div class="cut-num">Question 1: What does the money support?</div>
    <h2>Most grant funding supports research that depends on open infrastructure; far less sustains the infrastructure itself.</h2>
    <p class="cut-intro">We classify grants as <em>direct</em> (funding an OI), <em>adjacent</em> (funding research that depends on an OI), or <em>adoption</em> (funding an entity to deploy an OI). The imbalance between direct and adjacent is the clearest signal in the data of how funders allocate funding: more heavily toward the research, and lightly toward the infrastructure beneath it. The ratio varies widely by infrastructure; for some, a few hundred thousand in direct support underwrites tens of millions in dependent research.</p>

    <div class="fig">
      <div class="cut-num">Figure 3</div>
      <div class="fig-title">Adjacent funding per dollar of direct funding</div>
      <div class="ratio-wrap">
      <div class="ratio-row"><div class="ratio-name">Creative Commons</div><div class="ratio-track"><div class="ratio-fill" style="width:100%">28.7×</div></div><div class="ratio-amt">$9.3M adjacent<br>$325K direct</div></div>
      <div class="ratio-row"><div class="ratio-name">DOAJ</div><div class="ratio-track"><div class="ratio-fill" style="width:83%">23.9×</div></div><div class="ratio-amt">$934K adjacent<br>$39K direct</div></div>
      <div class="ratio-row"><div class="ratio-name">RRID</div><div class="ratio-track"><div class="ratio-fill" style="width:79%">22.6×</div></div><div class="ratio-amt">$36.9M adjacent<br>$1.6M direct</div></div>
      <div class="ratio-row"><div class="ratio-name">DSpace</div><div class="ratio-track"><div class="ratio-fill" style="width:77%">22.2×</div></div><div class="ratio-amt">$16.1M adjacent<br>$724K direct</div></div>
      <div class="ratio-row"><div class="ratio-name">Biodiversity Heritage Library</div><div class="ratio-track"><div class="ratio-fill" style="width:57%">16.2×</div></div><div class="ratio-amt">$6.0M adjacent<br>$371K direct</div></div>
      <div class="ratio-row"><div class="ratio-name">OpenEdition</div><div class="ratio-track"><div class="ratio-fill" style="width:56%">15.9×</div></div><div class="ratio-amt">$4.7M adjacent<br>$297K direct</div></div>
      </div>
      <div class="caveat">Ratio shown only for OIs with both direct and adjacent funding. Ranking is restricted to OIs carrying at least $250K in adjacent funding and the top six are shown. Without that floor, a large ratio resting on a small adjacent total would top the chart. The adjacent figure depends on the classifier (F1 ≈ 0.93), so treat magnitudes as directional, not precise.</div>
    </div>

    <div class="leverage">
      <div class="lev-fig">
        <div class="big">$1.65</div><div class="lev-lab">Research funded</div>
        <div class="lev-one">$1</div><div class="lev-lab">Direct funding</div>
      </div>
      <div class="lev-body">
        <p>Across the ecosystem, <strong>every $1</strong> of direct funding that reaches an infrastructure sits beneath $1.65 of funded research that depends on that infrastructure. This could be interpreted in two ways:</p>
        <div class="lev-pair">
          <div><div class="lev-k">Efficiency</div><p>Modest infrastructure investment carries a much larger research enterprise</p></div>
          <div><div class="lev-k">Fragility</div><p>The wider the gap, the more output rests on support that hasn’t grown with it</p></div>
        </div>
      </div>
    </div>

    <div class="subhead"><h3>Within that thin slice of direct funding, most pays to build, not to run.</h3></div>
    <!-- HELD FOR SARAH: the Milestone 2 PDF opens this paragraph with "Of the $192M reaching infrastructure directly from our analysis,
         only 10% goes to maintaining the infrastructure it depends on. The majority funds new operations rather than building and maintaining
         a sustainable infrastructure for the long term." That contradicts cards.csv ($64M = 33% of $192M, 10% of $663M; R&D, not operations,
         is the majority). v6 wording kept for those sentences only; the rest of the paragraph follows the PDF. -->
    <p class="cut-intro">Of the $192M reaching infrastructure directly, the majority funds new development rather than sustained operation. This is not a failure of any funder’s judgement — grant proposals are designed around projects, and projects tend to build things. But project-based funding leaves ongoing operations (the part that keeps infrastructure available year after year) structurally harder to fund.</p>

    <!-- FLAG: "$64M · Of that pays to keep it running (10%)" — 10% is of $663M, not of the $192M "that" refers to. Printed as in PDF; Sarah to decide. -->
    <div class="eco eco-3">
      <div class="eco-card"><div class="n">$663M</div><div class="l">Funding tracked across the ecosystem</div><div class="s">2001–2026 · 1,065 award clusters</div></div>
      <div class="eco-card"><div class="n">$192M</div><div class="l">Reaches infrastructure directly (29%)</div><div class="s">the rest funds work that depends on it, or its adoption</div></div>
      <div class="eco-card"><div class="n">$64M</div><div class="l">Of that pays to keep it running (10%)</div><div class="s">paying for daily maintenance and costs</div></div>
    </div>

    <div class="fig">
      <div class="cut-num">Figure 4</div>
      <div class="fig-title">Distribution of direct funding to open infrastructures by category</div>
      <!-- Arcs now of $192M (was of the $176M classified): R&D 105.35 / ops 63.93 / other+unclassified 22.79 (=192.06-105.35-63.93; cards.csv) -->
      <div class="donut-wrap">
        <svg class="donut" width="200" height="200" viewBox="0 0 42 42">
          <circle cx="21" cy="21" r="15.915" fill="none" stroke="var(--border-light)" stroke-width="6"></circle>
          <circle cx="21" cy="21" r="15.915" fill="none" stroke="var(--rnd)" stroke-width="6" stroke-dasharray="54.9 45.1" stroke-dashoffset="25"></circle>
          <circle cx="21" cy="21" r="15.915" fill="none" stroke="var(--ops)" stroke-width="6" stroke-dasharray="33.3 66.7" stroke-dashoffset="-29.9"></circle>
          <circle cx="21" cy="21" r="15.915" fill="none" stroke="var(--other)" stroke-width="6" stroke-dasharray="11.8 88.2" stroke-dashoffset="-63.2"></circle>
          <text x="21" y="20" text-anchor="middle" font-size="6" font-weight="700" font-family="BW Gradual, Inter, sans-serif" fill="var(--text)">$192M</text>
          <text x="21" y="25" text-anchor="middle" font-size="2.6" font-family="Inter, sans-serif" fill="var(--text-tertiary)">DIRECT</text>
        </svg>
        <div class="donut-legend">
          <div class="dl-row"><span class="sw" style="background:var(--rnd)"></span><span class="name">Research &amp; development</span><span class="val">$105M</span><span class="desc">new capabilities</span></div>
          <div class="dl-row"><span class="sw" style="background:var(--ops)"></span><span class="name">Operations</span><span class="val">$64M</span><span class="desc">keeping it running</span></div>
          <div class="dl-row"><span class="sw" style="background:var(--other)"></span><span class="name">Other or not classified</span><span class="val">$23M</span></div>
        </div>
      </div>
    </div>
  </div>

  <!-- ============ Q2 ============ -->
  <div class="cut">
    <div class="nav-anchor" id="how-concentrated-are-the-sources"></div>
    <div class="cut-num">Question 2: How concentrated are the sources?</div>
    <h2>Research relies on open infrastructure globally. The funding that sustains infrastructure tends to come from single sources.</h2>
    <p class="cut-intro">Direct funding is concentrated by geography: most infrastructures draw their sustaining grants from one country even when they support global research. Seen two ways — by geography, and by funder — the pattern is the same, and it is not one any single organisation created or can resolve alone.</p>

    <div class="fig">
      <div class="cut-num">Figure 5</div>
      <div class="fig-title">Infrastructures supported by different funders</div>
      <div class="breadth">
      <div class="br-row"><div class="br-name">National Science Foundation (US)</div><div class="br-track"><div class="br-fill" style="width:100%"></div></div><div class="br-val">13</div></div>
      <div class="br-row"><div class="br-name">Institute of Museum and Library Services (US)</div><div class="br-track"><div class="br-fill" style="width:77%"></div></div><div class="br-val">10</div></div>
      <div class="br-row"><div class="br-name">Alfred P. Sloan Foundation</div><div class="br-track"><div class="br-fill" style="width:62%"></div></div><div class="br-val">8</div></div>
      <div class="br-row"><div class="br-name">Andrew W. Mellon Foundation</div><div class="br-track"><div class="br-fill" style="width:62%"></div></div><div class="br-val">8</div></div>
      <div class="br-row"><div class="br-name">European Commission</div><div class="br-track"><div class="br-fill" style="width:62%"></div></div><div class="br-val">8</div></div>
      </div>
      <p class="fig-note">Each bar counts the infrastructures a funder has supported directly, of the 52 that received any direct funding.</p>
    </div>

    <div class="conc-grid">
      <div class="conc-card">
        <div class="big">22</div>
        <h3>Infrastructures funded directly from a single country</h3>
        <p>Of the 34 infrastructures with more than one direct grant, 22 receive that support from one country, while the research depending on them is funded from 2.6 countries on average. Single-source funding ties an infrastructure’s continuity to one country’s budget cycles and policy priorities, however global its users.</p>
      </div>
      <div class="conc-card">
        <div class="big">13</div>
        <h3>Distinct infrastructures the National Science Foundation (US) alone has funded directly</h3>
        <p>A small number of agencies and funders underwrite much of the ecosystem: NSF appears in the direct funding of 13 different infrastructures, IMLS 10, Mellon, Sloan and EC 8 each. When one funder’s priorities shift, the effects reach many infrastructures at once, and the risk is correlated.</p>
      </div>
    </div>
    <div class="caveat">The European Commission (EC) is treated as pan-European, not as Belgium (its registered country), so EC-funded OIs are not counted as single-country. Country diversity is measured by award <em>presence</em> (≥1 grant, any amount), which restores consortial grants that carry no allocatable dollar figure. This dataset undersamples non-US funders — so true single-country concentration is, if anything, <em>lower</em> than shown.</div>

    <div class="subhead"><h3>The asymmetry up close: Award counts by country.</h3></div>
    <p class="cut-intro">Nine countries have funded research that depends on arXiv; one provided grant funds for arXiv itself. For Open Science Framework (OSF), this ratio is seven to one. The reliance is distributed across the research world; the funding that sustains the infrastructure is not.</p>
    <div class="maps">
      <div class="mapcard">
        <div class="cut-num">Figure 6</div>
        <div class="fig-title">Direct and adjacent funding (arXiv) by country</div>
        <span class="oi">arXiv</span>
        <div class="cl-row dir"><span class="cl-sym"><span style="width:22.5px;height:22.5px;background:var(--direct)"></span></span><span>United States · 27 direct</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:22.5px;height:22.5px;background:var(--adjacent)"></span></span><span>United States · 27 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:13.1px;height:13.1px;background:var(--adjacent)"></span></span><span>United Kingdom · 5 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:12.4px;height:12.4px;background:var(--adjacent)"></span></span><span>Japan · 4 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:12.4px;height:12.4px;background:var(--adjacent)"></span></span><span>Portugal · 4 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:9.2px;height:9.2px;background:var(--adjacent)"></span></span><span>France · 1 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:9.2px;height:9.2px;background:var(--adjacent)"></span></span><span>Canada · 1 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:9.2px;height:9.2px;background:var(--adjacent)"></span></span><span>Switzerland · 1 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:9.2px;height:9.2px;background:var(--adjacent)"></span></span><span>Brazil · 1 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:9.2px;height:9.2px;background:var(--adjacent)"></span></span><span>European Union (pooled) · 1 adjacent</span></div>
      </div>
      <div class="mapcard">
        <div class="cut-num">Figure 7</div>
        <div class="fig-title">Direct and adjacent funding (OSF) by country</div>
        <span class="oi">OSF</span>
        <div class="cl-row dir"><span class="cl-sym"><span style="width:13.8px;height:13.8px;background:var(--direct)"></span></span><span>United States · 6 direct</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:28.0px;height:28.0px;background:var(--adjacent)"></span></span><span>United States · 48 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:16.0px;height:16.0px;background:var(--adjacent)"></span></span><span>United Kingdom · 10 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:14.4px;height:14.4px;background:var(--adjacent)"></span></span><span>Canada · 7 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:10.5px;height:10.5px;background:var(--adjacent)"></span></span><span>Switzerland · 2 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:9.2px;height:9.2px;background:var(--adjacent)"></span></span><span>Sweden · 1 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:9.2px;height:9.2px;background:var(--adjacent)"></span></span><span>France · 1 adjacent</span></div>
        <div class="cl-row"><span class="cl-sym"><span style="width:9.2px;height:9.2px;background:var(--adjacent)"></span></span><span>Bahamas · 1 adjacent</span></div>
      </div>
    </div>
    <p class="fig-note">Symbol size is proportional to award count.</p>
    <div class="caveat">This analysis covers grant funding only. Several infrastructures shown, arXiv among them, also sustain themselves through membership programs and institutional contributions, which diversify their income across many countries. The pattern here describes the grant layer specifically: even where operating revenue is internationally distributed, the discretionary grant investment that funds new capacity and major initiatives remains concentrated in a single country.</div>

    <!-- FEDERAL -->
    <div class="cut-num" style="margin-top:44px">Single-country concentration</div>
    <h3>Where that concentration meets current risk.</h3>
    <div class="fed">
      <div class="fed-head">
        <div><div class="big">$42.1M</div><div class="fed-lab">US Federal Funds for Open Infrastructure</div></div>
        <p>Since January 2025, US federal research funding has faced sustained pressure: agency budget threats, indirect cost caps, and the near-elimination of IMLS. $42.1M in active federal grants run to open infrastructure through this period. The point is bigger than the US: infrastructure the world depends on, sustained mainly by one government, is only as durable as that government’s priorities.</p>
      </div>
      <div class="cut-num">Figure 8</div>
      <div class="fig-title">Open infrastructure reliance on US federal funding</div>
      <table class="fed-table">
        <thead><tr><th>Infrastructure</th><th>Federal funder(s)</th><th class="amt">Active grant value</th></tr></thead>
        <tbody>
          <tr><td><strong>ICPSR</strong></td><td>NSF · HHS</td><td class="amt">$18.1M</td></tr>
          <tr><td><strong>arXiv</strong></td><td>NASA · NSF</td><td class="amt">$6.4M</td></tr>
          <tr><td><strong>Dataverse</strong></td><td>NIH · HHS</td><td class="amt">$3.3M</td></tr>
          <tr><td><strong>Zenodo</strong></td><td>HHS</td><td class="amt">$2.3M</td></tr>
          <tr><td><strong>Dryad</strong></td><td>HHS</td><td class="amt">$2.2M</td></tr>
          <tr><td><strong>Galaxy</strong></td><td>NIH · HHS</td><td class="amt">$1.9M</td></tr>
          <tr><td><strong>OSF</strong></td><td>NSF</td><td class="amt">$1.5M</td></tr>
          <tr><td class="muted">+ PUDL, DMPTool</td><td></td><td class="amt muted">$0.6M</td></tr>
          <tr><td class="muted">Multi-recipient grants span several OIs</td><td></td><td class="amt muted">$5.8M</td></tr>
          <tr><td><strong>Total at risk</strong></td><td></td><td class="amt">$42.1M</td></tr>
        </tbody>
      </table>
    </div>
    <div class="caveat">Cutoff held at Jan 2025 (last edition’s threshold): the harvest thins after 2024 (78 grants in 2024 → 41 in 2025 → 5 in 2026), so a later cutoff would undercount active grants not yet captured, not grants that have ended.</div>

    <div class="door">None of these patterns were intentionally designed, and none belongs to any single organisation to resolve. Our aim with this analysis is simpler: coordination starts when funders, institutions, and infrastructure providers are looking at the same evidence.</div>
  </div>

  <!-- DATA AVAILABILITY -->
  <div class="cut" style="margin-top:44px;padding-top:30px">
    <div class="nav-anchor" id="data-and-software-availability-statement"></div>
    <div class="cut-num">Data and software availability statement</div>
    <p class="cut-intro" style="margin-bottom:10px">The grant awards dataset used for the analysis presented here is available online at <a href="https://doi.org/10.5281/zenodo.21401121?ref=investinopen.org" target="_blank" rel="noopener">https://doi.org/10.5281/zenodo.21401121</a>, together with full methods documentation and a data dictionary. The code used for processing and analysis are available online at <a href="https://github.com/investinopen/state_of_open_funding_data_processing/?ref=investinopen.org" target="_blank" rel="noopener">https://github.com/investinopen/state_of_open_funding_data_processing/</a>.</p>
    <!-- FLAG: PDF URL below differs from v6 (…/data-room/grant-funding-data-dashboard/). Jerry to confirm which resolves. -->
    <p class="cut-intro" style="margin-bottom:10px">Interactive dashboards allowing direct exploration of the data are available at <a href="https://investinopen.org/grant-funding-data-dashboard/" target="_blank" rel="noopener">https://investinopen.org/grant-funding-data-dashboard/</a>.</p>
    <p class="cut-intro" style="margin-bottom:0">Questions or concerns? Please contact us at <a href="mailto:research@investinopen.org" target="_blank" rel="noopener">research@investinopen.org</a>.</p>
    <ol class="footnotes"><li id="sooi-s1-fn1">1 <a href="https://doi.org/10.5281/zenodo.21401121?ref=investinopen.org" target="_blank" rel="noopener">https://doi.org/10.5281/zenodo.21401121</a></li></ol>
  </div>
</div>
<!--kg-card-end: html-->
<h2 id="feedback">Feedback</h2>
<!--kg-card-begin: html-->
<iframe src="https://docs.google.com/forms/d/e/1FAIpQLSe434PpzujgkCFCWTmS_OSiUTqkrlWpw_qVAUD5rHzW8RwWUQ/viewform?usp=pp_url&entry.448320746=Where+the+money+goes" width="640" height="400" frameborder="0" marginheight="0" marginwidth="0">Loading…</iframe>
<!--kg-card-end: html-->
 ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ The infrastructure of integrity: What does it take to trust a published research output? ]]></title>
        <description><![CDATA[ Research integrity is supported by a chain of interconnected infrastructure. Publishers, funders, and researchers depend on this chain every day, yet many of the critical links remain invisible unless they break. This analysis traces the infrastructure required to support research integrity in the context of increasing challenges created by generative ]]></description>
        <link>https://investinopen.org/state-of-open-infrastructure-2026/sooi-the-infrastructure-of-integrity-what-does-it-take-to-trust-a-published-research-output-2026/</link>
        <guid isPermaLink="false">6a8d659febf8fa000181757c</guid>
        <category><![CDATA[ SOOI-2026 ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Thu, 01 Oct 2026 16:24:36 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ 
<!--kg-card-begin: html-->
<!-- ============================================================
SoOI 2026 · Section 2 (The infrastructure of integrity) · v10 · CMS embed
Source text: "State of Open Infrastructure 2026 (Milestone 2)" PDF.
Paste into an HTML block/card. Self-contained & scoped: all styles
apply only inside .sooi-s2 and cannot leak into site styles.
Fonts: loads Inter from Google Fonts; BW Gradual (headings) inherits from the site.
If the site already loads these (check site <head>), delete the
<link> line to avoid a duplicate request.
Page title + subtitle are owned by the CMS template (not in this block).
ONE HTML CARD: paste this whole file (down to the closing script tag) into a single Ghost HTML card.
v10 = single card. H2s carry the site-nav anchor ids; a nav guard script fixes theme mis-scrolling.
  FLAG: nav id …bolster-a-trustworthy-scholarly-record vs heading text "…bolster trustworthy knowledge" (PDF);
  an alias anchor for the heading-text id is included. Sarah to confirm final wording.
NEW components (no S1 precedent, pending Jerry's CMS review): intro box, threat cards, stage rows,
stage pipeline, recommendation cards, closing callout, citations list.
============================================================= -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<!-- BW Gradual (headings) is loaded by the site; the embed inherits it. -->
<style>
/* ================= BRAND TOKENS =================
   Copied verbatim from sooi-s1-embed.html. Edit ONLY this block to re-theme.
   ================================================= */
.sooi-s2{--bg:transparent;--text:#000000;--text-secondary:#262626;--text-tertiary:#6f6f6f;
    --border:#e6e4df;--border-light:#f0efec;
    /* IOI brand. Blue is FILL-ONLY (2.1:1 on white as text); numbers & links are black, per site. */
    --accent:#000000;--accent-light:#d9f0fc;
    --brand-yellow:#ffde17;--brand-mint:#83fed1;--brand-blue:#69b3f2;--brand-peach:#ffbea1;
    --card-bg:#ffffff;--highlight:#fdf6e3;
    /* No red in IOI palette: risk maps to peach backgrounds with black text. */
    --risk-critical:#000000;--risk-critical-bg:#fff1e6;--risk-high:#262626;--risk-high-bg:#ffe9d6;--risk-low:#262626;--risk-low-bg:#dcfbee;
    --direct:#69b3f2;--adjacent:#9aeef7;--adoption:#b6fcdf;--unknown:#e6e4df;
    --ops:#ffbea1;--rnd:#69b3f2;--other:#e6e4df;--land:#ecebe7}
.sooi-s2 *{margin:0;padding:0;box-sizing:border-box}
.sooi-s2{font-family:'Inter',var(--site-body-font,sans-serif);color:var(--text);line-height:1.6;-webkit-font-smoothing:antialiased;max-width:1080px;margin:0 auto;padding:8px 0 40px}
.sooi-s2 .lede{font-size:16px;color:var(--text-secondary);max-width:760px;line-height:1.7}
.sooi-s2 .lede + .lede{margin-top:14px}
.sooi-s2 .cut{border-top:1px solid var(--border-light);margin-top:52px;padding-top:38px}
.sooi-s2 .cut-num{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;letter-spacing:2px;color:var(--text-tertiary);text-transform:uppercase;margin-bottom:6px}
.sooi-s2 .cut-intro{font-size:15px;color:var(--text-secondary);max-width:740px;margin-bottom:22px}
.sooi-s2 .caveat{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);background:#fff;border:1px dashed var(--border);border-radius:6px;padding:8px 12px;margin-top:14px;line-height:1.5}
.sooi-s2 .door{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--accent);margin-top:18px;display:flex;align-items:center;gap:8px}
.sooi-s2 .door::before{content:'→'}
/* spacing after bare headings: styles the following element, never the heading */
.sooi-s2 h2 + p,.sooi-s2 h2 + div,.sooi-s2 h3 + p,.sooi-s2 h3 + div{margin-top:10px}
.sooi-s2 .subhead{margin-top:44px;margin-bottom:0}
/* figure labels + notes (new, minor) */
.sooi-s2 .fig{margin-top:30px}
.sooi-s2 .fig-title{font-size:15px;font-weight:600;color:var(--text);margin-bottom:12px}
.sooi-s2 .fig-note{font-size:12px;color:var(--text-tertiary);line-height:1.5;margin-top:12px;max-width:820px}
/* pull quote (new component) */
.sooi-s2 .pullquote{margin:44px 0;max-width:640px}
.sooi-s2 .pullquote .marks{display:flex;gap:6px;margin-bottom:14px}
.sooi-s2 .pullquote .marks span{display:block;height:10px;border-radius:5px}
.sooi-s2 .pullquote .marks .m1{width:32px;background:#000}
.sooi-s2 .pullquote .marks .m2{width:18px;background:var(--brand-yellow)}
.sooi-s2 .pullquote .marks .m3{width:10px;background:var(--adjacent)}
.sooi-s2 .pullquote p{font-size:22px;font-weight:700;line-height:1.3;color:var(--text)}
/* ---- defensive reset: site link styles ---- */
.sooi-s2 a{color:var(--text) !important;font-weight:inherit !important;background:transparent !important;border:0 !important;box-shadow:none !important;
  text-decoration:underline !important;text-decoration-color:var(--brand-yellow) !important;text-decoration-thickness:2px !important;text-underline-offset:3px;overflow-wrap:anywhere}
.sooi-s2 a:hover{text-decoration-color:var(--text) !important}
.sooi-s2 sup{font-size:.7em;line-height:0;vertical-align:super}
.sooi-s2 sup a{text-decoration:none !important}
.sooi-s2 .footnotes{list-style:none !important;margin-top:28px !important;border-top:1px solid var(--border-light) !important;padding-top:12px !important;font-size:12px !important;color:var(--text-tertiary) !important}
.sooi-s2 .footnotes li{margin-bottom:4px !important}
/* ---- defensive reset: site list styles (ol/ul/li) bleed into references & lists ---- */
.sooi-s2 ol,.sooi-s2 ul{list-style:none !important;margin:0 !important;padding:0 !important;background:transparent !important;border:0 !important;box-shadow:none !important;counter-reset:none !important}
.sooi-s2 li{list-style:none !important;margin:0 !important;padding:0 !important;background:transparent !important;border:0 !important;box-shadow:none !important;text-indent:0 !important;font-size:inherit !important;line-height:inherit !important;color:inherit !important}
.sooi-s2 li::marker{content:none !important}
.sooi-s2 li::before,.sooi-s2 li::after{content:none !important;display:none !important}
/* intro box — IOI Black (new) */
.sooi-s2 .threats,.sooi-s2 .stages{margin-top:6px !important}
.sooi-s2 .intro-box{background:#000;color:#fff;border-radius:8px;padding:28px 32px 28px 30px;font-size:17px;line-height:1.65;max-width:820px;margin:0 0 8px auto;border-left:8px solid var(--brand-yellow)}
/* threat cards (new) */
.sooi-s2 .threats{display:grid;grid-template-columns:1fr 1fr;gap:28px 40px;margin-top:22px}
.sooi-s2 .threat{background:var(--risk-critical-bg);border:1px solid var(--brand-peach);border-top:6px solid #000;border-radius:10px;padding:22px 24px}
.sooi-s2 .threat h3{font-size:18px;font-weight:600;line-height:1.3;margin-bottom:8px}
.sooi-s2 .threat p{font-size:14px;color:var(--text-secondary);line-height:1.55}
.sooi-s2 .threats{gap:18px}
/* stage rows (new) */
.sooi-s2 .stages{margin-top:22px}
.sooi-s2 .stage{display:grid;grid-template-columns:190px 230px 1fr;gap:16px;border-top:2px solid #000;padding:20px 0}
.sooi-s2 .stage .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:44px;font-weight:700;color:var(--text);line-height:1}
.sooi-s2 .stage h3{font-size:18px;font-weight:600;margin:14px 0 4px}
.sooi-s2 .stage .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .stage .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
.sooi-s2 .chip{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;font-weight:600;background:var(--accent-light);color:var(--accent);padding:2px 8px;border-radius:3px}
.sooi-s2 .stage .cell{border-radius:8px;padding:14px 16px}
.sooi-s2 .stage .cell.r{background:var(--risk-critical-bg);border-left:4px solid var(--brand-peach)}
.sooi-s2 .stage .cell.i{background:var(--risk-low-bg);border-left:4px solid var(--brand-mint)}
.sooi-s2 .stage .k{font-size:10px;letter-spacing:1.5px;text-transform:uppercase;font-weight:700;margin-bottom:4px}
.sooi-s2 .stage .risk{font-size:14px;font-weight:600;line-height:1.45}
.sooi-s2 .stage .int{font-size:14px;color:var(--text-secondary);line-height:1.6}
/* stage pipeline (new) */
.sooi-s2 .chain{display:grid;grid-template-columns:repeat(4,1fr);border:1px solid var(--border);border-radius:10px;overflow:hidden}
.sooi-s2 .chain-step{background:var(--card-bg);padding:0 0 18px;border-right:1px solid var(--border);position:relative}
.sooi-s2 .chain-step > div{padding:0 18px}
.sooi-s2 .chain-step:not(:last-child)::after{content:'→';position:absolute;right:-11px;top:19px;width:22px;height:22px;border-radius:50%;background:#000;color:var(--brand-yellow);font-size:12px;line-height:22px;text-align:center;z-index:1}
.sooi-s2 .chain-step:last-child{border-right:0}
.sooi-s2 .chain{overflow:visible}
.sooi-s2 .chain-step:first-child{border-radius:10px 0 0 10px}
.sooi-s2 .chain-step:last-child{border-radius:0 10px 10px 0}
.sooi-s2 .chain-step .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:26px;font-weight:700;color:#000;background:var(--brand-blue);padding:12px 18px !important;margin-bottom:12px;border-radius:inherit;border-bottom-left-radius:0;border-bottom-right-radius:0}
.sooi-s2 .chain-step .name{font-size:17px;font-weight:600;margin:2px 0 4px}
.sooi-s2 .chain-step .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .chain-step .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
/* recommendations (new) */
.sooi-s2 .lead-strong{font-size:19px;font-weight:600;line-height:1.45;max-width:760px;margin-top:24px;color:var(--text)}
.sooi-s2 .lead-strong span{background:linear-gradient(transparent 62%,var(--brand-yellow) 62%)}
.sooi-s2 .recs{display:grid;grid-template-columns:repeat(3,1fr);gap:24px;margin-top:24px}
.sooi-s2 .rec{background:var(--accent-light);border-top:6px solid var(--brand-blue);border-radius:10px;padding:20px 22px}
.sooi-s2 .rec .rk{font-size:16px;font-weight:700;line-height:1.3;margin-bottom:8px}
.sooi-s2 .rec p{font-size:14px;color:var(--text-secondary);line-height:1.55}
/* closing callout — IOI Black (new) */
.sooi-s2 .closing{background:#000;color:#fff;border-radius:12px;padding:28px 32px 28px 30px;margin-top:28px;font-size:16px;line-height:1.65;border-left:8px solid var(--brand-yellow)}
/* citations (new) */
.sooi-s2 .cites{list-style:none !important;margin-top:10px !important}
.sooi-s2 .cites li{font-size:13px !important;color:var(--text-secondary) !important;line-height:1.55 !important;padding:10px 0 !important;border-bottom:1px solid var(--border-light) !important}
.sooi-s2 .cites li:last-child{border-bottom:0 !important}
/* nav anchors: invisible jump targets for the report navigation */
.sooi-s2 .nav-anchor{display:block;height:0;scroll-margin-top:90px}
.sooi-s2 [id]{scroll-margin-top:90px}

/* ---- responsive ---- */
@media (max-width: 900px){
  .sooi-s2 .threats{grid-template-columns:1fr}
  .sooi-s2 .stage{grid-template-columns:1fr;gap:12px}
  .sooi-s2 .stage h3{margin-top:8px}
  .sooi-s2 .chain{grid-template-columns:1fr 1fr}
  .sooi-s2 .chain-step::after{display:none}
  .sooi-s2 .chain-step{border-radius:0 !important}
  .sooi-s2 .chain{overflow:hidden}
  .sooi-s2 .chain-step:nth-child(2){border-right:0}
  .sooi-s2 .chain-step:nth-child(-n+2){border-bottom:1px solid var(--border)}
  .sooi-s2 .recs{grid-template-columns:1fr}
}
@media (max-width: 640px){
  .sooi-s2 .pullquote p{font-size:18px}
  .sooi-s2 .intro-box{padding:22px 20px;font-size:16px}
  .sooi-s2 .closing{padding:22px 20px}
  .sooi-s2 .lead-strong{font-size:17px}
}
@media (max-width: 420px){
  .sooi-s2 .chain{grid-template-columns:1fr}
  .sooi-s2 .chain-step{border-right:0;border-bottom:1px solid var(--border)}
  .sooi-s2 .chain-step:last-child{border-bottom:0}
}
</style>
<div class="sooi-s2">
<div class="intro-box">Research integrity is supported by a chain of interconnected infrastructure. Publishers, funders, and researchers depend on this chain every day, yet many of the critical links remain invisible unless they break. This analysis traces the infrastructure required to support research integrity in the context of increasing challenges created by generative AI. These infrastructures are more critical than ever, and many are under growing strain.</div>

  <div class="cut">
    <h2 id="generative-ai-is-prompting-a-research-integrity-crisis">Generative AI is prompting a research integrity crisis</h2>

  <div class="threats">
    <div class="threat"><h3>Preprint Flooding</h3><p>LLM-generated manuscripts submitted en masse to preprint servers are overwhelming review systems. Fabricated data, hallucinated citations, and plausible-sounding methodology can pass automated checks and cursory human screening (Singh, 2025).</p></div>
    <div class="threat"><h3>Identity Theft &amp; Ghost Authors</h3><p>Paper mills and fraudulent or low-quality journals falsely attribute authorship to real researchers to lend credibility (Grove, 2023).</p></div>
    <div class="threat"><h3>AI-Powered Paper Mills</h3><p>Organised networks now use generative AI to produce hundreds of superficially coherent papers monthly, defeating manual peer review through sheer volume and automated reviewer impersonation (Richardson et al., 2025).</p></div>
    <div class="threat"><h3>Citation Chain Corruption</h3><p>AI systems hallucinate references that appear in real papers, creating citation chains that lead to non-existent or misrepresented sources, potentially leading to large-scale pollution of the scholarly record (Zhao et al., 2026).</p></div>
  </div>

  </div>
  <div class="cut">
    <div class="nav-anchor" id="open-infrastructure-interventions-bolster-trustworthy-knowledge"></div>
    <h2 id="open-infrastructure-interventions-bolster-a-trustworthy-scholarly-record">Open Infrastructure interventions bolster trustworthy knowledge</h2>

  <div class="stages">
    <div class="stage">
      <div><div class="num">01</div><h3>Identify</h3><div class="q">Who is the researcher?</div><div class="tag"><span class="chip">ORCID</span></div></div>
      <div class="cell r"><div class="k">AI risk</div><div class="risk">AI-generated papers steal the identities of real researchers to lend credibility to fabricated or low-quality publications.</div></div>
      <div class="cell i"><div class="k">OI intervention</div><div class="int">Persistent, globally unique researcher identifiers create a trustworthy link between an individual and their work. Open identity infrastructure makes impersonation and ghost authorship detectable. An ORCID — a free, unique identifier that follows a researcher for their entire career regardless of name changes, or institutional moves — can prevent fraudulent authorship claims. Authentication via ORCID when authors submit data, manuscripts, or other outputs, provides a layer of identity validation.</div></div>
    </div>
    <div class="stage">
      <div><div class="num">02</div><h3>Affiliate</h3><div class="q">Where does the work come from?</div><div class="tag"><span class="chip">ROR</span> <span class="chip">ImpactU</span></div></div>
      <div class="cell r"><div class="k">AI risk</div><div class="risk">Fabricated affiliations allow paper-mill output to look like it came from research-intensive and prestigious institutions.</div></div>
      <div class="cell i"><div class="k">OI intervention</div><div class="int">ROR (Research Organization Registry) assigns a persistent, openly-licensed identifier to over 116,000 institutions worldwide. ROR is structurally embedded in Crossref DOI metadata, DataCite DOI metadata, and ORCID, making it much more difficult to assert false affiliations when these persistent identifiers are used in concert. Current Research Information Systems (CRIS) like ImpactU make affiliations visible by tracking verified institutional output. This permits cross-checking of affiliation claims against an institution’s actual, indexed publication record.</div></div>
    </div>
    <div class="stage">
      <div><div class="num">03</div><h3>Connect</h3><div class="q">What other outputs support this work?</div><div class="tag"><span class="chip">Dryad</span> <span class="chip">DMP Tool</span> <span class="chip">DataCite</span></div></div>
      <div class="cell r"><div class="k">AI risk</div><div class="risk">It is easier than ever to fabricate or alter datasets using generative AI tools. Falsified data can be used to support misleading, untrue, or exaggerated claims in published research.</div></div>
      <div class="cell i"><div class="k">OI intervention</div><div class="int">Data Management Plans (DMPs) enforce pre-registration of methodology before results are known. DMPTool, for example, provides a click-through wizard for creating a DMP that complies with funder requirements, making after-the-fact alterations easier to spot. Open data repositories and platforms make datasets available for validation by the research community. At Dryad, for example, submissions are self-deposited, then vetted by Dryad curators and given a citable DOI. The published dataset becomes persistently available for peer review and validation. As the primary DOI registration agency specializing in research data and software, DataCite provides persistent identifiers that link datasets to research articles and other outputs, building an interconnected bundle of evidence and analysis that can be independently validated.</div></div>
    </div>
    <div class="stage">
      <div><div class="num">04</div><h3>Propagate</h3><div class="q">Metadata flows into the scholarly record</div><div class="tag"><span class="chip">Crossref</span> <span class="chip">OpenAlex</span></div></div>
      <div class="cell r"><div class="k">AI risk</div><div class="risk">Papers (whether AI-generated or assisted) contain hallucinated citations.</div></div>
      <div class="cell i"><div class="k">OI intervention</div><div class="int">Persistent Identifiers (PIDs) such as DOIs and handles create easy, timestamped metadata about citations that AI tools could use and research integrity services can use to verify citations. Crossref’s 2026 public data file contains nearly 180 million structured, machine-readable DOI records, providing an authoritative source of truth on the published record. OpenAlex, a free, open-source index of hundreds of millions of scholarly works, provides another portal to verifying citations.</div></div>
    </div>
  </div>
  <div class="subhead"><h3>A chain of interconnected infrastructure</h3></div>
  <div class="chain">
    <div class="chain-step"><div class="num">01</div><div class="name">Identify</div><div class="q">Who is the researcher?</div><div class="tag"><span class="chip">ORCID</span></div></div>
    <div class="chain-step"><div class="num">02</div><div class="name">Affiliate</div><div class="q">Where does the work come from?</div><div class="tag"><span class="chip">ROR</span> <span class="chip">ImpactU</span></div></div>
    <div class="chain-step"><div class="num">03</div><div class="name">Connect</div><div class="q">What other outputs support this work?</div><div class="tag"><span class="chip">Dryad</span> <span class="chip">DMP Tool</span> <span class="chip">DataCite</span></div></div>
    <div class="chain-step"><div class="num">04</div><div class="name">Propagate</div><div class="q">Metadata flows into the scholarly record</div><div class="tag"><span class="chip">Crossref</span> <span class="chip">OpenAlex</span></div></div>
  </div>

  </div>
  <div class="cut">
    <h2 id="what-needs-to-happen">What needs to happen</h2>

  <p class="cut-intro">Generative AI lowers the cost of producing poor-quality and fraudulent research by orders of magnitude. Research integrity, trust in science, and the foundations of how we communicate knowledge are at risk. As this analysis shows, we already have the infrastructure we need to face this risk — but only if it’s adequately funded, adopted, and maintained. Free to use does not mean free to run.</p>
  <p class="lead-strong"><span>Funders, institutions, and libraries must sustain tools that help to ensure research integrity. Sustained investment ensures the shared, open foundations that the entire research ecosystem depends on.</span></p>
  <div class="recs">
    <div class="rec"><div class="rk">Build PIDs into policy.</div><p>Top-down requirements from public and private funders can help to build adoption. Mandate ORCID iDs for PIs and co-investigators, ROR IDs for all named institutions, and DOIs for funded datasets and outputs.</p></div>
    <div class="rec"><div class="rk">Fund the infrastructure directly, not just the research it supports.</div><p>Infrastructures like ORCID, ROR, DataCite, Crossref, and Dryad are largely nonprofit, community governed, and chronically underfunded relative to how much the research ecosystem depends on them. Fund institutional memberships rather than passing off costs to researchers to absorb individually.</p></div>
    <div class="rec"><div class="rk">Treat open infrastructure maintenance as a budget line, not a one-time subscription.</div><p>Sustained, multi-year commitments allow open infrastructure to plan capacity to keep pace with AI-driven changes.</p></div>
  </div>
  <div class="closing">Scholarly communications relies on shared open infrastructure to provide critical integrity functions. This infrastructure works because it’s shared, which means its cost has to be shared too. Sustained, coordinated investment from funders, institutions, and publishers is what keeps identity, affiliation, data, and citation infrastructure ahead of AI-driven risks that impact the entire knowledge ecosystem.</div>

  </div>
  <div class="cut" style="margin-top:44px;padding-top:30px">
    <h2 id="works-cited">Works Cited</h2>

  <!-- URLs for Grove and Singh were re-joined across PDF line breaks (hyphens restored). Click-test before publish. -->
  <ol class="cites">
    <li>Grove, Jack. (2023, February 2). Identity theft victims back legal action against journals. Times Higher Education (THE). <a href="https://www.timeshighereducation.com/news/identity-theft-victims-back-legal-action-against-journals?ref=investinopen.org" target="_blank" rel="noopener">https://www.timeshighereducation.com/news/identity-theft-victims-back-legal-action-against-journals</a></li>
    <li>Richardson, Reese A. K., Hong, Spencer S., Byrne, Jennifer A., Stoeger, Thomas, &amp; Amaral, Luís A. Nunes. (2025, August 12). The entities enabling scientific fraud at scale are large, resilient, and growing rapidly. Proceedings of the National Academy of Sciences (PNAS). <a href="https://pubmed.ncbi.nlm.nih.gov/40758886/?ref=investinopen.org" target="_blank" rel="noopener">https://pubmed.ncbi.nlm.nih.gov/40758886/</a></li>
    <li>Singh, Ranjit. (2025, October 30). On arXiv, an Influx of AI Slop Pits Surface Against Substance. Data &amp; Society. <a href="https://datasociety.net/research-library/on-arxiv-an-influx-of-ai-slop-pits-surface-against-substance/?ref=investinopen.org" target="_blank" rel="noopener">https://datasociety.net/research-library/on-arxiv-an-influx-of-ai-slop-pits-surface-against-substance/</a></li>
    <li>Zhao, Zhenyue, Wang, Yihe, Stuart, Toby, De Vaan, Mathijs, Ginsparg, Paul, &amp; Yin, Yian. (2026, May 8). LLM hallucinations in the wild: Large-scale evidence from non-existent citations. arXiv. <a href="https://arxiv.org/pdf/2605.07723?ref=investinopen.org" target="_blank" rel="noopener">https://arxiv.org/pdf/2605.07723</a></li>
  </ol>

  </div>
</div>
<script>
/* SoOI S2 · in-page navigation guard (same as S3 v9).
   Handles clicks on links whose #anchor points INTO this embed, so theme smooth-scroll
   scripts can't mis-scroll headings inside the HTML card. Other links are left alone. */
(function(){
  if (window.__sooiS2Nav) return; window.__sooiS2Nav = true;
  var ROOT = '.sooi-s2';
  function target(hash){
    if (!hash || hash.length < 2) return null;
    var id; try { id = decodeURIComponent(hash.slice(1)); } catch(e) { id = hash.slice(1); }
    var el = document.getElementById(id);
    return (el && el.closest && el.closest(ROOT)) ? el : null;
  }
  function go(el, smooth){
    try { el.scrollIntoView({ behavior: smooth ? 'smooth' : 'auto', block: 'start' }); }
    catch(e) { el.scrollIntoView(true); }
  }
  window.addEventListener('click', function(e){
    var a = e.target && e.target.closest ? e.target.closest('a[href*="#"]') : null;
    if (!a || a.host !== location.host || a.pathname !== location.pathname) return;
    var el = target(a.hash); if (!el) return;
    e.preventDefault(); e.stopImmediatePropagation();
    go(el, true);
    if (history.pushState) history.pushState(null, '', a.hash);
  }, true);
  function onLoad(){ var el = target(location.hash); if (el) setTimeout(function(){ go(el, false); }, 60); }
  if (document.readyState === 'complete') onLoad(); else window.addEventListener('load', onLoad);
})();
</script>
<!--kg-card-end: html-->
<h2 id="feedback">Feedback </h2>
<!--kg-card-begin: html-->
<iframe src="https://docs.google.com/forms/d/e/1FAIpQLSe434PpzujgkCFCWTmS_OSiUTqkrlWpw_qVAUD5rHzW8RwWUQ/viewform?usp=pp_url&entry.448320746=The+infrastructure+of+integrity:+What+does+it+take+to+trust+a+published+research+output?" width="640" height="400" frameborder="0" marginheight="0" marginwidth="0">Loading…</iframe>
<!--kg-card-end: html-->
 ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ Where the sector is heading ]]></title>
        <description><![CDATA[ The forces reshaping open infrastructure


The open infrastructure sector is being reshaped by forces that are often discussed as though they are separate — the AI investment boom, tightening public science budgets, and a growing emphasis on digital sovereignty — but that are, in practice, deeply intertwined. Below are seven signals we’ ]]></description>
        <link>https://investinopen.org/state-of-open-infrastructure-2026/sooi-where-the-sector-is-heading-2026/</link>
        <guid isPermaLink="false">6abd7548e6358500010afde3</guid>
        <category><![CDATA[ SOOI-2026 ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Thu, 01 Oct 2026 15:53:29 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ 
<!--kg-card-begin: html-->
<!-- ============================================================
SoOI 2026 · Section 3 (Where the sector is heading) · v9 · CMS embed
Source text: "State of Open Infrastructure 2026 (Milestone 2)" PDF.
Paste into an HTML block/card. Self-contained & scoped: all styles
apply only inside .sooi-s3 and cannot leak into site styles.
Fonts: loads Inter from Google Fonts; BW Gradual (headings) inherits from the site.
If the site already loads these (check site <head>), delete the
<link> line to avoid a duplicate request.
Page title + subtitle are owned by the CMS template (not in this block).
Rebuilt from the Milestone 2 PDF on sooi-s1-embed conventions. sooi-s3-embed-v1.html was not
available in this session, so class names may differ from v1 — diff before replacing.
v9 = nav guard uses scrollIntoView (v8 used window.scrollTo, which failed on themes with an inner scroller).
v8 = nav guard script (fixes theme scripts mis-scrolling in-page links into S3).
v7 = alias anchors for "What's moving" (what-s- / what's- / what’s- variants).
v6 = nav anchor #where-the-sector-is-heading (top of section).
v5 = H2 anchors: #2026-signal-scorecard, #whats-moving-and-why-it-matters-for-open-infrastructure.
v4 = list + link-weight defensive reset (references, scorecard).
NEW components (no S1 precedent, pending Jerry + Sarah review): signal scorecard (Risk/Watch/
Opportunity), signal cards with "Why we're watching" box, pull quote, references list with
footnote anchors.
============================================================= -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<!-- BW Gradual (headings) is loaded by the site; the embed inherits it. -->
<style>
/* ================= BRAND TOKENS =================
   Copied verbatim from sooi-s1-embed.html. Edit ONLY this block to re-theme.
   ================================================= */
.sooi-s3{--bg:transparent;--text:#000000;--text-secondary:#262626;--text-tertiary:#6f6f6f;
    --border:#e6e4df;--border-light:#f0efec;
    /* IOI brand. Blue is FILL-ONLY (2.1:1 on white as text); numbers & links are black, per site. */
    --accent:#000000;--accent-light:#d9f0fc;
    --brand-yellow:#ffde17;--brand-mint:#83fed1;--brand-blue:#69b3f2;--brand-peach:#ffbea1;
    --card-bg:#ffffff;--highlight:#fdf6e3;
    /* No red in IOI palette: risk maps to peach backgrounds with black text. */
    --risk-critical:#000000;--risk-critical-bg:#fff1e6;--risk-high:#262626;--risk-high-bg:#ffe9d6;--risk-low:#262626;--risk-low-bg:#dcfbee;
    --direct:#69b3f2;--adjacent:#9aeef7;--adoption:#b6fcdf;--unknown:#e6e4df;
    --ops:#ffbea1;--rnd:#69b3f2;--other:#e6e4df;--land:#ecebe7}
.sooi-s3 *{margin:0;padding:0;box-sizing:border-box}
.sooi-s3{font-family:'Inter',var(--site-body-font,sans-serif);color:var(--text);line-height:1.6;-webkit-font-smoothing:antialiased;max-width:1080px;margin:0 auto;padding:8px 0 40px}
.sooi-s3 .lede{font-size:16px;color:var(--text-secondary);max-width:760px;line-height:1.7}
.sooi-s3 .lede + .lede{margin-top:14px}
.sooi-s3 .cut{border-top:1px solid var(--border-light);margin-top:52px;padding-top:38px}
.sooi-s3 .cut-num{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;letter-spacing:2px;color:var(--text-tertiary);text-transform:uppercase;margin-bottom:6px}
.sooi-s3 .cut-intro{font-size:15px;color:var(--text-secondary);max-width:740px;margin-bottom:22px}
.sooi-s3 .caveat{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);background:#fff;border:1px dashed var(--border);border-radius:6px;padding:8px 12px;margin-top:14px;line-height:1.5}
.sooi-s3 .door{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--accent);margin-top:18px;display:flex;align-items:center;gap:8px}
.sooi-s3 .door::before{content:'→'}
/* spacing after bare headings: styles the following element, never the heading */
.sooi-s3 h2 + p,.sooi-s3 h2 + div,.sooi-s3 h3 + p,.sooi-s3 h3 + div{margin-top:10px}
.sooi-s3 .subhead{margin-top:44px;margin-bottom:0}
/* figure labels + notes (new, minor) */
.sooi-s3 .fig{margin-top:30px}
.sooi-s3 .fig-title{font-size:15px;font-weight:600;color:var(--text);margin-bottom:12px}
.sooi-s3 .fig-note{font-size:12px;color:var(--text-tertiary);line-height:1.5;margin-top:12px;max-width:820px}
/* pull quote (new component) */
.sooi-s3 .pullquote{margin:44px 0;max-width:640px}
.sooi-s3 .pullquote .marks{display:flex;gap:6px;margin-bottom:14px}
.sooi-s3 .pullquote .marks span{display:block;height:10px;border-radius:5px}
.sooi-s3 .pullquote .marks .m1{width:32px;background:#000}
.sooi-s3 .pullquote .marks .m2{width:18px;background:var(--brand-yellow)}
.sooi-s3 .pullquote .marks .m3{width:10px;background:var(--adjacent)}
.sooi-s3 .pullquote p{font-size:22px;font-weight:700;line-height:1.3;color:var(--text)}
/* ---- defensive reset: site link styles ---- */
.sooi-s3 a{color:var(--text) !important;font-weight:inherit !important;background:transparent !important;border:0 !important;box-shadow:none !important;
  text-decoration:underline !important;text-decoration-color:var(--brand-yellow) !important;text-decoration-thickness:2px !important;text-underline-offset:3px;overflow-wrap:anywhere}
.sooi-s3 a:hover{text-decoration-color:var(--text) !important}
.sooi-s3 sup{font-size:.7em;line-height:0;vertical-align:super}
.sooi-s3 sup a{text-decoration:none !important}
.sooi-s3 .footnotes{list-style:none !important;margin-top:28px !important;border-top:1px solid var(--border-light) !important;padding-top:12px !important;font-size:12px !important;color:var(--text-tertiary) !important}
.sooi-s3 .footnotes li{margin-bottom:4px !important}
/* ---- defensive reset: site list styles (ol/ul/li) bleed into references & lists ---- */
.sooi-s3 ol,.sooi-s3 ul{list-style:none !important;margin:0 !important;padding:0 !important;background:transparent !important;border:0 !important;box-shadow:none !important;counter-reset:none !important}
.sooi-s3 li{list-style:none !important;margin:0 !important;padding:0 !important;background:transparent !important;border:0 !important;box-shadow:none !important;text-indent:0 !important;font-size:inherit !important;line-height:inherit !important;color:inherit !important}
.sooi-s3 li::marker{content:none !important}
.sooi-s3 li::before,.sooi-s3 li::after{content:none !important;display:none !important}
/* signal scorecard (new) */
.sooi-s3 .scorecard{border:1px solid var(--border);border-radius:12px;overflow:hidden;margin-top:16px}
.sooi-s3 .sc-head{padding:18px 24px;border-bottom:1px solid var(--border);background:var(--card-bg)}
.sooi-s3 .sc-sub{font-size:14px;color:var(--text-secondary)}
/* anchor targets: non-visual, keeps H2s clear of a sticky site header when jumped to */
.sooi-s3 h2[id]{scroll-margin-top:90px}
.sooi-s3 [id]{scroll-margin-top:90px}
.sooi-s3 .nav-anchor{display:block;height:0;scroll-margin-top:90px}
.sooi-s3 .sc-cols{display:grid;grid-template-columns:repeat(3,1fr)}
.sooi-s3 .sc-col{padding:20px 22px}
.sooi-s3 .sc-col.risk{background:var(--risk-critical-bg)}
.sooi-s3 .sc-col.watch{background:var(--accent-light)}
.sooi-s3 .sc-col.opp{background:var(--risk-low-bg)}
.sooi-s3 .sc-count{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:44px;font-weight:700;line-height:1;color:var(--text)}
.sooi-s3 .sc-lab{font-size:11px;letter-spacing:2px;text-transform:uppercase;font-weight:600;margin:6px 0 12px;color:var(--text)}
.sooi-s3 .sc-list{list-style:none !important}
.sooi-s3 .sc-list li{font-size:14px !important;line-height:1.4 !important;padding:10px 0 !important;border-top:1px solid rgba(0,0,0,.12) !important}
.sooi-s3 .sc-list a{text-decoration-color:rgba(0,0,0,.25) !important}
/* signal cards (new) */
.sooi-s3 .signals{margin-top:18px}
.sooi-s3 .signal{display:grid;grid-template-columns:240px 1fr;gap:36px;border-top:1px solid var(--border);padding:30px 0;scroll-margin-top:90px}
.sooi-s3 .pill{display:inline-block;font-size:10px;letter-spacing:1.5px;text-transform:uppercase;font-weight:700;padding:3px 10px;border-radius:4px;color:#000}
.sooi-s3 .pill.risk{background:var(--brand-peach)}
.sooi-s3 .pill.watch{background:var(--adjacent)}
.sooi-s3 .pill.opp{background:var(--brand-mint)}
.sooi-s3 .signal h3{font-size:19px;font-weight:600;line-height:1.3;margin-top:12px}
.sooi-s3 .signal .body > p{font-size:14px;color:var(--text-secondary);line-height:1.65}
.sooi-s3 .why{background:var(--highlight);border-radius:8px;padding:16px 20px;margin-top:16px}
.sooi-s3 .why .k{font-size:10px;letter-spacing:1.5px;text-transform:uppercase;font-weight:700;margin-bottom:4px}
.sooi-s3 .why p{font-size:14px;color:var(--text);line-height:1.6}
/* references (new) */
.sooi-s3 .refs{list-style:none !important;margin-top:10px !important}
.sooi-s3 .refs li{font-size:13px !important;color:var(--text-secondary) !important;line-height:1.5 !important;padding:6px 0 !important;display:grid !important;grid-template-columns:24px 1fr !important;scroll-margin-top:90px !important}

/* ---- responsive ---- */
@media (max-width: 900px){
  .sooi-s3 .signal{grid-template-columns:1fr;gap:14px}
  .sooi-s3 .sc-cols{grid-template-columns:1fr}
}
@media (max-width: 640px){
  .sooi-s3 .pullquote p{font-size:18px}
  .sooi-s3 .sc-count{font-size:36px}
}
@media (max-width: 420px){
  .sooi-s3 .sc-head,.sooi-s3 .sc-col{padding:16px}
}
</style>
<div class="sooi-s3">
<div class="nav-anchor" id="where-the-sector-is-heading"></div>
  <h2>The forces reshaping open infrastructure</h2>
  <p class="lede">The open infrastructure sector is being reshaped by forces that are often discussed as though they are separate — the AI investment boom, tightening public science budgets, and a growing emphasis on digital sovereignty — but that are, in practice, deeply intertwined. Below are seven signals we’re tracking as early indicators of where the sector may be headed over the next few years. Some point to critical risks as philanthropic and public funders redirect resources toward AI even as the maintenance costs of existing infrastructure remain unaddressed. Others point to openings for collective action, from national-level investment decisions to policymakers rethinking how infrastructure, publishing, and digital sovereignty should work in an AI-mediated research environment.</p>

  <div class="pullquote"><div class="marks"><span class="m1"></span><span class="m2"></span><span class="m3"></span></div><p>Taken together, these signals demonstrate a clear need to invest in maintenance, coordination, and expansion of open infrastructure as a shared foundation for research.</p></div>

  <div class="cut-num">At a glance</div>
  <h2 id="2026-signal-scorecard">2026 signal scorecard</h2>
  <p class="sc-sub">Headline indicators for the open infrastructure landscape heading into 2026–2027</p>
  <!-- Print page numbers replaced with in-page anchor links to each signal. -->
  <div class="scorecard">
    <div class="sc-cols">
      <div class="sc-col risk"><div class="sc-count">2</div><div class="sc-lab">Risk signals</div>
        <ul class="sc-list">
          <li><a href="#sooi-s3-sig1">Funders exit the open infrastructure space</a></li>
          <li><a href="#sooi-s3-sig2">AI decimates Tailwind’s business model</a></li>
        </ul>
      </div>
      <div class="sc-col watch"><div class="sc-count">3</div><div class="sc-lab">Watch signals</div>
        <ul class="sc-list">
          <li><a href="#sooi-s3-sig3">European Commission announces the creation of the EDIC Digital Commons</a></li>
          <li><a href="#sooi-s3-sig4">COS streamlines OSF</a></li>
          <li><a href="#sooi-s3-sig5">PLOS report proposes moving beyond the article as the unit of value in publishing</a></li>
        </ul>
      </div>
      <div class="sc-col opp"><div class="sc-count">2</div><div class="sc-lab">Opportunity signals</div>
        <ul class="sc-list">
          <li><a href="#sooi-s3-sig6">Coalition of funders launches HumanityAI</a></li>
          <li><a href="#sooi-s3-sig7">Dutch government invests in training for open science infrastructure sustainability</a></li>
        </ul>
      </div>
    </div>
  </div>

  <div class="cut">
    <!-- Alias anchors: the apostrophe in "What's" slugs differently across tools; all variants land here. -->
    <div class="nav-anchor" id="what-s-moving-and-why-it-matters-for-open-infrastructure"></div>
    <div class="nav-anchor" id="what's-moving-and-why-it-matters-for-open-infrastructure"></div>
    <div class="nav-anchor" id="what’s-moving-and-why-it-matters-for-open-infrastructure"></div>
    <div class="cut-num">Signals in detail</div>
    <h2 id="whats-moving-and-why-it-matters-for-open-infrastructure">What's moving and why it matters for open infrastructure</h2>
    <div class="signals">
    <div class="signal" id="sooi-s3-sig1">
      <div><span class="pill risk">Risk</span><h3>Funders exit the open infrastructure space</h3></div>
      <div class="body"><p>The Navigation Fund quietly closed its open science program. Astera discontinued its Open Science Fellowship<sup><a href="#sooi-s3-ref1">1</a></sup> and, in February 2026, sharpened its focus around intelligence and AI-enabled life sciences, pulling back from what had been a more expansive open science program. The Chan Zuckerberg Initiative (CZI), which had been one of the more prominent funders in the open science and research software space, laid off roughly 70 employees at the start of this year as it restructured to go “all in on AI-powered biology” through its Biohub program.<sup><a href="#sooi-s3-ref2">2</a></sup> Other funders like Omidyar<sup><a href="#sooi-s3-ref3">3</a></sup> and McGovern who had been meaningfully funding data infrastructure and responsible technology, including increasing direct engagement with the open infrastructure space, have also shifted priorities toward AI governance and civic infrastructure in ways that undermine conversations about the maintenance and operational costs of the existing ecosystem.<sup><a href="#sooi-s3-ref4">4</a></sup></p>
        <div class="why"><div class="k">Why we’re watching</div><p>The reduction in available funding sends signals that open science is no longer valuable enough to support monetarily. This philanthropic reshuffling is happening at the same time as US federal science funding cuts, leaving an ever-narrowing pool of funders responsible for critical infrastructure.</p></div>
      </div>
    </div>
    <div class="signal" id="sooi-s3-sig2">
      <div><span class="pill risk">Risk</span><h3>AI decimates Tailwind’s business model</h3></div>
      <div class="body"><p>The use of AI tools and agents led to an 80 percent drop in revenue for the open source web tool Tailwind. Even as the framework itself became more popular than ever, a precipitous drop in direct traffic meant developers no longer discovered the commercial plans that sustained the business.<sup><a href="#sooi-s3-ref5">5</a></sup></p>
        <div class="why"><div class="k">Why we’re watching</div><p>An infrastructure can be more widely used than ever and simultaneously more vulnerable to collapse. AI and other forces have contributed to skyrocketing traffic (and associated costs), while disintermediating users from content creators, often eroding certain monetization models. Funders, including companies that benefit directly from open infrastructure their models rely on, could move from ad hoc sponsorship toward proactive, sustained support for the infrastructure their own products depend on.</p></div>
      </div>
    </div>
    <div class="pullquote"><div class="marks"><span class="m1"></span><span class="m2"></span><span class="m3"></span></div><p>An infrastructure can be more widely used than ever and simultaneously more vulnerable to collapse.</p></div>
    <div class="signal" id="sooi-s3-sig3">
      <div><span class="pill watch">Watch</span><h3>European Commission announces the creation of the EDIC Digital Commons</h3></div>
      <div class="body"><p>The European Digital Infrastructure Consortium (EDIC) provides a framework to develop an interoperable, EU-based digital commons grounded in the public interest.<sup><a href="#sooi-s3-ref6">6</a></sup> It will encourage public-private partnerships to develop alternatives in key infrastructure areas such as AI and cybersecurity.</p>
        <div class="why"><div class="k">Why we’re watching</div><p>“Digital sovereignty” is no longer just a value, but a procurement and policy lever that could reshape which infrastructures get public legitimacy and funds in Europe. It sets a powerful precedent that funders and consortia could point to when arguing for large scale, sovereignty-aligned financing of research infrastructure. This move also illustrates increasing global mistrust of US-based tech and risks for US-based infrastructure providers, showing real consequences of US government and tech firms’ policies and behaviours. We are watching to see how digital sovereignty can manifest in regions that lack funding and capacity to fully disengage with US-based tech giants.<sup><a href="#sooi-s3-ref7">7</a></sup></p></div>
      </div>
    </div>
    <div class="signal" id="sooi-s3-sig4">
      <div><span class="pill watch">Watch</span><h3>COS streamlines OSF</h3></div>
      <div class="body"><p>The Center for Open Science (COS) is streamlining the Open Science Framework (OSF), the flagship project-management/collaboration platform it has developed and run since 2012. Rather than trying to be an all-in-one home for study planning, file storage, collaboration, and archiving, COS is narrowing OSF to what it calls its “unique strengths” — preregistration, linking of research outputs, and sharing preprints — while dealing with the reality of an austere funding environment.</p>
        <div class="why"><div class="k">Why we’re watching</div><p>In their rationale for narrowing OSF services, COS explicitly cites the ability to “lean on our open infrastructure colleagues and partners to fill use cases that OSF no longer supports.”<sup><a href="#sooi-s3-ref8">8</a></sup> COS’s work to proactively focus OSF’s future development is coupled with its encouragement of its users to embrace other open infrastructures for parts of lifecycle management that OSF no longer fulfils — displaying a clear sense of ecosystem responsibility and reciprocity. This decision bears resonance with Jisc’s decision to formally sunset IRUS, its institutional repository usage metrics service, in April 2026. Jisc’s Head of Product, John Kaye, attributed the decision to an evolving ecosystem and encouraged their former users to embrace a robust open alternative from OpenAIRE.<sup><a href="#sooi-s3-ref9">9</a></sup> Examples like these show how organizations are willingly giving up parts of their portfolio so they can focus on their unique contributions and acting in support of others. As open infrastructures look for sustainable solutions in a time of acute austerity, funders can encourage and directly support thoughtful cooperation.</p></div>
      </div>
    </div>
    <div class="signal" id="sooi-s3-sig5">
      <div><span class="pill watch">Watch</span><h3>PLOS report proposes moving beyond the article as the unit of value in publishing</h3></div>
      <div class="body"><p>After 18 months of independent economic analysis, multistakeholder convenings, and design research with roughly 650 researchers, PLOS published “Redefining Publishing: Practical pathways to open science,” arguing that the concepts of ‘article as unit of value’ and ‘APC as funding mechanism’ are increasingly out of step with how research actually happens.<sup><a href="#sooi-s3-ref10">10</a></sup> The report proposes a “knowledge stack”: a structured, machine-readable layer that links articles to the data, code, methods, and materials underpinning them, crediting contributors and making distributed outputs legible as a coherent whole, without requiring those outputs to move from where they already live.</p>
        <div class="why"><div class="k">Why we’re watching</div><p>Open infrastructure funders and maintainers have long argued for reuse as the end goal of openness. The PLOS report presents the case for open infrastructure as a facilitator of reuse, and illustrates the risk that, without it, the value of open science gets captured by vertically integrated commercial platforms instead. The report emphasizes the importance of coupling infrastructure improvements with a move away from the article processing charge (APC). These are collective action challenges that no single organization or sector can solve alone. Funders and institutions, in collaboration with publishers, can push for assessment reform, and the investment in the connective infrastructure this model depends on. The report explicitly highlights PLOS’ own continuing its investment in shared infrastructure like the Janeway platform.</p></div>
      </div>
    </div>
    <div class="signal" id="sooi-s3-sig6">
      <div><span class="pill opp">Opportunity</span><h3>Coalition of funders launches HumanityAI</h3></div>
      <div class="body"><p>HumanityAI, a coalition of philanthropic funders from across numerous sectors, has pledged US$500 million over five years to support AI designed in the public interest.<sup><a href="#sooi-s3-ref11">11</a></sup> Its members include the Doris Duke Foundation, Ford Foundation, Lumina Foundation, Kapor Foundation, John D. and Catherine T. MacArthur Foundation, Mellon Foundation, Mozilla Foundation, Omidyar Network, David and Lucile Packard Foundation, and Siegel Family Endowment. In spring 2026, the coalition announced its first cohort of grantees, whose projects will advance AI governance, build cross-sector partnerships, and support community-driven research.</p>
        <div class="why"><div class="k">Why we’re watching</div><p>HumanityAI represents one of the largest coordinated efforts to counterbalance corporate influence over AI’s trajectory with funding aimed at making sure people have a stake in the future of artificial intelligence. This kind of cross-sector alignment is rare in philanthropy, and its emergence here suggests funders see AI’s impact as too large and too cross-cutting for any single foundation’s portfolio to address alone. A coalition of this size and diversity can shape norms, set agendas, and provide opportunities for open infrastructures. Several of the initiative’s priority areas overlap with concerns central to open infrastructure work, particularly around who controls and benefits from the systems underpinning research and knowledge production. Connecting AI designed in the public interest with open science is a promising avenue for future support for open infrastructure, one that could help offset the evaporation of other, previously reliable funding sources.</p></div>
      </div>
    </div>
    <div class="signal" id="sooi-s3-sig7">
      <div><span class="pill opp">Opportunity</span><h3>Dutch government invests in training for open science infrastructure sustainability</h3></div>
      <div class="body"><p>Open Science NL’s 2026–27 work program includes funding to develop and deliver “a sustainability training for those responsible for open science infrastructure in all lifecycle stages.”<sup><a href="#sooi-s3-ref12">12</a></sup> The work program identifies a critical skills gap for infrastructure maintainers: designing and implementing business models that can sustain these critical resources and ensure their continued availability to the research community.</p>
        <div class="why"><div class="k">Why we’re watching</div><p>A national government-backed program is treating infrastructure sustainability skills as a systemic gap worth funding directly, rather than leaving individual maintainers to figure out business models on their own. The work program explicitly acknowledges that technical infrastructure work and sustainability planning are distinct skill sets, and that the latter has been under-supported. Sustainability challenges have been brought into sharper focus by recent geopolitical crises that reveal the risks of depending on a single government or funder. While many funders require sustainability plans for infrastructure projects, the Dutch approach aims also to build the skills required for maintainers to craft such documented plans. Other countries and funders could look to this national-level action as a model. Rather than expecting each project or institution to develop this expertise independently, what would it look like to build in training and support for exploration of different business models, revenue diversification, and financial management, e.g., at the outset of a project rather than when it is in crisis?</p></div>
      </div>
    </div>
    </div>
  </div>

  <div class="cut" style="margin-top:44px;padding-top:30px">
    <div class="cut-num">References</div>
    <!-- Refs 1, 3, 7, 9, 11 were re-joined across PDF line breaks (hyphens restored). Click-test before publish. -->
    <ol class="refs">
    <li id="sooi-s3-ref1"><span>1</span><span><a href="https://www.openresearchbeacon.org/project/astera-institute-open-science-fellowship/?ref=investinopen.org" target="_blank" rel="noopener">https://www.openresearchbeacon.org/project/astera-institute-open-science-fellowship/</a></span></li>
    <li id="sooi-s3-ref2"><span>2</span><span><a href="https://biohub.org/blog/founders-update-ai-powered-biology/?ref=investinopen.org" target="_blank" rel="noopener">https://biohub.org/blog/founders-update-ai-powered-biology/</a></span></li>
    <li id="sooi-s3-ref3"><span>3</span><span><a href="https://omidyar.com/update/omidyar-networks-strategy-evolution-bending-the-arc-of-the-digital-revolution-toward-shared-power-prosperity-and-possibility/?ref=investinopen.org" target="_blank" rel="noopener">https://omidyar.com/update/omidyar-networks-strategy-evolution-bending-the-arc-of-the-digital-revolution-toward-shared-power-prosperity-and-possibility/</a></span></li>
    <li id="sooi-s3-ref4"><span>4</span><span><a href="https://www.mcgovern.org/2025-press-release/?ref=investinopen.org" target="_blank" rel="noopener">https://www.mcgovern.org/2025-press-release/</a></span></li>
    <li id="sooi-s3-ref5"><span>5</span><span><a href="https://finance.yahoo.com/news/tailwind-lays-off-75-4-171658591.html?ref=investinopen.org" target="_blank" rel="noopener">https://finance.yahoo.com/news/tailwind-lays-off-75-4-171658591.html</a></span></li>
    <li id="sooi-s3-ref6"><span>6</span><span><a href="https://www.sovereign.tech/press/edic-digital-commons?ref=investinopen.org" target="_blank" rel="noopener">https://www.sovereign.tech/press/edic-digital-commons</a></span></li>
    <li id="sooi-s3-ref7"><span>7</span><span><a href="https://data-landscapers.com/2026/06/16/sovereignty-dividing-line/?ref=investinopen.org" target="_blank" rel="noopener">https://data-landscapers.com/2026/06/16/sovereignty-dividing-line/</a></span></li>
    <li id="sooi-s3-ref8"><span>8</span><span><a href="https://www.cos.io/blog/osf-changes-a-note-to-users?ref=investinopen.org" target="_blank" rel="noopener">https://www.cos.io/blog/osf-changes-a-note-to-users</a></span></li>
    <li id="sooi-s3-ref9"><span>9</span><span><a href="https://investinopen.org/blog/sunsetting-for-progress-irus-jisc/" target="_blank" rel="noopener">https://investinopen.org/blog/sunsetting-for-progress-irus-jisc/</a></span></li>
    <li id="sooi-s3-ref10"><span>10</span><span><a href="https://explore.plos.org/practical-pathways-to-open-science?ref=investinopen.org" target="_blank" rel="noopener">https://explore.plos.org/practical-pathways-to-open-science</a></span></li>
    <li id="sooi-s3-ref11"><span>11</span><span><a href="https://www.macfound.org/press/press-releases/humanity-ai-commits-500-million-to-build-a-people-centered-future-for-ai?ref=investinopen.org" target="_blank" rel="noopener">https://www.macfound.org/press/press-releases/humanity-ai-commits-500-million-to-build-a-people-centered-future-for-ai</a></span></li>
    <li id="sooi-s3-ref12"><span>12</span><span><a href="https://zenodo.org/records/17579089?ref=investinopen.org" target="_blank" rel="noopener">https://zenodo.org/records/17579089</a></span></li>
    </ol>
  </div>
</div>
<script>
/* SoOI S3 · in-page navigation guard.
   Handles clicks on any link whose #anchor points INTO this embed (site nav, scorecard),
   before theme scripts can mis-scroll. Links to other pages/anchors are left alone. */
(function(){
  if (window.__sooiS3Nav) return; window.__sooiS3Nav = true;
  var ROOT = '.sooi-s3';
  function target(hash){
    if (!hash || hash.length < 2) return null;
    var id; try { id = decodeURIComponent(hash.slice(1)); } catch(e) { id = hash.slice(1); }
    var el = document.getElementById(id);
    return (el && el.closest && el.closest(ROOT)) ? el : null;
  }
  function go(el, smooth){
    /* scrollIntoView scrolls whichever container actually scrolls (window OR a theme's inner
       scroller) and honours CSS scroll-margin-top (90px) so headings clear a sticky header. */
    try { el.scrollIntoView({ behavior: smooth ? 'smooth' : 'auto', block: 'start' }); }
    catch(e) { el.scrollIntoView(true); }
  }
  window.addEventListener('click', function(e){
    var a = e.target && e.target.closest ? e.target.closest('a[href*="#"]') : null;
    if (!a || a.host !== location.host || a.pathname !== location.pathname) return;
    var el = target(a.hash); if (!el) return;
    e.preventDefault(); e.stopImmediatePropagation();
    go(el, true);
    if (history.pushState) history.pushState(null, '', a.hash);
  }, true);
  function onLoad(){ var el = target(location.hash); if (el) setTimeout(function(){ go(el, false); }, 60); }
  if (document.readyState === 'complete') onLoad(); else window.addEventListener('load', onLoad);
})();
</script>
<!--kg-card-end: html-->
<h2 id="feedback">Feedback</h2>
<!--kg-card-begin: html-->
<iframe src="https://docs.google.com/forms/d/e/1FAIpQLSe434PpzujgkCFCWTmS_OSiUTqkrlWpw_qVAUD5rHzW8RwWUQ/viewform?usp=pp_url&entry.448320746=Where+the+sector+is+heading&embedded=true" width="640" height="400" frameborder="0" marginheight="0" marginwidth="0">Loading…</iframe>
<!--kg-card-end: html-->
 ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ Foreword ]]></title>
        <description><![CDATA[ The funding disruptions that made headlines last year were real, and we have documented them carefully in this report. But the story I most want to tell is not the one that made the news.The loud disruptions – the cancelled federal grants, the agencies dismantled, the program closures that generated ]]></description>
        <link>https://investinopen.org/state-of-open-infrastructure-2026/sooi-foreword-2026/</link>
        <guid isPermaLink="false">6abd3c8f1ec33d0001a84bb4</guid>
        <category><![CDATA[ SOOI-2026 ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Thu, 01 Oct 2026 13:39:08 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ 
<!--kg-card-begin: html-->
<!-- ============================================================
SoOI 2026 · Foreword · v1 · CMS embed
Source text: "State of Open Infrastructure 2026 (Milestone 2)" PDF.
Paste into an HTML block/card. Self-contained & scoped: all styles
apply only inside .sooi-foreword and cannot leak into site styles.
Fonts: loads Inter from Google Fonts; BW Gradual (headings) inherits from the site.
If the site already loads these (check site <head>), delete the
<link> line to avoid a duplicate request.
Page title + subtitle are owned by the CMS template (not in this block).
NEW components (pending Jerry's CMS review): pull quote, yellow aside, sign-off block.
============================================================= -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<!-- BW Gradual (headings) is loaded by the site; the embed inherits it. -->
<style>
/* ================= BRAND TOKENS =================
   Copied verbatim from sooi-s1-embed.html. Edit ONLY this block to re-theme.
   ================================================= */
.sooi-foreword{--bg:transparent;--text:#000000;--text-secondary:#262626;--text-tertiary:#6f6f6f;
    --border:#e6e4df;--border-light:#f0efec;
    /* IOI brand. Blue is FILL-ONLY (2.1:1 on white as text); numbers & links are black, per site. */
    --accent:#000000;--accent-light:#d9f0fc;
    --brand-yellow:#ffde17;--brand-mint:#83fed1;--brand-blue:#69b3f2;--brand-peach:#ffbea1;
    --card-bg:#ffffff;--highlight:#fdf6e3;
    /* No red in IOI palette: risk maps to peach backgrounds with black text. */
    --risk-critical:#000000;--risk-critical-bg:#fff1e6;--risk-high:#262626;--risk-high-bg:#ffe9d6;--risk-low:#262626;--risk-low-bg:#dcfbee;
    --direct:#69b3f2;--adjacent:#9aeef7;--adoption:#b6fcdf;--unknown:#e6e4df;
    --ops:#ffbea1;--rnd:#69b3f2;--other:#e6e4df;--land:#ecebe7}
.sooi-foreword *{margin:0;padding:0;box-sizing:border-box}
.sooi-foreword{font-family:'Inter',var(--site-body-font,sans-serif);color:var(--text);line-height:1.6;-webkit-font-smoothing:antialiased;max-width:1080px;margin:0 auto;padding:8px 0 40px}
.sooi-foreword .lede{font-size:16px;color:var(--text-secondary);max-width:760px;line-height:1.7}
.sooi-foreword .lede + .lede{margin-top:14px}
.sooi-foreword .cut{border-top:1px solid var(--border-light);margin-top:52px;padding-top:38px}
.sooi-foreword .cut-num{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;letter-spacing:2px;color:var(--text-tertiary);text-transform:uppercase;margin-bottom:6px}
.sooi-foreword .cut-intro{font-size:15px;color:var(--text-secondary);max-width:740px;margin-bottom:22px}
.sooi-foreword .caveat{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);background:#fff;border:1px dashed var(--border);border-radius:6px;padding:8px 12px;margin-top:14px;line-height:1.5}
.sooi-foreword .door{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--accent);margin-top:18px;display:flex;align-items:center;gap:8px}
.sooi-foreword .door::before{content:'→'}
/* spacing after bare headings: styles the following element, never the heading */
.sooi-foreword h2 + p,.sooi-foreword h2 + div,.sooi-foreword h3 + p,.sooi-foreword h3 + div{margin-top:10px}
.sooi-foreword .subhead{margin-top:44px;margin-bottom:0}
/* figure labels + notes (new, minor) */
.sooi-foreword .fig{margin-top:30px}
.sooi-foreword .fig-title{font-size:15px;font-weight:600;color:var(--text);margin-bottom:12px}
.sooi-foreword .fig-note{font-size:12px;color:var(--text-tertiary);line-height:1.5;margin-top:12px;max-width:820px}
/* pull quote (new component) */
.sooi-foreword .pullquote{margin:44px 0;max-width:640px}
.sooi-foreword .pullquote .marks{display:flex;gap:6px;margin-bottom:14px}
.sooi-foreword .pullquote .marks span{display:block;height:10px;border-radius:5px}
.sooi-foreword .pullquote .marks .m1{width:32px;background:#000}
.sooi-foreword .pullquote .marks .m2{width:18px;background:var(--brand-yellow)}
.sooi-foreword .pullquote .marks .m3{width:10px;background:var(--adjacent)}
.sooi-foreword .pullquote p{font-size:22px;font-weight:700;line-height:1.3;color:var(--text)}
/* ---- defensive reset: site link styles ---- */
.sooi-foreword a{color:var(--text) !important;background:transparent !important;border:0 !important;box-shadow:none !important;
  text-decoration:underline !important;text-decoration-color:var(--brand-yellow) !important;text-decoration-thickness:2px !important;text-underline-offset:3px;overflow-wrap:anywhere}
.sooi-foreword a:hover{text-decoration-color:var(--text) !important}
.sooi-foreword sup{font-size:.7em;line-height:0;vertical-align:super}
.sooi-foreword sup a{text-decoration:none !important}
.sooi-foreword .footnotes{list-style:none;margin-top:28px;border-top:1px solid var(--border-light);padding-top:12px;font-size:12px;color:var(--text-tertiary)}
.sooi-foreword .footnotes li{margin-bottom:4px}
.sooi-foreword .fw-body{max-width:760px}
.sooi-foreword .fw-body p{font-size:16px;line-height:1.75;color:var(--text-secondary);margin-bottom:16px}
.sooi-foreword .fw-pair{display:grid;grid-template-columns:minmax(260px,1fr) 1.35fr;gap:36px;align-items:start;margin-top:12px}
/* yellow aside (new) — IOI Yellow fill, black text */
.sooi-foreword .aside-yellow{background:var(--brand-yellow);color:#000;border-radius:10px;padding:26px 28px;font-size:15px;line-height:1.6}
.sooi-foreword .signoff{margin-top:22px;font-size:15px;color:var(--text-secondary)}
.sooi-foreword .signoff .who{font-weight:700;color:var(--text);margin-top:10px}
.sooi-foreword .signoff .role{font-size:13px;color:var(--text-tertiary)}

/* ---- responsive ---- */
@media (max-width: 900px){
  .sooi-foreword .fw-pair{grid-template-columns:1fr}
}
@media (max-width: 640px){
  .sooi-foreword .pullquote p{font-size:18px}

}
@media (max-width: 420px){

}
</style>
<div class="sooi-foreword">
<!-- Portrait of Kaitlin Thaney: insert via CMS image block above this embed (not included). -->
  <!-- Standfirst "The funding disruptions that made headlines…" goes in the CMS subtitle field. -->
  <div class="fw-body">
    <p>The funding disruptions that made headlines last year were real, and we have documented them carefully in this report. But the story I most want to tell is not the one that made the news.The loud disruptions – the cancelled federal grants, the agencies dismantled, the program closures that generated urgent email threads and emergency convenings – those were visible. What concerns me more is what has been happening quietly alongside them. The US$5,000 or US$10,000 institutional membership that got cut as a discretionary line item, multiplied across dozens of universities making decisions that were reasonable in isolation, but without knowing what anyone else in the same consortium was doing. The program officers who built years of knowledge of this space and then moved on, taking with them the relationships and context that take years to rebuild. The in-kind institutional support that absorbs significant costs for open infrastructure while remaining invisible in any formal accounting, quietly eroding as positions go unfilled and staff take on broader portfolios. None of those things generated a press release. Together, they may matter more than the ones that did.</p>
    <p>I want this year’s report to help the field see clearly that the challenge facing open infrastructure is structural and distributed, not reducible to any one political moment or national funding crisis. We track funding to open infrastructures across dozens of funders and jurisdictions, and the patterns that concern us are showing up across contexts that have very little else in common. Funding flows to the researchers using open infrastructure far more readily than it flows to the infrastructure itself. Priorities consistently skew toward new development and away from the operational costs that keep existing systems running. Underneath all of that is an assumption, shared across funders and institutions and developers alike, that someone else is handling the baseline.</p>
    <p>That assumption is increasingly wrong, and the consequences are starting to show up in the data.</p>
  </div>
  <div class="pullquote"><div class="marks"><span class="m1"></span><span class="m2"></span><span class="m3"></span></div><p>What the data shows, most plainly, is that high citation is not the same as adequate support.</p></div>
  <div class="fw-body">
    <p>I am proud to share our team’s latest analysis with you, produced for the first time with sponsorship from our community that wants to see these numbers and stories. In particular, we thank Crossref for being the first to step up and put their money where their values are. That affirmation from the community helped us develop this report amidst a lot of noise, funding disruptions, political shifts, and the constant churn of an ecosystem that never stops moving. The analysis is grounded in the open infrastructures tracked in our Infra Finder discovery tool, which catalogs over 100 open infrastructures serving research and scholarship globally, alongside publicly available grant funding data and signals from our broader work. What follows is not a comfortable read in every respect. We have tried to be honest about what the data shows rather than what the field might prefer to hear, and some of what we see is genuinely concerning.</p>
    <p>What the data shows, most plainly, is that high citation is not the same as adequate support. The most relied-upon systems in the research ecosystem are not necessarily the best funded. Free to use does not mean zero risk. It means the risk is less visible, and often displaced onto the next grant cycle, the next institutional budget decision, the next program officer who inherits a relationship and has to rebuild context from scratch. Responsibility has been passed around the same small table for a long time, with each player making a reasonable argument for why it belongs to someone else. The data in this report help make visible what that passing of this responsibility has actually cost.</p>
  </div>
  <div class="fw-pair">
    <div class="aside-yellow">IOI is an independent organization working across the research sector, not a funder with a portfolio to protect or infrastructure with a service to sell. Through strategic consulting, ecosystem intelligence, and coordinated funding work including our community investment fund supporting infrastructure implementation projects in Latin America and Africa, we have spent years building close relationships with every kind of sector stakeholder. That span is what lets us see connections, gaps, and opportunities that are not visible from inside any single part of the network. It is also what makes this report possible, and what makes us willing to say plainly what we think the patterns mean, not just describe them.</div>
    <div class="fw-body">
      <p>Our aim with this report is to give the people making decisions about open infrastructure something more useful than another argument for why it matters. Most of the people reading this already believe it matters. What we are trying to provide is a clearer picture of where things actually stand, where the risks are concentrated, where there are genuine opportunities to strengthen the ecosystem, and what kinds of investment and coordination would most change the trajectory. Some of those opportunities are more tractable than they might appear. The funder pool for this work is far smaller than it should be, but a lot of that is habit rather than structural inevitability. The costs of keeping these systems running are far lower than what it would cost to rebuild them. The dependencies are clear. The case is there. The question is whether the field will act on it before the quiet disruptions become ones loud enough to make the news.</p>
      <div class="signoff">In appreciation,<div class="who">Kaitlin Thaney</div><div class="role">Executive Director, Invest in Open Infrastructure</div></div>
    </div>
  </div>
</div>
<!--kg-card-end: html-->
 ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ Contributors ]]></title>
        <description><![CDATA[ We use the Contributor Roles Taxonomy (CRediT) to specify collaborators’ contributions: https://credit.niso.org/



Emmy Tsanghttps://orcid.org/0000-0002-9248-1280data curation, formal analysis, investigation, methodology, validation, visualization, writing – original draft, writing – review &amp; editing
Sarah Lippincotthttps://orcid.org/0000-0002-5700-5844data curation, formal analysis, investigation, methodology, ]]></description>
        <link>https://investinopen.org/state-of-open-infrastructure-2026/sooi-contributors-2026/</link>
        <guid isPermaLink="false">6abd5920e6358500010afd89</guid>
        <category><![CDATA[ SOOI-2026 ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Thu, 01 Oct 2026 13:37:49 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ 
<!--kg-card-begin: html-->
<!-- ============================================================
SoOI 2026 · Contributors · v1 · CMS embed
Source text: "State of Open Infrastructure 2026 (Milestone 2)" PDF.
Paste into an HTML block/card. Self-contained & scoped: all styles
apply only inside .sooi-contributors and cannot leak into site styles.
Fonts: loads Inter from Google Fonts; BW Gradual (headings) inherits from the site.
If the site already loads these (check site <head>), delete the
<link> line to avoid a duplicate request.
Page title + subtitle are owned by the CMS template (not in this block).
NEW components (pending Jerry's CMS review): contributor grid.
============================================================= -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<!-- BW Gradual (headings) is loaded by the site; the embed inherits it. -->
<style>
/* ================= BRAND TOKENS =================
   Copied verbatim from sooi-s1-embed.html. Edit ONLY this block to re-theme.
   ================================================= */
.sooi-contributors{--bg:transparent;--text:#000000;--text-secondary:#262626;--text-tertiary:#6f6f6f;
    --border:#e6e4df;--border-light:#f0efec;
    /* IOI brand. Blue is FILL-ONLY (2.1:1 on white as text); numbers & links are black, per site. */
    --accent:#000000;--accent-light:#d9f0fc;
    --brand-yellow:#ffde17;--brand-mint:#83fed1;--brand-blue:#69b3f2;--brand-peach:#ffbea1;
    --card-bg:#ffffff;--highlight:#fdf6e3;
    /* No red in IOI palette: risk maps to peach backgrounds with black text. */
    --risk-critical:#000000;--risk-critical-bg:#fff1e6;--risk-high:#262626;--risk-high-bg:#ffe9d6;--risk-low:#262626;--risk-low-bg:#dcfbee;
    --direct:#69b3f2;--adjacent:#9aeef7;--adoption:#b6fcdf;--unknown:#e6e4df;
    --ops:#ffbea1;--rnd:#69b3f2;--other:#e6e4df;--land:#ecebe7}
.sooi-contributors *{margin:0;padding:0;box-sizing:border-box}
.sooi-contributors{font-family:'Inter',var(--site-body-font,sans-serif);color:var(--text);line-height:1.6;-webkit-font-smoothing:antialiased;max-width:1080px;margin:0 auto;padding:8px 0 40px}
.sooi-contributors .lede{font-size:16px;color:var(--text-secondary);max-width:760px;line-height:1.7}
.sooi-contributors .lede + .lede{margin-top:14px}
.sooi-contributors .cut{border-top:1px solid var(--border-light);margin-top:52px;padding-top:38px}
.sooi-contributors .cut-num{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;letter-spacing:2px;color:var(--text-tertiary);text-transform:uppercase;margin-bottom:6px}
.sooi-contributors .cut-intro{font-size:15px;color:var(--text-secondary);max-width:740px;margin-bottom:22px}
.sooi-contributors .caveat{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);background:#fff;border:1px dashed var(--border);border-radius:6px;padding:8px 12px;margin-top:14px;line-height:1.5}
.sooi-contributors .door{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--accent);margin-top:18px;display:flex;align-items:center;gap:8px}
.sooi-contributors .door::before{content:'→'}
/* spacing after bare headings: styles the following element, never the heading */
.sooi-contributors h2 + p,.sooi-contributors h2 + div,.sooi-contributors h3 + p,.sooi-contributors h3 + div{margin-top:10px}
.sooi-contributors .subhead{margin-top:44px;margin-bottom:0}
/* figure labels + notes (new, minor) */
.sooi-contributors .fig{margin-top:30px}
.sooi-contributors .fig-title{font-size:15px;font-weight:600;color:var(--text);margin-bottom:12px}
.sooi-contributors .fig-note{font-size:12px;color:var(--text-tertiary);line-height:1.5;margin-top:12px;max-width:820px}
/* pull quote (new component) */
.sooi-contributors .pullquote{margin:44px 0;max-width:640px}
.sooi-contributors .pullquote .marks{display:flex;gap:6px;margin-bottom:14px}
.sooi-contributors .pullquote .marks span{display:block;height:10px;border-radius:5px}
.sooi-contributors .pullquote .marks .m1{width:32px;background:#000}
.sooi-contributors .pullquote .marks .m2{width:18px;background:var(--brand-yellow)}
.sooi-contributors .pullquote .marks .m3{width:10px;background:var(--adjacent)}
.sooi-contributors .pullquote p{font-size:22px;font-weight:700;line-height:1.3;color:var(--text)}
/* ---- defensive reset: site link styles ---- */
.sooi-contributors a{color:var(--text) !important;background:transparent !important;border:0 !important;box-shadow:none !important;
  text-decoration:underline !important;text-decoration-color:var(--brand-yellow) !important;text-decoration-thickness:2px !important;text-underline-offset:3px;overflow-wrap:anywhere}
.sooi-contributors a:hover{text-decoration-color:var(--text) !important}
.sooi-contributors sup{font-size:.7em;line-height:0;vertical-align:super}
.sooi-contributors sup a{text-decoration:none !important}
.sooi-contributors .footnotes{list-style:none;margin-top:28px;border-top:1px solid var(--border-light);padding-top:12px;font-size:12px;color:var(--text-tertiary)}
.sooi-contributors .footnotes li{margin-bottom:4px}
.sooi-contributors .ct-grid{display:grid;grid-template-columns:repeat(3,1fr);gap:26px 32px;margin-top:26px}
.sooi-contributors .person .nm{font-size:15px;font-weight:700;color:var(--text)}
.sooi-contributors .person .orcid{font-size:13px;margin-top:2px}
.sooi-contributors .person .roles{font-size:13px;color:var(--text-secondary);line-height:1.5;margin-top:4px}
.sooi-contributors .ai-note{font-size:13px;color:var(--text-tertiary);margin-top:36px;border-top:1px solid var(--border-light);padding-top:14px}

/* ---- responsive ---- */
@media (max-width: 900px){
  .sooi-contributors .ct-grid{grid-template-columns:1fr 1fr}
}
@media (max-width: 640px){
  .sooi-contributors .pullquote p{font-size:18px}

}
@media (max-width: 420px){
  .sooi-contributors .ct-grid{grid-template-columns:1fr}
}
</style>
<div class="sooi-contributors">
<p class="lede">We use the Contributor Roles Taxonomy (CRediT) to specify collaborators’ contributions: <a href="https://credit.niso.org/?ref=investinopen.org" target="_blank" rel="noopener">https://credit.niso.org/</a></p>
  <div class="ct-grid">
    <div class="person"><div class="nm">Emmy Tsang</div><div class="orcid"><a href="https://orcid.org/0000-0002-9248-1280?ref=investinopen.org" target="_blank" rel="noopener">https://orcid.org/0000-0002-9248-1280</a></div><div class="roles">data curation, formal analysis, investigation, methodology, validation, visualization, writing – original draft, writing – review &amp; editing</div></div>
    <div class="person"><div class="nm">Sarah Lippincott</div><div class="orcid"><a href="https://orcid.org/0000-0002-5700-5844?ref=investinopen.org" target="_blank" rel="noopener">https://orcid.org/0000-0002-5700-5844</a></div><div class="roles">data curation, formal analysis, investigation, methodology, validation, visualization, writing – original draft, writing – review &amp; editing</div></div>
    <div class="person"><div class="nm">Katherine Skinner</div><div class="orcid"><a href="https://orcid.org/0000-0003-0139-7524?ref=investinopen.org" target="_blank" rel="noopener">https://orcid.org/0000-0003-0139-7524</a></div><div class="roles">data curation, formal analysis, investigation, methodology, supervision, writing – original draft, writing – review &amp; editing</div></div>
    <div class="person"><div class="nm">Kaitlin Thaney</div><div class="orcid"><a href="https://orcid.org/0000-0002-7217-4494?ref=investinopen.org" target="_blank" rel="noopener">https://orcid.org/0000-0002-7217-4494</a></div><div class="roles">conceptualization, funding acquisition, writing – original draft, writing – review &amp; editing</div></div>
    <div class="person"><div class="nm">Chun-Kai Huang</div><div class="orcid"><a href="https://orcid.org/0000-0002-9656-5932?ref=investinopen.org" target="_blank" rel="noopener">https://orcid.org/0000-0002-9656-5932</a></div><div class="roles">data curation, software, visualization</div></div>
    <div class="person"><div class="nm">Cameron Neylon</div><div class="orcid"><a href="https://orcid.org/0000-0002-0068-716X?ref=investinopen.org" target="_blank" rel="noopener">https://orcid.org/0000-0002-0068-716X</a></div><div class="roles">data curation, software, visualization</div></div>
    <div class="person"><div class="nm">Lauren Collister</div><div class="orcid"><a href="https://orcid.org/0000-0001-5767-8486?ref=investinopen.org" target="_blank" rel="noopener">https://orcid.org/0000-0001-5767-8486</a></div><div class="roles">writing – original draft, writing – review &amp; editing</div></div>
    <div class="person"><div class="nm">Jerry Sellanga</div><div class="orcid"><a href="https://orcid.org/0009-0006-1224-0548?ref=investinopen.org" target="_blank" rel="noopener">https://orcid.org/0009-0006-1224-0548</a></div><div class="roles">writing – review &amp; editing, production coordination</div></div>
    <div class="person"><div class="nm">Madelyn Waterbury</div><div class="roles">writing – review &amp; editing</div></div>
    <div class="person"><div class="nm">Julia Smith</div><div class="roles">visualization</div></div>
    <div class="person"><div class="nm">Juan Paz</div><div class="roles">visualization</div></div>
  </div>
  <p class="ai-note">This report was edited with assistance from AI tools and has been reviewed and verified by IOI staff.</p>
</div>
<!--kg-card-end: html-->
 ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ Sponsors ]]></title>
        <description><![CDATA[ The State of Open Infrastructure is not simply a record of where the sector stands today. It draws on IOI’s position across the ecosystem to ask questions that individual institutions and funders rarely have the vantage point to ask: what should be sustained, where investment is most needed, how ]]></description>
        <link>https://investinopen.org/state-of-open-infrastructure-2026/sooi-sponsors-2026/</link>
        <guid isPermaLink="false">6abd5976e6358500010afd91</guid>
        <category><![CDATA[ SOOI-2026 ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Thu, 01 Oct 2026 13:37:09 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ 
<!--kg-card-begin: html-->
<!-- ============================================================
SoOI 2026 · Sponsors · v2 · CMS embed
Source text: "State of Open Infrastructure 2026 (Milestone 2)" PDF.
Paste into an HTML block/card. Self-contained & scoped: all styles
apply only inside .sooi-sponsors and cannot leak into site styles.
Fonts: loads Inter from Google Fonts; BW Gradual (headings) inherits from the site.
If the site already loads these (check site <head>), delete the
<link> line to avoid a duplicate request.
Page title + subtitle are owned by the CMS template (not in this block).
NEW components (pending Jerry's CMS review): linked logo tiles.
Logos are hosted on Ghost storage (2026/09); each tile opens the sponsor site in a new tab.
============================================================= -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<!-- BW Gradual (headings) is loaded by the site; the embed inherits it. -->
<style>
/* ================= BRAND TOKENS =================
   Copied verbatim from sooi-s1-embed.html. Edit ONLY this block to re-theme.
   ================================================= */
.sooi-sponsors{--bg:transparent;--text:#000000;--text-secondary:#262626;--text-tertiary:#6f6f6f;
    --border:#e6e4df;--border-light:#f0efec;
    /* IOI brand. Blue is FILL-ONLY (2.1:1 on white as text); numbers & links are black, per site. */
    --accent:#000000;--accent-light:#d9f0fc;
    --brand-yellow:#ffde17;--brand-mint:#83fed1;--brand-blue:#69b3f2;--brand-peach:#ffbea1;
    --card-bg:#ffffff;--highlight:#fdf6e3;
    /* No red in IOI palette: risk maps to peach backgrounds with black text. */
    --risk-critical:#000000;--risk-critical-bg:#fff1e6;--risk-high:#262626;--risk-high-bg:#ffe9d6;--risk-low:#262626;--risk-low-bg:#dcfbee;
    --direct:#69b3f2;--adjacent:#9aeef7;--adoption:#b6fcdf;--unknown:#e6e4df;
    --ops:#ffbea1;--rnd:#69b3f2;--other:#e6e4df;--land:#ecebe7}
.sooi-sponsors *{margin:0;padding:0;box-sizing:border-box}
.sooi-sponsors{font-family:'Inter',var(--site-body-font,sans-serif);color:var(--text);line-height:1.6;-webkit-font-smoothing:antialiased;max-width:1080px;margin:0 auto;padding:8px 0 40px}
.sooi-sponsors .lede{font-size:16px;color:var(--text-secondary);max-width:760px;line-height:1.7}
.sooi-sponsors .lede + .lede{margin-top:14px}
.sooi-sponsors .cut{border-top:1px solid var(--border-light);margin-top:52px;padding-top:38px}
.sooi-sponsors .cut-num{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;letter-spacing:2px;color:var(--text-tertiary);text-transform:uppercase;margin-bottom:6px}
.sooi-sponsors .cut-intro{font-size:15px;color:var(--text-secondary);max-width:740px;margin-bottom:22px}
.sooi-sponsors .caveat{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);background:#fff;border:1px dashed var(--border);border-radius:6px;padding:8px 12px;margin-top:14px;line-height:1.5}
.sooi-sponsors .door{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--accent);margin-top:18px;display:flex;align-items:center;gap:8px}
.sooi-sponsors .door::before{content:'→'}
/* spacing after bare headings: styles the following element, never the heading */
.sooi-sponsors h2 + p,.sooi-sponsors h2 + div,.sooi-sponsors h3 + p,.sooi-sponsors h3 + div{margin-top:10px}
.sooi-sponsors .subhead{margin-top:44px;margin-bottom:0}
/* figure labels + notes (new, minor) */
.sooi-sponsors .fig{margin-top:30px}
.sooi-sponsors .fig-title{font-size:15px;font-weight:600;color:var(--text);margin-bottom:12px}
.sooi-sponsors .fig-note{font-size:12px;color:var(--text-tertiary);line-height:1.5;margin-top:12px;max-width:820px}
/* pull quote (new component) */
.sooi-sponsors .pullquote{margin:44px 0;max-width:640px}
.sooi-sponsors .pullquote .marks{display:flex;gap:6px;margin-bottom:14px}
.sooi-sponsors .pullquote .marks span{display:block;height:10px;border-radius:5px}
.sooi-sponsors .pullquote .marks .m1{width:32px;background:#000}
.sooi-sponsors .pullquote .marks .m2{width:18px;background:var(--brand-yellow)}
.sooi-sponsors .pullquote .marks .m3{width:10px;background:var(--adjacent)}
.sooi-sponsors .pullquote p{font-size:22px;font-weight:700;line-height:1.3;color:var(--text)}
/* ---- defensive reset: site link styles ---- */
.sooi-sponsors a{color:var(--text) !important;background:transparent !important;border:0 !important;box-shadow:none !important;
  text-decoration:underline !important;text-decoration-color:var(--brand-yellow) !important;text-decoration-thickness:2px !important;text-underline-offset:3px;overflow-wrap:anywhere}
.sooi-sponsors a:hover{text-decoration-color:var(--text) !important}
.sooi-sponsors sup{font-size:.7em;line-height:0;vertical-align:super}
.sooi-sponsors sup a{text-decoration:none !important}
.sooi-sponsors .footnotes{list-style:none;margin-top:28px;border-top:1px solid var(--border-light);padding-top:12px;font-size:12px;color:var(--text-tertiary)}
.sooi-sponsors .footnotes li{margin-bottom:4px}
.sooi-sponsors .sp-body{max-width:760px}
.sooi-sponsors .sp-body p{font-size:16px;line-height:1.7;color:var(--text-secondary);margin-bottom:14px}
.sooi-sponsors .sp-body strong{color:var(--text)}
/* linked logo tiles (new) */
.sooi-sponsors .sp-group{margin-top:36px}
.sooi-sponsors .logos{display:grid;grid-template-columns:repeat(4,1fr);gap:16px;margin-top:10px}
.sooi-sponsors .logo-tile{border:1px solid var(--border) !important;border-radius:10px;padding:18px 20px;min-height:110px;display:flex !important;align-items:center;justify-content:center;background:var(--card-bg) !important;text-decoration:none !important;transition:border-color .15s}
.sooi-sponsors .logo-tile:hover,.sooi-sponsors .logo-tile:focus-visible{border-color:#000 !important}
/* ---- defensive reset: site/Ghost content-image styles ---- */
.sooi-sponsors .logo-tile img{display:block !important;max-width:100% !important;max-height:64px !important;width:auto !important;height:auto !important;margin:0 !important;padding:0 !important;border:0 !important;box-shadow:none !important;border-radius:0 !important;object-fit:contain}

/* ---- responsive ---- */
@media (max-width: 900px){

}
@media (max-width: 640px){
  .sooi-sponsors .pullquote p{font-size:18px}
  .sooi-sponsors .logos{grid-template-columns:1fr 1fr}
}
@media (max-width: 420px){

}
</style>
<div class="sooi-sponsors">
  <div class="sp-body">
    <p>The State of Open Infrastructure is not simply a record of where the sector stands today. It draws on IOI’s position across the ecosystem to ask questions that individual institutions and funders rarely have the vantage point to ask: what should be sustained, where investment is most needed, how dependencies can be understood, and how the research community can work together to build infrastructure resilient enough for the future it will support.</p>
    <p>That work depends on collective support, and the process of developing this report reflects the solidarity across stakeholders in scholarly communication that makes it possible.</p>
    <p>We are glad to have allies in the ecosystem who believe in the importance of our work led by the Andrew W. Mellon Foundation and Arcadia Fund.</p>
    <p>Special thanks go to <strong><a href="https://www.crossref.org/?ref=investinopen.org" target="_blank" rel="noopener">Crossref</a></strong>, the report’s Supporting Sponsor, and to our Community Supporters: the <strong><a href="https://www.rd-alliance.org/?ref=investinopen.org" target="_blank" rel="noopener">Research Data Alliance (RDA)</a></strong>, the <strong><a href="https://www.clir.org/?ref=investinopen.org" target="_blank" rel="noopener">Council on Library and Information Resources (CLIR)</a></strong>, the <strong><a href="https://www.agu.org/?ref=investinopen.org" target="_blank" rel="noopener">American Geophysical Union (AGU)</a></strong>, and <strong><a href="https://cassyni.com/?ref=investinopen.org" target="_blank" rel="noopener">Cassyni</a></strong>. Their financial and in-kind support has been invaluable in making this report a reality.</p>
    <p>We are also grateful to our Sustaining Circle members, whose support is critical to IOI’s capacity to conduct targeted research, provide strategic tools for decision-makers, pilot funding mechanisms, and foster a shared agenda for investment in and adoption of open infrastructure. To learn more about joining, visit <a href="https://investinopen.org/" target="_blank" rel="noopener">investinopen.org</a>.</p>
  </div>
  <div class="sp-group"><div class="cut-num">Supporting sponsor</div>
    <div class="logos">
      <a class="logo-tile" href="https://www.crossref.org/?ref=investinopen.org" target="_blank" rel="noopener" aria-label="Crossref (opens in a new tab)"><img src="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/09/crossref_logo.svg" alt="Crossref logo" loading="lazy"></a>
    </div></div>
  <div class="sp-group"><div class="cut-num">Community supporters</div>
    <div class="logos">
      <a class="logo-tile" href="https://www.rd-alliance.org/?ref=investinopen.org" target="_blank" rel="noopener" aria-label="Research Data Alliance (RDA) (opens in a new tab)"><img src="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/09/RDA_Logotype_Hight.jpeg" alt="Research Data Alliance (RDA) logo" loading="lazy"></a>
      <a class="logo-tile" href="https://www.clir.org/?ref=investinopen.org" target="_blank" rel="noopener" aria-label="Council on Library and Information Resources (CLIR) (opens in a new tab)"><img src="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/09/CLIR-logo.png" alt="Council on Library and Information Resources (CLIR) logo" loading="lazy"></a>
      <a class="logo-tile" href="https://www.agu.org/?ref=investinopen.org" target="_blank" rel="noopener" aria-label="American Geophysical Union (AGU) (opens in a new tab)"><img src="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/09/AGU-logo.webp" alt="American Geophysical Union (AGU) logo" loading="lazy"></a>
      <a class="logo-tile" href="https://cassyni.com/?ref=investinopen.org" target="_blank" rel="noopener" aria-label="Cassyni (opens in a new tab)"><img src="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/09/Cassyni-logo.jpeg" alt="Cassyni logo" loading="lazy"></a>
    </div></div>
</div>
<!--kg-card-end: html-->
 ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ Test ]]></title>
        <description><![CDATA[ Research integrity is supported by a chain of interconnected infrastructure. Publishers, funders, and researchers depend on this chain every day, yet many of the critical links remain invisible unless they break. This analysis traces the infrastructure required to support research integrity in the context of increasing challenges created by generative ]]></description>
        <link>https://investinopen.org/state-of-open-infrastructure-2026/test/</link>
        <guid isPermaLink="false">6abd65abe6358500010afdb3</guid>
        <category><![CDATA[ SOOI-2026 ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Wed, 30 Sep 2026 20:38:29 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ 
<!--kg-card-begin: html-->
<!-- ============================================================
SoOI 2026 · Section 2 (The infrastructure of integrity) · v6 · card 1 of 5 · CMS embed
Source text: "State of Open Infrastructure 2026 (Milestone 2)" PDF.
Paste into an HTML block/card. Self-contained & scoped: all styles
apply only inside .sooi-s2 and cannot leak into site styles.
Fonts: loads Inter from Google Fonts; BW Gradual (headings) inherits from the site.
If the site already loads these (check site <head>), delete the
<link> line to avoid a duplicate request.
Page title + subtitle are owned by the CMS template (not in this block).
CARD 1 of 5 — intro box. Paste this WHOLE file into one Ghost HTML card.
First S2 block on the page (no heading above).
Ghost H2 block BELOW this card: Generative AI is prompting a research integrity crisis
Each card is self-contained (own font link + styles), so cards can be pasted in any order.
Rebuilt from the Milestone 2 PDF on sooi-s1-embed conventions. sooi-s2-embed-v2.html was not
available in this session, so component class names may differ from v2 — diff before replacing.
NEW components (no S1 precedent, pending Jerry's CMS review): intro box, threat cards, stage rows,
stage pipeline, recommendation cards, closing callout, citations list.
v6 = 5 self-contained HTML cards around 4 native Ghost H2 heading blocks (navigable).
v4 = styling pass (no copy changes): peach risk cards/cells, mint intervention cells,
blue pipeline bands + tag chips (S1 .oi precedent), yellow accents on black boxes.
Section images (Unsplash) are print-layout only and omitted; add via CMS if wanted.
============================================================= -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<!-- BW Gradual (headings) is loaded by the site; the embed inherits it. -->
<style>
/* ================= BRAND TOKENS =================
   Copied verbatim from sooi-s1-embed.html. Edit ONLY this block to re-theme.
   ================================================= */
.sooi-s2{--bg:transparent;--text:#000000;--text-secondary:#262626;--text-tertiary:#6f6f6f;
    --border:#e6e4df;--border-light:#f0efec;
    /* IOI brand. Blue is FILL-ONLY (2.1:1 on white as text); numbers & links are black, per site. */
    --accent:#000000;--accent-light:#d9f0fc;
    --brand-yellow:#ffde17;--brand-mint:#83fed1;--brand-blue:#69b3f2;--brand-peach:#ffbea1;
    --card-bg:#ffffff;--highlight:#fdf6e3;
    /* No red in IOI palette: risk maps to peach backgrounds with black text. */
    --risk-critical:#000000;--risk-critical-bg:#fff1e6;--risk-high:#262626;--risk-high-bg:#ffe9d6;--risk-low:#262626;--risk-low-bg:#dcfbee;
    --direct:#69b3f2;--adjacent:#9aeef7;--adoption:#b6fcdf;--unknown:#e6e4df;
    --ops:#ffbea1;--rnd:#69b3f2;--other:#e6e4df;--land:#ecebe7}
.sooi-s2 *{margin:0;padding:0;box-sizing:border-box}
.sooi-s2{font-family:'Inter',var(--site-body-font,sans-serif);color:var(--text);line-height:1.6;-webkit-font-smoothing:antialiased;max-width:1080px;margin:0 auto;padding:8px 0 40px}
.sooi-s2 .lede{font-size:16px;color:var(--text-secondary);max-width:760px;line-height:1.7}
.sooi-s2 .lede + .lede{margin-top:14px}
.sooi-s2 .cut{border-top:1px solid var(--border-light);margin-top:52px;padding-top:38px}
.sooi-s2 .cut-num{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;letter-spacing:2px;color:var(--text-tertiary);text-transform:uppercase;margin-bottom:6px}
.sooi-s2 .cut-intro{font-size:15px;color:var(--text-secondary);max-width:740px;margin-bottom:22px}
.sooi-s2 .caveat{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);background:#fff;border:1px dashed var(--border);border-radius:6px;padding:8px 12px;margin-top:14px;line-height:1.5}
.sooi-s2 .door{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--accent);margin-top:18px;display:flex;align-items:center;gap:8px}
.sooi-s2 .door::before{content:'→'}
/* spacing after bare headings: styles the following element, never the heading */
.sooi-s2 h2 + p,.sooi-s2 h2 + div,.sooi-s2 h3 + p,.sooi-s2 h3 + div{margin-top:10px}
.sooi-s2 .subhead{margin-top:44px;margin-bottom:0}
/* figure labels + notes (new, minor) */
.sooi-s2 .fig{margin-top:30px}
.sooi-s2 .fig-title{font-size:15px;font-weight:600;color:var(--text);margin-bottom:12px}
.sooi-s2 .fig-note{font-size:12px;color:var(--text-tertiary);line-height:1.5;margin-top:12px;max-width:820px}
/* pull quote (new component) */
.sooi-s2 .pullquote{margin:44px 0;max-width:640px}
.sooi-s2 .pullquote .marks{display:flex;gap:6px;margin-bottom:14px}
.sooi-s2 .pullquote .marks span{display:block;height:10px;border-radius:5px}
.sooi-s2 .pullquote .marks .m1{width:32px;background:#000}
.sooi-s2 .pullquote .marks .m2{width:18px;background:var(--brand-yellow)}
.sooi-s2 .pullquote .marks .m3{width:10px;background:var(--adjacent)}
.sooi-s2 .pullquote p{font-size:22px;font-weight:700;line-height:1.3;color:var(--text)}
/* ---- defensive reset: site link styles ---- */
.sooi-s2 a{color:var(--text) !important;background:transparent !important;border:0 !important;box-shadow:none !important;
  text-decoration:underline !important;text-decoration-color:var(--brand-yellow) !important;text-decoration-thickness:2px !important;text-underline-offset:3px;overflow-wrap:anywhere}
.sooi-s2 a:hover{text-decoration-color:var(--text) !important}
.sooi-s2 sup{font-size:.7em;line-height:0;vertical-align:super}
.sooi-s2 sup a{text-decoration:none !important}
.sooi-s2 .footnotes{list-style:none;margin-top:28px;border-top:1px solid var(--border-light);padding-top:12px;font-size:12px;color:var(--text-tertiary)}
.sooi-s2 .footnotes li{margin-bottom:4px}
/* intro box — IOI Black (new) */
.sooi-s2 .threats,.sooi-s2 .stages{margin-top:6px !important}
.sooi-s2 .intro-box{background:#000;color:#fff;border-radius:8px;padding:28px 32px 28px 30px;font-size:17px;line-height:1.65;max-width:820px;margin:0 0 8px auto;border-left:8px solid var(--brand-yellow)}
/* threat cards (new) */
.sooi-s2 .threats{display:grid;grid-template-columns:1fr 1fr;gap:28px 40px;margin-top:22px}
.sooi-s2 .threat{background:var(--risk-critical-bg);border:1px solid var(--brand-peach);border-top:6px solid #000;border-radius:10px;padding:22px 24px}
.sooi-s2 .threat h3{font-size:18px;font-weight:600;line-height:1.3;margin-bottom:8px}
.sooi-s2 .threat p{font-size:14px;color:var(--text-secondary);line-height:1.55}
.sooi-s2 .threats{gap:18px}
/* stage rows (new) */
.sooi-s2 .stages{margin-top:22px}
.sooi-s2 .stage{display:grid;grid-template-columns:190px 230px 1fr;gap:16px;border-top:2px solid #000;padding:20px 0}
.sooi-s2 .stage .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:44px;font-weight:700;color:var(--text);line-height:1}
.sooi-s2 .stage h3{font-size:18px;font-weight:600;margin:14px 0 4px}
.sooi-s2 .stage .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .stage .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
.sooi-s2 .chip{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;font-weight:600;background:var(--accent-light);color:var(--accent);padding:2px 8px;border-radius:3px}
.sooi-s2 .stage .cell{border-radius:8px;padding:14px 16px}
.sooi-s2 .stage .cell.r{background:var(--risk-critical-bg);border-left:4px solid var(--brand-peach)}
.sooi-s2 .stage .cell.i{background:var(--risk-low-bg);border-left:4px solid var(--brand-mint)}
.sooi-s2 .stage .k{font-size:10px;letter-spacing:1.5px;text-transform:uppercase;font-weight:700;margin-bottom:4px}
.sooi-s2 .stage .risk{font-size:14px;font-weight:600;line-height:1.45}
.sooi-s2 .stage .int{font-size:14px;color:var(--text-secondary);line-height:1.6}
/* stage pipeline (new) */
.sooi-s2 .chain{display:grid;grid-template-columns:repeat(4,1fr);border:1px solid var(--border);border-radius:10px;overflow:hidden}
.sooi-s2 .chain-step{background:var(--card-bg);padding:0 0 18px;border-right:1px solid var(--border);position:relative}
.sooi-s2 .chain-step > div{padding:0 18px}
.sooi-s2 .chain-step:not(:last-child)::after{content:'→';position:absolute;right:-11px;top:19px;width:22px;height:22px;border-radius:50%;background:#000;color:var(--brand-yellow);font-size:12px;line-height:22px;text-align:center;z-index:1}
.sooi-s2 .chain-step:last-child{border-right:0}
.sooi-s2 .chain{overflow:visible}
.sooi-s2 .chain-step:first-child{border-radius:10px 0 0 10px}
.sooi-s2 .chain-step:last-child{border-radius:0 10px 10px 0}
.sooi-s2 .chain-step .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:26px;font-weight:700;color:#000;background:var(--brand-blue);padding:12px 18px !important;margin-bottom:12px;border-radius:inherit;border-bottom-left-radius:0;border-bottom-right-radius:0}
.sooi-s2 .chain-step .name{font-size:17px;font-weight:600;margin:2px 0 4px}
.sooi-s2 .chain-step .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .chain-step .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
/* recommendations (new) */
.sooi-s2 .lead-strong{font-size:19px;font-weight:600;line-height:1.45;max-width:760px;margin-top:24px;color:var(--text)}
.sooi-s2 .lead-strong span{background:linear-gradient(transparent 62%,var(--brand-yellow) 62%)}
.sooi-s2 .recs{display:grid;grid-template-columns:repeat(3,1fr);gap:24px;margin-top:24px}
.sooi-s2 .rec{background:var(--accent-light);border-top:6px solid var(--brand-blue);border-radius:10px;padding:20px 22px}
.sooi-s2 .rec .rk{font-size:16px;font-weight:700;line-height:1.3;margin-bottom:8px}
.sooi-s2 .rec p{font-size:14px;color:var(--text-secondary);line-height:1.55}
/* closing callout — IOI Black (new) */
.sooi-s2 .closing{background:#000;color:#fff;border-radius:12px;padding:28px 32px 28px 30px;margin-top:28px;font-size:16px;line-height:1.65;border-left:8px solid var(--brand-yellow)}
/* citations (new) */
.sooi-s2 .cites{list-style:none;margin-top:10px}
.sooi-s2 .cites li{font-size:13px;color:var(--text-secondary);line-height:1.55;padding:10px 0;border-bottom:1px solid var(--border-light)}
.sooi-s2 .cites li:last-child{border-bottom:0}

/* ---- responsive ---- */
@media (max-width: 900px){
  .sooi-s2 .threats{grid-template-columns:1fr}
  .sooi-s2 .stage{grid-template-columns:1fr;gap:12px}
  .sooi-s2 .stage h3{margin-top:8px}
  .sooi-s2 .chain{grid-template-columns:1fr 1fr}
  .sooi-s2 .chain-step::after{display:none}
  .sooi-s2 .chain-step{border-radius:0 !important}
  .sooi-s2 .chain{overflow:hidden}
  .sooi-s2 .chain-step:nth-child(2){border-right:0}
  .sooi-s2 .chain-step:nth-child(-n+2){border-bottom:1px solid var(--border)}
  .sooi-s2 .recs{grid-template-columns:1fr}
}
@media (max-width: 640px){
  .sooi-s2 .pullquote p{font-size:18px}
  .sooi-s2 .intro-box{padding:22px 20px;font-size:16px}
  .sooi-s2 .closing{padding:22px 20px}
  .sooi-s2 .lead-strong{font-size:17px}
}
@media (max-width: 420px){
  .sooi-s2 .chain{grid-template-columns:1fr}
  .sooi-s2 .chain-step{border-right:0;border-bottom:1px solid var(--border)}
  .sooi-s2 .chain-step:last-child{border-bottom:0}
}
</style>
<div class="sooi-s2">
<div class="intro-box">Research integrity is supported by a chain of interconnected infrastructure. Publishers, funders, and researchers depend on this chain every day, yet many of the critical links remain invisible unless they break. This analysis traces the infrastructure required to support research integrity in the context of increasing challenges created by generative AI. These infrastructures are more critical than ever, and many are under growing strain.</div>
</div>
<!--kg-card-end: html-->
<h2 id="generative-ai-is-prompting-a-research-integrity-crisis">Generative AI is prompting a research integrity crisis</h2>
<!--kg-card-begin: html-->
<!-- ============================================================
SoOI 2026 · Section 2 (The infrastructure of integrity) · v6 · card 2 of 5 · CMS embed
Source text: "State of Open Infrastructure 2026 (Milestone 2)" PDF.
Paste into an HTML block/card. Self-contained & scoped: all styles
apply only inside .sooi-s2 and cannot leak into site styles.
Fonts: loads Inter from Google Fonts; BW Gradual (headings) inherits from the site.
If the site already loads these (check site <head>), delete the
<link> line to avoid a duplicate request.
Page title + subtitle are owned by the CMS template (not in this block).
CARD 2 of 5 — threat cards. Paste this WHOLE file into one Ghost HTML card.
Ghost H2 block ABOVE this card: Generative AI is prompting a research integrity crisis
Ghost H2 block BELOW this card: Open Infrastructure interventions bolster trustworthy knowledge
Each card is self-contained (own font link + styles), so cards can be pasted in any order.
Rebuilt from the Milestone 2 PDF on sooi-s1-embed conventions. sooi-s2-embed-v2.html was not
available in this session, so component class names may differ from v2 — diff before replacing.
NEW components (no S1 precedent, pending Jerry's CMS review): intro box, threat cards, stage rows,
stage pipeline, recommendation cards, closing callout, citations list.
v6 = 5 self-contained HTML cards around 4 native Ghost H2 heading blocks (navigable).
v4 = styling pass (no copy changes): peach risk cards/cells, mint intervention cells,
blue pipeline bands + tag chips (S1 .oi precedent), yellow accents on black boxes.
Section images (Unsplash) are print-layout only and omitted; add via CMS if wanted.
============================================================= -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<!-- BW Gradual (headings) is loaded by the site; the embed inherits it. -->
<style>
/* ================= BRAND TOKENS =================
   Copied verbatim from sooi-s1-embed.html. Edit ONLY this block to re-theme.
   ================================================= */
.sooi-s2{--bg:transparent;--text:#000000;--text-secondary:#262626;--text-tertiary:#6f6f6f;
    --border:#e6e4df;--border-light:#f0efec;
    /* IOI brand. Blue is FILL-ONLY (2.1:1 on white as text); numbers & links are black, per site. */
    --accent:#000000;--accent-light:#d9f0fc;
    --brand-yellow:#ffde17;--brand-mint:#83fed1;--brand-blue:#69b3f2;--brand-peach:#ffbea1;
    --card-bg:#ffffff;--highlight:#fdf6e3;
    /* No red in IOI palette: risk maps to peach backgrounds with black text. */
    --risk-critical:#000000;--risk-critical-bg:#fff1e6;--risk-high:#262626;--risk-high-bg:#ffe9d6;--risk-low:#262626;--risk-low-bg:#dcfbee;
    --direct:#69b3f2;--adjacent:#9aeef7;--adoption:#b6fcdf;--unknown:#e6e4df;
    --ops:#ffbea1;--rnd:#69b3f2;--other:#e6e4df;--land:#ecebe7}
.sooi-s2 *{margin:0;padding:0;box-sizing:border-box}
.sooi-s2{font-family:'Inter',var(--site-body-font,sans-serif);color:var(--text);line-height:1.6;-webkit-font-smoothing:antialiased;max-width:1080px;margin:0 auto;padding:8px 0 40px}
.sooi-s2 .lede{font-size:16px;color:var(--text-secondary);max-width:760px;line-height:1.7}
.sooi-s2 .lede + .lede{margin-top:14px}
.sooi-s2 .cut{border-top:1px solid var(--border-light);margin-top:52px;padding-top:38px}
.sooi-s2 .cut-num{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;letter-spacing:2px;color:var(--text-tertiary);text-transform:uppercase;margin-bottom:6px}
.sooi-s2 .cut-intro{font-size:15px;color:var(--text-secondary);max-width:740px;margin-bottom:22px}
.sooi-s2 .caveat{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);background:#fff;border:1px dashed var(--border);border-radius:6px;padding:8px 12px;margin-top:14px;line-height:1.5}
.sooi-s2 .door{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--accent);margin-top:18px;display:flex;align-items:center;gap:8px}
.sooi-s2 .door::before{content:'→'}
/* spacing after bare headings: styles the following element, never the heading */
.sooi-s2 h2 + p,.sooi-s2 h2 + div,.sooi-s2 h3 + p,.sooi-s2 h3 + div{margin-top:10px}
.sooi-s2 .subhead{margin-top:44px;margin-bottom:0}
/* figure labels + notes (new, minor) */
.sooi-s2 .fig{margin-top:30px}
.sooi-s2 .fig-title{font-size:15px;font-weight:600;color:var(--text);margin-bottom:12px}
.sooi-s2 .fig-note{font-size:12px;color:var(--text-tertiary);line-height:1.5;margin-top:12px;max-width:820px}
/* pull quote (new component) */
.sooi-s2 .pullquote{margin:44px 0;max-width:640px}
.sooi-s2 .pullquote .marks{display:flex;gap:6px;margin-bottom:14px}
.sooi-s2 .pullquote .marks span{display:block;height:10px;border-radius:5px}
.sooi-s2 .pullquote .marks .m1{width:32px;background:#000}
.sooi-s2 .pullquote .marks .m2{width:18px;background:var(--brand-yellow)}
.sooi-s2 .pullquote .marks .m3{width:10px;background:var(--adjacent)}
.sooi-s2 .pullquote p{font-size:22px;font-weight:700;line-height:1.3;color:var(--text)}
/* ---- defensive reset: site link styles ---- */
.sooi-s2 a{color:var(--text) !important;background:transparent !important;border:0 !important;box-shadow:none !important;
  text-decoration:underline !important;text-decoration-color:var(--brand-yellow) !important;text-decoration-thickness:2px !important;text-underline-offset:3px;overflow-wrap:anywhere}
.sooi-s2 a:hover{text-decoration-color:var(--text) !important}
.sooi-s2 sup{font-size:.7em;line-height:0;vertical-align:super}
.sooi-s2 sup a{text-decoration:none !important}
.sooi-s2 .footnotes{list-style:none;margin-top:28px;border-top:1px solid var(--border-light);padding-top:12px;font-size:12px;color:var(--text-tertiary)}
.sooi-s2 .footnotes li{margin-bottom:4px}
/* intro box — IOI Black (new) */
.sooi-s2 .threats,.sooi-s2 .stages{margin-top:6px !important}
.sooi-s2 .intro-box{background:#000;color:#fff;border-radius:8px;padding:28px 32px 28px 30px;font-size:17px;line-height:1.65;max-width:820px;margin:0 0 8px auto;border-left:8px solid var(--brand-yellow)}
/* threat cards (new) */
.sooi-s2 .threats{display:grid;grid-template-columns:1fr 1fr;gap:28px 40px;margin-top:22px}
.sooi-s2 .threat{background:var(--risk-critical-bg);border:1px solid var(--brand-peach);border-top:6px solid #000;border-radius:10px;padding:22px 24px}
.sooi-s2 .threat h3{font-size:18px;font-weight:600;line-height:1.3;margin-bottom:8px}
.sooi-s2 .threat p{font-size:14px;color:var(--text-secondary);line-height:1.55}
.sooi-s2 .threats{gap:18px}
/* stage rows (new) */
.sooi-s2 .stages{margin-top:22px}
.sooi-s2 .stage{display:grid;grid-template-columns:190px 230px 1fr;gap:16px;border-top:2px solid #000;padding:20px 0}
.sooi-s2 .stage .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:44px;font-weight:700;color:var(--text);line-height:1}
.sooi-s2 .stage h3{font-size:18px;font-weight:600;margin:14px 0 4px}
.sooi-s2 .stage .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .stage .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
.sooi-s2 .chip{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;font-weight:600;background:var(--accent-light);color:var(--accent);padding:2px 8px;border-radius:3px}
.sooi-s2 .stage .cell{border-radius:8px;padding:14px 16px}
.sooi-s2 .stage .cell.r{background:var(--risk-critical-bg);border-left:4px solid var(--brand-peach)}
.sooi-s2 .stage .cell.i{background:var(--risk-low-bg);border-left:4px solid var(--brand-mint)}
.sooi-s2 .stage .k{font-size:10px;letter-spacing:1.5px;text-transform:uppercase;font-weight:700;margin-bottom:4px}
.sooi-s2 .stage .risk{font-size:14px;font-weight:600;line-height:1.45}
.sooi-s2 .stage .int{font-size:14px;color:var(--text-secondary);line-height:1.6}
/* stage pipeline (new) */
.sooi-s2 .chain{display:grid;grid-template-columns:repeat(4,1fr);border:1px solid var(--border);border-radius:10px;overflow:hidden}
.sooi-s2 .chain-step{background:var(--card-bg);padding:0 0 18px;border-right:1px solid var(--border);position:relative}
.sooi-s2 .chain-step > div{padding:0 18px}
.sooi-s2 .chain-step:not(:last-child)::after{content:'→';position:absolute;right:-11px;top:19px;width:22px;height:22px;border-radius:50%;background:#000;color:var(--brand-yellow);font-size:12px;line-height:22px;text-align:center;z-index:1}
.sooi-s2 .chain-step:last-child{border-right:0}
.sooi-s2 .chain{overflow:visible}
.sooi-s2 .chain-step:first-child{border-radius:10px 0 0 10px}
.sooi-s2 .chain-step:last-child{border-radius:0 10px 10px 0}
.sooi-s2 .chain-step .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:26px;font-weight:700;color:#000;background:var(--brand-blue);padding:12px 18px !important;margin-bottom:12px;border-radius:inherit;border-bottom-left-radius:0;border-bottom-right-radius:0}
.sooi-s2 .chain-step .name{font-size:17px;font-weight:600;margin:2px 0 4px}
.sooi-s2 .chain-step .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .chain-step .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
/* recommendations (new) */
.sooi-s2 .lead-strong{font-size:19px;font-weight:600;line-height:1.45;max-width:760px;margin-top:24px;color:var(--text)}
.sooi-s2 .lead-strong span{background:linear-gradient(transparent 62%,var(--brand-yellow) 62%)}
.sooi-s2 .recs{display:grid;grid-template-columns:repeat(3,1fr);gap:24px;margin-top:24px}
.sooi-s2 .rec{background:var(--accent-light);border-top:6px solid var(--brand-blue);border-radius:10px;padding:20px 22px}
.sooi-s2 .rec .rk{font-size:16px;font-weight:700;line-height:1.3;margin-bottom:8px}
.sooi-s2 .rec p{font-size:14px;color:var(--text-secondary);line-height:1.55}
/* closing callout — IOI Black (new) */
.sooi-s2 .closing{background:#000;color:#fff;border-radius:12px;padding:28px 32px 28px 30px;margin-top:28px;font-size:16px;line-height:1.65;border-left:8px solid var(--brand-yellow)}
/* citations (new) */
.sooi-s2 .cites{list-style:none;margin-top:10px}
.sooi-s2 .cites li{font-size:13px;color:var(--text-secondary);line-height:1.55;padding:10px 0;border-bottom:1px solid var(--border-light)}
.sooi-s2 .cites li:last-child{border-bottom:0}

/* ---- responsive ---- */
@media (max-width: 900px){
  .sooi-s2 .threats{grid-template-columns:1fr}
  .sooi-s2 .stage{grid-template-columns:1fr;gap:12px}
  .sooi-s2 .stage h3{margin-top:8px}
  .sooi-s2 .chain{grid-template-columns:1fr 1fr}
  .sooi-s2 .chain-step::after{display:none}
  .sooi-s2 .chain-step{border-radius:0 !important}
  .sooi-s2 .chain{overflow:hidden}
  .sooi-s2 .chain-step:nth-child(2){border-right:0}
  .sooi-s2 .chain-step:nth-child(-n+2){border-bottom:1px solid var(--border)}
  .sooi-s2 .recs{grid-template-columns:1fr}
}
@media (max-width: 640px){
  .sooi-s2 .pullquote p{font-size:18px}
  .sooi-s2 .intro-box{padding:22px 20px;font-size:16px}
  .sooi-s2 .closing{padding:22px 20px}
  .sooi-s2 .lead-strong{font-size:17px}
}
@media (max-width: 420px){
  .sooi-s2 .chain{grid-template-columns:1fr}
  .sooi-s2 .chain-step{border-right:0;border-bottom:1px solid var(--border)}
  .sooi-s2 .chain-step:last-child{border-bottom:0}
}
</style>
<div class="sooi-s2">
<div class="threats">
    <div class="threat"><h3>Preprint Flooding</h3><p>LLM-generated manuscripts submitted en masse to preprint servers are overwhelming review systems. Fabricated data, hallucinated citations, and plausible-sounding methodology can pass automated checks and cursory human screening (Singh, 2025).</p></div>
    <div class="threat"><h3>Identity Theft &amp; Ghost Authors</h3><p>Paper mills and fraudulent or low-quality journals falsely attribute authorship to real researchers to lend credibility (Grove, 2023).</p></div>
    <div class="threat"><h3>AI-Powered Paper Mills</h3><p>Organised networks now use generative AI to produce hundreds of superficially coherent papers monthly, defeating manual peer review through sheer volume and automated reviewer impersonation (Richardson et al., 2025).</p></div>
    <div class="threat"><h3>Citation Chain Corruption</h3><p>AI systems hallucinate references that appear in real papers, creating citation chains that lead to non-existent or misrepresented sources, potentially leading to large-scale pollution of the scholarly record (Zhao et al., 2026).</p></div>
  </div>
</div>
<!--kg-card-end: html-->
<h2 id="open-infrastructure-interventions-bolster-trustworthy-knowledge">Open Infrastructure interventions bolster trustworthy knowledge</h2>
<!--kg-card-begin: html-->
<!-- ============================================================
SoOI 2026 · Section 2 (The infrastructure of integrity) · v6 · card 3 of 5 · CMS embed
Source text: "State of Open Infrastructure 2026 (Milestone 2)" PDF.
Paste into an HTML block/card. Self-contained & scoped: all styles
apply only inside .sooi-s2 and cannot leak into site styles.
Fonts: loads Inter from Google Fonts; BW Gradual (headings) inherits from the site.
If the site already loads these (check site <head>), delete the
<link> line to avoid a duplicate request.
Page title + subtitle are owned by the CMS template (not in this block).
CARD 3 of 5 — stage rows + pipeline. Paste this WHOLE file into one Ghost HTML card.
Ghost H2 block ABOVE this card: Open Infrastructure interventions bolster trustworthy knowledge
Ghost H2 block BELOW this card: What needs to happen
Each card is self-contained (own font link + styles), so cards can be pasted in any order.
Rebuilt from the Milestone 2 PDF on sooi-s1-embed conventions. sooi-s2-embed-v2.html was not
available in this session, so component class names may differ from v2 — diff before replacing.
NEW components (no S1 precedent, pending Jerry's CMS review): intro box, threat cards, stage rows,
stage pipeline, recommendation cards, closing callout, citations list.
v6 = 5 self-contained HTML cards around 4 native Ghost H2 heading blocks (navigable).
v4 = styling pass (no copy changes): peach risk cards/cells, mint intervention cells,
blue pipeline bands + tag chips (S1 .oi precedent), yellow accents on black boxes.
Section images (Unsplash) are print-layout only and omitted; add via CMS if wanted.
============================================================= -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<!-- BW Gradual (headings) is loaded by the site; the embed inherits it. -->
<style>
/* ================= BRAND TOKENS =================
   Copied verbatim from sooi-s1-embed.html. Edit ONLY this block to re-theme.
   ================================================= */
.sooi-s2{--bg:transparent;--text:#000000;--text-secondary:#262626;--text-tertiary:#6f6f6f;
    --border:#e6e4df;--border-light:#f0efec;
    /* IOI brand. Blue is FILL-ONLY (2.1:1 on white as text); numbers & links are black, per site. */
    --accent:#000000;--accent-light:#d9f0fc;
    --brand-yellow:#ffde17;--brand-mint:#83fed1;--brand-blue:#69b3f2;--brand-peach:#ffbea1;
    --card-bg:#ffffff;--highlight:#fdf6e3;
    /* No red in IOI palette: risk maps to peach backgrounds with black text. */
    --risk-critical:#000000;--risk-critical-bg:#fff1e6;--risk-high:#262626;--risk-high-bg:#ffe9d6;--risk-low:#262626;--risk-low-bg:#dcfbee;
    --direct:#69b3f2;--adjacent:#9aeef7;--adoption:#b6fcdf;--unknown:#e6e4df;
    --ops:#ffbea1;--rnd:#69b3f2;--other:#e6e4df;--land:#ecebe7}
.sooi-s2 *{margin:0;padding:0;box-sizing:border-box}
.sooi-s2{font-family:'Inter',var(--site-body-font,sans-serif);color:var(--text);line-height:1.6;-webkit-font-smoothing:antialiased;max-width:1080px;margin:0 auto;padding:8px 0 40px}
.sooi-s2 .lede{font-size:16px;color:var(--text-secondary);max-width:760px;line-height:1.7}
.sooi-s2 .lede + .lede{margin-top:14px}
.sooi-s2 .cut{border-top:1px solid var(--border-light);margin-top:52px;padding-top:38px}
.sooi-s2 .cut-num{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;letter-spacing:2px;color:var(--text-tertiary);text-transform:uppercase;margin-bottom:6px}
.sooi-s2 .cut-intro{font-size:15px;color:var(--text-secondary);max-width:740px;margin-bottom:22px}
.sooi-s2 .caveat{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);background:#fff;border:1px dashed var(--border);border-radius:6px;padding:8px 12px;margin-top:14px;line-height:1.5}
.sooi-s2 .door{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--accent);margin-top:18px;display:flex;align-items:center;gap:8px}
.sooi-s2 .door::before{content:'→'}
/* spacing after bare headings: styles the following element, never the heading */
.sooi-s2 h2 + p,.sooi-s2 h2 + div,.sooi-s2 h3 + p,.sooi-s2 h3 + div{margin-top:10px}
.sooi-s2 .subhead{margin-top:44px;margin-bottom:0}
/* figure labels + notes (new, minor) */
.sooi-s2 .fig{margin-top:30px}
.sooi-s2 .fig-title{font-size:15px;font-weight:600;color:var(--text);margin-bottom:12px}
.sooi-s2 .fig-note{font-size:12px;color:var(--text-tertiary);line-height:1.5;margin-top:12px;max-width:820px}
/* pull quote (new component) */
.sooi-s2 .pullquote{margin:44px 0;max-width:640px}
.sooi-s2 .pullquote .marks{display:flex;gap:6px;margin-bottom:14px}
.sooi-s2 .pullquote .marks span{display:block;height:10px;border-radius:5px}
.sooi-s2 .pullquote .marks .m1{width:32px;background:#000}
.sooi-s2 .pullquote .marks .m2{width:18px;background:var(--brand-yellow)}
.sooi-s2 .pullquote .marks .m3{width:10px;background:var(--adjacent)}
.sooi-s2 .pullquote p{font-size:22px;font-weight:700;line-height:1.3;color:var(--text)}
/* ---- defensive reset: site link styles ---- */
.sooi-s2 a{color:var(--text) !important;background:transparent !important;border:0 !important;box-shadow:none !important;
  text-decoration:underline !important;text-decoration-color:var(--brand-yellow) !important;text-decoration-thickness:2px !important;text-underline-offset:3px;overflow-wrap:anywhere}
.sooi-s2 a:hover{text-decoration-color:var(--text) !important}
.sooi-s2 sup{font-size:.7em;line-height:0;vertical-align:super}
.sooi-s2 sup a{text-decoration:none !important}
.sooi-s2 .footnotes{list-style:none;margin-top:28px;border-top:1px solid var(--border-light);padding-top:12px;font-size:12px;color:var(--text-tertiary)}
.sooi-s2 .footnotes li{margin-bottom:4px}
/* intro box — IOI Black (new) */
.sooi-s2 .threats,.sooi-s2 .stages{margin-top:6px !important}
.sooi-s2 .intro-box{background:#000;color:#fff;border-radius:8px;padding:28px 32px 28px 30px;font-size:17px;line-height:1.65;max-width:820px;margin:0 0 8px auto;border-left:8px solid var(--brand-yellow)}
/* threat cards (new) */
.sooi-s2 .threats{display:grid;grid-template-columns:1fr 1fr;gap:28px 40px;margin-top:22px}
.sooi-s2 .threat{background:var(--risk-critical-bg);border:1px solid var(--brand-peach);border-top:6px solid #000;border-radius:10px;padding:22px 24px}
.sooi-s2 .threat h3{font-size:18px;font-weight:600;line-height:1.3;margin-bottom:8px}
.sooi-s2 .threat p{font-size:14px;color:var(--text-secondary);line-height:1.55}
.sooi-s2 .threats{gap:18px}
/* stage rows (new) */
.sooi-s2 .stages{margin-top:22px}
.sooi-s2 .stage{display:grid;grid-template-columns:190px 230px 1fr;gap:16px;border-top:2px solid #000;padding:20px 0}
.sooi-s2 .stage .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:44px;font-weight:700;color:var(--text);line-height:1}
.sooi-s2 .stage h3{font-size:18px;font-weight:600;margin:14px 0 4px}
.sooi-s2 .stage .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .stage .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
.sooi-s2 .chip{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;font-weight:600;background:var(--accent-light);color:var(--accent);padding:2px 8px;border-radius:3px}
.sooi-s2 .stage .cell{border-radius:8px;padding:14px 16px}
.sooi-s2 .stage .cell.r{background:var(--risk-critical-bg);border-left:4px solid var(--brand-peach)}
.sooi-s2 .stage .cell.i{background:var(--risk-low-bg);border-left:4px solid var(--brand-mint)}
.sooi-s2 .stage .k{font-size:10px;letter-spacing:1.5px;text-transform:uppercase;font-weight:700;margin-bottom:4px}
.sooi-s2 .stage .risk{font-size:14px;font-weight:600;line-height:1.45}
.sooi-s2 .stage .int{font-size:14px;color:var(--text-secondary);line-height:1.6}
/* stage pipeline (new) */
.sooi-s2 .chain{display:grid;grid-template-columns:repeat(4,1fr);border:1px solid var(--border);border-radius:10px;overflow:hidden}
.sooi-s2 .chain-step{background:var(--card-bg);padding:0 0 18px;border-right:1px solid var(--border);position:relative}
.sooi-s2 .chain-step > div{padding:0 18px}
.sooi-s2 .chain-step:not(:last-child)::after{content:'→';position:absolute;right:-11px;top:19px;width:22px;height:22px;border-radius:50%;background:#000;color:var(--brand-yellow);font-size:12px;line-height:22px;text-align:center;z-index:1}
.sooi-s2 .chain-step:last-child{border-right:0}
.sooi-s2 .chain{overflow:visible}
.sooi-s2 .chain-step:first-child{border-radius:10px 0 0 10px}
.sooi-s2 .chain-step:last-child{border-radius:0 10px 10px 0}
.sooi-s2 .chain-step .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:26px;font-weight:700;color:#000;background:var(--brand-blue);padding:12px 18px !important;margin-bottom:12px;border-radius:inherit;border-bottom-left-radius:0;border-bottom-right-radius:0}
.sooi-s2 .chain-step .name{font-size:17px;font-weight:600;margin:2px 0 4px}
.sooi-s2 .chain-step .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .chain-step .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
/* recommendations (new) */
.sooi-s2 .lead-strong{font-size:19px;font-weight:600;line-height:1.45;max-width:760px;margin-top:24px;color:var(--text)}
.sooi-s2 .lead-strong span{background:linear-gradient(transparent 62%,var(--brand-yellow) 62%)}
.sooi-s2 .recs{display:grid;grid-template-columns:repeat(3,1fr);gap:24px;margin-top:24px}
.sooi-s2 .rec{background:var(--accent-light);border-top:6px solid var(--brand-blue);border-radius:10px;padding:20px 22px}
.sooi-s2 .rec .rk{font-size:16px;font-weight:700;line-height:1.3;margin-bottom:8px}
.sooi-s2 .rec p{font-size:14px;color:var(--text-secondary);line-height:1.55}
/* closing callout — IOI Black (new) */
.sooi-s2 .closing{background:#000;color:#fff;border-radius:12px;padding:28px 32px 28px 30px;margin-top:28px;font-size:16px;line-height:1.65;border-left:8px solid var(--brand-yellow)}
/* citations (new) */
.sooi-s2 .cites{list-style:none;margin-top:10px}
.sooi-s2 .cites li{font-size:13px;color:var(--text-secondary);line-height:1.55;padding:10px 0;border-bottom:1px solid var(--border-light)}
.sooi-s2 .cites li:last-child{border-bottom:0}

/* ---- responsive ---- */
@media (max-width: 900px){
  .sooi-s2 .threats{grid-template-columns:1fr}
  .sooi-s2 .stage{grid-template-columns:1fr;gap:12px}
  .sooi-s2 .stage h3{margin-top:8px}
  .sooi-s2 .chain{grid-template-columns:1fr 1fr}
  .sooi-s2 .chain-step::after{display:none}
  .sooi-s2 .chain-step{border-radius:0 !important}
  .sooi-s2 .chain{overflow:hidden}
  .sooi-s2 .chain-step:nth-child(2){border-right:0}
  .sooi-s2 .chain-step:nth-child(-n+2){border-bottom:1px solid var(--border)}
  .sooi-s2 .recs{grid-template-columns:1fr}
}
@media (max-width: 640px){
  .sooi-s2 .pullquote p{font-size:18px}
  .sooi-s2 .intro-box{padding:22px 20px;font-size:16px}
  .sooi-s2 .closing{padding:22px 20px}
  .sooi-s2 .lead-strong{font-size:17px}
}
@media (max-width: 420px){
  .sooi-s2 .chain{grid-template-columns:1fr}
  .sooi-s2 .chain-step{border-right:0;border-bottom:1px solid var(--border)}
  .sooi-s2 .chain-step:last-child{border-bottom:0}
}
</style>
<div class="sooi-s2">
<div class="stages">
    <div class="stage">
      <div><div class="num">01</div><h3>Identify</h3><div class="q">Who is the researcher?</div><div class="tag"><span class="chip">ORCID</span></div></div>
      <div class="cell r"><div class="k">AI risk</div><div class="risk">AI-generated papers steal the identities of real researchers to lend credibility to fabricated or low-quality publications.</div></div>
      <div class="cell i"><div class="k">OI intervention</div><div class="int">Persistent, globally unique researcher identifiers create a trustworthy link between an individual and their work. Open identity infrastructure makes impersonation and ghost authorship detectable. An ORCID — a free, unique identifier that follows a researcher for their entire career regardless of name changes, or institutional moves — can prevent fraudulent authorship claims. Authentication via ORCID when authors submit data, manuscripts, or other outputs, provides a layer of identity validation.</div></div>
    </div>
    <div class="stage">
      <div><div class="num">02</div><h3>Affiliate</h3><div class="q">Where does the work come from?</div><div class="tag"><span class="chip">ROR</span> <span class="chip">ImpactU</span></div></div>
      <div class="cell r"><div class="k">AI risk</div><div class="risk">Fabricated affiliations allow paper-mill output to look like it came from research-intensive and prestigious institutions.</div></div>
      <div class="cell i"><div class="k">OI intervention</div><div class="int">ROR (Research Organization Registry) assigns a persistent, openly-licensed identifier to over 116,000 institutions worldwide. ROR is structurally embedded in Crossref DOI metadata, DataCite DOI metadata, and ORCID, making it much more difficult to assert false affiliations when these persistent identifiers are used in concert. Current Research Information Systems (CRIS) like ImpactU make affiliations visible by tracking verified institutional output. This permits cross-checking of affiliation claims against an institution’s actual, indexed publication record.</div></div>
    </div>
    <div class="stage">
      <div><div class="num">03</div><h3>Connect</h3><div class="q">What other outputs support this work?</div><div class="tag"><span class="chip">Dryad</span> <span class="chip">DMP Tool</span> <span class="chip">DataCite</span></div></div>
      <div class="cell r"><div class="k">AI risk</div><div class="risk">It is easier than ever to fabricate or alter datasets using generative AI tools. Falsified data can be used to support misleading, untrue, or exaggerated claims in published research.</div></div>
      <div class="cell i"><div class="k">OI intervention</div><div class="int">Data Management Plans (DMPs) enforce pre-registration of methodology before results are known. DMPTool, for example, provides a click-through wizard for creating a DMP that complies with funder requirements, making after-the-fact alterations easier to spot. Open data repositories and platforms make datasets available for validation by the research community. At Dryad, for example, submissions are self-deposited, then vetted by Dryad curators and given a citable DOI. The published dataset becomes persistently available for peer review and validation. As the primary DOI registration agency specializing in research data and software, DataCite provides persistent identifiers that link datasets to research articles and other outputs, building an interconnected bundle of evidence and analysis that can be independently validated.</div></div>
    </div>
    <div class="stage">
      <div><div class="num">04</div><h3>Propagate</h3><div class="q">Metadata flows into the scholarly record</div><div class="tag"><span class="chip">Crossref</span> <span class="chip">OpenAlex</span></div></div>
      <div class="cell r"><div class="k">AI risk</div><div class="risk">Papers (whether AI-generated or assisted) contain hallucinated citations.</div></div>
      <div class="cell i"><div class="k">OI intervention</div><div class="int">Persistent Identifiers (PIDs) such as DOIs and handles create easy, timestamped metadata about citations that AI tools could use and research integrity services can use to verify citations. Crossref’s 2026 public data file contains nearly 180 million structured, machine-readable DOI records, providing an authoritative source of truth on the published record. OpenAlex, a free, open-source index of hundreds of millions of scholarly works, provides another portal to verifying citations.</div></div>
    </div>
  </div>
  <div class="subhead"><h3>A chain of interconnected infrastructure</h3></div>
  <div class="chain">
    <div class="chain-step"><div class="num">01</div><div class="name">Identify</div><div class="q">Who is the researcher?</div><div class="tag"><span class="chip">ORCID</span></div></div>
    <div class="chain-step"><div class="num">02</div><div class="name">Affiliate</div><div class="q">Where does the work come from?</div><div class="tag"><span class="chip">ROR</span> <span class="chip">ImpactU</span></div></div>
    <div class="chain-step"><div class="num">03</div><div class="name">Connect</div><div class="q">What other outputs support this work?</div><div class="tag"><span class="chip">Dryad</span> <span class="chip">DMP Tool</span> <span class="chip">DataCite</span></div></div>
    <div class="chain-step"><div class="num">04</div><div class="name">Propagate</div><div class="q">Metadata flows into the scholarly record</div><div class="tag"><span class="chip">Crossref</span> <span class="chip">OpenAlex</span></div></div>
  </div>
</div>
<!--kg-card-end: html-->
<h2 id="what-needs-to-happen">What needs to happen</h2>
<!--kg-card-begin: html-->
<!-- ============================================================
SoOI 2026 · Section 2 (The infrastructure of integrity) · v6 · card 4 of 5 · CMS embed
Source text: "State of Open Infrastructure 2026 (Milestone 2)" PDF.
Paste into an HTML block/card. Self-contained & scoped: all styles
apply only inside .sooi-s2 and cannot leak into site styles.
Fonts: loads Inter from Google Fonts; BW Gradual (headings) inherits from the site.
If the site already loads these (check site <head>), delete the
<link> line to avoid a duplicate request.
Page title + subtitle are owned by the CMS template (not in this block).
CARD 4 of 5 — recommendations + closing box. Paste this WHOLE file into one Ghost HTML card.
Ghost H2 block ABOVE this card: What needs to happen
Ghost H2 block BELOW this card: Works Cited
Each card is self-contained (own font link + styles), so cards can be pasted in any order.
Rebuilt from the Milestone 2 PDF on sooi-s1-embed conventions. sooi-s2-embed-v2.html was not
available in this session, so component class names may differ from v2 — diff before replacing.
NEW components (no S1 precedent, pending Jerry's CMS review): intro box, threat cards, stage rows,
stage pipeline, recommendation cards, closing callout, citations list.
v6 = 5 self-contained HTML cards around 4 native Ghost H2 heading blocks (navigable).
v4 = styling pass (no copy changes): peach risk cards/cells, mint intervention cells,
blue pipeline bands + tag chips (S1 .oi precedent), yellow accents on black boxes.
Section images (Unsplash) are print-layout only and omitted; add via CMS if wanted.
============================================================= -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<!-- BW Gradual (headings) is loaded by the site; the embed inherits it. -->
<style>
/* ================= BRAND TOKENS =================
   Copied verbatim from sooi-s1-embed.html. Edit ONLY this block to re-theme.
   ================================================= */
.sooi-s2{--bg:transparent;--text:#000000;--text-secondary:#262626;--text-tertiary:#6f6f6f;
    --border:#e6e4df;--border-light:#f0efec;
    /* IOI brand. Blue is FILL-ONLY (2.1:1 on white as text); numbers & links are black, per site. */
    --accent:#000000;--accent-light:#d9f0fc;
    --brand-yellow:#ffde17;--brand-mint:#83fed1;--brand-blue:#69b3f2;--brand-peach:#ffbea1;
    --card-bg:#ffffff;--highlight:#fdf6e3;
    /* No red in IOI palette: risk maps to peach backgrounds with black text. */
    --risk-critical:#000000;--risk-critical-bg:#fff1e6;--risk-high:#262626;--risk-high-bg:#ffe9d6;--risk-low:#262626;--risk-low-bg:#dcfbee;
    --direct:#69b3f2;--adjacent:#9aeef7;--adoption:#b6fcdf;--unknown:#e6e4df;
    --ops:#ffbea1;--rnd:#69b3f2;--other:#e6e4df;--land:#ecebe7}
.sooi-s2 *{margin:0;padding:0;box-sizing:border-box}
.sooi-s2{font-family:'Inter',var(--site-body-font,sans-serif);color:var(--text);line-height:1.6;-webkit-font-smoothing:antialiased;max-width:1080px;margin:0 auto;padding:8px 0 40px}
.sooi-s2 .lede{font-size:16px;color:var(--text-secondary);max-width:760px;line-height:1.7}
.sooi-s2 .lede + .lede{margin-top:14px}
.sooi-s2 .cut{border-top:1px solid var(--border-light);margin-top:52px;padding-top:38px}
.sooi-s2 .cut-num{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;letter-spacing:2px;color:var(--text-tertiary);text-transform:uppercase;margin-bottom:6px}
.sooi-s2 .cut-intro{font-size:15px;color:var(--text-secondary);max-width:740px;margin-bottom:22px}
.sooi-s2 .caveat{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);background:#fff;border:1px dashed var(--border);border-radius:6px;padding:8px 12px;margin-top:14px;line-height:1.5}
.sooi-s2 .door{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--accent);margin-top:18px;display:flex;align-items:center;gap:8px}
.sooi-s2 .door::before{content:'→'}
/* spacing after bare headings: styles the following element, never the heading */
.sooi-s2 h2 + p,.sooi-s2 h2 + div,.sooi-s2 h3 + p,.sooi-s2 h3 + div{margin-top:10px}
.sooi-s2 .subhead{margin-top:44px;margin-bottom:0}
/* figure labels + notes (new, minor) */
.sooi-s2 .fig{margin-top:30px}
.sooi-s2 .fig-title{font-size:15px;font-weight:600;color:var(--text);margin-bottom:12px}
.sooi-s2 .fig-note{font-size:12px;color:var(--text-tertiary);line-height:1.5;margin-top:12px;max-width:820px}
/* pull quote (new component) */
.sooi-s2 .pullquote{margin:44px 0;max-width:640px}
.sooi-s2 .pullquote .marks{display:flex;gap:6px;margin-bottom:14px}
.sooi-s2 .pullquote .marks span{display:block;height:10px;border-radius:5px}
.sooi-s2 .pullquote .marks .m1{width:32px;background:#000}
.sooi-s2 .pullquote .marks .m2{width:18px;background:var(--brand-yellow)}
.sooi-s2 .pullquote .marks .m3{width:10px;background:var(--adjacent)}
.sooi-s2 .pullquote p{font-size:22px;font-weight:700;line-height:1.3;color:var(--text)}
/* ---- defensive reset: site link styles ---- */
.sooi-s2 a{color:var(--text) !important;background:transparent !important;border:0 !important;box-shadow:none !important;
  text-decoration:underline !important;text-decoration-color:var(--brand-yellow) !important;text-decoration-thickness:2px !important;text-underline-offset:3px;overflow-wrap:anywhere}
.sooi-s2 a:hover{text-decoration-color:var(--text) !important}
.sooi-s2 sup{font-size:.7em;line-height:0;vertical-align:super}
.sooi-s2 sup a{text-decoration:none !important}
.sooi-s2 .footnotes{list-style:none;margin-top:28px;border-top:1px solid var(--border-light);padding-top:12px;font-size:12px;color:var(--text-tertiary)}
.sooi-s2 .footnotes li{margin-bottom:4px}
/* intro box — IOI Black (new) */
.sooi-s2 .threats,.sooi-s2 .stages{margin-top:6px !important}
.sooi-s2 .intro-box{background:#000;color:#fff;border-radius:8px;padding:28px 32px 28px 30px;font-size:17px;line-height:1.65;max-width:820px;margin:0 0 8px auto;border-left:8px solid var(--brand-yellow)}
/* threat cards (new) */
.sooi-s2 .threats{display:grid;grid-template-columns:1fr 1fr;gap:28px 40px;margin-top:22px}
.sooi-s2 .threat{background:var(--risk-critical-bg);border:1px solid var(--brand-peach);border-top:6px solid #000;border-radius:10px;padding:22px 24px}
.sooi-s2 .threat h3{font-size:18px;font-weight:600;line-height:1.3;margin-bottom:8px}
.sooi-s2 .threat p{font-size:14px;color:var(--text-secondary);line-height:1.55}
.sooi-s2 .threats{gap:18px}
/* stage rows (new) */
.sooi-s2 .stages{margin-top:22px}
.sooi-s2 .stage{display:grid;grid-template-columns:190px 230px 1fr;gap:16px;border-top:2px solid #000;padding:20px 0}
.sooi-s2 .stage .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:44px;font-weight:700;color:var(--text);line-height:1}
.sooi-s2 .stage h3{font-size:18px;font-weight:600;margin:14px 0 4px}
.sooi-s2 .stage .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .stage .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
.sooi-s2 .chip{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;font-weight:600;background:var(--accent-light);color:var(--accent);padding:2px 8px;border-radius:3px}
.sooi-s2 .stage .cell{border-radius:8px;padding:14px 16px}
.sooi-s2 .stage .cell.r{background:var(--risk-critical-bg);border-left:4px solid var(--brand-peach)}
.sooi-s2 .stage .cell.i{background:var(--risk-low-bg);border-left:4px solid var(--brand-mint)}
.sooi-s2 .stage .k{font-size:10px;letter-spacing:1.5px;text-transform:uppercase;font-weight:700;margin-bottom:4px}
.sooi-s2 .stage .risk{font-size:14px;font-weight:600;line-height:1.45}
.sooi-s2 .stage .int{font-size:14px;color:var(--text-secondary);line-height:1.6}
/* stage pipeline (new) */
.sooi-s2 .chain{display:grid;grid-template-columns:repeat(4,1fr);border:1px solid var(--border);border-radius:10px;overflow:hidden}
.sooi-s2 .chain-step{background:var(--card-bg);padding:0 0 18px;border-right:1px solid var(--border);position:relative}
.sooi-s2 .chain-step > div{padding:0 18px}
.sooi-s2 .chain-step:not(:last-child)::after{content:'→';position:absolute;right:-11px;top:19px;width:22px;height:22px;border-radius:50%;background:#000;color:var(--brand-yellow);font-size:12px;line-height:22px;text-align:center;z-index:1}
.sooi-s2 .chain-step:last-child{border-right:0}
.sooi-s2 .chain{overflow:visible}
.sooi-s2 .chain-step:first-child{border-radius:10px 0 0 10px}
.sooi-s2 .chain-step:last-child{border-radius:0 10px 10px 0}
.sooi-s2 .chain-step .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:26px;font-weight:700;color:#000;background:var(--brand-blue);padding:12px 18px !important;margin-bottom:12px;border-radius:inherit;border-bottom-left-radius:0;border-bottom-right-radius:0}
.sooi-s2 .chain-step .name{font-size:17px;font-weight:600;margin:2px 0 4px}
.sooi-s2 .chain-step .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .chain-step .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
/* recommendations (new) */
.sooi-s2 .lead-strong{font-size:19px;font-weight:600;line-height:1.45;max-width:760px;margin-top:24px;color:var(--text)}
.sooi-s2 .lead-strong span{background:linear-gradient(transparent 62%,var(--brand-yellow) 62%)}
.sooi-s2 .recs{display:grid;grid-template-columns:repeat(3,1fr);gap:24px;margin-top:24px}
.sooi-s2 .rec{background:var(--accent-light);border-top:6px solid var(--brand-blue);border-radius:10px;padding:20px 22px}
.sooi-s2 .rec .rk{font-size:16px;font-weight:700;line-height:1.3;margin-bottom:8px}
.sooi-s2 .rec p{font-size:14px;color:var(--text-secondary);line-height:1.55}
/* closing callout — IOI Black (new) */
.sooi-s2 .closing{background:#000;color:#fff;border-radius:12px;padding:28px 32px 28px 30px;margin-top:28px;font-size:16px;line-height:1.65;border-left:8px solid var(--brand-yellow)}
/* citations (new) */
.sooi-s2 .cites{list-style:none;margin-top:10px}
.sooi-s2 .cites li{font-size:13px;color:var(--text-secondary);line-height:1.55;padding:10px 0;border-bottom:1px solid var(--border-light)}
.sooi-s2 .cites li:last-child{border-bottom:0}

/* ---- responsive ---- */
@media (max-width: 900px){
  .sooi-s2 .threats{grid-template-columns:1fr}
  .sooi-s2 .stage{grid-template-columns:1fr;gap:12px}
  .sooi-s2 .stage h3{margin-top:8px}
  .sooi-s2 .chain{grid-template-columns:1fr 1fr}
  .sooi-s2 .chain-step::after{display:none}
  .sooi-s2 .chain-step{border-radius:0 !important}
  .sooi-s2 .chain{overflow:hidden}
  .sooi-s2 .chain-step:nth-child(2){border-right:0}
  .sooi-s2 .chain-step:nth-child(-n+2){border-bottom:1px solid var(--border)}
  .sooi-s2 .recs{grid-template-columns:1fr}
}
@media (max-width: 640px){
  .sooi-s2 .pullquote p{font-size:18px}
  .sooi-s2 .intro-box{padding:22px 20px;font-size:16px}
  .sooi-s2 .closing{padding:22px 20px}
  .sooi-s2 .lead-strong{font-size:17px}
}
@media (max-width: 420px){
  .sooi-s2 .chain{grid-template-columns:1fr}
  .sooi-s2 .chain-step{border-right:0;border-bottom:1px solid var(--border)}
  .sooi-s2 .chain-step:last-child{border-bottom:0}
}
</style>
<div class="sooi-s2">
<p class="cut-intro">Generative AI lowers the cost of producing poor-quality and fraudulent research by orders of magnitude. Research integrity, trust in science, and the foundations of how we communicate knowledge are at risk. As this analysis shows, we already have the infrastructure we need to face this risk — but only if it’s adequately funded, adopted, and maintained. Free to use does not mean free to run.</p>
  <p class="lead-strong"><span>Funders, institutions, and libraries must sustain tools that help to ensure research integrity. Sustained investment ensures the shared, open foundations that the entire research ecosystem depends on.</span></p>
  <div class="recs">
    <div class="rec"><div class="rk">Build PIDs into policy.</div><p>Top-down requirements from public and private funders can help to build adoption. Mandate ORCID iDs for PIs and co-investigators, ROR IDs for all named institutions, and DOIs for funded datasets and outputs.</p></div>
    <div class="rec"><div class="rk">Fund the infrastructure directly, not just the research it supports.</div><p>Infrastructures like ORCID, ROR, DataCite, Crossref, and Dryad are largely nonprofit, community governed, and chronically underfunded relative to how much the research ecosystem depends on them. Fund institutional memberships rather than passing off costs to researchers to absorb individually.</p></div>
    <div class="rec"><div class="rk">Treat open infrastructure maintenance as a budget line, not a one-time subscription.</div><p>Sustained, multi-year commitments allow open infrastructure to plan capacity to keep pace with AI-driven changes.</p></div>
  </div>
  <div class="closing">Scholarly communications relies on shared open infrastructure to provide critical integrity functions. This infrastructure works because it’s shared, which means its cost has to be shared too. Sustained, coordinated investment from funders, institutions, and publishers is what keeps identity, affiliation, data, and citation infrastructure ahead of AI-driven risks that impact the entire knowledge ecosystem.</div>
</div>
<!--kg-card-end: html-->
<h2 id="works-cited">Works Cited</h2>
<!--kg-card-begin: html-->
<!-- ============================================================
SoOI 2026 · Section 2 (The infrastructure of integrity) · v8 · card 5 of 5 · CMS embed
Source text: "State of Open Infrastructure 2026 (Milestone 2)" PDF.
Paste into an HTML block/card. Self-contained & scoped: all styles
apply only inside .sooi-s2 and cannot leak into site styles.
Fonts: loads Inter from Google Fonts; BW Gradual (headings) inherits from the site.
If the site already loads these (check site <head>), delete the
<link> line to avoid a duplicate request.
Page title + subtitle are owned by the CMS template (not in this block).
CARD 5 of 5 — citations. Paste this WHOLE file into one Ghost HTML card.
Ghost H2 block ABOVE this card: Works Cited
Last S2 block on the page.
Each card is self-contained (own font link + styles), so cards can be pasted in any order.
Rebuilt from the Milestone 2 PDF on sooi-s1-embed conventions. sooi-s2-embed-v2.html was not
available in this session, so component class names may differ from v2 — diff before replacing.
NEW components (no S1 precedent, pending Jerry's CMS review): intro box, threat cards, stage rows,
stage pipeline, recommendation cards, closing callout, citations list.
v8 = list + link-weight defensive reset (references). v6 = 5 self-contained HTML cards around 4 native Ghost H2 heading blocks (navigable).
v4 = styling pass (no copy changes): peach risk cards/cells, mint intervention cells,
blue pipeline bands + tag chips (S1 .oi precedent), yellow accents on black boxes.
Section images (Unsplash) are print-layout only and omitted; add via CMS if wanted.
============================================================= -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<!-- BW Gradual (headings) is loaded by the site; the embed inherits it. -->
<style>
/* ================= BRAND TOKENS =================
   Copied verbatim from sooi-s1-embed.html. Edit ONLY this block to re-theme.
   ================================================= */
.sooi-s2{--bg:transparent;--text:#000000;--text-secondary:#262626;--text-tertiary:#6f6f6f;
    --border:#e6e4df;--border-light:#f0efec;
    /* IOI brand. Blue is FILL-ONLY (2.1:1 on white as text); numbers & links are black, per site. */
    --accent:#000000;--accent-light:#d9f0fc;
    --brand-yellow:#ffde17;--brand-mint:#83fed1;--brand-blue:#69b3f2;--brand-peach:#ffbea1;
    --card-bg:#ffffff;--highlight:#fdf6e3;
    /* No red in IOI palette: risk maps to peach backgrounds with black text. */
    --risk-critical:#000000;--risk-critical-bg:#fff1e6;--risk-high:#262626;--risk-high-bg:#ffe9d6;--risk-low:#262626;--risk-low-bg:#dcfbee;
    --direct:#69b3f2;--adjacent:#9aeef7;--adoption:#b6fcdf;--unknown:#e6e4df;
    --ops:#ffbea1;--rnd:#69b3f2;--other:#e6e4df;--land:#ecebe7}
.sooi-s2 *{margin:0;padding:0;box-sizing:border-box}
.sooi-s2{font-family:'Inter',var(--site-body-font,sans-serif);color:var(--text);line-height:1.6;-webkit-font-smoothing:antialiased;max-width:1080px;margin:0 auto;padding:8px 0 40px}
.sooi-s2 .lede{font-size:16px;color:var(--text-secondary);max-width:760px;line-height:1.7}
.sooi-s2 .lede + .lede{margin-top:14px}
.sooi-s2 .cut{border-top:1px solid var(--border-light);margin-top:52px;padding-top:38px}
.sooi-s2 .cut-num{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;letter-spacing:2px;color:var(--text-tertiary);text-transform:uppercase;margin-bottom:6px}
.sooi-s2 .cut-intro{font-size:15px;color:var(--text-secondary);max-width:740px;margin-bottom:22px}
.sooi-s2 .caveat{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;color:var(--text-tertiary);background:#fff;border:1px dashed var(--border);border-radius:6px;padding:8px 12px;margin-top:14px;line-height:1.5}
.sooi-s2 .door{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:12px;color:var(--accent);margin-top:18px;display:flex;align-items:center;gap:8px}
.sooi-s2 .door::before{content:'→'}
/* spacing after bare headings: styles the following element, never the heading */
.sooi-s2 h2 + p,.sooi-s2 h2 + div,.sooi-s2 h3 + p,.sooi-s2 h3 + div{margin-top:10px}
.sooi-s2 .subhead{margin-top:44px;margin-bottom:0}
/* figure labels + notes (new, minor) */
.sooi-s2 .fig{margin-top:30px}
.sooi-s2 .fig-title{font-size:15px;font-weight:600;color:var(--text);margin-bottom:12px}
.sooi-s2 .fig-note{font-size:12px;color:var(--text-tertiary);line-height:1.5;margin-top:12px;max-width:820px}
/* pull quote (new component) */
.sooi-s2 .pullquote{margin:44px 0;max-width:640px}
.sooi-s2 .pullquote .marks{display:flex;gap:6px;margin-bottom:14px}
.sooi-s2 .pullquote .marks span{display:block;height:10px;border-radius:5px}
.sooi-s2 .pullquote .marks .m1{width:32px;background:#000}
.sooi-s2 .pullquote .marks .m2{width:18px;background:var(--brand-yellow)}
.sooi-s2 .pullquote .marks .m3{width:10px;background:var(--adjacent)}
.sooi-s2 .pullquote p{font-size:22px;font-weight:700;line-height:1.3;color:var(--text)}
/* ---- defensive reset: site link styles ---- */
.sooi-s2 a{color:var(--text) !important;font-weight:inherit !important;background:transparent !important;border:0 !important;box-shadow:none !important;
  text-decoration:underline !important;text-decoration-color:var(--brand-yellow) !important;text-decoration-thickness:2px !important;text-underline-offset:3px;overflow-wrap:anywhere}
.sooi-s2 a:hover{text-decoration-color:var(--text) !important}
.sooi-s2 sup{font-size:.7em;line-height:0;vertical-align:super}
.sooi-s2 sup a{text-decoration:none !important}
.sooi-s2 .footnotes{list-style:none !important;margin-top:28px !important;border-top:1px solid var(--border-light) !important;padding-top:12px !important;font-size:12px !important;color:var(--text-tertiary) !important}
.sooi-s2 .footnotes li{margin-bottom:4px !important}
/* ---- defensive reset: site list styles (ol/ul/li) bleed into references & lists ---- */
.sooi-s2 ol,.sooi-s2 ul{list-style:none !important;margin:0 !important;padding:0 !important;background:transparent !important;border:0 !important;box-shadow:none !important;counter-reset:none !important}
.sooi-s2 li{list-style:none !important;margin:0 !important;padding:0 !important;background:transparent !important;border:0 !important;box-shadow:none !important;text-indent:0 !important;font-size:inherit !important;line-height:inherit !important;color:inherit !important}
.sooi-s2 li::marker{content:none !important}
.sooi-s2 li::before,.sooi-s2 li::after{content:none !important;display:none !important}
/* intro box — IOI Black (new) */
.sooi-s2 .threats,.sooi-s2 .stages{margin-top:6px !important}
.sooi-s2 .intro-box{background:#000;color:#fff;border-radius:8px;padding:28px 32px 28px 30px;font-size:17px;line-height:1.65;max-width:820px;margin:0 0 8px auto;border-left:8px solid var(--brand-yellow)}
/* threat cards (new) */
.sooi-s2 .threats{display:grid;grid-template-columns:1fr 1fr;gap:28px 40px;margin-top:22px}
.sooi-s2 .threat{background:var(--risk-critical-bg);border:1px solid var(--brand-peach);border-top:6px solid #000;border-radius:10px;padding:22px 24px}
.sooi-s2 .threat h3{font-size:18px;font-weight:600;line-height:1.3;margin-bottom:8px}
.sooi-s2 .threat p{font-size:14px;color:var(--text-secondary);line-height:1.55}
.sooi-s2 .threats{gap:18px}
/* stage rows (new) */
.sooi-s2 .stages{margin-top:22px}
.sooi-s2 .stage{display:grid;grid-template-columns:190px 230px 1fr;gap:16px;border-top:2px solid #000;padding:20px 0}
.sooi-s2 .stage .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:44px;font-weight:700;color:var(--text);line-height:1}
.sooi-s2 .stage h3{font-size:18px;font-weight:600;margin:14px 0 4px}
.sooi-s2 .stage .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .stage .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
.sooi-s2 .chip{font-family:'Inter',var(--site-mono-font,sans-serif);font-size:11px;font-weight:600;background:var(--accent-light);color:var(--accent);padding:2px 8px;border-radius:3px}
.sooi-s2 .stage .cell{border-radius:8px;padding:14px 16px}
.sooi-s2 .stage .cell.r{background:var(--risk-critical-bg);border-left:4px solid var(--brand-peach)}
.sooi-s2 .stage .cell.i{background:var(--risk-low-bg);border-left:4px solid var(--brand-mint)}
.sooi-s2 .stage .k{font-size:10px;letter-spacing:1.5px;text-transform:uppercase;font-weight:700;margin-bottom:4px}
.sooi-s2 .stage .risk{font-size:14px;font-weight:600;line-height:1.45}
.sooi-s2 .stage .int{font-size:14px;color:var(--text-secondary);line-height:1.6}
/* stage pipeline (new) */
.sooi-s2 .chain{display:grid;grid-template-columns:repeat(4,1fr);border:1px solid var(--border);border-radius:10px;overflow:hidden}
.sooi-s2 .chain-step{background:var(--card-bg);padding:0 0 18px;border-right:1px solid var(--border);position:relative}
.sooi-s2 .chain-step > div{padding:0 18px}
.sooi-s2 .chain-step:not(:last-child)::after{content:'→';position:absolute;right:-11px;top:19px;width:22px;height:22px;border-radius:50%;background:#000;color:var(--brand-yellow);font-size:12px;line-height:22px;text-align:center;z-index:1}
.sooi-s2 .chain-step:last-child{border-right:0}
.sooi-s2 .chain{overflow:visible}
.sooi-s2 .chain-step:first-child{border-radius:10px 0 0 10px}
.sooi-s2 .chain-step:last-child{border-radius:0 10px 10px 0}
.sooi-s2 .chain-step .num{font-family:'BW Gradual','Inter',var(--site-heading-font,sans-serif);font-size:26px;font-weight:700;color:#000;background:var(--brand-blue);padding:12px 18px !important;margin-bottom:12px;border-radius:inherit;border-bottom-left-radius:0;border-bottom-right-radius:0}
.sooi-s2 .chain-step .name{font-size:17px;font-weight:600;margin:2px 0 4px}
.sooi-s2 .chain-step .q{font-size:13px;color:var(--text-secondary);line-height:1.4}
.sooi-s2 .chain-step .tag{margin-top:10px;display:flex;flex-wrap:wrap;gap:4px}
/* recommendations (new) */
.sooi-s2 .lead-strong{font-size:19px;font-weight:600;line-height:1.45;max-width:760px;margin-top:24px;color:var(--text)}
.sooi-s2 .lead-strong span{background:linear-gradient(transparent 62%,var(--brand-yellow) 62%)}
.sooi-s2 .recs{display:grid;grid-template-columns:repeat(3,1fr);gap:24px;margin-top:24px}
.sooi-s2 .rec{background:var(--accent-light);border-top:6px solid var(--brand-blue);border-radius:10px;padding:20px 22px}
.sooi-s2 .rec .rk{font-size:16px;font-weight:700;line-height:1.3;margin-bottom:8px}
.sooi-s2 .rec p{font-size:14px;color:var(--text-secondary);line-height:1.55}
/* closing callout — IOI Black (new) */
.sooi-s2 .closing{background:#000;color:#fff;border-radius:12px;padding:28px 32px 28px 30px;margin-top:28px;font-size:16px;line-height:1.65;border-left:8px solid var(--brand-yellow)}
/* citations (new) */
.sooi-s2 .cites{list-style:none !important;margin-top:10px !important}
.sooi-s2 .cites li{font-size:13px !important;color:var(--text-secondary) !important;line-height:1.55 !important;padding:10px 0 !important;border-bottom:1px solid var(--border-light) !important}
.sooi-s2 .cites li:last-child{border-bottom:0 !important}

/* ---- responsive ---- */
@media (max-width: 900px){
  .sooi-s2 .threats{grid-template-columns:1fr}
  .sooi-s2 .stage{grid-template-columns:1fr;gap:12px}
  .sooi-s2 .stage h3{margin-top:8px}
  .sooi-s2 .chain{grid-template-columns:1fr 1fr}
  .sooi-s2 .chain-step::after{display:none}
  .sooi-s2 .chain-step{border-radius:0 !important}
  .sooi-s2 .chain{overflow:hidden}
  .sooi-s2 .chain-step:nth-child(2){border-right:0}
  .sooi-s2 .chain-step:nth-child(-n+2){border-bottom:1px solid var(--border)}
  .sooi-s2 .recs{grid-template-columns:1fr}
}
@media (max-width: 640px){
  .sooi-s2 .pullquote p{font-size:18px}
  .sooi-s2 .intro-box{padding:22px 20px;font-size:16px}
  .sooi-s2 .closing{padding:22px 20px}
  .sooi-s2 .lead-strong{font-size:17px}
}
@media (max-width: 420px){
  .sooi-s2 .chain{grid-template-columns:1fr}
  .sooi-s2 .chain-step{border-right:0;border-bottom:1px solid var(--border)}
  .sooi-s2 .chain-step:last-child{border-bottom:0}
}
</style>
<div class="sooi-s2">
<!-- URLs for Grove and Singh were re-joined across PDF line breaks (hyphens restored). Click-test before publish. -->
  <ol class="cites">
    <li>Grove, Jack. (2023, February 2). Identity theft victims back legal action against journals. Times Higher Education (THE). <a href="https://www.timeshighereducation.com/news/identity-theft-victims-back-legal-action-against-journals?ref=investinopen.org" target="_blank" rel="noopener">https://www.timeshighereducation.com/news/identity-theft-victims-back-legal-action-against-journals</a></li>
    <li>Richardson, Reese A. K., Hong, Spencer S., Byrne, Jennifer A., Stoeger, Thomas, &amp; Amaral, Luís A. Nunes. (2025, August 12). The entities enabling scientific fraud at scale are large, resilient, and growing rapidly. Proceedings of the National Academy of Sciences (PNAS). <a href="https://pubmed.ncbi.nlm.nih.gov/40758886/?ref=investinopen.org" target="_blank" rel="noopener">https://pubmed.ncbi.nlm.nih.gov/40758886/</a></li>
    <li>Singh, Ranjit. (2025, October 30). On arXiv, an Influx of AI Slop Pits Surface Against Substance. Data &amp; Society. <a href="https://datasociety.net/research-library/on-arxiv-an-influx-of-ai-slop-pits-surface-against-substance/?ref=investinopen.org" target="_blank" rel="noopener">https://datasociety.net/research-library/on-arxiv-an-influx-of-ai-slop-pits-surface-against-substance/</a></li>
    <li>Zhao, Zhenyue, Wang, Yihe, Stuart, Toby, De Vaan, Mathijs, Ginsparg, Paul, &amp; Yin, Yian. (2026, May 8). LLM hallucinations in the wild: Large-scale evidence from non-existent citations. arXiv. <a href="https://arxiv.org/pdf/2605.07723?ref=investinopen.org" target="_blank" rel="noopener">https://arxiv.org/pdf/2605.07723</a></li>
  </ol>
</div>
<!--kg-card-end: html-->
 ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ Making rescued data usable, starting with wildfire ]]></title>
        <description><![CDATA[ IOI&#39;s new prototype that uses wildfire data to explore how we can move from data rescue to data resilience ]]></description>
        <link>https://investinopen.org/blog/making-rescued-data-usable-starting-with-wildfire/</link>
        <guid isPermaLink="false">6ab3e40024038a0001d4ea12</guid>
        <category><![CDATA[ Blog ]]></category>
        <dc:creator><![CDATA[ Kaitlin Thaney ]]></dc:creator>
        <pubDate>Thu, 24 Sep 2026 11:24:27 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ <p>We're proud to launch, as part of Climate Week and the UN General Assembly's High-Level Week, a proof-of-concept built on and with existing open infrastructures to more closely prod at some of the technical implementation and usability questions in the data rescue space once the data is preserved.&nbsp;&nbsp;</p><p>We wanted to move from strategic planning and naming of technical considerations to testing approaches in a tangible way – and we’re excited to share more about what we’ve been working on as a first attempt at answering some of the questions we believe the data rescue movement hasn’t fully tackled yet, including what happens once the data is rescued. This work sits alongside countless efforts and existing open data infrastructure solutions working to mirror, host, improve discoverability, and map out intersection points, and is designed to test a few assumptions before committing to a full build and catalyze further action.&nbsp;</p><p>We started with a few baseline questions such as once critical scientific data is saved from disappearing, how do you actually make it usable again, by the people who need it most, across the many disciplines a real emergency touches? And what does it look like to build with and across existing open data infrastructures and repositories in a networked way, without duplication and without them colliding with each other? The in-between reality is even messier to follow. Data rarely goes dark all at once. Some federal sources stay up while others disappear, some come back, some are replaced quietly with something incomplete. What does a workable interim solution look like when the picture is that uneven, rather than a clean before and after?</p><p>Back in June, <a href="https://www.linkedin.com/pulse/building-long-run-just-crisis-kaitlin-thaney-txdhc/?ref=investinopen.org"><u>we wrote about</u></a> what it actually looks like when the dependencies underneath research break down. That piece used <a href="https://www.npr.org/2026/06/12/nx-s1-5819899/president-trump-is-taking-aim-at-forest-and-wildfire-research-just-as-the-west-is-poised-to-burn?ref=investinopen.org"><u>the example of wildfire smoke maps in Ruidoso, New Mexico</u></a>, tools that help people figure out where smoke is drifting and which immunocompromised neighbors might be at risk, built with Forest Service research funding that was, at the time, disappearing in real time. It ended with a promise – that we were starting to build what we refer to as an “existence proof”, a working demonstration of what a genuinely open, federated infrastructure solution that draws on existing investments in open data could look like for this class of problem.&nbsp;</p><p>Today we want to share more about that proof, in its first form – and why we’re taking the approach we are (and what we’re learning).</p><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/09/ro-kazui-kvmzDvbjrYg-unsplash-2.jpg" class="kg-image" alt="" loading="lazy" width="2000" height="1333" srcset="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w600/2026/09/ro-kazui-kvmzDvbjrYg-unsplash-2.jpg 600w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w1000/2026/09/ro-kazui-kvmzDvbjrYg-unsplash-2.jpg 1000w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w1600/2026/09/ro-kazui-kvmzDvbjrYg-unsplash-2.jpg 1600w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w2400/2026/09/ro-kazui-kvmzDvbjrYg-unsplash-2.jpg 2400w" sizes="(min-width: 720px) 720px"><figcaption><span style="white-space: pre-wrap;">Photo by </span><a href="https://unsplash.com/@rokazuiii?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><span style="white-space: pre-wrap;">RO Kazui</span></a><span style="white-space: pre-wrap;"> on </span><a href="https://unsplash.com/photos/a-large-fire-is-burning-in-a-field-kvmzDvbjrYg?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><span style="white-space: pre-wrap;">Unsplash</span></a></figcaption></figure><h3 id="a-focus-on-wildfire-as-a-start"><strong>A focus on wildfire (as a start)&nbsp;</strong></h3><p>We picked wildfire as our test case for a simple reason. It's emblematic of a rare data problem that everyone already understands is urgent – and that by its very nature involves users and data sources beyond traditional academic research walls. The story underneath is bigger than fire. It's about whether we can build a system that pulls from many different data sources, disciplines, and infrastructures at once and keeps answering questions even when one of those sources goes dark, whether that's a NOAA smoke feed in New Mexico, public health data or a Forest Service research dataset losing its funding mid stream, or something in between where one agency's data is fine and its neighbor's isn't.&nbsp;</p><p>There’s some interesting aspects in querying data across a variety of sources, mirroring of data if a source goes dark, and also perhaps a bigger question (as we at IOI look to drive more attention and investment to data infrastructures and the organisations behind them) – is the data being rescued usable and getting into the hands of those who need it most?&nbsp;</p><p>As we built the proof-of-concept, we spoke with volunteer firefighters and emergency managers about what they actually rely on today. One collaborator, a volunteer firefighter and emergency manager in Colorado, put it plainly.</p><p>"There is very little data analysis in emergency management and the fire service, and relatively little technical expertise. Nobody writes code. In essence the role of Emergency Management during an emergency is to create and support a human decision making and information dissemination machine that is not reliant on digital technologies."</p><p>He sent us a photo of his department's map binder. It was dated 2011.</p><p>Between that binder and the Ruidoso smoke maps sit a whole range of reasons to rethink data resilience, from someone deciding whether it's safe to send their kid outside, to a department trying to get better information than a fifteen year old paper map during an active incident. A wildfire scenario forces you to reckon with weather, terrain, vegetation, public health, energy infrastructure, and socioeconomic data all at once. That cross domain assembly problem is exactly what a resilient data system needs to be able to handle, and it's much easier to make it real through a scenario like this than to explain in the abstract.</p><h3 id="the-gap-were-responding-to"><strong>The gap we're responding to</strong></h3><p>Over the past year and a half, IOI has been a part of a series of coalitions that have mobilized to rescue federal data at risk from funding cuts, policy changes, and takedowns and design new approaches and business models to build back better. This has included collaborations with groups convened by the Center for Open Science, the American Geophysical Union, the Internet Archive, Data Rescue Project, Public Environmental Data Partners, <a href="http://source.coop/?ref=investinopen.org"><u>Source.coop</u></a>, Dryad, ICPSR, our own mappings of over 87 initiatives and collaboration efforts, and that’s just scratching the surface.&nbsp;</p><p>That work has mattered, and it continues to matter. Efforts are shifting from saving bytes, archiving copies, and moving data somewhere safer to starting to explore what’s next. At IOI, we’re working to do our part to push on the infrastructure elements we know best . We’re building on and with existing investments in open data and repository infrastructure, looking at where we can (and need to) build better given geopolitical and funding volatility, and making the case for increased resourcing for these critical systems at a time we need to increase speed, not lose momentum.&nbsp;</p><p>Some of what's been rescued so far is now sitting in archives without stable identifiers, consistent metadata, or any clear sense of who maintains access to it over time. That's not a criticism of the people doing that work, most of it has been done under real duress, on volunteer time. It's a reflection of where the investment has and hasn't gone, and where we think it needs to go next.</p><p>We watched something similar happen after COVID. A wave of energy moved toward open science, shared data, and collective infrastructure. Much of that energy receded once the acute phase passed, and a lot of research and discovery drifted back toward business as usual. We can't afford for critical scientific and disaster response data to make the same round trip, especially with funding and political conditions as volatile as they are right now. The data crisis facing federally funded research isn't a moment that passes and then gets fixed. It's a structural condition, and it needs a response built to outlast any single news cycle. </p><p>We've watched ambitious plans to build a full alternative to federal data infrastructure struggle to get off the ground, not for lack of good ideas, but because replicating something at the scale of a national government system is a genuinely hard problem to solve all at once – and funders are reticent to take on that capital cost alone. So instead of trying to build the whole thing, we scoped something much smaller and testable, a working proof of concept aimed at a specific set of real questions for a timely issue we’re seeing quickly affect not just fire prone areas in North America, but across Europe and beyond.</p><h3 id="what-we-are-building"><strong>What we are building</strong></h3><p>Under the hood, this is a demonstration of what it looks like to query across existing open infrastructures as if they were one system, rather than a pile of disconnected repositories, and to do it without asking any single one of them to become the new central point of failure.</p><p>The proof-of-concept pulls from a mix of data sources chosen specifically because none of them alone can answer the questions an emergency manager actually needs answered. We’ve included data from Source Cooperative such as cloud native spatial risk data, fire perimeters, burn probability, and wetlands data, all queryable directly over the open web. Data from Dryad provides research grade, DOI backed datasets like a quality controlled multi decade wildfire database and modeled smoke exposure data, so a dataset keeps a stable, citable identity even if the agency that originally published it goes dark. Live federal feeds from NOAA and NASA FIRMS supply near real time fire detections, Red Flag Warnings, and smoke plumes, the ground truth layer that shows what's happening right now, the same category of data behind the Ruidoso smoke maps. OpenStreetMap fills in the human and built environment layer, roads, power lines, and hydrants, the pieces that matter most once you're thinking about response capacity rather than just risk. (And that’s just a sampling.)</p><p>We query across all of that using DuckDB, which can reach directly into remote data without requiring us to first copy and store it ourselves. That matters for two reasons. It keeps compute on the researcher's own machine rather than centralizing it somewhere new, and it means the project stays useful even if we, IOI, weren't around to keep something running.</p><p>Then there's the fallback layer, which is really the heart of the demo, and where the uneven, partial outage problem actually gets handled. If a source dataset becomes unavailable, whether because an agency takes it down or a server quietly disappears, the system checks whether it's already been rescued elsewhere, using the Data Rescue Project's growing catalog of known mirrors, and routes the request there instead, while everything still reachable keeps flowing through normally. If a resource isn't already archived anywhere, the same tooling passively triggers an Internet Archive capture the moment someone tries to use it, so future users aren't left stranded the way today's users so often are. This is a proxy and a small set of tools, not a new central repository. We're intentionally not trying to become the permanent home for this data. We're trying to show what the connective tissue between existing homes could look like, including in the messy middle state where some sources are healthy and others aren't.</p><h3 id="what-this-is-and-what-it-isnt"><strong>What this is, and what it isn't</strong></h3><p>This is a proof, not a product. We built it at a concentrated, testable scale specifically so we could learn quickly rather than spend years building toward something that might not hold up in practice. It's meant to sit alongside, and make more visible, the tremendous work already being done by the repositories, archives, and rescue efforts we're drawing from, not to replace or compete with any of it. And it names its gaps and tradeoffs openly rather than papering over them, because the honest accounting of what a durable version of this would actually cost is as much a part of the point as the demo itself.</p><p>What we're testing is a hypothesis. That rescued and existing open data, spread across research repositories, federal systems, and citizen science platforms, can function as one queryable, resilient system, that it can do so without duplicating effort or stepping on the infrastructure already doing this work well, and that the people who most need that data, not just researchers, but the operational people making decisions in the field, can actually get something usable out of it, even when the underlying sources are only partly working.</p><p>We think the answer so far is promising enough to be worth a much deeper investment in the infrastructure layer that data resilience work has largely skipped, the coordination layer that sits on top of and between repositories rather than inside any one of them. That layer doesn't currently exist as a shared resource, and it's still unclear who is building it. We'll be sharing more from the proof-of-concept, and what we learned building it, in the weeks ahead.</p><p>Want to learn more about getting involved or supporting our work? Contact <a href="mailto:contribute@investinopen.org" rel="noreferrer"><u>contribute</u></a><a href="mailto:contribute@investinopen.org" rel="noreferrer"><u>@investinopen.org</u></a> – we’d love to talk. <em>To take a peek under the hood, you can also check out our work in progress </em><a href="https://investinopen.github.io/ptps-wildfire-demo/?ref=investinopen.org"><em><u>here</u></em></a><em>.  </em></p> ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ Fondo de IOI para la Adopción en Redes: actualización sobre los primeros seis meses de avance de LA Referencia ]]></title>
        <description><![CDATA[ Adopción en red con una sólida base técnica. ]]></description>
        <link>https://investinopen.org/fondo-de-ioi-para-la-adopcion-en-redes-la-referencia-6meses-es/</link>
        <guid isPermaLink="false">6a91cc6aa644ab00015706dd</guid>
        <category><![CDATA[  ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Mon, 31 Aug 2026 12:30:33 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ <p><em>Este artículo también está disponible en </em><a href="https://investinopen.org/blog/ioi-fund-for-network-adoption-la-referencia-6mo-en" rel="noreferrer"><em>inglés</em></a>.</p><p>A finales de 2025, <a href="https://investinopen.org/ioi-fund/"><u>Invest in Open Infrastructure lanzó el Fondo de IOI para la Adopción en Redes</u></a>, un nuevo tipo de inversión diseñado para acelerar la adopción global de infraestructura abierta para la investigación y el intercambio de datos. En lugar de financiar herramientas individuales o instituciones aisladas, el Fondo invierte en <em>redes</em>: consorcios de instituciones e investigadores con relaciones ya establecidas, una gobernanza activa de sus miembros y un compromiso demostrado con la ciencia abierta. La lógica es que fortalecer la infraestructura compartida que una red ya opera puede multiplicar el impacto en todas sus instituciones miembro al mismo tiempo.</p><p>El Fondo surgió del diálogo directo con las comunidades de investigación para identificar los proyectos de infraestructura abierta que más necesitan apoyo sostenido, y reúne contribuciones de un grupo de financiadores interesados en fortalecer el ecosistema global de investigación abierta. Cada red seleccionada recibe hasta 1,5 millones de dólares durante un período de dos a tres años, junto con apoyo continuo del equipo de IOI para la implementación en ámbitos como gobernanza, participación comunitaria y modelos de negocio. El objetivo de IOI con el Fondo no es solamente permitir que las organizaciones beneficiarias desarrollen proyectos capaces de generar un gran impacto en sus redes, sino también contribuir a la resiliencia de esas redes mucho después de finalizada la subvención.</p><p><a href="https://investinopen.org/our-work/la-referencia/"><u>LA Referencia</u></a> fue seleccionada como una de las dos primeras beneficiarias del Fondo, <a href="https://investinopen.org/blog/empowering-networks-advancing-openness-invest-in-open-infrastructure-announces-inaugural-grantees-of-the-ioi-fund-for-network-adoption/"><u>entre más de 100 postulaciones provenientes de 22 países</u></a>. En conjunto, las dos primeras organizaciones beneficiarias del Fondo están en condiciones de beneficiar a más de 1.300 instituciones de investigación en 36 países de América Latina y África. Este artículo ofrece una visión general de lo que LA Referencia ha realizado durante los primeros seis meses de esta inversión. En los próximos meses publicaremos también una actualización sobre la otra organización beneficiaria inaugural, UbuntuNet Alliance.</p><figure class="kg-card kg-image-card"><img src="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/08/lareferencia.png" class="kg-image" alt="Logo de LA Referencia" loading="lazy" width="1038" height="240" srcset="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w600/2026/08/lareferencia.png 600w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w1000/2026/08/lareferencia.png 1000w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/08/lareferencia.png 1038w" sizes="(min-width: 720px) 720px"></figure><h1 id="introducci%C3%B3n-al-proyecto-de-la-referencia"><strong>Introducción al proyecto de LA Referencia</strong></h1><p>LA Referencia es una red regional de cooperación que agrega y proporciona infraestructura de&nbsp; acceso abierto a la producción académica y científica de repositorios nacionales de América Latina y España, basada en un modelo de gobernanza federada y en una infraestructura de propiedad pública y no comercial. Con el apoyo del Fondo de IOI, LA Referencia está desarrollando un proyecto para el período 2026–2028 destinado a ampliar el alcance regional y la profundidad técnica de esta infraestructura mediante cuatro grandes objetivos: incorporar más países y repositorios a la red, modernizar la forma en que los investigadores descubren contenidos en múltiples idiomas, construir un sistema soberano y verificable de identificadores persistentes y poner en marcha un repositorio regional compartido junto con un programa de capacitación para datos de investigación. El avance completo del proyecto está documentado en detalle en el <a href="https://la-referencia-ioi.github.io/reports/?ref=investinopen.org"><u>sitio de informes del proyecto de LA Referencia</u></a>, y el relato que sigue se basa directamente en el <a href="https://github.com/LA-Referencia-IOI/reports/blob/main/executive-mid-year-report-2026-07-es.md?ref=investinopen.org"><u>informe ejecutivo del equipo correspondiente a enero–julio de 2026</u></a>.</p><p>El proyecto está organizado en tres componentes complementarios que conectan contenidos, tecnologías de descubrimiento, infraestructura de identificadores y capacidades humanas:</p><ul><li><strong>Componente A — Expansión de la infraestructura de agregación de LA Referencia:</strong> ampliar la cobertura regional, mejorar y normalizar los metadatos e introducir búsqueda semántica multilingüe en la capa de descubrimiento de LA Referencia.</li><li><strong>Componente B — Identificadores ARK descentralizados y preservación de metadatos (dARK):</strong> desarrollar dARK 2.0, una infraestructura modular basada en blockchain e ipfs para asignar, publicar y resolver identificadores persistentes.</li><li><strong>Componente C — Repositorio regional de datos&nbsp; datos para instituiones sin infraestructura local y soporte para Dataverse:</strong> poner en marcha un repositorio regional para datos de investigación basado en Dataverse, acompañado de un programa federado de capacitación y curaduría.</li></ul><p>En el resto de este artículo profundizamos en los avances realizados en cada uno de estos componentes y compartimos productos y resultados del trabajo de LA Referencia que ya pueden ser explorados.</p><h1 id="componente-a-expansi%C3%B3n-de-la-infraestructura-de-agregaci%C3%B3n-de-la-referencia"><strong>Componente A: Expansión de la infraestructura de agregación de LA Referencia</strong></h1><p>El descubrimiento depende de contar con buenos metadatos para las colecciones, por lo que el Componente A combina la ampliación de la cobertura regional de LA Referencia con el trabajo sobre calidad de metadatos y una nueva capacidad de búsqueda multilingüe que permite descubrir contenidos independientemente del idioma utilizado en la búsqueda o del idioma del contenido.</p><h3 id="avances-hasta-la-fecha"><strong>Avances hasta la fecha</strong></h3><p>Durante el período del informe, LA Referencia implementó una metodología regional para identificar instituciones y repositorios candidatos a ser cosechados con el objetivo de ampliar su colección. Este trabajo incluyó la verificación de servicios OAI-PMH, la revisión de metadatos, la actualización de la Interoperability and Registry Database (IRD) de COAR y la verificación cruzada de información institucional con ROR. El trabajo de curaduría se completó para los países miembros Ecuador, Uruguay y Costa Rica, y para los países no miembros Colombia, Paraguay, Venezuela, Bolivia y Cuba; los registros de otros países se encuentran en proceso.</p><p>En total, el equipo actualizó los registros de 362 repositorios: 187 fueron editados, 77 incorporados como nuevos y 98 archivados. Venezuela fue el país con mayores avances, con dos repositorios cosechados exitosamente como experiencia piloto para la incorporación de contenidos provenientes de países que todavía no operan como nodos completos de LA Referencia.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://la-referencia-ioi.github.io/reports/productos/a1-expansion-regional/es/index.html?ref=investinopen.org" class="kg-btn kg-btn-accent">Explorar el informe completo de avances sobre la expansión de la cobertura regional</a></div><p>En relación con esta expansión geográfica, LA Referencia está desarrollando una solución para un problema común identificado en su comunidad: muchos investigadores realizan búsquedas en un idioma mientras que el trabajo que necesitan está descrito en otro. Un registro de un repositorio en español podría no aparecer nunca para una persona que realiza una búsqueda en inglés, o viceversa, porque la búsqueda tradicional por palabras clave solo puede hacer coincidir las palabras exactas presentes en la página. El Componente A busca cerrar esa brecha mediante búsqueda semántica multilingüe, que encuentra resultados haciendo coincidir significados en lugar de palabras exactas. Para determinar la mejor manera de hacerlo, el equipo realizó una evaluación rigurosa y reproducible, comparando aproximadamente treinta modelos diferentes de IA en dos colecciones de prueba de entre 30.000 y 50.000 documentos, con miles de búsquedas de prueba en hasta 10 idiomas. Este trabajo produjo resultados prometedores: en el piloto, la búsqueda semántica y la búsqueda combinada recuperaron aproximadamente el doble de resultados relevantes entre los primeros 10 resultados —pasando de un promedio de 4,5 a 9,1— en comparación con la búsqueda únicamente por palabras clave. Las mayores mejoras se observaron en idiomas que suelen presentar mayores dificultades para la búsqueda por palabras clave, como chino, japonés y árabe. El equipo <a href="https://la-referencia-ioi.github.io/reports/productos/a4-seleccion-modelos/es/index.html?ref=investinopen.org"><u>evaluó distintos modelos</u></a> y seleccionó uno que ofrecía un equilibrio entre resultados de alta calidad, eficiencia y velocidad para operar sobre millones de registros.</p><p>Esta evaluación ya fue incorporada a un sistema beta funcional dentro de la plataforma de búsqueda de LA Referencia. Cuando una persona realiza una búsqueda, puede elegir entre la coincidencia tradicional por palabras clave, una coincidencia “basada en significado” que funciona entre distintos idiomas o un modo combinado que integra ambas aproximaciones. La reindexación se vuelve considerablemente más rápida cuando se reutilizan embeddings generados previamente. Reconstruir el índice completo para un conjunto de prueba de aproximadamente 28.000 registros requirió alrededor de 5 horas la primera vez, pero solamente unos 10 minutos cuando los datos basados en significado ya estaban almacenados, lo que hace posible realizar actualizaciones regulares a medida que la colección continúa creciendo. Paralelamente, el equipo incorporó <a href="https://la-referencia-ioi.github.io/lareferencia-anubis-demo/?lang=es&ref=investinopen.org"><u>un WAF abierto que filtra bots automatizados y scrapers</u></a>, junto con una forma de aplicar esa misma protección simultáneamente en múltiples sitios de LA Referencia.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://semantic.lareferencia.info/?ref=investinopen.org" class="kg-btn kg-btn-accent">Probar la demostración de búsqueda semántica e híbrida</a></div><p>También es posible profundizar en los detalles técnicos consultando el <a href="https://github.com/LA-Referencia-IOI/reports/blob/main/component-a-mid-year-report-2026-07-es.md?ref=investinopen.org"><u>informe completo del Componente A de LA Referencia</u></a>.</p><h3 id="pr%C3%B3ximos-pasos"><strong>Próximos pasos</strong></h3><p>LA Referencia continúa revisando e incorporando repositorios de otros países miembros y de nuevos países fuera de su red. El equipo planea ampliar la evaluación de la búsqueda semántica multilingüe a toda la colección regional y consolidar la versión beta de búsqueda semántica antes de avanzar hacia un despliegue más amplio.</p><h1 id="componente-b-identificadores-ark-descentralizados-dark-y-preservaci%C3%B3n-de-metadatos"><strong>Componente B: Identificadores ARK descentralizados (dARK) y preservación de metadatos</strong></h1><p>El Componente B comprende el desarrollo de dARK 2.0, la próxima generación de la infraestructura de LA Referencia para asignar, publicar y resolver identificadores persistentes ARK. Este componente contempla una <a href="https://la-referencia-ioi.github.io/reports/productos/b1-dark-2/es/index.html?ref=investinopen.org"><u>infraestructura regional, soberana y sostenible</u></a>, construida específicamente para la región a la que sirve LA Referencia.</p><h3 id="avances-hasta-la-fecha-1"><strong>Avances hasta la fecha</strong></h3><p>Los identificadores persistentes son los que permiten que una producción de investigación continúe siendo localizable y citable a largo plazo mediante un enlace permanente que sigue conduciendo al artículo, conjunto de datos o informe correcto años después, incluso si el archivo cambia de ubicación o si cambia el sistema que lo aloja. Actualmente, gran parte de esta infraestructura es gestionada por un pequeño grupo de proveedores externos. dARK 2.0 representa la visión de LA Referencia de una infraestructura que la propia región pueda operar, gobernar y considerar confiable, sin depender de una única organización como centro de control.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://la-referencia-ioi.github.io/reports/productos/b1-dark-2/es/index.html?ref=investinopen.org" class="kg-btn kg-btn-accent">Explorar dARK: identificadores persistentes como bien público regional</a></div><p>Para lograrlo, el equipo dividió dARK 2.0 en componentes separados que pueden ser verificados, actualizados o escalados de manera independiente. Un registro compartido y resistente a manipulaciones —un tipo de blockchain— mantiene el registro autoritativo de qué identificadores existen y hacia dónde apuntan, mientras que los metadatos descriptivos de cada registro se almacenan por separado, permitiendo que cualquiera pueda verificar que no han sido alterados. Esta separación mantiene la capa de “prueba” simple y confiable, mientras que los datos descriptivos pueden continuar creciendo sin necesidad de modificar esa capa de “prueba”. El equipo también construyó todo el flujo de procesamiento que requiere el sistema: reservar nuevos identificadores, preparar y almacenar sus metadatos, publicar la referencia en el registro y permitir que cualquier persona consulte un identificador y lo resuelva hacia el registro correcto.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://la-referencia-ioi.github.io/reports/productos/b2-infraestructura-multisitio/es/index.html?ref=investinopen.org" class="kg-btn kg-btn-accent">Explorar la arquitectura técnica de dARK 2.0</a></div><p>El equipo sometió este flujo de trabajo a pruebas de estrés con millones de registros y ejecutó cientos de verificaciones automatizadas para confirmar su robustez, además de construir herramientas administrativas para que el personal pueda monitorear identificadores, actividad y consultas. El flujo de dARK ya está listo para ser desplegado y conectado con el sistema regional de cosecha de LA Referencia, por lo que el proceso de cosecha se está integrando con el flujo de dARK para permitir la asignación de identificadores a medida que los registros son procesados, incluso en colecciones grandes y en constante cambio.</p><p><a href="https://github.com/LA-Referencia-IOI/reports/blob/main/component-b-mid-year-report-2026-07-es.md?ref=investinopen.org"><u>Profundizar en los detalles en el informe completo del Componente B</u></a>.</p><h3 id="pr%C3%B3ximos-pasos-1"><strong>Próximos pasos</strong></h3><p>El siguiente paso consiste en distribuir la infraestructura dARK entre distintas instituciones en lugar de ejecutarla desde un único lugar. Se está preparando una instalación equivalente en RNP, en Brasil, y la institución socia IBICT está preparando la migración de sus identificadores desde la versión original 1.0 de dARK. Con múltiples instituciones utilizando el sistema, LA Referencia planea validar su funcionamiento entre distintos sitios y formalizar el modelo de seguridad y gobernanza de esta infraestructura regional federada.</p><h1 id="componente-c-repositorio-regional-para-datos-sin-infraestructura-institucional-y-soporte-para-dataverse"><strong>Componente C: Repositorio regional para datos sin infraestructura institucional y soporte para Dataverse</strong></h1><p>El Componente C combina un nuevo repositorio regional basado en Dataverse con un programa federado de capacitación y curaduría, cuyo objetivo es ofrecer un espacio para aquellos datos de investigación que carecen de infraestructura institucional, al mismo tiempo que se difunden las capacidades necesarias para operar servicios de datos de manera sostenible en toda la región.</p><h3 id="avances-hasta-la-fecha-2"><strong>Avances hasta la fecha</strong></h3><p>El equipo comenzó con un diagnóstico regional que identificó aproximadamente 96 repositorios de datos registrados y alrededor de 30 instalaciones de Dataverse en América Latina, concentradas principalmente en Brasil, Argentina, México y Colombia. El diagnóstico se basó en cuestionarios y entrevistas que abordaron gobernanza, infraestructura, curaduría, preservación, soporte e interoperabilidad. Este análisis confirmó que la región ya cuenta con una experiencia y conocimientos significativos, lo que dio forma a una estrategia de colaboración entre pares que concibe al repositorio como un servicio sociotécnico: software e infraestructura combinados con políticas, equipos multidisciplinarios, apoyo a investigadores y capacitación continua.</p><p>El principal resultado técnico es una versión de prueba funcional y en línea del repositorio —un “Dataverse Alpha”— que funciona sobre la propia infraestructura de LA Referencia. El repositorio está disponible en inglés, español y portugués, incluye campos para indicar el país de origen de un conjunto de datos y con cuáles de los 17 Objetivos de Desarrollo Sostenible de las Naciones Unidas se relaciona, y utiliza licencias abiertas (CC0 y CC BY) para que los datos puedan ser reutilizados libremente. Ya se han cargado conjuntos de datos de ejemplo para que el equipo pueda probar la carga, descripción, búsqueda y acceso a archivos antes de que comiencen a recibirse depósitos institucionales reales.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://data.lareferencia.info/?ref=investinopen.org" class="kg-btn kg-btn-accent"> Explorar el Dataverse Alpha de LA Referencia</a></div><p>Junto con el desarrollo técnico, el equipo está elaborando un MOOC asincrónico de 16 horas, <em>Introducción a la Gestión y Curaduría de Datos en Dataverse</em>, que abarca fundamentos y publicación, metadatos y documentación, verificación técnica y formatos, y ética, licenciamiento y aprobación. Este es uno de los tres productos de capacitación planificados; los otros incluyen capacitación práctica en curaduría y apoyo directo a las instituciones piloto. El curso será construido e instalado en un entorno Moodle de producción, con materiales en español y portugués.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://la-referencia-ioi.github.io/reports/productos/c2-curso-curaduria-datos/es/index.html?ref=investinopen.org" class="kg-btn kg-btn-accent">Leer más sobre el MOOC y sus módulos</a></div><p>Invitamos a los lectores a explorar todos los detalles técnicos en el <a href="https://github.com/LA-Referencia-IOI/reports/blob/main/component-c-mid-year-report-2026-07-es.md?ref=investinopen.org"><u>informe completo del Componente C</u></a>.</p><h3 id="pr%C3%B3ximos-pasos-2"><strong>Próximos pasos</strong></h3><p>El equipo finalizará los contenidos del curso, validará de extremo a extremo los flujos de trabajo del repositorio, seleccionará las primeras instituciones piloto y transformará las lecciones aprendidas durante la fase Alpha en un modelo estable para el servicio regional.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://la-referencia-ioi.github.io/reports/index.html?ref=investinopen.org" class="kg-btn kg-btn-accent">Explorar el sitio completo de informes del proyecto de LA Referencia</a></div><h1 id="el-proyecto-de-la-referencia-apoyando-los-objetivos-del-fondo-de-ioi-para-la-adopci%C3%B3n-en-redes"><strong>El proyecto de LA Referencia: apoyando los objetivos del Fondo de IOI para la Adopción en Redes</strong></h1><p>A seis meses de iniciado el proyecto, LA Referencia ha pasado del diseño y el trabajo de diagnóstico a sistemas funcionales: una experiencia de descubrimiento multilingüe con mejoras medibles, una arquitectura funcional para identificadores persistentes soberanos y verificables, y un repositorio regional de datos en funcionamiento acompañado de un proceso de capacitación diseñado para perdurar más allá de una única subvención. Nada de esto fue construido para una sola institución; cada mejora contribuye a una infraestructura compartida y federada de la que ya dependen los repositorios miembros de LA Referencia en toda América Latina.</p><p>Esta es la premisa del Fondo de IOI para la Adopción en Redes: que la forma más rápida y duradera de hacer crecer la adopción de infraestructura abierta es invertir en redes que ya cuentan con la gobernanza, la confianza y el alcance necesarios para poner nuevas capacidades al servicio de muchas instituciones simultáneamente. Los primeros seis meses de LA Referencia muestran esta tesis en acción. La base técnica que están construyendo permitirá avanzar hacia la próxima fase del proyecto: expandirse hacia nuevos países e idiomas, validar dARK entre distintas instituciones e incorporar las primeras instituciones piloto al Dataverse regional.</p><hr><p><em>Leé más sobre el proyecto en el</em> <a href="https://la-referencia-ioi.github.io/reports/index.html?ref=investinopen.org" rel="noreferrer"><em><u>sitio de informes del proyecto de LA Referencia</u></em></a><em>, incluido el</em> <a href="https://github.com/LA-Referencia-IOI/reports/blob/main/executive-mid-year-report-2026-07-es.md?ref=investinopen.org"><em><u>informe ejecutivo completo</u></em></a><em>en el que se basa este artículo, o conocé más sobre</em> <a href="https://investinopen.org/our-work/la-referencia/"><em><u>el trabajo de IOI con LA Referencia</u></em></a> <em>y el</em> <a href="https://investinopen.org/ioi-fund/"><em><u>Fondo de IOI para la Adopción en Redes</u></em></a><em>.</em></p> ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ IOI Fund for Network Adoption: LA Referencia’s six-month progress update ]]></title>
        <description><![CDATA[ Network adoption with a strong technical foundation. ]]></description>
        <link>https://investinopen.org/blog/ioi-fund-for-network-adoption-la-referencia-6mo-en/</link>
        <guid isPermaLink="false">6a91c03ea644ab0001570692</guid>
        <category><![CDATA[ Blog ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Mon, 31 Aug 2026 12:30:19 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ <p><em>This article is also available in </em><a href="https://investinopen.org/fondo-de-ioi-para-la-adopcion-en-redes-la-referencia-6meses-es/" rel="noreferrer"><em>Spanish</em></a><em>. </em></p><p>In late 2025, Invest in Open Infrastructure launched the <a href="https://investinopen.org/ioi-fund/"><u>IOI Fund for Network Adoption</u></a>, a new kind of investment designed to accelerate the global adoption of open infrastructure for research and data sharing. Rather than funding individual tools or single institutions, the Fund invests in <em>networks</em>: consortia of institutions and researchers with established relationships, active member governance, and a demonstrated commitment to open science. The logic is that strengthening the shared infrastructure that a network already runs can multiply impact across every member institution at once.</p><p>The Fund grew out of direct engagement with research communities to identify the open infrastructure projects most in need of sustained support, and it pools contributions from a group of funders all interested in strengthening the global open research ecosystem. Each selected network receives up to $1.5 million over two to three years, paired with ongoing implementation support from IOI staff on governance, community engagement, and business modeling. IOI’s goal with the Fund is not only to enable grantees to do projects that can have a big impact on their networks, but also to support the resilience of these networks long after the grant ends.</p><p><a href="https://investinopen.org/our-work/la-referencia/"><u>LA Referencia</u></a> was named one of the Fund's two inaugural grantees,<a href="https://investinopen.org/blog/empowering-networks-advancing-openness-invest-in-open-infrastructure-announces-inaugural-grantees-of-the-ioi-fund-for-network-adoption/"> <u>selected from more than 100 applications spanning 22 countries</u></a>. Together, the Fund's first two grantees are positioned to benefit more than 1,300 research institutions across 36 countries in Latin America and Africa. This post provides an overview of what LA Referencia has done with the first six months of that investment. Look for an update post about our other inaugural grantee, UbuntuNet Alliance, in the coming months.&nbsp;</p><figure class="kg-card kg-image-card"><a href="https://new.lareferencia.info/?ref=investinopen.org"><img src="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/08/lareferencia-1.png" class="kg-image" alt="Logo of LA Referencia" loading="lazy" width="1038" height="240" srcset="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w600/2026/08/lareferencia-1.png 600w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w1000/2026/08/lareferencia-1.png 1000w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/08/lareferencia-1.png 1038w" sizes="(min-width: 720px) 720px"></a></figure><h2 id="an-introduction-to-la-referencia%E2%80%99s-project">An introduction to LA Referencia’s project</h2><p>LA Referencia is a regional cooperation network that aggregates and provides open access to the scholarly and scientific output of national repositories across Latin America and Spain, built on a model of federated governance and publicly owned, non-commercial infrastructure. With IOI Fund support, LA Referencia is running a 2026–2028 project to expand that infrastructure's regional reach and technical depth with four major goals: bringing more countries and repositories into the network, modernizing how researchers discover content in multiple languages, building a sovereign and verifiable system of persistent identifiers, and standing up a shared regional repository and training program for research data. The project's full progress is documented in detail on<a href="https://la-referencia-ioi.github.io/reports/en/?ref=investinopen.org"> <u>LA Referencia's project reporting site</u></a>, and the account below draws directly on the team's own<a href="https://github.com/LA-Referencia-IOI/reports/blob/main/executive-mid-year-report-2026-07-en.md?ref=investinopen.org"> <u>executive report for January–July 2026</u></a>.&nbsp;</p><p>The project is organized into three complementary components that connect content, discovery technology, identifier infrastructure, and human capacity:</p><ul><li><strong>Component A — Expanding LA Referencia’s Aggregation Infrastructure:</strong> growing regional coverage, improving and normalizing metadata, and introducing multilingual semantic search to LA Referencia's discovery layer.</li><li><strong>Component B — Decentralized ARK Identifiers and Metadata Preservation (dARK):</strong> building dARK 2.0, a modular, blockchain-backed infrastructure for assigning, publishing, and resolving persistent identifiers.</li><li><strong>Component C — Regional Orphan Data Repository &amp; Dataverse Support:</strong> standing up a Dataverse-based regional repository for research data alongside a federated training and curation program.</li></ul><p>In the rest of this post, we dive deeper into the progress made on each of these components and share explorable outputs of LA Referencia’s work to date.&nbsp;</p><h2 id="component-a-expanding-la-referencia%E2%80%99s-aggregation-infrastructure">Component A: Expanding LA Referencia’s Aggregation Infrastructure</h2><p>Discovery depends on good metadata for the collections, so Component A pairs the expansion of LA Referencia's regional coverage with metadata quality work and a new multilingual search capability that enables discovery regardless of the language of the search or the content. </p><h3 id="progress-to-date">Progress to date</h3><p>Over the reporting period, LA Referencia enacted a regional methodology for identifying candidate institutions and repositories for harvesting to bolster their collection. This work involved verifying OAI-PMH services, reviewing metadata, updating COAR's Interoperability and Registry Database (IRD), and cross-checking institutional information against ROR. Curation work was completed for member countries Ecuador, Uruguay, and Costa Rica, and non-member countries Colombia, Paraguay, Venezuela, Bolivia, and Cuba; records for another countries are in progress.&nbsp;</p><p>In total, the team updated records for 362 repositories: 187 edited, 77 newly added, and 98 archived. Venezuela was the country with the greatest progress, with two repositories successfully harvested as a pilot for incorporating content from countries that do not yet operate as full nodes in LA Referencia.&nbsp;</p><div class="kg-card kg-button-card kg-align-center"><a href="https://la-referencia-ioi.github.io/reports/productos/a1-expansion-regional/en/index.html?ref=investinopen.org" class="kg-btn kg-btn-accent">Explore the full progress report on expanding regional coverage</a></div><p>Related to this geographic expansion, LA Referencia is building a solution for a common problem they encountered in their community: many researchers search in one language while the work they need is described in another. A record from a Spanish-language repository might never surface for someone searching in English, or vice versa, because traditional keyword search can only match the exact words on the page. Component A set out to close that gap with multilingual semantic search, which finds results by matching meaning instead of exact wording. To figure out the best way to do this, the team ran a rigorous, reproducible evaluation, comparing roughly thirty different AI models across two test collections of 30,000 to 50,000 documents, with thousands of test searches in as many as 10 languages. This work resulted in promising outcomes: in the pilot, semantic and blended search surfaced roughly twice as many relevant results in the top 10 (up from an average of 4.5 to 9.1) compared with keyword search alone, with the biggest gains for languages that keyword matching tends to handle poorly, like Chinese, Japanese, and Arabic. The team <a href="https://la-referencia-ioi.github.io/reports/productos/a4-seleccion-modelos/en/index.html?ref=investinopen.org"><u>evaluated different models</u></a> and chose one that balanced high-quality results with efficiency and speed to run on millions of records.&nbsp;</p><p>That evaluation has now been built into a beta working system on LA Referencia's search platform. When someone runs a search, they can choose the traditional keyword match, a "meaning-based" match that works across languages, or a blended mode that combines both. Reindexing becomes substantially faster when previously generated embeddings are reused. Rebuilding the full index for a test set of about 28,000 records took roughly 5 hours the first time, but only about 10 minutes once the meaning-based data was already stored, making regular updates practical as the collection keeps growing. Alongside this, the team added <a href="https://la-referencia-ioi.github.io/lareferencia-anubis-demo/?lang=en&ref=investinopen.org"><u>a open WAF that screens out automated bots and scrapers</u></a>, plus a way to apply that same protection across multiple LA Referencia sites at once.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://semantic.lareferencia.info/?ref=investinopen.org" class="kg-btn kg-btn-accent">Try a demo of semantic and hybrid search</a></div><p>You can also dive into the technical details by reading LA Referencia’s <a href="https://github.com/LA-Referencia-IOI/reports/blob/main/component-a-mid-year-report-2026-07-en.md?ref=investinopen.org"><u>full Component A report</u></a>.</p><h3 id="whats-next">What's next</h3><p>LA Referencia continues to review and add repositories from additional member countries and new countries beyond their network. The team plans to expand its multilingual semantic search evaluation across the full regional collection and consolidate the semantic search beta ahead of broader rollout.</p><h2 id="component-b-decentralized-ark-identifiers-dark-and-metadata-preservation">Component B: Decentralized ARK Identifiers (dARK)&nbsp; and Metadata Preservation</h2><p>Component B involves building dARK 2.0, the next generation of LA Referencia's infrastructure for assigning, publishing, and resolving persistent ARK identifiers.&nbsp; This component accounts for <a href="https://la-referencia-ioi.github.io/reports/productos/b1-dark-2/en/index.html?ref=investinopen.org"><u>regional, sovereign, and sustainable infrastructure</u></a> built specifically for the region served by LA Referencia.</p><h3 id="progress-to-date-1">Progress to date</h3><p>Persistent identifiers are what keep a piece of research findable and citable for the long term by using a permanent link that still leads to the right paper, dataset, or report years later, even if the file moves or the system hosting it changes. Today, most of that infrastructure is run by a handful of external providers. dARK 2.0 is LA Referencia's vision for an infrastructure the region can run, govern, and trust for itself without relying on one single organization as a locus of control.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://la-referencia-ioi.github.io/reports/productos/b1-dark-2/en/index.html?ref=investinopen.org" class="kg-btn kg-btn-accent">Explore dARK: Persistent identifiers as a regional public good</a></div><p>To do that, the team split dARK 2.0 into separate components that can each be checked, updated, or scaled independently. A shared, tamper-evident ledger (a type of blockchain) maintains the authoritative record of which identifiers exist and what they point to, while the descriptive metadata for each record is stored separately, allowing anyone to verify it hasn't been altered. That split keeps the "proof" layer simple and trustworthy, while the descriptive data can keep growing without needing to touch the "proof" layer. The team also built the full pipeline this system requires: reserving new identifiers, preparing and storing their metadata, publishing the reference to the ledger, and allowing anyone to look up an identifier and resolve it to the correct record.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://la-referencia-ioi.github.io/reports/productos/b2-infraestructura-multisitio/en/index.html?ref=investinopen.org" class="kg-btn kg-btn-accent">Explore the dARK 2.0 technical architecture</a></div><p>The team stress-tested this workflow against millions of records and ran hundreds of automated checks to confirm it holds up, and built administrative tools so staff can monitor identifiers, activity, and lookups. The dARK pipeline is now ready to be deployed and connected to LA Referencia's regional harvesting system, so the harvesting workflow is being integrated with the dARK pipeline to support identifier assignment as records are processed, even across large, constantly changing collections.&nbsp;</p><p><a href="https://github.com/LA-Referencia-IOI/reports/blob/main/component-b-mid-year-report-2026-07-en.md?ref=investinopen.org"><u>Dive into the details in the full Component B report</u></a>.</p><h3 id="what%E2%80%99s-next">What’s next</h3><p>The next step is spreading the dARK infrastructure across institutions rather than running it from one place. A matching setup is being prepared at RNP in Brazil, and partner institution IBICT is preparing to migrate its identifiers over from the original 1.0 version of dARK. With multiple institutions using the system, LA Referencia plans to validate cross-site operation and formalize the security and governance model for this federated regional infrastructure. </p><h1 id="component-c-regional-orphan-data-repository-dataverse-support">Component C: Regional Orphan Data Repository &amp; Dataverse Support</h1><p>Component C pairs a new Dataverse-based regional repository with a federated training and curation program, aimed at giving research data lacking institutional infrastructure a home while spreading the skills needed to run data services sustainably across the region.</p><h3 id="progress-to-date-2">Progress to date</h3><p>The team began with a regional diagnostic that identified roughly 96 registered data repositories and around 30 Dataverse installations across Latin America, concentrated in Brazil, Argentina, Mexico, and Colombia, drawing on questionnaires and interviews covering governance, infrastructure, curation, preservation, support, and interoperability. That diagnostic confirmed the region already has significant experience and expertise, which has shaped a peer-collaboration strategy treating the repository as a socio-technical service: software and infrastructure paired with policy, multidisciplinary teams, researcher support, and ongoing training.</p><p>The headline technical result is a live, working test version of the repository (a "Dataverse Alpha") running on LA Referencia's own infrastructure. The repository works in English, Spanish, and Portuguese, includes fields to tag a dataset's country of origin and which of the UN's 17 Sustainable Development Goals it relates to, and uses open licenses (CC0 and CC BY) so the data can be freely reused. Sample datasets are already loaded so the team can test uploading, describing, searching, and accessing files before real institutional deposits start coming in.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://data.lareferencia.info/?ref=investinopen.org" class="kg-btn kg-btn-accent">Explore Dataverse Alpha at LA Referencia</a></div><p>Alongside the technical build, the team is developing a 16-hour asynchronous MOOC, <em>Introduction to Data Management and Curation in Dataverse</em>, covering foundations and publication, metadata and documentation, technical verification and formats, and ethics, licensing, and approval. This is one of three planned training products; the others include hands-on curation training and direct support for pilot institutions. The course will be built and installed on a production Moodle environment with materials in Spanish and Portuguese.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://la-referencia-ioi.github.io/reports/productos/c2-curso-curaduria-datos/en/index.html?ref=investinopen.org" class="kg-btn kg-btn-accent">Read more about the MOOC and its modules</a></div><p>We encourage readers to explore the full technical details in the <a href="https://github.com/LA-Referencia-IOI/reports/blob/main/component-c-mid-year-report-2026-07-en.md?ref=investinopen.org"><u>full Component C report</u></a>.</p><h3 id="what%E2%80%99s-next-1">What’s next</h3><p>The team will finish course content, validate repository workflows end-to-end, select the first pilot institutions, and turn the lessons from the Alpha into a stable model for the regional service.</p><div class="kg-card kg-button-card kg-align-center"><a href="https://la-referencia-ioi.github.io/reports/en/?ref=investinopen.org" class="kg-btn kg-btn-accent">Explore the full project reporting website</a></div><h1 id="la-referencia%E2%80%99s-project-supporting-the-goals-of-the-ioi-fund-for-network-adoption">LA Referencia’s Project: Supporting the Goals of the IOI Fund for Network Adoption</h1><p>Six months in, LA Referencia has moved from design and diagnostic work to functioning systems: a measurably better multilingual discovery experience, a working architecture for verifiable, sovereign persistent identifiers, and a live regional data repository paired with a training pipeline built to outlast any single grant. None of this was built for one institution; every improvement contributes to shared, federated infrastructure that LA Referencia's member repositories across Latin America already rely on.&nbsp;</p><p>That is the premise of the IOI Fund for Network Adoption: that the fastest, most durable way to grow open infrastructure adoption is to invest in networks that already have the governance, trust, and reach to put new capacity to work across many institutions at once. LA Referencia's first six months show that thesis in motion. The technical foundation that they are building will enable the project's next phase, expanding to new countries and languages, validating dARK across institutions, and bringing its first pilot institutions onto the regional Dataverse.</p><hr><p><em>Read more about the project on</em><a href="https://la-referencia-ioi.github.io/reports/en/?ref=investinopen.org"><em> <u>LA Referencia's project reporting site</u></em></a><em>, including the full</em><a href="https://github.com/LA-Referencia-IOI/reports/blob/main/executive-mid-year-report-2026-07-en.md?ref=investinopen.org"><em> <u>executive report</u></em></a><em> this post is based on, or learn more about</em><a href="https://investinopen.org/our-work/la-referencia/"><em> <u>IOI's work with LA Referencia</u></em></a><em> and the</em><a href="https://investinopen.org/ioi-fund/"><em> <u>IOI Fund for Network Adoption</u></em></a><em>.&nbsp; </em></p> ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ Charting a sustainable future for TDCC-NES ]]></title>
        <description><![CDATA[ IOI is partnering with TDCC-NES, a collaborative network across the Dutch natural and engineering sciences domain that addresses FAIR data and other digital-related research challenges, to co-develop a post-NWO sustainability and co-investment model with its community. ]]></description>
        <link>https://investinopen.org/our-work/charting-a-sustainable-future-for-tdcc-nes/</link>
        <guid isPermaLink="false">6a5f3e0ddca8a0000125669a</guid>
        <category><![CDATA[ Our Work ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Tue, 21 Jul 2026 10:11:37 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ <!-- START case study metadata -->
<p><strong>Duration:</strong> April 2026 to December 2026<br>
<strong>Team:</strong> Emmy Tsang, Emma Green, Sarah Lippincott<br>
<strong>Funder:</strong> TDCC-NES<br>
<strong>Skillset:</strong> Strategic Planning, Convening / Facilitation, Fiscal Assessment &amp; Planning</p>
<!-- END case study metadata →
--><h2 id="overview"><strong>Overview</strong></h2><p>TDCC-NES is the Thematic Digital Competence Centre for the Natural &amp; Engineering Sciences in the Netherlands, a network organisation that helps Dutch researchers and digital support experts explore digital competency challenges and find solutions through connection and collaboration, reducing fragmentation and duplication across the domain. Funded by NWO as part of its investment in digital research infrastructure, TDCC-NES engaged IOI to develop a credible long-term sustainability model ahead of the end of the NWO funding window.</p><h2 id="what-we-will-do"><strong>What we will do</strong></h2><p>Through a phased engagement, IOI is building a shared, evidence-based understanding of TDCC-NES's value proposition, stakeholder landscape, and sustainability options, through stakeholder interviews, document review, and a discovery findings presentation to the governing board. In late 2026, we will convene key stakeholders in a sustainability workshop to co-develop the foundations of a co-investment model and build co-ownership of the path to 2030.</p><h2 id="outcomes"><strong>Outcomes</strong></h2><p>Phase 1 delivered a discovery findings report and board presentation that established a shared evidence base for the board's sustainability conversation. Further outcomes will be added as the engagement progresses.</p><h3 id="facing-a-funding-transition-lets-design-your-next-model-together">Facing a funding transition? Let's design your next model together.</h3><p>Many publicly funded infrastructure and network organisations face the end of an initial grant or funding window. IOI helps organisations like yours understand your value to stakeholders and design sustainable co-investment models.<a href="https://investinopen.org/free-consult/"> <u>Book a free consult</u></a>.</p> ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ Wellcome partners with IOI to map the data resources powering open research ]]></title>
        <description><![CDATA[ IOI&#39;s new initiative that maps the data resource ecosystem ]]></description>
        <link>https://investinopen.org/blog/wellcome-partners-with-ioi-to-map-the-data-resources-powering-open-research/</link>
        <guid isPermaLink="false">6a59cd496d07bb0001928f10</guid>
        <category><![CDATA[ Blog ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Fri, 17 Jul 2026 06:56:40 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ <p>We're excited to announce a new partnership with Wellcome, the global charitable foundation supporting science to solve urgent challenges. Our work will help Wellcome to gain deeper insight into the data resource ecosystem, providing a snapshot of the resources their researchers rely on.</p><p>Data resources that researchers rely on are critical to advancing science and discovery. That research often starts with data that research funders, such as Wellcome, did not create and does not maintain, including biodata repositories, population cohort databases, and environmental and climate data resources, built and sustained by organizations that often operate out of public view. At a moment when the research community is paying closer attention than ever to the resilience of the data infrastructure it depends on, we are supporting Wellcome to gain&nbsp;a clearer, deeper picture of that landscape. In turn, this will enable collective conversations within the research community about how we sustain these resources.</p><p>IOI is leading that effort, drawing on our track record of working alongside infrastructure providers, not just evaluating them from the outside. We'll be engaging directly with the teams running these resources to understand their governance, funding models, technical dependencies, open policies, sustainability outlooks and the broader ecosystem they operate within, the kind of insight that only comes from sustained, trust based engagement.</p><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/07/markus-winkler-kA7zREkzrBw-unsplash-2.jpg" class="kg-image" alt="scrabble pieces spelling the word data" loading="lazy" width="1920" height="1280" srcset="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w600/2026/07/markus-winkler-kA7zREkzrBw-unsplash-2.jpg 600w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w1000/2026/07/markus-winkler-kA7zREkzrBw-unsplash-2.jpg 1000w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w1600/2026/07/markus-winkler-kA7zREkzrBw-unsplash-2.jpg 1600w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/07/markus-winkler-kA7zREkzrBw-unsplash-2.jpg 1920w" sizes="(min-width: 720px) 720px"><figcaption><span style="white-space: pre-wrap;">Photo by </span><a href="https://unsplash.com/@markuswinkler?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><span style="white-space: pre-wrap;">Markus Winkler</span></a><span style="white-space: pre-wrap;"> on </span><a href="https://unsplash.com/photos/a-wooden-block-spelling-data-on-a-table-kA7zREkzrBw?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><span style="white-space: pre-wrap;">Unsplas</span></a><span style="white-space: pre-wrap;">h</span></figcaption></figure><p>The foundation for this work is<a href="https://infrafinder.investinopen.org/?ref=investinopen.org"> <u>Infra Finder</u></a>, IOI's open discovery platform for research infrastructure. We'll build verified, publicly accessible profiles for each resource in scope, using our established research and diligence process.This is also a significant expansion for Infra Finder, which has grown to include nearly 150 profiles of open infrastructure since its 2024 launch. Infra Finder is more than a directory. It's the foundation of our annual<a href="https://investinopen.org/data-room/state-of-oi/"> <u>State of Open Infrastructure</u></a> report, which tracks how the field is evolving year over year. Adding this cohort brings these data resources into that same yearly monitoring and analysis, giving Wellcome and the broader community longitudinal visibility into how they change and how they're funded over time.</p><p>We're looking forward to the work ahead. Stay tuned for more in the coming months! </p> ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ The Data Resilience Funding Landscape: A Preliminary Analysis ]]></title>
        <description><![CDATA[ Mapping where the money is (and isn&#39;t) going in the data rescue movement. ]]></description>
        <link>https://investinopen.org/blog/data-resilience-funding-landscape/</link>
        <guid isPermaLink="false">6a4c03fa34b98500012af011</guid>
        <category><![CDATA[ Blog ]]></category>
        <dc:creator><![CDATA[ Katherine E Skinner ]]></dc:creator>
        <pubDate>Tue, 07 Jul 2026 14:13:01 +0000</pubDate>
        <media:content url="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/07/christian-j-w8u0d3UPovw-unsplash.jpg" medium="image"/>
        <content:encoded><![CDATA[ <p>Between January 2025 and the time of writing (July 2026), hundreds of organizations, from grassroots volunteer networks to major research institutions, have mobilized to rescue, preserve, and provide access to at-risk federal data in a rapid response to a sustained and accelerating assault on these knowledge assets. While this wave of work began with many ad hoc and siloed efforts, it has developed into a movement, and invested stakeholders have stepped forward to take on “hub” roles, helping to coordinate and guide the rescue efforts. A sense of movement generosity has also been building among the players, perhaps most evident in hard-hit fields such as environmental and climate science. Those with resources and know-how are sharing wherever they can, particularly via their time, energy, and networks.&nbsp;</p><p>Funders have responded to the crisis, with the Robert Wood Johnson Foundation, Hewlett Foundation, David and Lucile Packard Foundation, John D. and Catherine T. MacArthur Foundation, Alfred P. Sloan Foundation, Mellon Foundation, and others directing significant resources toward data rescue and resilience efforts. Some funders are working together in formal coordination groups (e.g., Funders for the Future of Public Data (3FPD) and the Portfolio to Protect Science) in hopes of moving resources in ways that reduce duplication, “noise,” while increasing investment alignment.</p><p>But a close look at where that money is flowing reveals concerning patterns that could subvert or undercut this work, limiting its ability to outlast the crisis that prompted it. Concretely, this includes dangerously low investments made in open infrastructures – including the technical platforms, standards, and software required to produce, share, discover, access, and preserve knowledge.</p><h2 id="crisis-reveals-what-was-always-true"><strong>Crisis reveals what was always true</strong></h2><p>Funding is moving in familiar, system-driven ways that we have witnessed many times before. As my colleagues and I have noted elsewhere (e.g., <a href="https://educopia.org/blog/why-are-so-many-scholarly-communication-infrastructure-providers-running-a-red-queens-race/?ref=investinopen.org"><u>Red Queen’s Race</u></a>, <a href="https://investinopen.org/blog/the-emperors-new-clothes-common-myths-hindering-open-infrastructure/"><u>Emperor’s New Clothes</u></a>), stakeholders in the knowledge and information ecosystem have for years been rewarded for ways of working that provide short-term gains but that tend to fail to add up to long-term success.</p><p><strong>Incentive structures, including funding and career advancement, encourage stakeholders to pursue innovation over maintenance, to build competing siloes rather than grow interoperability and coordination, and to misinterpret bare survival of open infrastructure communities and services as though that survival somehow signifies success. </strong></p><p>The resulting fragility of open infrastructure components has been persistent, and the current political crisis of 2025-2026 hasn’t created precarity so much as it has exposed it. Data is disappearing because the infrastructure in which it is nested was already brittle. This moment is an opportunity, not just to rescue data, but to correct a long-standing dependency on temporary and inadequate funding for infrastructure-level work.</p><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/07/christian-j-w8u0d3UPovw-unsplash-1.jpg" class="kg-image" alt="A close up of petrified wood, showing intricate marble-like details of the rock-like texture in reds, blues, yellows, and whites. " loading="lazy" width="2000" height="1333" srcset="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w600/2026/07/christian-j-w8u0d3UPovw-unsplash-1.jpg 600w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w1000/2026/07/christian-j-w8u0d3UPovw-unsplash-1.jpg 1000w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w1600/2026/07/christian-j-w8u0d3UPovw-unsplash-1.jpg 1600w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w2400/2026/07/christian-j-w8u0d3UPovw-unsplash-1.jpg 2400w" sizes="(min-width: 720px) 720px"><figcaption><span style="white-space: pre-wrap;">Photo by </span><a href="https://unsplash.com/@chrisk91?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><span style="white-space: pre-wrap;">Christian J.</span></a><span style="white-space: pre-wrap;"> on </span><a href="https://unsplash.com/photos/a-close-up-of-a-red-and-white-marble-w8u0d3UPovw?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><span style="white-space: pre-wrap;">Unsplash</span></a></figcaption></figure><h2 id="tracking-investment-flows"><strong>Tracking investment flows</strong></h2><p>IOI has been mapping the emerging data resilience ecosystem, tracking more than 85 “data rescue” and “data resilience” projects, initiatives, forums, and funding efforts that have launched or significantly evolved since 2025. The landscape clusters into recognizable functional layers: active rescue and collection efforts; tools, repositories, and discovery systems; monitoring and tracking; coordination and strategy; and advocacy and fundraising. Across these clusters, coordination-style work — convenings, roadmaps, governance documentation, advocacy campaigns — dominates the funded project list. Rescue and collection efforts, including some remarkable grassroots mobilizations, are also well represented in the list.</p><p>What is almost entirely absent in the projects and initiatives we are tracking is investment in the technical infrastructure layer:&nbsp; the tools, pipelines, standards, systems, and people that make any of the other work durable. Of the 87 projects and initiatives we are tracking, 34 involve coordination activities, 28 involve advocacy, and 33 involve data collection, while only 16 are actively building and maintaining technical tools, and more than half of those are building for their own project's needs rather than building shared, reusable infrastructure.&nbsp;</p><p>Those who are conducting “data rescue” or aiming for “data resilience,” depend on tools, pipelines, and standards to do their work, but those elements often are not being resourced through these funding streams. Rescued data has to be collected, and then it has to go somewhere; it has to be validated, described, made findable, and kept accessible. The systems that do that work, from web archiving tools to identifier infrastructure, from metadata standards to format normalization, and from discovery layers to storage and preservation activities, are either assumed to already exist and be adequately supported, or they are simply not visible in the investment picture.&nbsp;</p><p>The danger is hidden: much of the content that is being rescued is flowing onto known and trusted infrastructures, e.g., Internet Archive, ICPSR and Data LUMOS, and Texas Advanced Computing Center (TACC). The longevity of these environments is unknown and they are not being funded to take on a permanent or future-facing role for this content. What does that mean for the maintenance and reliability of these resources over time?</p><p>The infrastructure layer is chronically underfunded relative to the work it enables, with costs hidden through volunteerism and institutional subsidy. The data resilience funding landscape is replicating that failure under crisis conditions.</p><h2 id="learning-from-previous-experiences"><strong>Learning from previous experiences</strong></h2><p>This is, of course, far from the first time activist communities have mobilized to rescue endangered digital collections at scale. For example, the 2016 data rescue movement, responding to the first round of federal data threats, activated DataRefuge, Preserving Electronic Government Information (PEGI), and the Environmental Data and Governance Initiative (EDGI), among other efforts. Libraries, cultural heritage professionals, and researchers have also mobilized around a myriad of events over time, from the Estonian cyberattacks of 2007 to the conflict zones in Sudan, Syria, Ukraine, and Afghanistan; and from responses to the British Library ransomware attack of 2023 to rescue efforts in the wake of wildfires, floods, and other major natural disasters. Each of these efforts generated hard-won knowledge about what works — distributed custody models, community triage processes, the limits of dark archiving sans deliberate attention to access, and the differences between rescue and preservation.&nbsp;</p><p>That knowledge is not being systematically drawn on in many of today’s projects, and the current US focus is producing efforts that are, in some cases, re-learning lessons that have already been learned elsewhere. We need to actively encourage and fund work that connects today's actors to this history.&nbsp;</p><p>For example, do we know what parts of the 2016-17 data rescue tooling and environment still exist, and what parts do not? Do we know what characteristics differentiate still-active groups like EDGI, ICPSR, and Internet Archive from other groups and toolsets that have sunset? Knowing more about the past can help us to invest more wisely and sunset more adeptly, establishing stronger scaffolding for the field. That requires directing some portion of the funding towards practical analysis of these past efforts.&nbsp;</p><h2 id="duplication-of-backbone-human-infrastructure"><strong>Duplication of backbone (human) infrastructure</strong></h2><p>Our analysis shows a third gap that is perhaps the most costly today: instead of reinforcing the successful networks that already exist and distilling models from those that we can activate in other fields and disciplines, much of the funding available today is flowing to external contractors and consultants to build landscape analyses in order to better understand where the connectors and touchpoints between current efforts are.&nbsp;</p><p>Unintentionally, these external groups are both duplicating and undermining long-standing, often mature or maturing networks on the ground. While the contractors and consultants entering this space for the first time gain remarkable resourcing, existing network players, including strong hubs of activation, struggle for survival, with staff living from contract to contract, and no organizational runway available to them to enable the strategic planning or expansion work they may be uniquely suited to do. In other words, rather than directing funds to strong cornerstone players (e.g., EDGI, PEDP) in support of the (volunteer-driven) bridge building they already have underway, resources are going to external and/or new groups.</p><p>This problem is structural, not intentional, but it still deletes resources from the grassroots actors and specialists in the field in at least three ways. It happens first as dollars flow out of the information management ecosystem to fuel the work of often expensive, deliberately temporary players that promise to provide a system-level view and unbiased recommendations. It happens again, as those consultants build their own maps and recommendations only by drawing heavily on the time and knowledge of the very specialists they are shadowing — asking them to explain what they do, who the key voices are, who is and isn’t connected, and where funding is most needed. And then it happens again as the specialists don’t spare attention for funding calls and proposal deadlines because they are spending their time doing the work.&nbsp;</p><h2 id="an-unresolved-strategic-question"><strong>An unresolved strategic question</strong></h2><p>Underneath the funding gaps lies a more fundamental question that the field has not yet answered: what is today’s data rescue and resilience effort actually building toward? There is a significant difference between building <strong><u>survival infrastructure</u></strong> to keep specific repositories and datasets alive through the current period of threat, versus building <strong><u>perpetuity infrastructure</u></strong> – systems and services that repositories and datasets can plug into for long-term, stable access regardless of political conditions or other threats. Both are needed. Neither is being resourced with that distinction in mind.</p><p>Key, instructive models and seasoned players, ones that have actively solved this problem for adjacent challenges, seem to be missing from the current networks that are assembling: for example, CLOCKSS and Portico for journal content, DataCite for research data identifiers, Crossref for publication metadata, OpenAlex as an open catalog of scholarly works, and Digital Preservation Coalition and National Digital Stewardship Alliance for community standards. Each of these longstanding and well-embedded infrastructure elements has succeeded by defining a function, building infrastructure to serve it collectively, and creating a governance and funding model that distributes the cost across many stakeholders. None of them emerged from crisis response; all of them were built in periods of relative stability. Many of them could provide strong, grounded perspective and leadership to help tie today’s activity to years of preservation practice.&nbsp;</p><p>The current moment is not stable, but it is not too early to ask what long-term preservation and access infrastructure for federal data looks like, and to begin directing some portion of crisis-response investment toward building it.&nbsp;</p><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/2026/07/tim-mossholder-2RUZ3S32hi8-unsplash.jpg" class="kg-image" alt="Wood texture on a tree. The bark diverts in a curve to reinforce a weak spot. " loading="lazy" width="2000" height="1333" srcset="https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w600/2026/07/tim-mossholder-2RUZ3S32hi8-unsplash.jpg 600w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w1000/2026/07/tim-mossholder-2RUZ3S32hi8-unsplash.jpg 1000w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w1600/2026/07/tim-mossholder-2RUZ3S32hi8-unsplash.jpg 1600w, https://storage.ghost.io/c/e3/0f/e30f355d-2d35-423e-a82d-26c811a07bf5/content/images/size/w2400/2026/07/tim-mossholder-2RUZ3S32hi8-unsplash.jpg 2400w" sizes="(min-width: 720px) 720px"><figcaption><span style="white-space: pre-wrap;">Photo by </span><a href="https://unsplash.com/@timmossholder?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><span style="white-space: pre-wrap;">Tim Mossholder</span></a><span style="white-space: pre-wrap;"> on </span><a href="https://unsplash.com/photos/brown-tree-trunk-2RUZ3S32hi8?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><span style="white-space: pre-wrap;">Unsplash</span></a></figcaption></figure><h2 id="what-this-means"><strong>What this means</strong></h2><p>The data resilience field is doing to data rescue what scholarly communications has done to open infrastructure for thirty years: funding the visible and easy-to-narrate activities while underinvesting in the operational and technical layer that makes those activities durable. Coordination without tools is a map without roads. Rescue without perpetuity infrastructure is a temporary holding action, not a long-term solution.</p><p>Three specific redirections could materially improve the current investment picture.&nbsp;</p><ul><li>First, dedicated funding for the tools layer, including web archiving software, ingest pipelines, metadata infrastructure, and identifier systems needs to appear in funding portfolios alongside rescue and coordination projects. Both types of funding are needed, and neither can be substituted for the other.&nbsp;</li><li>Second, structured knowledge exchange with communities that have done this work before, e.g., the digital preservation community, the 2016-2017 data rescue efforts, SUCHO and other more recent engagement, should itself be an active, funded transfer-of-knowledge activity. Where are there tools, models, and examples that we might build on, and who can quickly help us identify their value? Funding these groups to do this research could vastly improve our readiness to act in the near future.</li><li>Third, instead of funding external groups to tell us what our experts know, let’s fund the lynchpins that are already in place and doing the work, and let’s free up some of their time to help surface and advance the models they are already successfully using. Too many of the organizations best positioned to lead this work, including the established data stewards and the coordination hubs, are operating on project-to-project funding with no runway for strategic planning. Shoring up those existing human and organizational network agents so that they can shift from crisis response to longer-term strategizing is likely to be the best investment we can make.&nbsp;</li></ul><p>The urgency of this moment is real, and so is the opportunity it offers. The infrastructure we build in response to this crisis will shape what is possible for data access and preservation for a generation. Building it on the same underfunded, fragmented, misaligned model that has characterized open infrastructure for decades would be a preventable mistake.</p><hr><p><em>IOI is actively mapping the data resilience landscape and tracking investment trends across the ecosystem, and as we do so, we are grateful for the help and perspective of many other groups, including American Geophysical Union, Center for Open Science, Data Rescue Network, Internet Archive, Public Environmental Data Partners, and The Data Foundation. Please contact </em><a href="mailto:katherine@investinopen.org" rel="noreferrer"><em>katherine@investinopen.org</em></a><em> to contribute to or build on this analysis.</em></p> ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ LA Referencia ]]></title>
        <description><![CDATA[ Scaling federated open science infrastructure across Latin America ]]></description>
        <link>https://investinopen.org/our-work/la-referencia/</link>
        <guid isPermaLink="false">6a3cbdd3a978af0001e1f28b</guid>
        <category><![CDATA[ Collective Funding ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Tue, 30 Jun 2026 19:02:36 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ <h2 id="overview">Overview</h2><!-- START case study metadata -->
<p><strong>Duration:</strong> Ongoing<br>
<strong>Team:</strong> Katherine Skinner, Kaitlin Thaney, Lauren Collister, Madelyn Waterbury<br>
<strong>Funders:</strong> <em>Wellcome, Digital Science, Arcadia, Karger Publishers Foundation, Kahle Austin Foundation, EBSCO, Lyrasis</em><br>
<strong>Skillset:</strong> <em>Business Development Advisory, Capacity Building, Collective Funding</em></p>
<!-- END case study metadata --><p>Latin America has built one of the most successful federated open science networks in the world. <a href="https://www.lareferencia.info/?ref=investinopen.org" rel="noreferrer">LA Referencia</a>'s aggregation and discovery platform connects national repositories across Latin America and Spain, making research from more than 500 institutions easier to share, preserve, and discover. It's a model of what regional coordination can accomplish, and the region is ready to take it further.</p><p>LA Referencia's proposal to the IOI Fund for Network Adoption stood out from more than 100 applications across 22 countries for the scale of its ambition, its track record of effective delivery, and its clear vision for the future. </p><h2 id="what-the-project-will-do">What the project will do</h2><p>LA Referencia will extend its platform to an additional 10 Latin American countries, creating a more inclusive and equitable regional network and bringing national science agencies and their repositories into a shared infrastructure.</p><p>The platform itself is getting a major upgrade. An AI-powered multilingual semantic search system will help researchers discover and connect work across languages, supported by metadata enrichment that opens the door to new metrics and more transparent approaches to research assessment throughout the region. The project will publish close to 6 million enriched metadata records through this system.</p><p>Underneath it all, LA Referencia is building a decentralized persistent identifier system and long-term metadata preservation based on blockchain technology and already running at IBICT in Brazil. A regional Dataverse repository for orphan datasets, along with expanded training and translated documentation, rounds out the work.</p><h2 id="where-ioi-comes-in"><strong>Where IOI comes in</strong></h2><p>Infrastructure at this scale thrives on more than good engineering. It needs a story the world can hear, a business model built to last, and connections to the people who can help it grow. That's where our support is focused.</p><p>We're helping LA Referencia organize and amplify its communications so the project's progress reaches funders, institutions, and peer networks across Latin America and beyond. We're also providing project monitoring to support a shared picture of what's working and where momentum is building.</p><p>Alongside that day-to-day work, we're researching the strategic questions that will shape the platform's future, including licensing models and business model options for the long term, and connecting LA Referencia with other projects and partners across our network.</p><h2 id="what%E2%80%99s-next">What’s next?</h2><p>By the end of the project, LA Referencia's platform will reach further than ever before, with a multilingual discovery layer that helps researchers find work unbound by linguistic barriers and a decentralized preservation network that keeps research outputs permanently accessible and verifiable. Technical capacity grows right along with it.</p><p>The larger outcome is strengthened digital sovereignty for Latin America: research infrastructure that the region's own institutions build, govern, and sustain, with scholarship in Spanish and Portuguese as discoverable as work published anywhere else in the world.</p><h3 id="have-a-vision-for-your-region">Have a vision for your region?</h3><p>Some of the most exciting open infrastructure work happens when institutions pool their strengths across borders. If your network has an ambitious idea and needs the funding, business planning, or connections to bring it to life, we want to hear about it. Get in touch to learn how IOI's Coordinated Funding efforts pair investment with hands-on support. </p><div class="kg-card kg-button-card kg-align-left"><a href="https://investinopen.org/contact-us/" class="kg-btn kg-btn-accent">Contact Us</a></div><hr><h2 id="outputs">Outputs: </h2><ul><li><a href="https://investinopen.org/blog/empowering-networks-advancing-openness-invest-in-open-infrastructure-announces-inaugural-grantees-of-the-ioi-fund-for-network-adoption/" rel="noreferrer">Empowering networks, advancing openness: Invest in Open Infrastructure announces inaugural grantees of the IOI Fund for Network Adoption</a></li></ul> ]]></content:encoded>
    </item>
    <item>
        <title><![CDATA[ Infra Finder ]]></title>
        <description><![CDATA[ Building a public tool to help funders and adopters find the open infrastructure they need ]]></description>
        <link>https://investinopen.org/our-work/infra-finder/</link>
        <guid isPermaLink="false">6a3ec205a978af0001e1f43a</guid>
        <category><![CDATA[ Ecosystem Intelligence ]]></category>
        <dc:creator><![CDATA[ Invest In Open Infrastructure ]]></dc:creator>
        <pubDate>Tue, 30 Jun 2026 02:45:01 +0000</pubDate>
        <media:content url="" medium="image"/>
        <content:encoded><![CDATA[ <!-- START case study metadata -->
<p><strong>Duration:</strong> 2024 – present<br>
<strong>Team:</strong> Chrys Wu, Lauren Collister, Emmy Tsang, Sarah Lippincott, Katherine Skinner, Gail Steinhart<br>
<strong>Funders:</strong> Mellon Foundation, Arcadia, Digital Infrastructure Insights Fund, National Science Foundation, Sustaining Circle members<br>
<strong>Skillset:</strong> <em>Ecosystem Intelligence, Landscape Analysis</em></p>
<!-- END case study metadata --><h2 id="overview">Overview</h2><p>The open infrastructure landscape is large and growing but the information needed to navigate it is scattered, inconsistent and held by no neutral party with a view across the whole. There are platforms, standards, repositories, and persistent identifier services doing important work, but they can be difficult to discover and even harder to evaluate side by side. For funders, that made it difficult to direct resources well. For adopters, it made decision-making slower and riskier than it needed to be. And for the infrastructures themselves, it made visibility a persistent challenge.</p><p>IOI, funded by the Mellon Foundation, set out to build something practical: a public tool that gave both funders and adopters the clear, verified, comparable information they needed.</p><h2 id="what-we-did">What we did</h2><p>Before building anything, we needed to understand what funders and adopters actually needed. IOI’s position at the intersection of both stakeholder groups meant that we knew who to talk to and what the real questions were. We spoke with more than 40 institutional budget holders and 26 infrastructure service providers in one-on-one meetings, focus groups, and user testing sessions.&nbsp;</p><p>From there, we built <a href="https://infrafinder.investinopen.org/solutions?ref=investinopen.org"><u>Infra Finder</u></a> as a public-facing product: a searchable, filterable database of open infrastructures that could grow with input from the community. Each entry covers the areas that matter most to evaluators: technical attributes, governance, community engagement, key policies, and funding models — each area a different facet of what it means to be "open".</p><p>Getting the information right required more than a one-time data collection effort. We also built the workflows to source, validate, and keep that information current, working directly with infrastructure providers to make sure what users find in the tool is accurate and up to date. A comparison view lets users look at up to four services side by side, with links to deeper detail where they need it.</p><h2 id="outcomes"><strong>Outcomes</strong></h2><p>Infra Finder launched with coverage of 57 infrastructure services and has since grown to more than 130 thanks to community input.&nbsp;</p><p>For funders, it offers a clearer view of the landscape than existed before, with enough detail to inform real investment decisions. For adopters, it shortens the research process and reduces the risk of choosing infrastructure that turns out to be a poor fit.</p><p>For the infrastructures themselves, it creates a new kind of visibility. As Niels Stern, Managing Director of the OAPEN Foundation, put it: "Participating in this tool provides us with the opportunity to disseminate a lot of information in a very concise way and be more transparent about what we do. This is useful because we can share our entries with institutions, funders, and anyone who wants to work with us or is interested in learning more about our work."</p><p>That transparency matters. Open infrastructure often does essential work quietly, without the visibility that helps funders find it or institutions trust it. Infra Finder was built on the premise that better information, in one place, for everyone, changes that dynamic.</p><h3 id="impact-by-the-numbers">Impact by the numbers</h3><p>In the two years since its inception, Infra Finder has become a go-to resource for open infrastructure diligence in the scholarly community. The site has received over 30,000+ visits, 40,000+ unique pageviews from 130 countries globally since launch. Of these numbers, close to 7,000 returning visits (23% of total visits), highlighting its value as a trusted resource.</p><h2 id="finding-your-way-through-the-landscape">Finding your way through the landscape&nbsp;</h2><p>The open infrastructure ecosystem does not stand still. Platforms emerge, mature, merge, and sometimes close. Funding models shift. The expectations placed on infrastructure by institutions, by policy, and by researchers keep growing. Keeping track of what exists, what it does, and whether it is still the right fit for your needs is genuinely hard work.</p><p>If you're trying to make better decisions about where to invest or what to adopt, <a href="https://infrafinder.investinopen.org/solutions?ref=investinopen.org"><u>Infra Finder</u></a> is a great place to start. And if you need support thinking through what those decisions actually require, we would love to chat!</p> ]]></content:encoded>
    </item>

</channel>
</rss>
