What makes a digital infrastructure genuinely public rather than just state-backed or widely used?

Host: Welcome to A.I.S. Insights — powered by Living Knowledge. I'm Anna Ivy Summers.

Expert: And I'm Alex Ian Sutherland. Today, we're looking at a 2026 study from the International Conference on Information Systems by Luca Tom Bauer, Selin Arpaci, Konrad Degen, Sasha Köster, and Björn Niehaves. It is titled "Digital Public Infrastructure Through the Lens of Dimensional Publicness."

Host: Alex, digital public infrastructure—or DPI—has become a major topic across tech policy and enterprise strategy. We often hear about systems like digital identity networks or national payment rails referred to simply as "public." But this study argues that the concept is often misunderstood.

Expert: Exactly, Anna. Many policymakers and industry observers assume an infrastructure is automatically "public" just because a government sponsored it, mandated it, or because it operates at national scale. The authors point out that this binary view hides massive variations in actual ownership, operational control, and access rules. An infrastructure can be state-backed, yet privately run and weakly accountable, or broad in reach but practically exclusionary.

Host: So calling something "public" doesn't mean it operates in the public interest. How did the authors approach breaking down this problem?

Expert: They adapted "dimensional publicness" theory from public administration into the information systems field. Methodologically, they used a two-step knowledge synthesis. First, they analyzed twenty-one core theoretical papers on publicness. Then, they conducted a deductive document analysis of sixty-one practical DPI reports and policy documents from around the world to ensure the concepts matched real-world implementations.

Host: And what did that synthesis reveal?

Expert: It produced twelve distinct dimensions of publicness, grouped into three practical layers across an infrastructure's lifecycle. The first is constitutive publicness, which covers how a system is built and funded—things like legal status, political mandate, and ownership of codebases and APIs. The second is normative-relational publicness, looking at ongoing governance, accountability, and ecosystem rules. The third is experienced-realized publicness, focusing on actual use, citizen trust, and delivered socioeconomic outcomes.

Host: That layered view makes a lot of sense. How do those layers interact in practice?

Expert: The authors formulate propositions showing path dependencies. Architectural decisions made during the building phase constrain future governance. Furthermore, the middle governance layer mediates whether formal mandates actually lead to equitable user outcomes. To demonstrate this, the authors compared two major cases: India's Aadhaar and UPI ecosystem, and the European Union's Digital Identity Wallet.

Host: What did that comparison show?

Expert: With India's Aadhaar and UPI, you see very strong constitutive publicness through state authority, paired with massive realized adoption and lower transaction costs. However, the study notes weaknesses in the middle layer: documented data exposures, limited contestability, and challenges with biometric redress. It operates as an "output-legitimated" system where scale compensates for weaker accountability.

Host: And the European Digital Identity Wallet?

Expert: The EU wallet shows strong statutory backing under the revised eIDAS framework, but operational control is distributed across member states and certified private providers. It builds explicit privacy and user-control values into its governance layer, while its ultimate realized adoption and access equity remain to be seen as rollout continues.

Host: Why does this framework matter for business leaders and technology executives?

Expert: For private enterprises building on or integrating with national digital systems, this model provides an audit tool. It helps companies evaluate vendor lock-in risks, regulatory dependencies, and governance transparency before deeply embedding their operations into so-called public rails. It also clarifies where private firms might face compliance bottlenecks when operationalizing public mandates.

Host: In short, it moves the discussion from high-level rhetoric to concrete operational criteria. Thank you, Alex, and thank you to our listeners. Join us next time on A.I.S. Insights.