nondominium

Apply Complexity Driven Development (CDD) and Complexity Oriented Programming (COP) principles when writing requirements, architecting systems, or implementing code. Treats software as an evolving coordination structure rather than a deterministic machine. Use when designing distributed, peer-to-peer, agent-centric, governance-heavy, or commons-based systems; when a user mentions complexity, coordination, emergence, holonic/fractal architecture, stigmergy, governance-as-operator, agent-centric design, or Nondominium/Holochain/AD4M-style systems; or when reviewing an architecture for resilience and evolvability under rising complexity.

Nondominium-specific architecture knowledge: NDO three-layer model (Prima Materia/Identity, Specified/ResourceSpec, Custodial/Process), Private Participation Receipt (PPR) system with 16 categories, capability slots as stigmergic attachment surface, ValueFlows alignment patterns for Nondominium's specific EconomicEvent/Commitment usage. USE WHEN working on resource zome, governance zome, lifecycle transitions, PPR issuance, NDO layer activation, capability slots, or any task touching the NDO architecture (ndo_prima_materia.md).