Engineering log

Weekly engineering notes — what shipped, what was decided, what's next.

Sunday, May 24, 2026 — Our signup form was quietly dropping everyone

The morning after we demoed at Canopy, I pulled up the waitlist over coffee on Sansome Street. Yesterday's signups were there. Today's weren't. I opened the site and got a server error. That made no sense; the site is static, and a static page can't throw a server error. The only thing that could was the form service behind it. It was down, and every signup that day had gone straight to nowhere.

Next: bring back the longer form and wire the email side, then go looking for whatever else we won't notice when it breaks.

Friday, May 22, 2026 — Lifecycle landed, system doc shipped, Canopy tonight

Next: post-demo conversations. Then capacity testing — first numbers we can stand behind in public.

Friday, May 15, 2026 — VC demo, system doc design, performance pass

Next: ship the documented endpoints, the alerting, and the system doc.

Friday, May 8, 2026 — Spec work, triage, external review

Next: ship the spec'd work, top to bottom.

Friday, May 1, 2026 — Lifecycle, first pass

Next: operator-facing views, and the alerting bundle.

Friday, April 24, 2026 — Egress shaping, DNS, knowledge capture

Two threads. Half the week on network controls, half on writing decisions down before they walk out the door.

Next: state machine refactor. Spec is mostly written; the cuts are next.

Friday, April 17, 2026 — Network hardening, agent scaffolding

Closing audit findings and standing up the daemon.

Next: per-VM bandwidth shaping, rate limiting verified from inside a real boot.