Who Is Developing Software Using Valueflows
Listed here are some of the developer teams and user groups who have implemented or are implementing Valueflows in open source projects. Please let us know if we have missed you and you would like to be listed.
A generic Valueflows backend is being developed in Holochain, called hREA. Information can be found on the website, on github, chat in discord. hREA exposes the graphql api for UI/UX apps to build on. Blog entry here. (The core is stable for use, but it is missing a few features.)
Some of the UI/UX apps being built on hREA are
Code A, an international group of university professors working on climate change issues, wants to create an application for classes to use as they do practical work to learn about methods for micro to macro climate accounting, and how to coordinate among themselves and with their communities. Code is on github. This is the first real visualization based core UI for Valueflows, and we think will be useful for other apps. (In process.)
New York Textile Lab is a supply chain network that connects designers to fiber producers and mills to help grow an economically diverse textile supply ecosystem. They are featured on this Holochain Ecosystem video. (In process.)
Sensorica, an open value network in Montreal, is just starting design on a new version of their NRP software, which was used as one input for Valueflows. (In process.)
A post called Economy as Ecosystem highlights these user groups.
Bonfire kicked the federation direction off by supporting Valueflows as an extension of ActivityPub, and including the same graphql api as hREA. This supports a user-friendly integration of social and economic networking, which we think is an important direction. Information is at their website, the Valueflows extension is on gitlab. (In process.)
Reflow was an EU funded project that seeks to understand and transform urban material flows, co-create and test regenerative solutions at business, governance, and citizen levels to create a resilient circular economy. The ReflowOS backend was developed by Dyne (see below), built on the Bonfire application. (Complete.)
Interfacer, a collaboration between FabCity Hamburg and Dyne (see below), will build on Reflow to support a global network of Fab Cities that proposes a new urban, economic, social and industrial model that relocalises production to the city and its bioregional context, while building a digital infrastructure enabling ecological, economic and social sustainability. Git repositories are listed here. You can try it here, webinar here, demo here. (Complete for single installations, federation not complete.)
LearnDeep, initially created by students at MSOE, supports a network of high school fablabs in Milwaukee that receive contributions of materials from the community and share these with each other. Their code has been merged upstream and is being completed as a Bonfire flavour by the Bonfire team on gitlab. (In process.)
Web of Needs. The goal is to do automated matching of intents with attached actors/resources on the one side and interaction patterns on the other, such that meaningful interactions can be automatically suggested to users. The code is on github. (In process.)
Basis Project is a protocol for scalable, ecological production. It's using an auto-generated (from the owl file) Valueflows class structure in Rust to drive a reference implementation. The code lives on github. (Complete.)
The Weather Makers are using Valueflows to model their ecosystem planning, engineering and management strategy for restoring water cycles as the key to achieving overall biosphere restoration. Green the Sinai is one ambitious potential project. (In process.)
Whither from here?
Valueflows philosophically seeks to develop in collaboration with user groups on the ground. This round of projects is providing valuable input to the Valueflows vocabulary. We can expect some additions and extensions.
As more implementations are becoming distributed, a particularly interesting direction is composing systems out of VF-enabled apps or modules, or using them to interact with each other. Two possible patterns:
- Composing bigger apps from many smaller apps
- Networks of apps interacting with one another
Following this direction, we will need to figure out the sweet spots for component size and shape for Valueflows Open Apps. If we do that well, many people should be able to create variations on any of the components, and they might be able to work together with any of the other variations. (Depending on devils in details...)