The Resource Center
From the white paper: section 4.4 describes the Resource Center, a service directory and guidance content connected to the wallet, as research on the roadmap; this page says what it is designed to be and confirms that no build exists.
What it is designed to be. The Resource Center Research: nothing is built is planned as a content platform for implementing partners with limited technical capacity. It is designed to hold four kinds of material:
- a service directory: which services exist for a person in a given country, and what each requires;
- guidance content: plain-language explanations of documents, rights and procedures, localizable by country and language;
- goal-path content: the service and requirement descriptions that the goal-path engine would turn into step-by-step journeys;
- partner configuration: an interface through which an implementing partner sets up its own content and goal-path connections without engineering support and without any access to the credential infrastructure.
Why it is not a static portal. The design intent is that information and the pathway to act on it live in one experience. A person reading about a service should be able to start the relevant goal path directly from the service description, carrying their credential context into the wallet flow without re-entering information. That connection is also where the development risk sits: the goal-path engine Research: no shipped code that would execute the started path is itself not built, so Civitas treats the Resource Center as a pilot deliverable rather than a settled design.
How it connects when built. Backend connectivity APIs are planned to link content delivery to the launched iOS and Android wallet Live and to the orchestration engine. Those APIs are intended for the core open-source stack, and the content layer for release under a Creative Commons license, and, like other components still in research, they will be released when they are built; the open-source release of the stack is planned for the first half of 2027, and no license is applied to any repository yet. A partner will be able to deploy the Resource Center on its own, connected to third-party standards-compliant wallet infrastructure, or as part of a full Civitas deployment.
What exists today. Nothing: no repository, no content schema, no prototype. The nearest live behavior sits in the wallet itself, which already guides a holder to the interaction that can issue a credential they are missing. The Resource Center generalizes that mechanism into a configurable content platform. A pilot has to show two things: that a partner with limited technical capacity can configure content and goal-path connections without engineering support, and that a person who begins at a service description completes the goal path the wallet then opens.
Status, 2026-10-01: the Resource Center is not built anywhere; it is a planned item on the funded roadmap, and its content layer is intended for Creative Commons release when it is built.