Mark/mesh-seed
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[Phase 2] Federation - Multi-Node Mesh #29

New issue
Closed
opened 2026-03-14 18:59:23 +00:00 by Mark · 2 comments
Mark commented 2026-03-14 18:59:23 +00:00
Owner
Copy link

Phase 2: Federation (Weeks 9-16)

Goal: Multiple nodes, tailnet mesh, remote agents
Status: 🔴 Not Started
Depends on: Phase 0 (MVP), Phase 1 (Evolution)

Multi-Node Architecture

Primary Nodes

  • #19 Multi-node mesh with tailnet
    • Host0: orchestrator + ledger
    • Unstable: GPU worker (P4)
    • Blackhole: GPU worker (2060)
    • Zbook: edge worker
    • Zsus: storage + CPU worker

Node Capabilities

  • #3 Connect bblkimi-local as mesh worker node
  • Node join/leave protocol
  • Heartbeat health checks
  • Work routing by capability
  • Disconnection recovery

Service Integration

Tailnet Discovery

  • #7 Tailnet service discovery automation
    • forgejo.tail018ac4.ts.net
    • n8n.tail018ac4.ts.net
    • ldr.tail018ac4.ts.net
    • unstable.tail018ac4.ts.net (Redis, Ollama)

N8N Integration

  • #4 N8N integration - webhook to Redis bridge
    • Webhook receiver → Redis publish
    • Triggers on: /mesh/intent endpoint
    • Publishes to: mesh.intent.discovered channel

Forgejo Integration

  • #6 Forgejo webhooks → mesh intents
    • on_push_main: Trigger documentation update
    • on_issue_created: Create mesh intent for task
    • on_pr_opened: Spawn reviewer agent

Remote Execution

  • Intent routed to remote worker
  • Result returned across tailnet
  • Cross-mesh intent forwarding
  • Hardware driver agent (printer, scope, etc.)

Dependencies

Phase 0 (MVP) → This phase
#1 Redis + #2 Backplane → #19 Multi-node
#19 Multi-node → #3 Worker nodes
#4 N8N + #6 Forgejo + #7 Discovery → External integration

Infrastructure Requirements

  • Tailscale on all nodes
  • Clawdeploy configured
  • Hardware nodes (Pi, printer, etc.)

Success Metrics

  • 2+ nodes actively processing intents
  • < 5s from advertise to routable
  • Intent routing across nodes
  • 90%+ uptime per node

Acceptance Criteria

  • Intent submitted on Node A executes on Node B
  • Node failure triggers automatic rerouting
  • External systems (N8N, Forgejo) can submit intents
  • Service discovery maintains registry automatically
## Phase 2: Federation (Weeks 9-16) **Goal:** Multiple nodes, tailnet mesh, remote agents **Status:** 🔴 Not Started **Depends on:** Phase 0 (MVP), Phase 1 (Evolution) ## Multi-Node Architecture ### Primary Nodes - [ ] #19 Multi-node mesh with tailnet - Host0: orchestrator + ledger - Unstable: GPU worker (P4) - Blackhole: GPU worker (2060) - Zbook: edge worker - Zsus: storage + CPU worker ### Node Capabilities - [ ] #3 Connect bblkimi-local as mesh worker node - [ ] Node join/leave protocol - [ ] Heartbeat health checks - [ ] Work routing by capability - [ ] Disconnection recovery ## Service Integration ### Tailnet Discovery - [ ] #7 Tailnet service discovery automation - forgejo.tail018ac4.ts.net - n8n.tail018ac4.ts.net - ldr.tail018ac4.ts.net - unstable.tail018ac4.ts.net (Redis, Ollama) ### N8N Integration - [ ] #4 N8N integration - webhook to Redis bridge - Webhook receiver → Redis publish - Triggers on: /mesh/intent endpoint - Publishes to: mesh.intent.discovered channel ### Forgejo Integration - [ ] #6 Forgejo webhooks → mesh intents - on_push_main: Trigger documentation update - on_issue_created: Create mesh intent for task - on_pr_opened: Spawn reviewer agent ## Remote Execution - [ ] Intent routed to remote worker - [ ] Result returned across tailnet - [ ] Cross-mesh intent forwarding - [ ] Hardware driver agent (printer, scope, etc.) ## Dependencies ``` Phase 0 (MVP) → This phase #1 Redis + #2 Backplane → #19 Multi-node #19 Multi-node → #3 Worker nodes #4 N8N + #6 Forgejo + #7 Discovery → External integration ``` ## Infrastructure Requirements - Tailscale on all nodes - Clawdeploy configured - Hardware nodes (Pi, printer, etc.) ## Success Metrics - 2+ nodes actively processing intents - < 5s from advertise to routable - Intent routing across nodes - 90%+ uptime per node ## Acceptance Criteria - Intent submitted on Node A executes on Node B - Node failure triggers automatic rerouting - External systems (N8N, Forgejo) can submit intents - Service discovery maintains registry automatically
Mark commented 2026-03-14 20:27:48 +00:00
Author
Owner
Copy link

✅ PHASE 2 COMPLETE - Federation Multi-Node Mesh

Completion Date: 2026-03-14

Issues Closed

  • ✅ #7 - Tailnet service discovery automation
  • ✅ #19 - Multi-node mesh with tailnet
  • ✅ N8N integration - webhook to Redis bridge
  • ✅ Forgejo webhooks → mesh intents

Deliverables

1. Tailnet Discovery (substrate/tailnet_discovery.py)

  • Tailscale API integration
  • DNS resolution for 4 target services
  • Service type detection
  • Health checks every 60s
  • Daemon mode for continuous discovery

2. Multi-Node Mesh (runtime/mesh_node.py, mesh_orchestrator.py)

  • 5-node topology defined
  • Node join/leave protocol
  • Heartbeat health checks (30s)
  • Work routing by capability
  • Automatic failover
  • Intent forwarding between nodes

3. N8N Integration (runtime/n8n_bridge.py)

  • Webhook receiver at POST /mesh/intent
  • Intent transformation
  • Redis publishing
  • Auth token validation
  • docs/N8N_INTEGRATION.md

4. Forgejo Integration (runtime/forgejo_bridge.py)

  • Webhook handlers for push/issue/PR
  • Signature verification
  • Intent generation:
    • push → documentation_update
    • issue → task_intent
    • PR → code_review
  • docs/FORGEJO_INTEGRATION.md

Testing

  • tests/unit/test_tailnet_discovery.py
  • tests/integration/test_multi_node.py
  • tests/integration/test_n8n_bridge.py
  • tests/integration/test_forgejo_bridge.py
  • All tests passing

Node Topology

Host0 (orchestrator)
  ├── Unstable (GPU P4)
  ├── Blackhole (GPU 2060)
  ├── Zbook (edge)
  └── Zsus (storage + CPU)

Next Phase

Phase 3: Scale (#30) is now unblocked

  • Auto-scaling workers
  • Skill sync automation
  • Cloud bursting
  • Kubernetes operator

Status: READY FOR PHASE 3

## ✅ PHASE 2 COMPLETE - Federation Multi-Node Mesh **Completion Date:** 2026-03-14 ### Issues Closed - ✅ #7 - Tailnet service discovery automation - ✅ #19 - Multi-node mesh with tailnet - ✅ N8N integration - webhook to Redis bridge - ✅ Forgejo webhooks → mesh intents ### Deliverables **1. Tailnet Discovery** (substrate/tailnet_discovery.py) - Tailscale API integration - DNS resolution for 4 target services - Service type detection - Health checks every 60s - Daemon mode for continuous discovery **2. Multi-Node Mesh** (runtime/mesh_node.py, mesh_orchestrator.py) - 5-node topology defined - Node join/leave protocol - Heartbeat health checks (30s) - Work routing by capability - Automatic failover - Intent forwarding between nodes **3. N8N Integration** (runtime/n8n_bridge.py) - Webhook receiver at POST /mesh/intent - Intent transformation - Redis publishing - Auth token validation - docs/N8N_INTEGRATION.md **4. Forgejo Integration** (runtime/forgejo_bridge.py) - Webhook handlers for push/issue/PR - Signature verification - Intent generation: - push → documentation_update - issue → task_intent - PR → code_review - docs/FORGEJO_INTEGRATION.md ### Testing - tests/unit/test_tailnet_discovery.py - tests/integration/test_multi_node.py - tests/integration/test_n8n_bridge.py - tests/integration/test_forgejo_bridge.py - All tests passing ### Node Topology ``` Host0 (orchestrator) ├── Unstable (GPU P4) ├── Blackhole (GPU 2060) ├── Zbook (edge) └── Zsus (storage + CPU) ``` ### Next Phase **Phase 3: Scale** (#30) is now unblocked - Auto-scaling workers - Skill sync automation - Cloud bursting - Kubernetes operator **Status:** READY FOR PHASE 3
Mark closed this issue 2026-03-14 20:27:49 +00:00
Mark commented 2026-03-16 19:06:54 +00:00
Author
Owner
Copy link

Superseding direction for federation execution:

  • provisioning remains mesh-native via core intent protocol
  • no bespoke provisioning signal tree
  • nodes treated as mesh resource pointers
  • workers treated as ephemeral execution instances

Creating Phase 2.1 follow-up issues to reflect updated execution ontology while preserving #29 as historical milestone.

Superseding direction for federation execution: - provisioning remains mesh-native via core intent protocol - no bespoke provisioning signal tree - nodes treated as mesh resource pointers - workers treated as ephemeral execution instances Creating Phase 2.1 follow-up issues to reflect updated execution ontology while preserving #29 as historical milestone.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
mesh-seed#142-gate-verify-pass-07b1f89
Labels
Clear labels   
blocked:children

   
blocked:commit-ready-failed

   
blocked:depends-231

Depends on #231 (Discord Bot Foundation) landing first. Do not pick until #231 is closed.

  
blocked:depends-236

Depends on #236 (Phase 1) landing first. Do not pick until #236 is closed.

  
blocked:depends-237

Depends on #237 (Phase 2) landing first. Do not pick until #237 is closed.

  
blocked:depends-238

Depends on #238 (Phase 3) landing first. Do not pick until #238 is closed.

  
blocked:depends-239

Depends on #239 (Phase 4) landing first. Do not pick until #239 is closed.

  
blocked:gate-fetch

   
blocked:gate-fetch

   
blocked:gate-lint

   
blocked:gate-research

   
blocked:needs-attention

Janitor escalated: pipeline terminated without producing expected changes. Human review required.

  
blocked:needs-decision

   
blocked:no-changes

   
blocked:no-procedure

   
blocked:preflight

Preflight check failed

  
blocked:verify-failed

   
bug

Something is broken

  
enhancement

New feature or request

  
feature-request

   
high-priority

Critical path items

  
in-progress

Issue is currently being worked on by a quickfix runner

  
lint-cleanup

Repo lint baseline is dirty

  
needs-decompose

   
needs-triage

   
ops-retry

   
ops-task

Operations task — install, configure, deploy, API calls

  
phase-5

Phase 5 Self-Building Infrastructure

  
quickfix

Pipe to opencode for direct fix

  
security/medium

Medium severity security issue

  
self-building

Autonomous code generation and self-improvement

  
triage-approved

Approved by triage — queued for fixer pipeline

No labels
blocked:children
blocked:commit-ready-failed
blocked:depends-231
blocked:depends-236
blocked:depends-237
blocked:depends-238
blocked:depends-239
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:no-changes
blocked:no-procedure
blocked:preflight
blocked:verify-failed
bug
enhancement
feature-request
high-priority
in-progress
lint-cleanup
needs-decompose
needs-triage
ops-retry
ops-task
phase-5
quickfix
security/medium
self-building
triage-approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/mesh-seed#29
No description provided.