nondominium

内容来源：README.md（说明文档） · 原始地址 · 查看安装指南

原始内容

Nondominium

Ask DeepWiki

Nondominium logo

A ValueFlows-compliant resource sharing Holochain application implementing distributed, agent-centric resource management with embedded governance.

Executive Summary

nondominium is a foundational infrastructure project aimed at enabling a new class of Resources that are organization-agnostic, uncapturable, and natively collaborative. These Resources are governed not by platforms or centralized authorities, but through embedded rules, transparent peer validation, and a comprehensive reputation system.

The project's central goal is to support a peer sharing economy, overcoming the structural flaws of centralized platforms (centralization of power, censorship, unsuitable regulations).

Built on the Holochain framework and using the ValueFlows standard, nondominium allows any Agent to interact with these Resources in a permissionless but accountable environment, with automatic reputation tracking through Private Participation Receipts (PPRs).

Overview

Nondominium is a 3-zome Holochain hApp that enables decentralized resource sharing through:

  • Agent identity management with role-based access control
  • Resource lifecycle tracking following ValueFlows standards
  • Embedded governance for access and transfer rules
  • Capability-based security using Holochain's native features

Architecture

Governance-as-Operator Design:

nondominium implements a modular governance-as-operator architecture that separates data management from business logic enforcement:

  • zome_person: Agent identity, profiles, roles, and capability-based access control
  • zome_resource: Pure data model for resource specifications and lifecycle management (state only)
  • zome_gouvernance: State transition operator that evaluates governance rules and validates changes

Key Architecture Benefits:

  • Modularity: Governance rules can be modified without changing resource data structures
  • Swappability: Different governance schemes can be applied to the same resource types
  • Testability: Governance logic can be unit tested independently of data management
  • Separation of Concerns: Clear boundaries between data persistence and business rule enforcement

Technology Stack:

  • Backend: Rust (Holochain HDK ^0.6.0 / HDI ^0.7.0) compiled to WASM
  • Frontend: Svelte 5.0 + TypeScript + Vite 6.2.5
  • Testing: Vitest 3.1.3 + @holochain/tryorama 0.18.2
  • Client: @holochain/client 0.19.0

Documentation map: See documentation/DOCUMENTATION_INDEX.md. Post-MVP NDO model and optional Unyt / Flowsta integrations are specified in documentation/requirements/ndo_prima_materia.md and the stubs under documentation/requirements/post-mvp/.

Environment Setup

PREREQUISITE: Set up the Holochain development environment.

Enter the nix shell by running this in the root folder of the repository:

nix develop              # Enter reproducible environment (REQUIRED)
bun install              # Install all dependencies

⚠️ Run all commands from within the nix shell, otherwise they won't work.

Development Workflow

Quick Start

bun run start           # Start 2-agent development network with UIs

This creates a network of 2 nodes with their respective UIs and the Holochain Playground for conductor introspection.

Custom Network

AGENTS=3 bun run network    # Bootstrap custom agent network (replace 3 with desired count)

Testing

bun run test                    # Run full test suite
npm run test:foundation         # Basic zome connectivity tests
npm run test:integration        # Multi-agent interaction tests
npm run test:scenarios          # Complete workflow simulations
npm run test:person             # Person management test suite
npm run test:debug              # Verbose test output

Build Pipeline

bun run build:zomes     # Compile Rust zomes to WASM
bun run build:happ      # Package DNA into .happ bundle
bun run package         # Create final .webhapp distribution

Individual Workspaces

bun run --filter ui start      # Frontend development server
bun run --filter tests test    # Backend test execution

Data Model

Core Principles

  • Agent-Centric: All data tied to individual agents with public/private separation
  • ValueFlows Compliance: EconomicResource, EconomicEvent, Commitment data structures
  • Privacy by Design: Public profiles with encrypted private data
  • Capability-Based Security: Role-based access using Holochain capability tokens

Entry Patterns

All zomes follow consistent patterns for:

  • create_[entry_type]: Creates entries with discovery anchor links
  • get_[entry_type]: Retrieves entries by hash
  • get_all_[entry_type]: Discovery via anchor traversal
  • update_[entry_type]: Updates with validation
  • delete_[entry_type]: Soft deletion marking

Testing Architecture

4-Layer Strategy:

  1. Foundation: Basic zome function calls and connectivity
  2. Integration: Cross-zome interactions and multi-agent scenarios
  3. Scenarios: Complete user journeys and workflows
  4. Performance: Load and stress testing (planned)

Test Configuration:

  • Timeout: 4 minutes for complex multi-agent scenarios
  • Concurrency: Single fork execution for DHT consistency
  • Agent Simulation: Supports 2+ distributed agents per test

Distribution

To package the web happ:

bun run package

This generates:

  • nondominium.webhapp in workdir/ (for Holochain Launcher installation)
  • nondominium.happ (subcomponent bundle)

Development Status

  • ✅ Phase 1: Person management with role-based access control
  • 🔄 Phase 2: Resource lifecycle and governance implementation

Documentation

Project Documentation

Zome Documentation

Governance & Security

Governance Architecture:

Reputation & Security:

Applications & Use Cases

Additional Resources

Technology Stack

本页内容由上游仓库自动镜像，如有疑问请访问原始仓库。