Compare commits
7 Commits
docs/archi
...
sonnet/iss
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
8a66ea8d3b | ||
| 5805d74efa | |||
| d9bc5c725d | |||
|
|
5f1f1f573d | ||
| df779609c4 | |||
| ef68d5558f | |||
| 2bae6ef4cf |
@@ -34,6 +34,12 @@ We implement an automated audit protocol to verify that no external API calls ar
|
||||
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.
|
||||
|
||||
|
||||
27
SOVEREIGN_MESH.md
Normal file
27
SOVEREIGN_MESH.md
Normal 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.*
|
||||
@@ -174,6 +174,12 @@ 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
|
||||
|
||||
21
docs/sonnet-workforce.md
Normal file
21
docs/sonnet-workforce.md
Normal file
@@ -0,0 +1,21 @@
|
||||
# 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
|
||||
Reference in New Issue
Block a user