Repository navigation
Stand up the closed Buzz relay stack on the estate VPS behind the wrapped update lane #8
Description
Cluster issue for Phase 2 / E2+E2b of the master blueprint (000-docs/001):
the closed relay stack on the estate VPS — DNS + sops secrets + digest-pinned
compose stack booted closed from first start; Caddy ingress with compensating
edge controls; smokes + functional membership probe + off-network unauth
matrix; backups + the wrapped updater + estate registration. Owner waived the
MX-cutover hold 2026-07-29. E3 drill gates stay BLOCKING before any invite.
Beads: buzz-ocv (epic) + children buzz-ocv.1–buzz-ocv.4
Plane: BUZZ (linked via bd-sync)
Operator-private detail (hosts, env, keys) lives in the private ops repo.
- Jeremy Longshore
intentsolutions.io
Activity
jeremylongshore commentedon Jul 29, 2026
Linked bead:
buzz-ocv(source of truth). Usebd-syncto mirror updates.jeremylongshore commentedon Jul 29, 2026
bd-sync from
buzz-ocv: TOPOLOGY RE-SCOPE (owner decision 2026-07-29, recorded as fork 000-docs/005): this shared-VPS stack is re-designated permanent STAGING — same compose, same gates; restore drills and updater planted-fault drills run here, never on prod. Production moves to a dedicated VPS (epic buzz-nry / GH #9 / Plane BUZZ-3). At cutover this env renames to buzz-staging.intentsolutions.io; staging keys never promote to prod. New Track-E children under this epic: .5 Tauri/CORS desktop-join fix, .6 mobile pairing sidecar overlay; updater promotion-checklist additions noted on .4.docs(topology): dedicated production VPS; shared-host stack becomes s…
jeremylongshore commentedon Jul 30, 2026
bd-sync from
buzz-ocv: Session 2026-07-30: two children COMPLETE — .6 mobile pairing (real device paired; sidecar via BUZZ_PAIR_RELAY_IMAGE + Caddy /pair; intent-os PR block#291) and .5 Tauri CORS (packaged Linux desktop client joined prod). Remaining under this staging epic: .2 (Caddy edge controls), .3 (smokes+unauth matrix), .4 (backups+updater register).chore(beads): flush JSONL mirror — buzz-ocv.5/.6 closed + parent notes
jeremylongshore commentedon Jul 30, 2026
bd-sync from
buzz-ocv: Track-A ultracode session 2026-07-30: child .2 (edge controls) CLOSED — fail2ban + nftables connlimit applied live on the prod host, verified no self-lock (intent-os PR block#292). Remaining children: .3 (staging probe matrix), .4 (backups+updater register).