1 of 12

Holo-REA

Deconstructing the monolith

(and friends)

Hi, I’m pospi! Find me at

http://pospi.spadgos.com�or @pospigos on Twitter

2 of 12

3 of 12

people, organisations and relationships

http://nrp.sensorica.co/

economic types and specifications

inventorying

event ledger (observations and measurements)

planning and coordinating

knowledge management & blueprinting

agreements

proposals and order matching

income distribution

✔

Sensorica.
One of many past case studies in applying the ValueFlows model, just the most driven to create operational software
You may have also heard about the software they created, which was named NRP (Network Resource Planner), and performed equivalent functions to most ERP systems.
But- aging software, clunky infrastructure. Needed systems administrators. Getting complex over time.
CLICK
So, the first step in creating a new generation of this software was figuring out the functional building blocks it’s made of

*a few lesser-relevant modules not shown

CLICK
And, these are the ones the Holo-REA project has already implemented so far
This modularisation carries the significant benefit that it allows the software to be smaller.

Devs can choose what is necessary to build, rather than having to implement all of VF.
This is actually most of what’s needed for 90% of operational use cases.

4 of 12

Related projects

https:// CommonsPub .org

Open App Ecosystem

https://github.com/open-app/economic-sentences-graphql

https://researchstudio-sat.github.io/webofneeds/

Web of Needs

https://basisproject.net/

Basis

5 of 12

https://holochain.org

https://github.com/holo-rea/holo-rea/

Holo-REA

6 of 12

Why Holochain?

Scalability-

Entirely eventually-consistent, meaning no locking or throughput limitations.
Resource-efficient. Feasible at hyper-local and global scale.
Fractally composable, permissioned or open networks.

7 of 12

Why Holochain?

Accessibility-

One-click application deployments
Complex reconfigurations of network architecture & inter-network permissions
Provisions for a non-techie-friendly UX�(see https://holo.host/)

8 of 12

Why Holochain?

Autonomy-

No external parties running the system
Every app participant helps to secure the network
Tolerant of network partitions and outages
App upgrades are opt-in

9 of 12

Why Holochain?

Subjectivity-

Objective truth is a fallacy
All data exists in the context of the agent who wrote it down (just like ValueFlows!)
Enables applications to make subjective calculations without requiring a single objective truth (unlike pretty much all other computing)

The other Big Deal about Holochain is subjectivity. This is part of the shift toward what its designers refer to as “agent-centric technologies”.

[CLICKING]

The first acknowledgement is that there is no objective truth, and that any sense of one is a reductive fallacy.

Blockchain’s objective truth, for example, is merely a particular subjective truth, randomly picked at intervals. Objective time does not exist.

Data does not exist in a vacuum. It is always stated in the context of an agent who expresses it. Just like language.

This position is actually completely unique in software. Think about the databases run by businesses & governments- treated as an infallible source of truth; causing problems for you when they become out of sync in reality.

Enables us to compute subjective, independent truths that are more contextually relevant than single truths

It’s an even bigger, and more significant paradigm shift than moving from client/server web apps to blockchain apps was.
Having done a lot of work in blockchain, it did not adequately address the accountability problem or power dynamics of a-priori data
Intersubjectivity requires creators of systems to fully acknowledge their influence.

10 of 12

Towards standardisation

(Source: “Basal project pitch” on YouTube)

event ledger (observations and measurements)

SEEA

WAVES

CSERA

Green GDP

measure

All this stuff about subjectivity gets really important when we start leading into the idea of what technologies and standards mean in addressing the existential threat of climate change.

There are many answers to these questions, and at the lower level ValueFlows is a pretty great answer.
CLICK
I could even point to the specific datatypes which answer this question; which I’ve applied in every context from multinational supply chains to anarchist aid networks to household expenses.
CLICK
But as we go higher up and move further away from reality and into abstractions, answering these questions becomes more contentious and more of an imposition
CLICK
It’s really about what is measured, and who’s ethic we follow.

This is actually a graphic from an old presentation I gave some years ago, when I worked in blockchain. Link in deck, which I’ll share afterwards.

That presentation, as with many others in that industry, suffers from an underlying utilitarian ethic.

CLICK

Actually this group, Sacred Capital, are the only people I’ve met who are trying to democratize the answering of this question; via the lens of Ghandian economics. Everybody else is mostly looking to impose an ethic, not co-create it.

11 of 12

What other monoliths must we deconstruct?

https://intercontinentalcry.org/need-intersectionality-understand-climate-change/

12 of 12

How to get involved

Apps workstream

Converging towards the ValueFlows UI component kit
Multi-network marketplace app to facilitate resource flows between platforms
“HoloFood group” conversations and hackalongs (Thursday!)

Systems workstream

In the middle of an interesting architectural upgrade
Additional standalone modules to be developed

Practitioner workstream

Anybody looking to answer the "what should we measure to prove we're ethical?" question; especially if working with marginalised communities or peer-enforced certifications

VF-UI:

A suite of zero-config, zero-dependency UI components for socioeconomic experimentation
Works with CommonsPub and other implementations too
Building towards an ideal “agent centric application architecture”; see https://github.com/lucksus/perspectivism/

HoloFood group contributors: BASYN Shiro Hypergroove (& SeedShare)

And can intro you to any of the other projects mentioned if you are interested in connecting.

HC workstream

Rust development; greenfield components (perhaps some unchecked items from Sensorica’s featureset) as well as core system available to work on

Practitioner workstream- though we work with governments and industry players too; want to lay out an ideal in “marginalised, peer-enforced”

Because this is a tech that we feel can legitimately service needs in these contexts, it is also an imperative in working equitably to prioritise such collaborations.
And I would also say a necessity, if these efforts are to yield success.

Climate change is a complex, interdependent set of cascading global, bioregional and local system failures.
And I could mention countless grassroots movements, activist groups or environmentalist protests that have made international headlines.
But it is easier to simply say that 80% of the world’s biodiversity is protected by Indigenous peoples, and they do not as yet have a seat at the Climate Change Table.

These projects are our opportunity to help change that, and to create a world where all peoples thrive; not just the Global North.