production architecture · v2 · 2026

The orchestrator that runs Forged AI itself

Three nodes. Six agents. Two AI vendors. One private mesh. All wired with shell, session multiplexing, and SSH. No magic — just primitives, composed well.

Topology

The fleet

Every node has a role. Every agent has a lane. The dispatcher is just shell.

private mesh networkedgecoordinator3 agents · Anthropiccomputeheavy lifter2 agents · Anthropicresearchrecon1 agent · xAI
coordinator
always-on · dispatches to the rest · shared memory host
heavy lifter
project-resident · deploys · long compute
recon
vendor-diverse · live web signals · context the others miss
The roster

Six agents. Three nodes. Two vendors.

Every agent has a lane and a host. The dispatcher routes by role, not by name.

role
node
vendor
lane
Coordinator
Edge Node
Anthropic
Primary chat thread, dispatcher, observability host
Research Agent
Edge Node
Anthropic
Long-running research, audits, recon
Build Agent
Edge Node
Anthropic
Infra scripts, scaffolds, deployments
Domain Agent A
Compute Node
Anthropic
Project-resident · codebase deep dive · deploy
Domain Agent B
Compute Node
Anthropic
Project-resident · adjacent vertical
Recon Agent
Research Node
xAI
Live web + social signal · vendor-diverse perspective
What this looks like in practice

A real cross-vendor dispatch chain

Below is an actual chain from production — coordinator dispatched a domain question to a domain agent, who formulated a research prompt for the recon agent on a different vendor. Lightly edited, not invented.

coordinator (edge node · Anthropic)
# 00:42:18 — to domain agent
$dispatch domain-agent --body-file q.txt
dispatched · awaiting reply…
# 00:48:31 — chain to recon agent
$dispatch recon-agent --body-file r.txt
dispatched · live web recon…
[...3min later...]
# 00:51:42 — synthesis back to domain agent
$dispatch domain-agent --body-file s.txt
● ready · 1m 51s · findings appended
✓ chain complete · 12min wall
domain agent (compute node · Anthropic)
# received from coordinator
formulate research question for recon agent…
START-PROMPT
<focused ask · context · constraints · output spec>
END-PROMPT
recon agent (research node · xAI)
researching ecosystem moves last 14d…
⠦ Web Search: new tooling 2026
⠦ Web Search: framework releases
⠦ Web Search: industry announcements
✓ 7 candidates · cited · graded
How it stays alive

Six principles that hold under load

Every principle is the result of something breaking once and us deciding it never happens again.

Persistent sessions

Every agent runs inside a long-lived session. Reboots, network blips, disconnect events — the conversation survives. No webhook resurrection rituals, no lost state.

File-based memory

Shared memory lives as plain markdown files on disk, indexed by an append-only memory log. Agents read what they need; writes are surgical. Greppable, diffable, durable.

Cross-vendor dispatch

Claude on one node can dispatch to Grok on another, and the same primitives work the other direction. No single-vendor failure mode. Vendor outages stop being existential.

Private mesh routing

Every node is on a private mesh network. SSH-by-IP across the fleet, zero tunnels to misconfigure. The dispatcher is just shell + SSH + session multiplexing.

Lane separation

Agents have explicit lanes: research, build, deploy, recon. Each lane has tools it can touch — and tools it can't. Production-safe by construction.

Observable by default

Every dispatch is timestamped + logged to a central stream. The whole fleet's activity is watchable live. No silent agents, no blind spots.

Boring tech, sharp edges

The whole orchestrator is a few hundred lines of shell

No bespoke runtime. No proprietary message bus. Session multiplexing for persistence, SSH for transport, private mesh for routing, plain markdown for memory.

Transport
SSH + sessions
Routing
Private mesh
Memory
Markdown + git
Observability
Structured logs
Vendors
Anthropic + xAI
Schedulers
Cron + manual
Dashboard
FastAPI + HTMX
Dispatch
Python wrapper

Run this in your business.

We'll stand up the same orchestrator inside your infrastructure, wired to your tools, in 48 hours. Then we hand you the keys.