Engineering notes
Blog.
Fourteen deep dives on building CommsCrew, one per architectural layer plus the concerns that cut across all of them. Each one is a real account of one decision: what was chosen, what it cost, and the bill it is still paying. Every diagram is drawn from the actual code, and nothing here claims a capability that has not been measured.
It Takes Them Days to Prepare a Campaign
The market is full of tools that write posts. I went looking for the one that runs the whole line, and could not find it.
Nothing Exists Yet
The campaign pipeline is four stages, and every decision worth explaining lives in the boundaries between them.
The Orchestrator's Tools Are the Other Agents
A typed blackboard, five delegation tools, and a dispatcher that refuses illegal moves. How the crew layer decides who works next.
Three Tiers of Memory, One Write Path
The text, the vector, and the name of the model that made the vector have to move together, or the crew ends up confidently retrieving nothing.
The API Layer Is Where the Model Bill Gets Bounded
Limits keyed by what they cost, two clocks on every stream, and authorization that refuses what it does not recognize
The frontend layer: turn every silence into a failure
A thin client over a streaming backend, where an unhandled server event is a compile error and a failed load can never render as an empty list.
Expand Only
The data layer is allowed to add to the schema and to do nothing else, and every other decision in it follows from that one rule.
A Cost Column That Is Allowed To Be NULL
The observability layer: one capture point, three sinks, and a number that refuses to be confidently wrong.
The Deploy Path Is the Recovery Path
One spot instance at six to eight dollars a month, where shipping a release and losing the server run the same code.
Four Kinds of Test, Because There Are Four Kinds of Wrong
The testing layer: unit tests check code, contract tests check a boundary you do not own, evals check behavior, and a control checks the eval.
Agent Engineering Is Not a Layer
Six concerns with no box in the architecture diagram, which is exactly why it is easy to believe you are doing them.
Security Is Four Boundaries, and the Bug Lives in the Seam
Authorization that fails closed, queries scoped to a tenant, egress checked on resolved IPs, and a deploy role that cannot overwrite what it deploys past
The Eval Has to Be Able to Embarrass You
Two suites, one deterministic mock, thresholds calibrated from a measurement, and the positive control almost nobody builds.
Every Decision in This System Has a Price Tag
Nine choices, the alternative each one rejected, and the bill each one is still paying.
Prefer one narrative pass instead? Read the five-part origin story first.