5 mins

1. DMS - Ali to review next steps, Nico to engage

2. AI WG next steps

3. Communication topics

4. Community

1. General catch-up: What has happened in the week that you want to share?

   1. David on Mosip connect

   2. CFR-Arch almost ready but changes a lot

   3. Playbook to go into feedback mode

10 mins

2. Community health:

   1. Tech Committee: Ali: Next meeting is tomorrow, I don’t have agenda but there’s plenty going on. Testing experiences, changes after CFR. CTA: What to do? Good prompt for this discussion is to look at the OKRs and status. There’s actionables for every group

   2. Quarterly Community call: Martha: CTA:

   3. Working Group pages: Nico/Martha: what’s the status, any CTA?

   4. Onboarding call: informational, Ali/David to align on what’s happened so far and how to move forward. No CTA.

5 min per person

3. GovSpecs:

   1. Country feedback mechanism: Informational: Ali and Nico should meet to align on the Information Playbook feedback. Ali has some news on CE. CTA is to meet.

   2. Communications planning: informational: Ali and Ana Julia will meet to agree to communicate Payments 3.0, CFID releases, eIDAS guide. eIDAS guide fb might be extended. We have this working doc for Spec release checklist.

   3. Blogpost on specs and regulations: Nico. Decisional. CTA: What to do? does it hold relevance after the Trust framework? it could actually be a part of releasing the eidas guide the comms piece

   4. ITU AI WG: Informational, Puja made a meeting thursday noon with them. Any CTA?

   5. IM. Informational. Ali to meet with Maksim to go into 1.1 data spaces this week. No CTA. Also IM has new implementation guide. we’ll see this week how to publish.

   6. CFR-Arch: Kristo: what’s next? CTA? after reformulation all specs need to be revised or at least the ones with active WG. Let’s tie to to machine readable specs.

4. GovStack product:

   1. Specs website is being reworked by Nico here. What’s next and CTA? - see point 5, this should be govlearn

   2. Testing and machine readibility: Informational: Ali to work Wallet w/Abraham this week and then move on to payments and CFID specs. Discussion to be had asynch w/nico. Maybe digest what we had on last arch call. cfrs will be reformulated on wallet spec. As an idea ux interviewing on the testing concept / experience can be piloted with wallet and payment solutions. We are working on this doc. https://govstack-global.atlassian.net/wiki/x/BgDuVw

5. GovLearn:

   1. WIGTC: Puja, informational?

   2. GovLearn OKRs. Ali: decisional. There’s no progress, but should be tied to the community and WIGT… and software solutions probably have a lot of knowledge themselves. i.e. they own deployment guides are govlearn content. what to do?

      1. MIFOS finished their content on cross border payments to mastercard. how to translate?

      2. govlearn should have the guides. eidas, AI, use cases, etc.

6. Gitbook housekeeping. Informational. Ali will ask asynch if we can delete the following spaces:

   1. New Landing page test https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/6mVO0w3D4QiEcYE3L9Nf/ seems empty

   2. Test spec https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/AlNE4hFSP2vB0NPFDghI/ seems empty

   3. cfr-security. Kristo migrated it to cfr-arch on a subpage https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/FqG7IwNWNrn5J6cexaf4/

.

.

BB Specifications

• Payments 2.1

• Registries X.X

• IM 1.2

• CMS 1.0-rc

• Architecture specifications (CFR, common terminology, specification framework)

• Payments 3.0 DONE! need comms help

• ID related BBs done, need comms help

• IM on its way

• CMS on its way

• Registries, help is being given by Kristo, Ali and David

• Payments: what next? David and Ali to meet on their tasks

Guidance and communication for the working groups on how to adhere to new architecture specification has been share (e.g. how to write CFR on specifications: both their own, and the Core CFR ones is provided to WG)

Arch meetings keep happening. We should brainstorm. ex. Kristo to make a vlog. A checklist of changes to be made to comply with specs can be made

https://docs.google.com/spreadsheets/d/1U49JSfXV2p_h4lRc-7q18wLWHPDqcKj4MLQmkZASfIg/edit?usp=sharing  

Implementation Playbook 1.0 (incl. service design, architecture guidance and DPI chapter)

February will see the feedback cycle

eIDAS Implementation Guide 1.0

2026-02-11: Published request for comments, need comms help

A Trust Framework concept or outline for all ID-related BBs has been published and circulated internally.

???

A country feedback mechanism has been tested (depending on ITU, GIZ and EstDev collaboration) based on https://govstack-global.atlassian.net/wiki/spaces/GH/pages/1420623878

??? nico and ali to agree on. First step is definitely to have CE sent RFC of Playbook to contractors

Publish a blog post on the intersection of specifications and regulations (currently draft 0.9 with comments of Mikael to be incorporated)

??

For this, identify the tooling, channels and rituals needed, and 1) operate the stablished ones, 2) socialize the new ones, 3) continue developing the needed ones and, 4) document any identified gaps and propose solutions

Community

• One Community Meet up

• Two Onboarding Calls

• Decide how to bring Alumni of all trainings together

AI Chatbot: Facilitator has been selected and WG has been formed and BB proposal has been handed in @Puja Raghavan

Link between Community and GovLearn is clarified:

• Where can they place any Videos/webinars

• How can they organize, conduct and communicate events

• How can they publish document and communicate demos on sandbox

Website Updates:

• Release Community Page

• Release Market Page

• GC Feedback on Landing Page

Have a machine readable version 0.0.9 published for all specifications - to be meta-spec by Q2

Publish version 0.9 of the machine-readable version for the specification (its schema)

A prototype of machine-readable specifications (Wallet BB) has been developed (covering parsing specs from gitbook to github json to Compliance WebApp, optionally test editing and reading UI or ITB)

• Present a decision proposal to GC on what parts of the Sandbox should be handed-over/maintained by the new GovStack Foundation