Payments BB - CR #121

COMPLETED

Payments BB 3.0 published

• To be presented at Tech committee

• Communication of this released to be coordinated with comms team

• Consent: #85 → v1.3

• e-Signature: #90 → v1.1

• Wallet: #47 → v1.1

• ID: Note / #55 (blocked)

community review

@David Higgins

• Most probably release to be finished this week

• Next steps tbd

• Craft the external communication about future of CFID and know we can put the ad-hoc on-boarding announcement

• @Ali González / @David Higgins to coordinate date for extra CFID onboarding

CFR Architecture release

@Kristo Vaher

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

• Arch WG to meet Wednesday 28th

• Ali to update Spec template docs

• Ali to circulate concept note about machine-readable specs with proposal to change spec template

Registries BB stuck on defining CFRs

@Ali González

Need help or advisory from team on what to do

• Bring this challenge to Arch WG

Implementation Playbook:

• Arch Design CR #29

• CE to test february pre-release of IP

• March they intend to release v1.0

eIDAS Implementation guide:

• CR #3

• CR #4

@Ali González

• @Ali González to work with Yuliia for merge and communicate

• Check with Yuliia what has she thought about feedback mechanism

• Feb 3, 2026 to be presented on tech committee

• February will be for feedback, march to apply feedback, and end of march to release

IM 1.2

• Ali to talk to maksim

Workflow

Ali to talk to maksim to see how to integrate workflow to rest of specs

use case guide status

CMS

Talk to Daniel about his WG and publication process

See when to publish as there is current porject in Senegal

BB-Specs release update:

• Payments: #121 - Waiting for B2G, G2B - Note → possibly jumps to version 3 and or 4

• Consent: #85 → v1.3

• e-Signature: #90 → v1.1

• Wallet: #47 → v1.1

• ID: Note / #55 (blocked)

@Ali González

CFR Architecture release

@Kristo Vaher

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

Communications for the week #90:

• CFR architecture release

• BB specs releases

Community health:

• Onboarding calls update

• Tech Committee call week 4

• others

@Ali González

• There a job posting for Mauritania. We’ll posting that on our internal channels

• @Puja Raghavan has a db for women

• We need to start a DB for the community

Copy https://govstack.gitbook.io/cfr-architecture  to development branch

• delete govstack before ux/ui guidelines

• add a square on for cfr https://govstack.global/our-offerings/govspecs/

•  

@Ali González

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!

•  

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)

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

eIDAS Implementation Guide 1.0

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

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