Compare commits

...

3 Commits

3 changed files with 40 additions and 0 deletions

View File

@@ -33,5 +33,12 @@ We implement an automated audit protocol to verify that no external API calls ar
## 6. Local Tool Orchestration (MCP) ## 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. 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.* *Intelligence is a utility. Sovereignty is a right. The Frontier is Local.*

27
SOVEREIGN_MESH.md Normal file
View File

@@ -0,0 +1,27 @@
# 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.*

View File

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