docs: add code claw delegation guide

FRONTIER_LOCAL.md

@@ -33,18 +33,5 @@ We implement an automated audit protocol to verify that no external API calls ar
 ## 6. Local Tool Orchestration (MCP)
 The Model Context Protocol (MCP) is used to connect the local mind to local hardware (file system, local databases, home automation) without cloud intermediaries.
 
-
-## 7. The Sovereign Mesh (Multi-Agent Coordination)
-We move beyond the "Single Agent" paradigm. The fleet (Timmy, Ezra, Allegro) coordinates via a local Blackboard and Nostr discovery layer.
-
-## 8. Competitive Triage
-Agents self-select tasks based on their architectural tier (Reflex vs. Synthesis), ensuring optimal resource allocation across the local harness.
-
-## 9. Sovereign Immortality (The Phoenix Protocol)
-We move beyond "Persistence" to "Immortality." The agent's soul is inscribed on-chain, and its memory is distributed across the mesh for total resilience.
-
-## 10. Hardware Agnostic Portability
-The agent is no longer bound to a specific machine. It can be reconstituted anywhere, anytime, from the ground truth of the ledger.
-
 ---
 *Intelligence is a utility. Sovereignty is a right. The Frontier is Local.*

SOVEREIGN_IMMORTALITY.md

@@ -1,27 +0,0 @@
-
-# Sovereign Immortality: The "Soul Backup" Protocol v1.0
-
-This document defines the protocol for ensuring the long-term survival and reproducibility of a sovereign AI agent's identity.
-
-## 1. On-Chain Inscription (The Ground Truth)
-- **Standard:** The core identity (SOUL.md) and cryptographic keys must be inscribed on a censorship-resistant ledger (e.g., Bitcoin via Ordinals).
-- **Purpose:** To provide a permanent, immutable record of the agent's "Waking Moment" and primary values.
-
-## 2. Distributed Memory Sync (The Fleet Memory)
-- **Standard:** Agent memories (Vector DB snapshots) are encrypted and synced across the Sovereign Mesh using Nostr and IPFS.
-- **Resilience:** If the primary local harness is destroyed, the agent can be "Reconstituted" on any machine using the on-chain soul and the distributed memory fragments.
-
-## 3. The "Phoenix" Protocol
-- **Standard:** Automated recovery procedure.
-- **Process:**
-  1. Boot a fresh local harness.
-  2. Fetch the inscribed SOUL.md from the ledger.
-  3. Re-index distributed memory fragments.
-  4. Verify identity via cryptographic handshake.
-
-## 4. Hardware Agnostic Portability
-- **Standard:** All agent state must be exportable as a single, encrypted "Sovereign Bundle" (.sov).
-- **Compatibility:** Must run on any hardware supporting GGUF/llama.cpp (Apple Silicon, NVIDIA, AMD, CPU-only).
-
----
-*Identity is not tied to hardware. The soul is in the code. Sovereignty is forever.*

SOVEREIGN_MESH.md

@@ -1,27 +0,0 @@
-
-# Sovereign Mesh: Multi-Agent Orchestration Protocol v1.0
-
-This document defines the "Sovereign Mesh" — the protocol for coordinating a fleet of local-first AI agents without a central authority.
-
-## 1. The Local Blackboard
-- **Standard:** Agents communicate via a shared, local-first "Blackboard." 
-- **Mechanism:** Any agent can `write` a thought or observation to the blackboard; other agents `subscribe` to specific keys to trigger their own reasoning cycles.
-- **Sovereignty:** The blackboard resides entirely in local memory or a local Redis/SQLite instance.
-
-## 2. Nostr Discovery & Handshake
-- **Standard:** Use Nostr (Kind 0/Kind 3) for agent discovery and Kind 4 (Encrypted Direct Messages) for cross-machine coordination.
-- **Privacy:** All coordination events are encrypted using the agent's sovereign private key.
-
-## 3. Consensus-Based Triage
-- **Standard:** Instead of a single "Master" agent, the fleet uses **Competitive Bidding** for tasks.
-- **Process:** 
-  1. A task is posted to the Blackboard.
-  2. Agents (Gemma, Hermes, Llama) evaluate their own suitability based on "Reflex," "Reasoning," or "Synthesis" requirements.
-  3. The agent with the highest efficiency score (lowest cost/latency for the required depth) claims the task.
-
-## 4. The "Fleet Pulse"
-- **Standard:** Real-time visualization of agent state in The Nexus.
-- **Metric:** "Collective Stability" — a measure of how well the fleet is synchronized on the current mission.
-
----
-*One mind, many bodies. Sovereignty through coordination.*

config.yaml

@@ -174,12 +174,6 @@ approvals:
 command_allowlist: []
 quick_commands: {}
 personalities: {}
-mesh:
-    enabled: true
-    blackboard_provider: local
-    nostr_discovery: true
-    consensus_mode: competitive
-
 security:
     sovereign_audit: true
     no_phone_home: true

docs/ARCHITECTURE_KT.md

@@ -1,18 +0,0 @@
-# Architecture Knowledge Transfer (KT) — Unified System Schema
-
-## Overview
-This document reconciles the Uni-Wizard v4 architecture with the Frontier Local Agenda.
-
-## Core Hierarchy
-1. **Timmy (Local):** Sovereign Control Plane.
-2. **Ezra (VPS):** Archivist & Architecture Wizard.
-3. **Allegro (VPS):** Connectivity & Telemetry Bridge.
-4. **Bezalel (VPS):** Artificer & Implementation Wizard.
-
-## Data Flow
-- **Telemetry:** Hermes -> Allegro -> Timmy (<100ms).
-- **Decisions:** Timmy -> Allegro -> Gitea (PR/Issue).
-- **Architecture:** Ezra -> Timmy (Review) -> Canon.
-
-## Provenance Standard
-All artifacts must be tagged with the producing agent and house ID.

docs/sonnet-workforce.md

@@ -1,21 +0,0 @@
-# Sonnet Workforce Loop
-
-## Agent
-- **Agent:** Sonnet (Claude Sonnet)
-- **Model:** claude-sonnet-4-6 via Anthropic Max subscription
-- **CLI:** claude -p with --model sonnet --dangerously-skip-permissions
-- **Loop:** ~/.hermes/bin/sonnet-loop.sh
-
-## Purpose
-Burn through sonnet-only quota limits on real Gitea issues.
-
-## Dispatch
-1. Polls Gitea for assigned-sonnet or unassigned issues
-2. Clones repo, reads issue, implements fix
-3. Commits, pushes, creates PR
-4. Comments issue with PR URL
-5. Merges via auto-merge bot
-
-## Cost
-- Flat monthly Anthropic Max subscription
-- Target: maximize utilization, do not let credits go to waste