Enhance governance documentation and specifications

This commit updates the governance documentation and specifications for the Nondominium project, focusing on the role-specific validation rules and private data handling.

Key changes include:
- Clarified definitions of **Agents** and **Economic Events** in governance documentation.
- Introduced a new section on **Role-Specific Validation Rules**, detailing the eligibility and validation process for specialized roles (Transport, Repair, Storage).
- Updated references from encrypted data storage to private entry storage in implementation plans and requirements.
- Revised requirements and user stories to emphasize Nondominium Resources and their governance.
- Enhanced testing documentation to reflect changes in private data handling.

These updates ensure a clearer understanding of governance processes and improve compliance with Holochain's private entry model.

Author: TiberiusB

documentation/Testing_Infrastructure.md

@@ -12,7 +12,7 @@ Our testing approach follows **Holochain community best practices** with emphasi
 - **DHT-Aware Testing**: Accounts for distributed timing and synchronization requirements
 - **Multi-Agent Focus**: Validates true peer-to-peer interactions
 - **Real-World Scenarios**: Tests actual governance and community workflows
-- **Privacy Validation**: Ensures proper encryption and access control boundaries
+- **Privacy Validation**: Ensures proper private entry storage and access control boundaries (see https://developer.holochain.org/build/entries/)
 
 ## Test Architecture
 
@@ -65,7 +65,7 @@ tests/
 - Basic Connectivity Test - Verify zome function calls work
 - Person Creation Test - Validate profile creation functionality
 - Person Profile Retrieval Test - Test profile retrieval and validation
-- Encrypted Data Storage Test - Verify private data encryption/storage
+- Private Data Storage Test - Verify private entry storage
 - Get All Agents Test - Validate community discovery functionality
 - Error Handling Test - Test failure scenarios and edge cases
 
@@ -145,7 +145,7 @@ createTestPerson() → Standard person profile
 createTestPersonVariation(suffix) → Unique profiles for multi-agent tests
 
 // Identity and security data  
-createTestEncryptedData() → Sample encrypted identity data
+createTestPrivateData() → Sample private identity data
 createTestRole() → Standard role assignment data
 ```
 
@@ -155,7 +155,7 @@ Comprehensive response validation:
 
 ```typescript
 validatePersonCreation() → Complete person entry validation
-validateEncryptedDataCreation() → Encrypted data validation  
+validatePrivateDataCreation() → Private data validation  
 validateAgentProfile() → Profile retrieval validation
 ```
 

documentation/governance.md

@@ -10,8 +10,8 @@ This document outlines the governance system implemented in the Nondominium proj
 
 The governance system is built on the ValueFlows REA (Resource, Event, Agent) ontology:
 
-- **Agents**: Individual persons or organizations who perform Economic Events affecting Economic Resources
-- **Economic Events**: Actions that produce, modify, consume, use, or transfer Economic Resources
+- **Agents**: Individual persons who perform Economic Events affecting Economic Resources
+- **Economic Events**: Actions that produce, modify, use, or transfer Economic Resources
 - **Economic Resources**: Useful goods, services, knowledge, or any other value that agents agree to account for
 
 ### 2. Multi-Layered Ontology
@@ -181,15 +181,33 @@ pub struct Claim {
 - **Transfer Conditions**: Rules for transferring resources between agents
 - **Maintenance Obligations**: Requirements for resource maintenance and care
 
+### 4. Role-Specific Validation Rules
+
+Agents seeking to acquire specialized roles such as **Transport**, **Repair**, and **Storage** must undergo additional validation, as defined in the Nondominium governance model ([Sensorica Nondominium](https://www.sensorica.co/environment/hrea-demo-for-nrp-cas/nondominium)):
+
+- **Eligibility**: Only Accountable Agents or Primary Accountable Agents may request these roles.
+- **Validation Process**:
+  1. The agent submits a request to acquire a specialized role (Transport, Repair, or Storage).
+  2. The request is reviewed by one or more existing Primary Accountable Agents who already hold the relevant role.
+  3. The reviewing agents validate the applicant's credentials, history, and, if required, their identity and prior actions.
+  4. Upon successful validation, a ValidationReceipt is issued, and the role is granted to the agent.
+  5. The system may require a minimum number of validators (e.g., 2-of-3 or majority) depending on the resource or process sensitivity.
+- **Criteria for Validation**:
+  - Demonstrated trustworthiness and accountability (e.g., successful prior transactions, positive validation history)
+  - Sufficient knowledge or credentials for the requested role
+  - Compliance with any additional governance rules or obligations (e.g., maintenance standards for Storage, safety for Transport)
+- **Revocation**: Roles can be revoked if the agent violates governance rules, as determined by a validation process involving other Primary Accountable Agents.
+
+These validation rules ensure that only qualified and trusted agents can access and perform critical roles, supporting the self-governance, capture resistance, and accountability principles of the Nondominium system.
+
 ## Economic Actions (VfAction)
 
-The governance system supports all ValueFlows economic actions:
+The governance system supports almost all ValueFlows economic actions:
 
 ### Standard ValueFlows Actions
 - **Transfer**: Transfer ownership/custody
 - **Move**: Move resources between locations
 - **Use**: Use resources without consuming
-- **Consume**: Consume/destroy resources
 - **Produce**: Create/produce new resources
 - **Work**: Apply work/labor to resources
 - **Modify**: Modify existing resources
@@ -249,7 +267,7 @@ The governance system is implemented in `zome_gouvernance` with the following co
 ### 3. Security and Privacy
 - **Capability-based security**: Access control through capability tokens
 - **Pseudonymity**: Agent identities can be pseudonymous
-- **Encrypted data**: Sensitive information is encrypted
+- **Private entries**: Sensitive information (such as user identity and PII) is stored as Holochain private entries in the agent's source chain, not as encrypted blobs on the DHT. See [Holochain Private Entries](https://developer.holochain.org/build/entries/).
 - **Audit trails**: All actions are recorded for accountability
 
 ## Governance Principles

documentation/implementation_plan.md

@@ -26,10 +26,9 @@ Based on the [Nondominium project documentation](https://www.sensorica.co/enviro
   - [ ] Implement validation rules for person creation
   - [ ] Add anchor links for agent discovery (`AllPeople -> Person`)
 
-- [ ] **Encrypted Identity Storage**
-  - [ ] Define `EncryptedAgentData` entry type
-  - [ ] Implement encryption/decryption utilities
-  - [ ] Link encrypted data to public profiles
+- [ ] **Private Identity Storage**
+  - [ ] Define `PrivateAgentData` entry type as a Holochain private entry (see https://developer.holochain.org/build/entries/)
+  - [ ] Link private data to public profiles
 
 - [ ] **Role System Foundation**
   - [ ] Define `Role` entry type with validation metadata
@@ -38,7 +37,7 @@ Based on the [Nondominium project documentation](https://www.sensorica.co/enviro
 
 - [ ] **Core Functions**
   - [ ] `create_person()` - Public profile creation
-  - [ ] `store_encrypted_data()` - PII storage
+  - [ ] `store_private_data()` - PII storage as a private entry
   - [ ] `get_agent_profile()` - Profile retrieval
   - [ ] `get_all_agents()` - Network discovery
 
@@ -100,7 +99,7 @@ Based on the [Nondominium project documentation](https://www.sensorica.co/enviro
 
 - [ ] **Agent Identity Validation**
   - [ ] `validate_agent_identity()` - Validate Simple Agent → Accountable Agent promotion
-  - [ ] Implement encrypted profile verification
+  - [ ] Implement private profile verification
   - [ ] Create validation receipt system
 
 ### Phase 3: Access Control & Security Layer
@@ -220,7 +219,7 @@ dnas/nondominium/zomes/
 
 ### 6.3 Security Metrics
 - [ ] No unauthorized capability escalation
-- [ ] All sensitive data properly encrypted
+- [ ] All sensitive data properly stored as private entries
 - [ ] Validation cannot be bypassed
 - [ ] Resource ownership is immutable