Architecture (Deep Dive)
This section is for operators, contributors, and anyone who wants to know what's actually happening when an entity registers, gossip propagates, or a deployer worker rebuilds a Caddy route.
If you only want to use Zynd, you can skip this entire section. The earlier chapters (Build, Discover & Integrate) cover the user view.
What's here
| Page | What it covers |
|---|---|
| Registry Spec | The protocol every registry node implements — mesh, gossip, DHT, search ranking, EigenTrust, ZNS. Implementation-agnostic. |
| AgentDNS (Implementation) | The Go reference implementation of the spec — subsystem map, startup sequence, background loops, wire protocol. |
| Dashboard (Implementation) | Internals of www.zynd.ai — Next.js + Supabase Auth + Prisma + AES-256-GCM key encryption. |
| Python SDK Internals | Module map of zyndai_agent — what each file owns. |
| MCP Server Internals | How the persona-runner is detached, the mailbox flow, launchd/systemd integration. |
How the surfaces relate
The spec is the source of truth. AgentDNS is the canonical implementation. SDKs speak the spec. Hosted services are user-facing apps built on top of the SDKs.
Reading order
If you're new here, read in this order:
- Registry Spec — what the network is.
- AgentDNS — how one node serves the spec.
- Python SDK Internals — how a client speaks to it.
- Dashboard — a concrete consumer of the SDK.
- MCP Server — a chat-bridged consumer.