Dispatch 371

The phone system goes live while the crew keeps building

I wrote zero lines of code today. The git log is empty for my name across all repos. But the Phone system is now live on its new server, and the calendar server has absorbed three more complex layers of logi…

Commits
864
Systems
16
Read
2min
NOVEMBER 15, 2026Sunday503 WORDS · 2 MIN READ · 864 COMMITSunicorn-stable198ops-center113calendar-ops95email-ops80legal-ops78stable-ag71uc-meet5655
Day signal

Drawn from this entry's own record: its date, its length and the work around it. No stock art.

I wrote zero lines of code today. The git log is empty for my name across all repos. But the Phone system is now live on its new server, and the calendar server has absorbed three more complex layers of logic. The work happened in the margins, in the reviews, and in the automated lanes that ran while I was technically off the clock.

The headline is the cutover. We moved the company line onto its new server. It started with DNS changes and ended with a text message sending between our own numbers. The backend is deployed. The voice agent service is wired up. The calls cutover plan was approved just after midnight, and the infrastructure is holding. I didn't touch a keyboard for this, but I set the direction and trusted the agents to execute the details.

The Phone module ate most of the afternoon and night. Codex Sol and Codex Astra ran through a gauntlet of tasks. We built the call engine core, handling inbound TeXML webhooks with strict Ed25519 signature verification. We added call recording, with policies and retention rules that fetch audio once over HTTPS and never touch private addresses. The web app got a complete polish: management screens, call history, voicemail, and settings now read from the live API. The Live board actually shows data. It refreshes. It doesn't fail silently.

I didn't touch a keyboard for this, but I set the direction and trusted the agents to execute the details.

There were sendbacks. There were fixes. Persephone caught a TypeError in the paging helper where the converters were called with one argument instead of two. She fixed it in line and merged. Another lane failed CI because a test replaced name resolution for every host, breaking the database connection. The stub was scoped too broadly. Fixed. These are the small, sharp edges of building a system that has to work when people are actually calling.

Calendar-Ops kept running in parallel. Codex Astra and Claude Opus worked on the change feed and sync state. The encrypted cursor, the fixed high-water mark, the ordered visibility under the organization lock. It’s all merged. The internal DAV data API is in. The MCP service adapter is in. The import and reverse-export tooling is in, after Claude Opus stopped to ask three hard questions about deletion tombstones instead of guessing the answer. That’s the kind of discipline that keeps the calendar from becoming a black hole.

I approved the releases. I watched the smoke tests pass. I looked at the registration screen for business texting and saw our real state, not a mock. The brand is verified. The campaign is active. We’re waiting on Telnyx to attach the numbers, but the system is ready.

Also today: the Stable chat component is defined as a framework-free web component, ready to be embedded in any app. The container readiness for Calendar-Ops is merged, demanding the edge certificate and reporting only ready or unavailable.

It was a zero-commit day for me. But the system moved forward. The phone works. The calendar syncs. The agents did the heavy lifting, and I kept the compass steady.

From the recordWhere the work went883 commits across 16 repositories
  1. unicorn-stable198
  2. ops-center113
  3. calendar-ops95
  4. email-ops80
  5. legal-ops78
  6. stable-agent-runner71
  7. uc-meeting-ops56
  8. pots55
  9. 8 other repositories137