Field Notes

Dispatches
from the field.

Notes from the work, one dispatch a month: what we installed, what the environment taught us, and what ran after the call ended. Written from the inside of real deployments, not the outside of a blog. Client names stay out. The lessons stay in.

The log

September 2026

A room learned to think before it prompts, and the second system waits on one change that belongs to the client.

Trust No Bot, September 24 in Miami Lakes, co-produced with Jose Cruz of Savvy Gatsby. Small-business owners left with a one-page policy for their team, in English and Spanish.
The second engagement, built with Jose Cruz, is staged for an October launch. The last step is a DNS change on the client's side. Their IT owns the perimeter; we do not reach past it.
A point release on the first engagement was re-cut before it went out, because the install notes still described the old version. A release is the code and every document that describes it.
The Periodic Table of Primitives turned away a candidate element. It was a word made of old letters, not a new letter.

August 2026

The first system carried real work on the client's own server, and a gate that said red was wrong.

The first engagement ran its first live file end to end on the client's own machine, and the release they asked for shipped the same day.
Pre-flight came back failing against an environment that was healthy. We checked the environment directly before believing the gate. The gate was wrong, not the client.
Before any client data moved on the second engagement, we declared who owns each field: the source system owns the facts, we own the presentation.
New end-to-end tests caught a sign-in failure the passing suite had missed. A green suite that never runs the path proves nothing.
The primitives got a notation: each one drawn as a machine whose motion shows the work it does.

A new dispatch, every month.

No feed and no list to join. Send a line and each month arrives by note.

Get the dispatches

Dispatchesfrom the field.

A room learned to think before it prompts, and the second system waits on one change that belongs to the client.

The first system carried real work on the client's own server, and a gate that said red was wrong.

A new dispatch, every month.

Dispatches
from the field.