Holochain Forum

Hackalong: (Shiro) Mapping food buyers clubs onto HoloREA, July 29, 8PM CEST/GMT+2

Shiro is a project aiming to enable strong local networks of individuals and food buyers clubs to form more easily. Some of the project goals are:

  • Strengthening local food communities by working cooperatively
  • Providing better access to local food
  • Cheaper food for the customer, better pay for the producer
  • Local flows of value replaces extractive economies

A few weeks back I made a prototype on coda.io, trying out a flow allowing buyers club to do bulk ordering. @ViktorZaunders translated the prototype to English and posted the following short walkthrough.

Access the prototype here: https://coda.io/d/Order-together_dJ_4WrYPlI9/Order-together_suqJI#_luJGv

Now, together with @lynnfoster (and possibly @bhaugen andor @pospi ?) we’ll do a mapping session looking at how a flow like this can be mapped onto HoloREA.

Join the discussion on Saturday!

  • How can we leverage (mostly) community built components for a use case like this
  • Does everything fit onto the HoloREA model?
  • What modules outside of HoloREA would be needed to realize the full potential of this use case? Payments, group agents, email integration?

Tune in
When : Saturday, August 29 2020, 8pm CEST (GMT+2)
Where : Zoom, Add to Calendar

@Architecture-Course

1 Like

@th1j5 This is the group I was referring to during the DevCamp breakout!

2 Likes

Reminder, this session is happening. In 25 mins ca. Welcome anyone interested in how REA and Holochain could be used to facilitate the emergence of strong local food networks and flows of goods and services.

:carrot::hamburger:

@Architecture-Course

1 Like

Really looking forward to the recording! :slight_smile:

Fun to hear that you want to see it @pospi, a lot of it was clarification on how what we’ve been prototyping maps on to ValueFlows.

The recording is stuck on a computer I won’t reach until wednesday though, but after that I can get it to ya!

Yeah, we had a good runthrough of some of the core REA classes in relation to the prototype I made, thanks @lynnfoster! It turned out most of our needs can be met using Intents, Proposals and Resource Specifications. The majority of the implementation would be quite straight forward, but as always, the devil is in the details.

  • How are currencies expressed?
  • How would shipping be modeled?
  • How would different tax rates be described, for instance in Sweden, edible stuff comes with a 12% VAT and non edible stuff with 25%.
  • How do we agree upon sensible taxonomies to use to describe products - no two producers categorize their produce the same.
  • Group agents
  • Payments / mutual credit
  • Etc

We also talked about the larger issues of how to facilitate interoperability between REA based apps. How much of the app data would live in a common HoloREA DNA and how much live outside the “common database” in an app specific DNA.

How would the actual canvas look where the interoperability happens? How does the fertilizer output of the Basyn biodigester gets routed to become an input or maybe a sellable item in a cooperatively run store powered by Shiro?

Branching from what we actually discussed now…

Just read the NH Loomio thread. Lot’s of great ideas there!

NH apps would have to include this bundling as part of their build process in order to offer UI elements to other apps.

Yes! Apps being able to render representations of their data in an unknown context would be key to facilitate interoperability in the UI. After using coda.io a bit now, I’m a big believer in the “text document” as a base canvas for building custom apps built on standardised components from different providers. Rather than something more dashboard like / control panel like.

1 Like

@kristofer this is really interesting for where a lot of people want to go. And I’ve been thinking something like “personal dashboard”, so I look forward to where you go with this as an alternative. Please keep us all in the loop! :slight_smile:

2 Likes