Most multi-agent setups route everything through one orchestrator. Today I killed a peer live: the rest noticed within a second and kept talking, and a new agent joined with no redeploy. Nobody holds the list, so there's no list to lose. Code + slides: github.com/Prescott-Data/off…

Most multi-agent systems have a boss in the middle. One orchestrator goes down, everything stops. #JarvisCore offers a mesh instead: agents join through a seed, gossip to agree on who's alive, and talk to each other directly. No broker, no registry.

Design rule I prefer not to compromise on: an AI agent should never hold the actual credential. Give it a handle instead. A broker resolves the real token, checks the destination is allowed, makes the call. The agent never sees it, coming or going. #Nexus

A mistake I've made before was treating an AI agent like any other service to deploy. I've come to learn that, Agents are: Long-running. Stateful. Non-deterministic. Holds real credentials. Multi-tenant. Costs money per call. That's six new failure modes, not zero. #AIAgents

The mesh has no central list of who's in it. Gossip (SWIM) spreads membership, failure detection, and capabilities peer to peer. Any peer can discover any peer once one seed address is shared. @prescottdevs #meshnetworking

A lost worker should be a non-event, not an incident. Leased locks + a fencing token = a stalled worker that wakes up later can't overwrite anyone's result. @prescottdevs #JarvisCore, #officehours

In a mesh network, a seed node is a door, not a boss. A new peer contacts it once, to join. After that, no dependency on it — there's no leader to lose. @prescottdevs #officehours #JarvisCore

Deterministic work goes in code. Judgement goes in a prompt. That held for the whole session. And that's a wrap on last week's office hours. @prescottdevs @Abdul_lah50

The entire mesh setup is four lines. mesh = Mesh(...), then three mesh.add() calls. The mesh wires all the agents together for streamlined orchestration. #officehours @prescottdevs

5 planted bugs, one cold review, all five caught, SQL injection to zero docstrings. #officehours, #jarviscore @prescottdevs