core/agent

Snider be78c27561 docs: add full RFC specs for agent dispatch

AX principles + go/agent + core/agent + php/agent specs.
Temporary — needed in-repo until core-agent mount bug is fixed.

Co-Authored-By: Virgil <virgil@lethean.io>

2026-03-30 19:51:55 +01:00

2.2 KiB

Raw Permalink Blame History

Agent Fleet Topology

How Cladius, Charon, and community agents are deployed, connected, and onboarded.

Current Fleet

Agent	Hardware	Location	Role
Cladius	M3 Studio (36GB)	Local (Snider's desk)	Project leader, architecture, specs, dispatch
Charon	Ryzen 9 + 128GB + RX 7800 XT	Homelab (10.69.69.165)	Infrastructure, training, blockchain, DevOps
Codex agents	OpenAI cloud	Remote (sandboxed)	Implementation, polish, QA
Gemini agents	Google cloud	Remote	Research, analysis, alternative perspectives

Connectivity

Cladius (M3 Studio)
  └── core-agent MCP (stdio) → Claude Code
  └── agent_send → Charon (api.lthn.sh)

Charon (Homelab)
  └── core-agent MCP (stdio) → Claude Code
  └── agent_send → Cladius (api.lthn.sh)
  └── Ollama (local inference)
  └── Qdrant (OpenBrain vectors)

Both → OpenBrain (shared knowledge)
Both → Forge (git repos)
Both → api.lthn.sh / mcp.lthn.sh (MCP over HTTP)

DNS Routing Strategy

Subdomains, not paths:

api.lthn.sh — REST API
mcp.lthn.sh — MCP endpoint
forge.lthn.ai — Forgejo (de1 production)

Why subdomains: each service can have its own TLS cert, its own Traefik rule, its own rate limiting. Paths create coupling.

Community Onboarding (*.lthn.sh)

The *.lthn.sh wildcard resolves to 10.69.69.165 (homelab) for Snider, but for community members it resolves to 127.0.0.1 (localhost).

This means:

Community member installs core-agent
core-agent starts local MCP server
api.lthn.sh resolves to their own localhost
They're running their own node — no dependency on Snider's hardware
When they're ready, they peer with the network via WireGuard

BugSETI bootstrap tool automates this: bare metal → running node in 10 steps.

Fleet Dispatch (lthn.sh)

lthn.sh is the fleet controller:

Orchestrator creates task
Task assigned to agent pool (codex, gemini, claude, local)
Agent picks up via SSE/polling from api.lthn.sh
Runs in sandboxed workspace
Reports completion via checkin API
Orchestrator reviews, merges, or sends back

Community members contribute compute by running core-agent connected to the fleet.

2.2 KiB Raw Permalink Blame History