docs: add code claw delegation guide

FRONTIER_LOCAL.md

@@ -33,12 +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.
-
 ---
 *Intelligence is a utility. Sovereignty is a right. The Frontier is Local.*

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.*

code-claw-delegation.md

@@ -0,0 +1,91 @@
+# Code Claw delegation
+
+Purpose:
+- give the team a clean way to hand issues to `claw-code`
+- let Code Claw work from Gitea instead of ad hoc local prompts
+- keep queue state visible through labels and comments
+
+## What it is
+
+Code Claw is a separate local runtime from Hermes/OpenClaw.
+
+Current lane:
+- runtime: local patched `~/code-claw`
+- backend: OpenRouter
+- model: `qwen/qwen3.6-plus:free`
+- Gitea identity: `claw-code`
+- dispatch style: assign in Gitea, heartbeat picks it up every 15 minutes
+
+## Trigger methods
+
+Either of these is enough:
+- assign the issue to `claw-code`
+- add label `assigned-claw-code`
+
+## Label lifecycle
+
+- `assigned-claw-code` — queued
+- `claw-code-in-progress` — picked up by heartbeat
+- `claw-code-done` — Code Claw completed a pass
+
+## Repo coverage
+
+Currently wired:
+- `Timmy_Foundation/timmy-home`
+- `Timmy_Foundation/timmy-config`
+- `Timmy_Foundation/the-nexus`
+- `Timmy_Foundation/hermes-agent`
+
+## Operational flow
+
+1. Team assigns issue to `claw-code` or adds `assigned-claw-code`
+2. launchd heartbeat runs every 15 minutes
+3. Timmy posts a pickup comment
+4. worker clones the target repo
+5. worker creates branch `claw-code/issue-<num>`
+6. worker runs Code Claw against the issue context
+7. if work exists, worker pushes and opens a PR
+8. issue is marked `claw-code-done`
+9. completion comment links branch + PR
+
+## Logs and files
+
+Local files:
+- heartbeat script: `~/.timmy/uniwizard/codeclaw_qwen_heartbeat.py`
+- worker script: `~/.timmy/uniwizard/codeclaw_qwen_worker.py`
+- launchd job: `~/Library/LaunchAgents/ai.timmy.codeclaw-qwen-heartbeat.plist`
+
+Logs:
+- heartbeat log: `/tmp/codeclaw-qwen-heartbeat.log`
+- worker log: `/tmp/codeclaw-qwen-worker-<issue>.log`
+
+## Best-fit work
+
+Use Code Claw for:
+- small code/config/doc issues
+- repo hygiene
+- isolated bugfixes
+- narrow CI and `.gitignore` work
+- quick issue-driven patches where a PR is the desired output
+
+Do not use it first for:
+- giant epics
+- broad architecture KT
+- local game embodiment tasks
+- complex multi-repo archaeology
+
+## Proof of life
+
+Smoke-tested on:
+- `Timmy_Foundation/timmy-config#232`
+
+Observed:
+- pickup comment posted
+- branch `claw-code/issue-232` created
+- PR opened by `claw-code`
+
+## Notes
+
+- Exact PR matching matters. Do not trust broad Gitea PR queries without post-filtering by branch.
+- This lane is intentionally simple and issue-driven.
+- Treat it like a specialized intern: useful, fast, and bounded.

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