What state was True Commons left in?

The repository is archived, and its README describes the project as a proof of concept whose backend was not fully integrated and whose interface ran on mock data. Real resource operations and agent authentication were still listed as in progress.

How were you meant to try it?

As a local development instance rather than an installable app: the README describes entering a Holochain development shell with Nix, installing dependencies, and running the SvelteKit interface locally, which then served demonstration data.

How does True Commons relate to Nondominium?

Both trace to Sensorica's commons work. During True Commons development the resource-transfer mechanism was separated out as a distinct component, and Nondominium was the system built to serve as that resource transfer and flow engine.

Project · digital-commons-platform

True Commons

Name: True Commons
Author: Sensorica

a platform for sharing resources in commonsTrue Commons built on REA + Valueflows + hREA + Holochain is a distributed multi-agent systems with reflexivity, learning, and local memory…Maintained by Soushi888, claimed 12 October 2026.

Explore this project Website All projects

How you run it: not recorded
Holochain version: 0.5.3
Activity: archived
Checked: 27 October 2026

What is True Commons and what is it for?

True Commons was a digital commons platform built on Holochain and the ValueFlows economic model, designed so that shared digital resources could be created, improved and passed on without a central owner. Its aim was to let the terms of access and the record of who contributed travel with each resource, so that a design could stay open and still credit the people who worked on it.

True Commons was initiated in 2025 by the Sensorica laboratory as a Holochain-based digital commons platform, a Web 3 successor to earlier Sensorica peer-production work. That earlier work included the Network Resource Planning and Contribution Accounting System, built with Lynn Foster and Bob Haugen in 2013, from which the Valueflows ontology grew. True Commons set out to bring that resource and contribution accounting into a decentralised setting, using Holochain for storage and hREA for Valueflows data.

The plain idea is that a shared digital resource — a design, a plan, a set of instructions — should not depend on one company or one server to keep existing. Anything published is meant to carry its own terms with it: who may use it, who may build on it, and how contributions are recorded. The resource can then circulate and improve while the people who added to it stay visible, and access is open under rules the resource itself carries.

The repository's own illustration is a pair of collaborators: one publishes an open-source irrigation design with build instructions and context attached, another finds it, builds it, improves it and contributes the change back, with the record of both contributions travelling with the design rather than sitting with a platform. The repository's README is the place to read more about the intended model and about how far the prototype got.

How to get it

In a browser

Treat this as a historical prototype: the repository is archived, and the project's own README states it was a proof of concept whose backend was not fully integrated, with the interface running on demonstration data.
The README's development path requires a Holochain development environment entered through its Nix shell (nix develop).
Install project dependencies with bun install, then install the interface dependencies with npm install inside the ui directory.
Start the development server from the ui directory (npm run dev) and open http://localhost:5173.

Source: https://raw.githubusercontent.com/Sensorica/true_commons/main/README.md

Questions people ask

What state was True Commons left in?: The repository is archived, and its README describes the project as a proof of concept whose backend was not fully integrated and whose interface ran on mock data. Real resource operations and agent authentication were still listed as in progress. source
How were you meant to try it?: As a local development instance rather than an installable app: the README describes entering a Holochain development shell with Nix, installing dependencies, and running the SvelteKit interface locally, which then served demonstration data. source
How does True Commons relate to Nondominium?: Both trace to Sensorica's commons work. During True Commons development the resource-transfer mechanism was separated out as a distinct component, and Nondominium was the system built to serve as that resource transfer and flow engine. source

From 4 public sources, checked 23 September 2026.

Try True Commons

Code on GitHubOpen on GitHub ↗Last change 15 October 2025.
Websitesensorica.co ↗
ReleaseNo GitHub release recorded.
The project's own files do not say how it is run.

Details & sources

Source: Sensorica/true_commons

Evidence

Last change: api.github.com/repos/Sensorica/true_commonslisted by a third party · seen since 20 October 2026 · github.repository@1
Activity: api.github.com/repos/Sensorica/true_commonslisted by a third party · seen since 20 October 2026 · liveness@1

Compatibility

hdk: 0.5.3 · Cargo.toml @ b18ed04
hdi: 0.6.3 · Cargo.toml @ b18ed04
holochain-client: 0.20.0-dev.1 · ui/package.json @ b18ed04
happ.yaml: present · workdir/happ.yaml @ b18ed04
web-happ.yaml: present · workdir/web-happ.yaml @ b18ed04

Maintained by Soushi888 since 12 October 2026.