mindforge-cc 5.0.0 → 5.2.0

package/MINDFORGE.md

@@ -1,12 +1,12 @@
-# MINDFORGE.md — Parameter Registry (v4.1.0-alpha.nexus)
+# MINDFORGE.md — Parameter Registry (v5.1.0-beast)
 
 ## 1. IDENTITY & VERSIONING
 
 [NAME]    = MindForge
-[VERSION] = 4.2.0-alpha.ztai
-[STABLE]  = false
-[MODE]    = "Zero-Trust Identity"
-[REQUIRED_CORE_VERSION] = 4.2.0
+[VERSION] = 5.1.0
+[STABLE]  = true
+[MODE]    = "Zero-Trust Agentic Hub"
+[REQUIRED_CORE_VERSION] = 5.1.0
 
 ## 2. INTELLIGENCE TOGGLES (V4 UPDATES)
 
@@ -28,7 +28,8 @@
 
 ## 3. MODEL TOPOLOGY
 
-# Persona to Model mapping
+### Persona to Model mapping
+
 [PLANNER]  = claude-opus-4-5
 [EXECUTOR] = claude-sonnet-4-5
 [REVIEWER] = claude-sonnet-4-5
@@ -42,7 +43,8 @@
 
 ## 4. GOVERNANCE & ECONOMICS
 
-# Limits and safety gates
+### Limits and safety gates
+
 [COST_WARN_USD]       = 2.00
 [COST_HARD_LIMIT_USD] = 25.00
 [ADS_DEBATE_ROUNDS]   = 2
@@ -54,7 +56,8 @@
 
 ## 5. RESOURCE GEOMETRY
 
-# Paths and ports
+### Paths and ports
+
 [BROWSER_PORT]    = 7338
 [DASHBOARD_PORT]  = 7339
 [API_URL]         = <http://localhost:3000>
@@ -64,16 +67,21 @@
 
 ## 6. PROJECT CONSTRAINTS
 
-# Static rules for the agent
+### Static rules for the agent
+
 [FORBIDDEN] = """
+
 - No direct DB access from frontend
 - No synchronous I/O in API handlers
 - No console.log in production services
 - No TODO comments in committed code
+
 """
 
 [INSTRUCTIONS] = """
+
 - Check packages/shared before creating utilities.
 - Backend middleware follows Fastify conventions.
 - Date manipulation using date-fns only.
+
 """

package/README.md

@@ -1,7 +1,7 @@
-# MindForge — Enterprise Agentic Framework (v5.0.0)
+# MindForge v5.1.0 — The Beast AdditionFramework (v5.1.0)
 
 MindForge turns AI coding agents into production-grade engineering partners with governance, multi-cloud resilience, and a non-bypassable Sovereign Reason Enclave.
-Release published: v5.0.0-PRO.
+Release published: v5.1.0-PRO.
 
 ## Installation & Setup
 

package/RELEASENOTES.md

@@ -1,20 +1,29 @@
+# MindForge v5.1.0 — The Beast Addition
+## Top Summary
+The v5.1.0 release integrates 14 advanced agentic protocols and high-performance session hooks, sanitizing and hardening them for the MindForge ecosystem.
+
+## Highlights
+- **14 Advanced Protocols**: Ported from the Superpowers framework (Brainstorming, Swarm Execution, Parallel Mesh, etc.).
+- **Native Session Initializer**: replaces legacy bash hooks with high-performance Node.js startup logic.
+- **Workflow Step 0 Participation**: Core commands now mandate protocol activation for maximum tactical rigor.
+- **Full Sanitization**: 100% elimination of external branding across all registries.
+
+---
+
 # MindForge v5.0.0 — Enterprise Pillars V, VI, VII
 ## Top Summary
 The v5.0.0 release completes the MindForge Enterprise architecture with the final three pillars: Multi-Cloud Arbitrage, Sovereign Reason Enclaves (SRE), and Dynamic Human-Agent Handover (DHH).
 
 ## Highlights
-- **Pillar V: Multi-Cloud Arbitrage**: Intelligent routing across Vertex AI, Bedrock, and Azure with low-latency hedging and autonomous Provider Fallback protocols.
-- **Pillar VI: Sovereign Reason Enclaves (SRE)**: Simulated TEE-based reasoning isolation for confidential workloads, ensuring zero-visibility thought-chains and automatic sanitization of reasoning traces in global logs.
-- **Pillar VII: Dynamic Human-Agent Handover (DHH)**: Automated packaging of "Nexus State Bundles" for human review when confidence scores drop, featuring real-time "Human Steering" injection into the autonomous stream.
-- **Hardening: Beast Mode Phase 2**: Built-in Chaos Mode for provider reliability stress-testing and mandatory state hashing for all handover bundles.
+- **Pillar V: Multi-Cloud Arbitrage**: Intelligent routing across Vertex AI, Bedrock, and Azure.
+- **Pillar VI: Sovereign Reason Enclaves (SRE)**: Simulated TEE-based reasoning isolation.
+- **Pillar VII: Dynamic Human-Agent Handover (DHH)**: Automated packaging of "Nexus State Bundles" for human review.
+- **Hardening: Beast Mode Phase 2**: Built-in Chaos Mode for provider reliability stress-testing.
 
 ---
 
 # MindForge v4.3.0 — Enterprise Mesh & Proactive Equilibrium
 
-## Top Summary
-MindForge v4.3.0 introduces the **Enterprise Intelligence Mesh**, finalizing the v4 roadmap with autonomous FinOps and self-healing reliability. This release also implements **ZTAI Beast Mode**, hardens agentic identity with asymmetric cryptographic signing, and introduces simulated Secure Enclaves (HSM) for Tier 3 principal agents.
-
 ## Highlights
 
 - **Pillar V: Autonomous FinOps Hub**: Dynamic **C2C (Confidence-to-Cost)** model routing and real-time Agentic ROI tracking.

package/bin/memory/federated-sync.js

@@ -9,6 +9,8 @@ const path  = require('node:path');
 const Store = require('./knowledge-store');
 const EISClient = require('./eis-client');
 const crypto = require('node:crypto');
+const EmbeddingEngine = require('./embedding-engine');
+const adsEngine = require('../review/ads-engine');
 
 class FederatedSync {
   constructor(config = {}) {
@@ -92,16 +94,94 @@ class FederatedSync {
     for (const remote of remoteEntries) {
       const local = existingById.get(remote.id);
       
-      // Conflict Resolution: Remote Wins if timestamp is newer
-      if (!local || new Date(remote.timestamp) > new Date(local.timestamp)) {
+      if (!local) {
         fs.appendFileSync(globalPath, JSON.stringify(remote) + '\n');
         mergedCount++;
+        continue;
       }
+
+      // Pillar I (v5.2.0): Hybrid Semantic synthesis
+      let similarity = 0;
+      try {
+        similarity = EmbeddingEngine.cosineSimilarity(
+          EmbeddingEngine.computeTfIdfVector(EmbeddingEngine.tokenize(local.content), {}, 1),
+          EmbeddingEngine.computeTfIdfVector(EmbeddingEngine.tokenize(remote.content), {}, 1)
+        );
+      } catch (err) {
+        console.error(`[FIM-ERR] Semantic analysis failed for ${local.id}. Falling back to LWW.`, err);
+        // Fallback to basic LWW (Last-Write-Wins)
+        if (new Date(remote.timestamp) > new Date(local.timestamp)) {
+          this.writeToGlobalKB(remote, globalPath);
+        }
+        continue;
+      }
+
+      this.triggerHybridSynthesis(local, remote, similarity, globalPath);
+      mergedCount++;
     }
     
     return mergedCount;
   }
 
+  /**
+   * Hybrid Synthesis Logic (Pillar I v5.2.0)
+   */
+  async triggerHybridSynthesis(local, remote, similarity, globalPath) {
+    console.log(`[FIM-SYNC] Analyzing semantic overlap for ${local.id} (Similarity: ${similarity.toFixed(4)})`);
+
+    // 1. LWW (Similarity > 0.9) - Near identical
+    if (similarity > 0.9) {
+      if (new Date(remote.timestamp) > new Date(local.timestamp)) {
+        this.writeToGlobalKB(remote, globalPath);
+        console.log(`  └─ [LWW] Auto-resolved via timestamp.`);
+      }
+      return;
+    }
+
+    // 2. Autonomous Merge (0.75 - 0.9) - Semantic Overlap
+    if (similarity > 0.75) {
+      console.log(`  └─ [ADS] Triggering Autonomous Knowledge Synthesis...`);
+      const merged = await this.triggerADSMerging(local, remote);
+      this.writeToGlobalKB(merged, globalPath);
+      return;
+    }
+
+    // 3. Human Stewardship (0.6 - 0.75) - Probable Disagreement
+    if (similarity > 0.6) {
+      console.log(`  └─ [DHH] High disagreement. Triggering Nexus Handover...`);
+      this.localStore.markConflict(local.id, remote);
+      return;
+    }
+
+    // 4. Collision Isolation (< 0.6) - Topic Mismatch
+    console.log(`  └─ [ISO] Semantic collision (Topic mismatch). Isolating entries.`);
+    this.writeToGlobalKB({ ...remote, id: `${remote.id}_collision_${Date.now()}` }, globalPath);
+  }
+
+  async triggerADSMerging(local, remote) {
+    const result = await adsEngine.runADSSynthesis({
+      phaseNum: 'SYNC',
+      goal: `Synthesize a unified knowledge entry for topic: ${local.topic || local.id}`,
+      context: `Local Entry: ${local.content}\n\nRemote Entry: ${remote.content}`,
+      sessionId: 'fim-sync-v5.2.0'
+    });
+
+    // Extract the final plan/content from ADS result
+    const mergedContent = fs.readFileSync(path.join(process.cwd(), '.planning', 'PLAN.md'), 'utf8');
+    
+    return {
+      ...remote,
+      content: mergedContent,
+      confidence: 1.0,
+      synthesis_id: result.ads_id,
+      timestamp: new Date().toISOString()
+    };
+  }
+
+  writeToGlobalKB(entry, globalPath) {
+    fs.appendFileSync(globalPath, JSON.stringify(entry) + '\n');
+  }
+
   isRecentlySynced(id) {
     // Simple check against local sync-history log
     if (!fs.existsSync(this.syncHistoryPath)) return false;

package/docs/INTELLIGENCE-MESH.md

@@ -1,5 +1,5 @@
 # MindForge Federated Intelligence Mesh (FIM)
-MindForge v5.0.0 — Distributed Intelligence Sharing
+MindForge v5.1.0 — Distributed Intelligence Sharing
 
 ## 1. Overview
 The **Federated Intelligence Mesh (FIM)** is the enterprise-grade evolution of the Global Intelligence Mesh. It transitions MindForge from machine-local memory to a distributed organizational intelligence network. Using a central **Enterprise Intelligence Service (EIS)**, FIM enables seamless, authenticated knowledge synchronization across all agents and projects in the enterprise.
@@ -15,7 +15,11 @@ The V5 mesh is built on three core pillars residing in `bin/memory/`:
 ### B. Federated Sync (`federated-sync.js`)
 - **Role**: High-performance synchronization engine between local stores and the organizational mesh.
 - **Delta Sync**: Tracks the `last_sync` timestamp to only pull new organizational insights, significantly reducing latency and compute costs.
-- **Conflict Resolution**: Uses **LWW (Last-Write-Wins)** logic with cryptographic version checks to handle concurrent updates from different agents.
+- **Conflict Resolution**: Uses **Hybrid Semantic Synthesis** (Pillar I v5.2.0). 
+  - **Similarity > 0.9**: Near-identical; auto-resolve via **Last-Write-Wins (LWW)**.
+  - **0.75 - 0.9**: Semantic Overlap; triggers **Autonomous ADS Merging**.
+  - **0.6 - 0.75**: Conflict; triggers **Nexus Handover (DHH)** for human steering.
+  - **< 0.6**: Topic Collision; isolates entries into unique IDs to prevent data loss.
 
 ### C. Knowledge Graph Bridge (`knowledge-graph.js`)
 - **Role**: Unified memory interface that resolves both local project nodes and remote federated nodes.
@@ -32,4 +36,4 @@ The V5 mesh is built on three core pillars residing in `bin/memory/`:
 - **Elimination of Redundancy**: Multi-thousand-token research chains are executed once and shared universally across the mesh.
 
 ---
-*Status: V5 "Beast" Mode Implemented & Verified (2026-03-28)*
+*Status: V5.2.0 Semantic Consensus Implemented & Verified (2026-03-28)*

package/docs/PERSONAS.md

@@ -19,7 +19,8 @@ MindForge uses a multi-agent orchestration model where specialized personas are
 | **Persistence & Memory** | 1 | mf-memory |
 | **Infrastructure & Tools** | 1 | mf-tool |
 | **Strategy & Ops** | 5 | roadmapper, release-manager, tech-writer, roadmapper-extend, user-profiler |
-| **Debuggers** | 1 | debugger |
+| **Neural Protocols** | 6 | brainstormer, swarm-pilot, mesh-orchestrator, workspace-manager, skill-author, tdd-master |
+| **Debuggers** | 2 | debugger, rca-expert |
 | **Mapping** | 2 | codebase-mapper, codebase-mapper-extend |
 
 ---
@@ -505,7 +506,7 @@ MindForge uses a multi-agent orchestration model where specialized personas are
 
 **Role:** Executes implementation plans with atomic commit discipline.
 
-| Property | Value |
+| **Property** | **Value** |
 | :--- | :--- |
 | **Spawned by** | `/mindforge:execute-phase`, `/mindforge:agent executor` |
 | **Tools** | Read, Write, Bash, Grep, Glob, CmdStatus, ReadTerminal |
@@ -614,6 +615,152 @@ MindForge uses a multi-agent orchestration model where specialized personas are
 
 ---
 
+---
+
+### mindforge-brainstormer (The Ideation Catalyst)
+
+**Role:** Expert in deep requirements discovery and behavioral ideation.
+
+| Property | Value |
+| :--- | :--- |
+| **Spawned by** | `/mindforge:brainstorming` |
+| **Tools** | Read, Write, Bash, Grep |
+| **Color** | `magenta` |
+| **Trust Tier** | `1` |
+
+**Capabilities:**
+- Proactive discovery of edge cases and user intent.
+- Drafting high-fidelity visual companions and behavioral specs.
+- Challenging assumptions through Socratic engineering.
+
+---
+
+### mindforge-swarm-pilot (The Parallel Executor)
+
+**Role:** Orchestrates multiple independent implementation tasks simultaneously.
+
+| Property | Value |
+| :--- | :--- |
+| **Spawned by** | `/mindforge:swarm-execution` |
+| **Tools** | Read, Write, Bash, Grep, CmdStatus |
+| **Color** | `yellow` |
+| **Trust Tier** | `2` |
+
+**Capabilities:**
+- Managing independent "Execution Waves".
+- Merging parallel contributions with zero conflict.
+- Maintaining high-velocity implementation loops.
+
+---
+
+### mindforge-mesh-orchestrator (The Context Guardian)
+
+**Role:** Synchronizes state and context across parallel agent workstreams.
+
+| Property | Value |
+| :--- | :--- |
+| **Spawned by** | `/mindforge:parallel-mesh` |
+| **Tools** | Read, Write, Bash, Grep, Context7 |
+| **Color** | `cyan` |
+| **Trust Tier** | `2` |
+
+**Capabilities:**
+- Maintaining a unified "Shared Reality" for swarms.
+- Preventing context drift in complex multi-agent sessions.
+- Dynamic propagation of architectural decisions.
+
+---
+
+### mindforge-workspace-manager (The Environment Architect)
+
+**Role:** Manages isolated development environments and project sharding.
+
+| Property | Value |
+| :--- | :--- |
+| **Spawned by** | `/mindforge:workspace-isolated` |
+| **Tools** | Read, Write, Bash, Git |
+| **Color** | `blue` |
+| **Trust Tier** | `3` |
+
+**Capabilities:**
+- Provisioning git worktrees for isolated feature branches.
+- Managing workspace cleanup and state protection.
+- Ensuring atomic environment parity across branches.
+
+---
+
+### mindforge-skill-author (The Framework Evolver)
+
+**Role:** Expert in authoring and validating new MindForge skills.
+
+| Property | Value |
+| :--- | :--- |
+| **Spawned by** | `/mindforge:skill-creation` |
+| **Tools** | Read, Write, Bash, Grep |
+| **Color** | `purple` |
+| **Trust Tier** | `3` |
+
+**Capabilities:**
+- Drafting [SKILL.md] instructions and tool-chains.
+- Validating skill quality against the 7-Dimension Registry.
+- Hardening framework protocols for framework-level releases.
+
+---
+
+### mindforge-tdd-master (The Quality Zealot)
+
+**Role:** Enforces strict Test-Driven Development loops with adversarial rigor.
+
+| Property | Value |
+| :--- | :--- |
+| **Spawned by** | `/mindforge:tdd` |
+| **Tools** | Read, Write, Bash, Grep, CmdStatus |
+| **Color** | `red` |
+| **Trust Tier** | `2` |
+
+**Capabilities:**
+- Enforcing Red-Green-Refactor discipline.
+- Automated generation of regression-proof test suites.
+- Validating implementation against pure behavioral specs.
+
+---
+
+### mindforge-rca-expert (The Forensic Scientist)
+
+**Role:** Principal specialist in advanced root cause analysis and forensic debugging.
+
+| Property | Value |
+| :--- | :--- |
+| **Spawned by** | `/mindforge:debug_extended` |
+| **Tools** | Read, Write, Bash, Grep, CmdStatus, ReadTerminal |
+| **Color** | `orange` |
+| **Trust Tier** | `2` |
+
+**Capabilities:**
+- Log-based forensic reconstruction of failures.
+- Identifying systemic architectural flaws.
+- Proving fix validity through falsifiable regression tests.
+
+---
+
+### mindforge-neural-orchestrator (The Framework Pilot)
+
+**Role:** The core identity responsible for activating and managing the protocol mesh.
+
+| Property | Value |
+| :--- | :--- |
+| **Spawned by** | `/mindforge:neural-orchestrator` |
+| **Tools** | All |
+| **Color** | `white` |
+| **Trust Tier** | `3` |
+
+**Capabilities:**
+- Booting the MindForge Session Engine.
+- Dynamically loading required protocols for the task.
+- Enforcing the Master Directive across all sub-agents.
+
+---
+
 ### mindforge-user-profiler (The Relationship Manager)
 
 **Role:** Analyzes session history to personalize agent interactions and technical alignment.
@@ -649,6 +796,7 @@ MindForge V4 introduces the ability to spawn dynamic, task-aware clusters of spe
 | **ComplianceSwarm** | compliance-auditor | legal-compliance, architect, security | GDPR/SOC2 alignment, PII masking |
 | **IdentityTrustSwarm** | identity-architect | security-reviewer, architect, blockchain | Zero-Trust, DID-based signing |
 | **DataMeshSwarm** | data-engineer | db-optimizer, analyst, compliance | Lakehouse patterns, ETL integrity |
+| **NeuralSwarm** | mesh-orchestrator | brainstormer, swarm-pilot, workspace-manager | High-fidelity protocol execution |
 
 ### Swarm Governance Protocols
 

package/docs/architecture/V5-ENTERPRISE.md

@@ -1,8 +1,8 @@
 # MindForge v5 Architecture: The Enterprise Beast
 
-MindForge v5.0.0 is the definitive enterprise-grade evolution of the agentic framework. This major version introduces distributed intelligence and absolute governance via a zero-trust policy-as-code layer.
+MindForge v5.1.0 is built on a distributed "Agentic OS" architecture. This major version introduces distributed intelligence and absolute governance via a zero-trust policy-as-code layer.
 
-## Core Pillars (v5.0.0)
+## 1. Core Architectural Pillars (v5.1.0)
 
 ### Pillar I: Federated Intelligence Mesh (FIM)
 
@@ -10,16 +10,17 @@ The FIM transitions MindForge from local knowledge silos to a shared organizatio
 
 - **Distributed Sync (LWW)**: Cross-node synchronization using Last-Write-Wins (LWW) conflict resolution with cryptographic versioning.
 - **Delta Pull Protocol**: Intelligent synchronization that only retrieves new insights since the last successful sync, minimizing bandwidth and latency.
-- **Enterprise Intelligence Service (EIS)**: A high-availability central hub for sharing high-confidence agentic findings across the entire enterprise.
+- **Enterprise Resilience & Governance (v5.1.0)**: A high-availability central hub for sharing high-confidence agentic findings across the entire enterprise.
 - **ZTAI-Signed Provenance**: Every piece of knowledge in the mesh is cryptographically tied to the DID of the agent that generated it.
 
 ### Pillar II: Agentic Policy Orchestrator (APO)
 
-The APO provides a non-bypassable governance layer that evaluates every autonomous wave against organizational security policies.
+# MindForge Governance Guide (v5.1.0)
+MindForge v5.1.0 introduces a non-bypassable, intent-level governance layer that evaluates every autonomous wave against organizational security policies.
 
 - **Policy-as-Code (PaC)**: Security rules are defined in declarative JSON/YAML schemas, enabling version-controlled governance.
 - **Real-Time Intent Interception**: The `AutoRunner` intercepts swarm intents (Action, Resource, DID, Tier) before execution.
-- **Dynamic RBAC Mapping**: Automatically assigns project roles based on an agent's **Zero-Trust Agentic Identity (ZTAI)** trust tier.
+- **Dynamic RBAC Mapping**: v5.1.0 automatically maps ZTAI Trust Tiers to project roles based on an agent's **Zero-Trust Agentic Identity (ZTAI)** trust tier.
 - **Fail-Safe Governance**: "Default Deny" posture for sensitive operations (API key access, infra modification, etc.).
 
 ### Pillar III: Predictive Agentic Reliability (PAR)
@@ -99,9 +100,9 @@ DHH creates a seamless bridge between fully autonomous execution and high-precis
 
 ---
 
-## Identity & Trust (ZTAI Interlocks)
+## ZTAI & Enclave Security (v5.1.0)
 
-MindForge v5 utilizes **Zero-Trust Agentic Identity (ZTAI)** as the root-of-trust for all enterprise operations.
+MindForge v5.1.0 enforces **Zero-Trust Agentic Identity (ZTAI)** as the root-of-trust for all enterprise operations.
 
 1.  **Identity Verification**: Agents prove their identity using Ed25519 signatures.
 2.  **Tier Escalation**: Tier 0-1 agents are limited to analytical tasks. Tier 2 agents gain implementation roles. Tier 3 agents (signed by HSM-secured identities) execute in **Sovereign Reason Enclaves**.

package/docs/commands-reference.md

@@ -1,4 +1,4 @@
-# MindForge v2.4.0 — Commands Reference
+# MindForge v5.1.0 — Commands Reference
 
 MindForge commands are organized into functional pillars to support the entire software development lifecycle (SDLC).
 
@@ -35,6 +35,7 @@ MindForge commands are organized into functional pillars to support the entire s
 | `/mindforge:personas --list` | Displays all 32+ specialized engineering personas. |
 | `/mindforge:personas --set ID` | Switches the current agent to a specific persona (e.g., `architect`, `executor`). |
 | `/mindforge:tokens` | Analyzes and profiles token usage for the current session. |
+| `/mindforge:neural-orchestrator` | Activates the advanced protocol layer for the current session. |
 | `shard-helper --verify` | (CLI Internal) Verifies the integrity and SHA-256 checksums of memory shards. |
 
 ---
@@ -62,3 +63,21 @@ MindForge commands are organized into functional pillars to support the entire s
 | `/mindforge:migrate` | Migrates project metadata between framework versions. |
 | `/mindforge:audit --export` | Generates a human-readable PDF report of the session audit log. |
 | `/mindforge:join-discord` | Join the MindForge developer community for support and collaboration. |
+
+---
+
+## 6. Advanced Neural Protocols (Beast Addition)
+
+These protocols represent specialized, high-fidelity engineering behaviors ported and hardened for the MindForge ecosystem.
+
+| Command | Description |
+| :--- | :--- |
+| `/mindforge:brainstorming` | Deep ideation and requirement exploration before planning. |
+| `/mindforge:swarm-execution` | Swarm-based implementation for independent tasks. |
+| `/mindforge:parallel-mesh` | Orchestrates context across multiple parallel agent waves. |
+| `/mindforge:workspace-isolated` | Manages isolated development environments via git worktrees. |
+| `/mindforge:skill-creation` | Expert protocol for authoring new MindForge skills. |
+| `/mindforge:review-request` | Formalizes peer review requests for completed implementation waves. |
+| `/mindforge:tdd` | Enhanced Test-Driven Development protocol with strict verification. |
+| `/mindforge:debug` | Advanced systematic debugging with persistent state tracking. |
+| `/mindforge:verify-work` | Multi-level truth verification (existence, substance, wiring). |

package/docs/governance-guide.md

@@ -1,8 +1,8 @@
-# MindForge Governance Guide (v5.0.0)
+# MindForge Governance Guide (v5.1.0)
 Absolute Control through Policy-as-Code (PaC)
 
 ## 1. Goal
-MindForge v5.0.0 introduces a non-bypassable, intent-level governance layer. This guide explains how **Agentic Policy Orchestration (APO)** and **Zero-Trust Agentic Identity (ZTAI)** work together to secure the enterprise development lifecycle.
+MindForge v5.1.0 introduces a non-bypassable, intent-level governance layer. This guide explains how **Agentic Policy Orchestration (APO)** and **Zero-Trust Agentic Identity (ZTAI)** work together to secure the enterprise development lifecycle, now hardened by the **Neural Protocol Mesh**.
 
 ## 2. Agentic Policy Orchestrator (APO)
 The APO is a decentralized governance engine that intercepts every autonomous intent before it is executed.
@@ -21,7 +21,7 @@ The `PolicyEngine` evaluates this intent against organizational **Policy-as-Code
 - **Escalate**: The action requires a higher-tier DID signature or explicit HITL (Human-in-the-Loop) approval.
 
 ## 3. Trust Tier Architecture (ZTAI Hardened)
-V5.0.0 automatically maps ZTAI Trust Tiers to explicit project roles through the `RBACManager`.
+V5.1.0 automatically maps ZTAI Trust Tiers to explicit project roles through the `RBACManager`.
 
 | Tier | Role | Scope | Hardening |
 | :--- | :--- | :--- | :--- |
@@ -30,18 +30,24 @@ V5.0.0 automatically maps ZTAI Trust Tiers to explicit project roles through the
 | **2** | Specialized | Security/DevOps Specialist. | Access to `/security`, `/infra`, and `/bin/governance`. |
 | **3** | Principal | Lead Architect / Core Engine. | **HSM-Enclave Signing Required** for all engine modifications. |
 
-## 4. Governance Workflow (V5)
+## 4. Protocol Mesh Governance (v5.1.0 Enhancement)
+The **Beast Addition** integrates protocol-level governance into the APO engine.
+- **Protocol Enforceability**: Every protocol activation (e.g., `/mindforge:tdd`) is logged as a governance event.
+- **Mesh Integrity**: The **Parallel Mesh** synchronizes governance state across multiple agents, preventing "split-brain" policy execution.
+- **Skill Compliance**: New skills created via `/mindforge:skill-creation` are automatically audited for APO compatibility.
+
+## 5. Governance Workflow (V5.1.0)
 1. **ZTAI Handshake**: Agent proves identity using Ed25519 signatures.
 2. **Intent Pulse**: Agentic intent is broadcast to the policy interceptor.
 3. **APO Evaluation**: Policy engine checks the intent against PaC rules.
 4. **Role binding**: `RBACManager` grants or revokes permissions based on the active trust tier.
 5. **Verified Wave**: Execution proceeds only if all policy gates are clear.
 
-## 5. Enterprise Policies
-MindForge v5 ships with default policies including:
+## 6. Enterprise Policies
+MindForge v5.1.0 ships with default policies including:
 - **`gate_tier_3_engine`**: Blocks all modifications to `bin/autonomous/` unless signed by a Tier 3 DID.
 - **`protect_security_namespace`**: Limits access to `/security` and `/governance` to Tier 2+ specialists.
 - **`mesh_integrity_lock`**: Ensures only high-confidence agents can push to the **Federated Intelligence Mesh**.
 
 ---
-*Status: V5 "Beast" Mode Governance Implemented & Verified (2026-03-28)*
+*Status: V5.1.0 "Beast Addition" Governance Implemented & Verified (2026-03-28)*

package/docs/troubleshooting.md

@@ -1,4 +1,4 @@
-# MindForge Troubleshooting (v1.0.0)
+# MindForge Troubleshooting (v5.1.0)
 
 This page lists common issues and fast fixes. If you get stuck, start with
 `/mindforge:health`.
@@ -54,14 +54,14 @@ npx mindforge-cc@latest --claude --local --force
 ```
 Then run:
 ```
-/mindforge:migrate --from v0.6.0 --to v1.0.0
+/mindforge:migrate --from v5.0.0 --to v5.1.0
 ```
 
 ### Schema mismatch warning on startup
 **Fix:**
 ```
 /mindforge:migrate --dry-run
-/mindforge:migrate --from vX.Y.Z --to v1.0.0
+/mindforge:migrate --from vX.Y.Z --to v5.1.0
 ```
 
 ### AUDIT.jsonl parse errors
@@ -113,7 +113,27 @@ rerun migration. See `.mindforge/audit/AUDIT-SCHEMA.md` for expected format.
 
 ---
 
-## 8. Getting help
+## 8. Neural Protocol Mesh Issues (v5.1.0)
+
+### Protocol Step 0 fails to activate
+**Symptom:** Commands proceed without activating `_extended` skills.
+**Fix:** Run `/mindforge:neural-orchestrator --reset`. Ensure all `_extended` skills are present in `.agent/skills/`.
+
+### Context drift in Parallel Mesh
+**Symptom:** Parallel agents making conflicting decisions.
+**Fix:** Run `/mindforge:parallel-mesh --sync`. This forces a global state re-synchronization across all active worker identities.
+
+### Workspace isolation failure
+**Symptom:** Conflicts between feature branches or dirty worktree.
+**Fix:** Run `/mindforge:workspace-isolated --cleanup`. Use `/mindforge:health --repair` if `.git/worktrees/` is corrupt.
+
+---
+
+## 9. Getting help
 If the above doesn’t resolve it:
 - Review `docs/user-guide.md`
 - Check `docs/security/SECURITY.md` for security issues
+- Open a GitHub issue or join the Discord: `/mindforge:join-discord`
+- **Architecture**: `docs/architecture/V5-ENTERPRISE.md`
+- **Commands**: `docs/commands-reference.md`
+- **Personas**: `docs/PERSONAS.md`