> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/the-worked-examples/e2.1-progressas-catalogue-of-higher-education-services-and-the-blocks-they-rest-on.md). # E2.1 — Progressa's catalogue of higher-education services, and the blocks they rest on Before anyone specifies one service, the sector lists every service its bodies owe, once, with what each rests on. **Subtopic:** 2.1 — One catalogue of the sector's services, and the blocks they share **Public anchor:** UNDP, "Digital public infrastructure", web page (foundational systems that many services connect to); UNDP, *Accelerating the SDGs through Digital Public Infrastructure: A Compendium*, 2023, pages 3 and 4 (digital identity, digital payments and consent-based data sharing); PAERA version 1.0 (GovStack, 2024), section 2.6 ("DPI is not neutral and shapes what can be built on top of it") **Simulated case:** This is a simulated case for Progressa, a fictional country; every institution, name, date and figure in it is invented. **What it shows.** Rows of Progressa's catalogue of higher-education services owed by PHEQA and MoEYS, each naming the body that owes it, its state today and the blocks it rests on, so that the column of the register of institutions shows six services resting on one register. **Form of this example.** The columns of the catalogue are the team's blank instrument and name no country. The rows are filled for Progressa. ## What the catalogue is for Before anyone specifies one service, the sector lists every service its bodies owe, once, with what each rests on. The catalogue is written for the whole sector, not for one project. It is the only document in which a manager can see that one building block, paid for once, carries many services. ## The rows "Rests on" means the service cannot run without the block. ● it rests on the block; ○ it will rest on the block when the block is in place; — it does not need it. | Service | Owed by | State today | PNIA's sign-in | The register of institutions | Linkup | The Payments block | | ------------------------------------------- | -------------------------------------- | --------------------------------------------------------------------------- | -------------- | ------------------------------------------------- | -------------------------------------------- | --------------------- | | Register an institution | PHEQA | On paper; the register is a spreadsheet at the registration desk | ● | ● writes it | — | — | | License an institution | PHEQA, with the minister's decision | On paper; the applicant visits the desk with printed documents | ● | ● | ● the minister's decision crosses from MoEYS | ● the application fee | | Hear an institution's appeal | PHEQA | By letter | ● | ● | — | — | | Approve a change of an institution's name | MoEYS, with PHEQA writing the register | By letter to both bodies; the institution writes twice | ● | ● | ● | — | | Publish the list of registered institutions | MoEYS | The ministry types the list from its own forms | ● | ● | ● | — | | Review a decision of PHEQA | MoEYS | By letter; the ministry asks PHEQA for the file by courier | ● | ● | ● | — | | Issue a learner's credential | PDCA | Not offered; a graduate obtains a certified paper copy from the institution | ○ | ○ only while the institution's licence is granted | ○ | — | ## What the register's column shows Read the column of the register of institutions from top to bottom. The first service writes the register. Every one of the other six rests on it: five now, and the credential later. If PHEQA builds the register once, as a block that others read across Linkup, six services stand on it. If each service keeps its own list of institutions, Progressa pays for seven lists and spends years reconciling them, as the institution in subtopic 1.1 found. Read the column of PNIA's sign-in the same way: six services rest on it now and the seventh will, and none of them needs to build its own way of knowing who a person is. ## Planning enables re-use Inside one project, building your own list of institutions is always faster than agreeing to read somebody else's. That is not a failure of discipline; it is what a project is paid to do. The sum that makes re-use worth it, one register paid for and six services carried, exists only at the level of the whole sector. Only someone who plans for the sector, and keeps this catalogue, can see it. The UNDP describes digital public infrastructure as foundational systems that many services connect to; PAERA adds that the infrastructure shapes what can be built on top of it. The catalogue is where a sector decides which foundation it will build on. **What to look for in your own sector.** Ask for the catalogue before you approve the first project. Look down each column of a block. A block with one service in its column is a project's tool. A block with many is the sector's infrastructure, and it should be planned and funded as such. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/the-worked-examples/e2.1-progressas-catalogue-of-higher-education-services-and-the-blocks-they-rest-on.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.