Architecture

These pages describe how synkd is put together. Read them when you need to place a change, debug a boundary, or explain the system to someone new.

Each diagram is an SVG that uses design tokens. They stay readable in greyscale and on the dark docs theme.

Dimensions

Dimension	What it answers
System context	Who talks to what at the edge
Package layers	How packages stack
Request path	What happens to one join
Trust boundaries	Where trust starts and stops
Control plane	Guest traffic versus operator `/v1`
Fleet topology	Caddy, Durable Object nodes, object store

A heavy stroke marks the important box in a step.
A dashed stroke marks something outside the main process boundary, or a shared durability path.
Labels under boxes use monospace for package or protocol names.