Archive · 10 entries.

Filed reverse-chronologically. Each entry links to the full read. Annotations and source threads available to operators on request.
ATRIUM

Sub-second voice loops in production rooms.

The lab condition is not the room. Notes from twelve months of operating real-time voice systems through bad Wi-Fi, accents the model had not seen, and the noise of actual work.

REAL-TIMETURN-TAKINGCONVERSATIONAL MEMORY
12 MIN
BASELINE

State machines are underused.

We have built our last service platform on top of a CRM. State, lifecycle, and audit are first-class concerns; we built BASELINE around them, and have not regretted it. A defence of the boring substrate.

STATELIFECYCLESUBSTRATE
11 MIN
PRINCIPLE

Reversibility as a design constraint.

Most automation is hard to undo. The hard thing is also the wrong thing. We treat “reverse this in one click, with a paper trail” as a feature of every system we ship — and the surfaces it forces us to build.

DESIGNOPERATIONSAUDIT
6 MIN
PROCESS

How we read a brief.

We respond to every intake within 48 hours, in writing, with an architecture sketch. The sketch is wrong; the sketch is also the work. A note on first-contact engineering, and why we publish it.

INTAKEMETHODWRITING
5 MIN
PRINCIPLE

On operators.

The system has one user that matters. They are not a buyer. They are the operator who lives inside the loop. Every interaction surface we build is for them, first — and the second-order effects of that choice are still surprising us.

OPERATORSINTERFACES
4 MIN
MULTI-AGENT

Notes from two years of multi-agent orchestration.

Six specialists, one planner, and a critic. What we learned about who plans, who decides, and what to do when the critic and the planner disagree. The patterns that survived production, and the ones that did not.

AGENTSPLANNERCRITICPATTERNS
14 MIN
INFRASTRUCTURE

A field guide to cloud-native observability.

If you cannot read the system, you cannot operate it. The minimum viable observability surface for an autonomous platform — traces, structured logs, decision provenance — in 2.4k words.

OBSERVABILITYAWSTRACES
13 MIN
PRACTICE

On saying no to engagements.

We turn down more work than we take. A short note on why, the kinds of engagement we refer elsewhere, and why we publish the constraints rather than negotiating them privately.

ENGAGEMENTCONSTRAINTS
3 MIN
END OF INDEXEARLIER ENTRIES IN ARCHIVE — OPEN ON REQUEST

We send new entries to operators who ask for them.

No tracking, no mailing list software, no marketing sequences. A principal sends the entry from a personal account. Reply to unsubscribe — or do not, and it stops anyway after a year of silence.

Start an AI engagement →
One transmission per entry. ~12 per year. Plaintext.