PSS Working Group Meeting - 23.11.07


Next Meeting:

Tue Dec 5
Join Link (BBB): People and Skills Specification Working Group


Interested in the People and Skills Initiative to capture maker expertise? This is a reminder of our working group meeting coming up next week:

Recap of Action Items

Prior to the next PSS WG Meeting:

  • @schutton will meet with Louis Holbrook and @Jessicang to discuss a proposal for a bilateral trust and promise accounting prototype - scheduled for Nov 16
  • Discuss OSS alternatives for nodes defined in n8n workflow reviewed during meeting - @kny5 has migrated datasets and is currently exploring alternatives including directusdocs/metabase/supabase w/ @schutton
  • Add additional members to the PSS WG on Signal as needed/requested

Meeting Notes

Links shared during meeting

  1. Welcome

  2. Recap / Review of previous action items - see framapad notes for details

  3. Meeting schedule through Spr 2024 - all meetings scheduled for 4pm GMT

  • Dec 5

  • Jan 9

  • Feb 6

  • Mar 5

  • Apr 2

  • May 7

  1. New Business / Items to Discuss

PSS and the Maker Passport - updates and current state

Use cases currently in testing

Framing the work - what is needed?

  • Moving spec from PubPub to IOP Git repo: Internet of Production Alliance · GitHub

  • Data collection, storage, and shareout

  • Continuation of PSS signup to collect more skills/credentials, locations

  • Q: Agents - who verifies credentials? What are the recommendations for adoption RE: microcredentials?

  • Q: Tooling - webform for signup; how do we get from current state to creation of user record?

  • Proposal:

Bilateral trust and promise accounting prototype (concept for discussion)

Base features

  • Define a “promise” or a “statement,” with zero or more data files attached as proof, that can collect any number of signed certifications.

  • Bilateral accounting of a promise using a mutually agreed value unit balance.

  • Management, visualization and management of identities and trust networks.

  • Optional publication of proofs to other ledgers and stores (holochain, blockchain, solid, web2…)

  • Eventual, local-first consistency where scaling is possible but optional.

Initial use case targets

  • Pre-paid credit at a store

  • Course diploma

  • Video documentation of an arbitrary promise (I’ve lent you my mixer and you should give it back in two days)

  • SSL certificate root chains


  • Independent, single process CLI tools to perform any applicaiton-specific action.

  • Well-documented manual discrete steps to perform all action sequences.

  • libgcrypt could be a good reference library for crypto

  • bash scripts mixing self-made CLI tools with common tools like openssl, gpg, hashers etc

  • Signature schemes should be compatible with legal standards (e.g. EU (X)AdES, aswell as QES minus the QSCD)

  • Qualified digital certificate - Wikipedia

  • Trust management, tagger, visualiser and renderer.

  • Open low-end hardware recipe to build special purpose devices for making crypographically signed promises that can be built in average makerspaces.

  • Trust navigator where you can choose who do you trust and how much, and even tag them with visual cue badges and/or stuff like “government I am told to trust” etc.

  • Use trust definitions with a sort of trust processing algo scripting language in the rendering of degree of trust on a certified promise you get from somewhere (who and what gets you to green checkmark or red X, client’s choice).


  • Must work without internet / connection hub (qr code, bluetooth, nfc, sneakernet, CB radio, custom small-area radio comm dongles…)

  • Must allow uninterrupted user interaction even through network latency and outage.

  • Maximum optimization for size for payloads and protocol when comms needed (CB radio carrier capacity may provide a good benchmark).


  • Should run on low-end hardware (perhaps as a challenge Pentium III / 512MB ram?)

  • Requirements for Linux/X11 | Qt 5.15.15 for Device Creation

  • List of Intel Pentium III processors - Wikipedia

  • Portable code, should BE ABLE TO target macos, windows (even if target builds arent actively maintained by us).

  • Specifically use linux phones as build targets (Vollaphone, Pinephone)

  • Specifically use generic/open android OS as build target (lineageos?)

  • At least one open hardware recipe for specific purpose device that can be built at low cost in common maker labs with reasonably common components (ref low-end hardware above).

  • perhaps aim to fulfill requirements for Secure signature creation device - Wikipedia

  • Should support RISCV architecture with as few extensions as necessary.


  • Kirigami/KDE (Qt, QtQuick) with C++ (can target android)

  • Rust, C, C++

  • Holochain WASM VM (if it can be clearly understood and isolated).

Below is a schedule of remaining meetings through Spring 2024 so you can mark your calendars:

  • Dec 5
  • Jan 9 (moved one week due to new calendar year holiday)
  • Feb 6
  • Mar 5
  • Apr 2
  • May 7

If you would like to have an ical forwarded directly to you and/or be added to the calendar invite, please get in touch!

Everyone is welcome to sit in on these meetings. You do not have to already be a part of the group - we look forward to new faces and voices joining the conversation! :v:t4:

1 Like