Add DPGs for DPI criteria

collections/README.md

@@ -8,7 +8,8 @@ Each collection applies a small set of **supplementary criteria** on top of the
 
 | Collection | Status | Criteria | Changelog |
 | :-- | :-- | :-- | :-- |
-| [DPGs for AI](./dpgs-for-ai/) | Draft for community input | [criteria.md](./dpgs-for-ai/criteria.md) | [CHANGELOG.md](./dpgs-for-ai/CHANGELOG.md) |
+| [DPGs for AI](./dpgs-for-ai/) | Published | [criteria.md](./dpgs-for-ai/criteria.md) | [CHANGELOG.md](./dpgs-for-ai/CHANGELOG.md) |
+| [DPGs for DPI](./dpgs-for-dpi/) | Published | [criteria.md](./dpgs-for-dpi/criteria.md) | [CHANGELOG.md](./dpgs-for-dpi/CHANGELOG.md) |
 
 ## Folder structure
 

collections/dpgs-for-dpi/CHANGELOG.md

@@ -0,0 +1,31 @@
+# Changelog — DPGs for DPI Collection criteria
+
+All notable changes to the DPGs for DPI [`criteria.md`](./criteria.md) are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this collection's criteria aim to follow [Semantic Versioning](https://semver.org/) (MAJOR = a change to which criteria are mandatory; MINOR = added/clarified criteria or evidence; PATCH = editorial fixes).
+
+## [0.1] - Unreleased
+
+- Initial draft criteria.
+
+## [1.0] — Published
+
+Supersedes the earlier unversioned working criteria (five flat criteria: society-wide, foundational/modular/reusable, interoperable, inclusive and accessible, secure and private by design).
+
+### Added
+
+- Explicit purpose statement, definitions (DPI, DPG, Building Block), and a table showing how the criteria sit alongside the DPG Standard and the DPG Maturity Model.
+- A "what is not in scope" boundary distinguishing DPI building blocks from general-purpose govtech.
+- "Beyond DPG Standard/Maturity" notes on each Layer 3 criterion, stating the additional DPI-specific expectation.
+- Summary self-assessment checklist.
+
+### Changed
+
+- **Layered model.** Reorganised into Layer 1 (DPG Registry prerequisite), Layer 2 (DPI relevance gateway) and Layer 3 (DPI architecture alignment).
+- **Domain fit is now a gateway test** in Layer 2, separated from the architecture criteria, so a solution outside the DPI domains does not need to read further.
+- **DPI domains expanded from four to five**, using the World Bank DPI framework as the basis. Verifiable credentials, consent management and wallets (previously under Digital ID) become their own **Trust Infrastructure** domain.
+- **Architecture criteria renamed A–E** to map onto CDPI's five DPI architecture principles: Interoperability, Minimalist/Reusable Building Blocks, Ecosystem Enablement, Federation/Decentralization, and Security & Privacy by Design.
+
+### Removed
+
+- **"Inclusive and accessible" as an entry criterion.** It is substantively covered by DPG Standard Indicator 9 (do no harm) and Maturity Model 1.1 (governance) and 3.4 (accessibility); repeating it here duplicated effort.

collections/dpgs-for-dpi/README.md

@@ -0,0 +1,46 @@
+# DPGs for DPI Collection
+
+A DPGA Collection of open-source solutions that function as **foundational building blocks for Digital Public Infrastructure (DPI)** — the shared digital systems that enable governments and markets to operate at population scale.
+
+**Status:** 🟢 Published
+
+**Co-stewards:** Digital Public Goods Alliance (DPGA) Secretariat, [Co-Develop](https://www.codevelop.fund/), and the [Center for Digital Public Infrastructure (CDPI)](https://cdpi.dev/).
+
+## Contents
+
+- [`criteria.md`](./criteria.md) — the technical criteria a DPG must meet to be included (Layers 1–3).
+- [`CHANGELOG.md`](./CHANGELOG.md) — version history of the criteria.
+
+## Objectives
+
+Unlike broader DPGs, solutions in this collection are specifically designed to be **reusable across sectors, interoperable through open standards, and deployable at national scale**. The Collection helps countries identify trusted, proven open-source options for their core digital public infrastructure — covering **identity, payments, data exchange, registries, and trust services** — reducing the need to build from scratch and accelerating safe, inclusive digital transformation.
+
+The public collection is available in the [DPG Registry](https://www.digitalpublicgoods.net/collections/coll-dpi).
+
+## How the criteria are built
+
+The collection asks one focused question: *does this DPG function as a building block for digital public infrastructure — or is it general-purpose govtech?* It answers it through a layered model:
+
+1. **Layer 1 — Prerequisite:** the solution is a recognized DPG in the [DPG Registry](https://www.digitalpublicgoods.net/registry).
+2. **Layer 2 — DPI relevance:** a gateway test (domain fit, cross-sector reusability, population-scale intent). All three must be true.
+3. **Layer 3 — DPI architecture alignment:** five criteria (A–E) drawn from [CDPI's DPI architecture principles](https://docs.cdpi.dev/the-dpi-wiki/dpi-tech-architecture-principles): interoperability, minimalist/reusable design, ecosystem enablement, federation readiness, and security & privacy at scale.
+
+Full detail is in [`criteria.md`](./criteria.md).
+
+## What we're looking for
+
+This is a working draft. We would value community input on, in particular:
+
+- **Domain boundaries** — are the five DPI domains (Digital Identity, Digital Payments, Data Exchange, Foundational Registries, Trust Infrastructure) and the "what is not in scope" boundary drawn in the right place?
+- **Gateway test** — are *cross-sector reusability* and *population-scale intent* assessable in practice, and what evidence should demonstrate them?
+- **Evidence expectations** — are the named evidence artifacts (OpenAPI specs, architecture diagrams, deployment guides, security policies, integration case studies) realistic and assessable from public documentation?
+- **Federation and data sovereignty (Criterion D)** — is the bar right for solutions whose deployment topology depends on the implementing country?
+- **Overlap** — anywhere the criteria unintentionally duplicate the DPG Standard or the Maturity Model rather than complementing them.
+
+## How to contribute
+
+1. **Discuss:** comment on the open pull request for this collection, or open an issue.
+2. **Propose changes:** open a pull request editing [`criteria.md`](./criteria.md) and add a matching entry to [`CHANGELOG.md`](./CHANGELOG.md).
+3. Please follow the repository [Code of Conduct](../../CODE_OF_CONDUCT.md).
+
+Decisions on which suggestions are integrated, adapted, or deferred are recorded so the rationale stays transparent to contributors and co-stewards.