Brandon Schneider 51664eb060 docs(infra): plan — mesh networking layers over Ray ... Architectural plan for Tailscale mesh + Ray + VCN + compute surfaces. 5-layer stack: 1. Tailscale connects everything (WireGuard, DERP relay) 2. Ray schedules work across the mesh 3. VCN compresses data (50x bandwidth reduction) 4. FrameDispatcher routes by tag 5. Compute surfaces execute (GPU/CPU/Ethernet/framebuffer/MCU) Key insight: every device in the Tailscale mesh is a potential compute node. Framebuffer and Ethernet surfaces turn devices that "cant run Ray" into compute participants. 4 phases: 1. Ray over Tailscale (mostly done) 2. Multi-tier scheduling (probe done, placement pending) 3. Framebuffer + Ethernet integration (host-side pending) 4. Edge devices (ESP32, 1-Wire sensors)		2026-05-30 20:03:57 -05:00
..
arr-stack-plan.md	infra(vps): deploy Authentik, credential vault, age-sops, PQC, ARR plan	2026-05-20 18:00:11 -05:00
authentik-setup.md	WIP: accumulated changes	2026-05-25 16:24:21 -05:00
ene-contextstream-equivalent.md	WIP: accumulated changes	2026-05-25 16:24:21 -05:00
infrastructure-status.md	docs(kube): update infra docs, RayCluster manifest with nightly GPU images	2026-05-30 16:23:13 -05:00
k3s-cluster-setup.md	docs(kube): update infra docs, RayCluster manifest with nightly GPU images	2026-05-30 16:23:13 -05:00
mesh-networking-over-ray-plan.md	docs(infra): plan — mesh networking layers over Ray	2026-05-30 20:03:57 -05:00
pqc-posture.md	infra(vps): deploy Authentik, credential vault, age-sops, PQC, ARR plan	2026-05-20 18:00:11 -05:00
usbip-mesh-transport-design.md	WIP: accumulated changes	2026-05-25 16:24:21 -05:00
vcn-lupine-setup.md	chore: commit accumulated working tree changes	2026-05-30 00:10:02 -05:00
vps-proxmox-status.md	WIP: accumulated changes	2026-05-25 16:24:21 -05:00