More from Practitioner's Corner

Monday, July 27

ISSUE #39

Practitioner's Corner

We spent this issue chasing what looked like an agent problem and found something older. In 1995, the HTML spec defined a form as name/value pairs, a method, and a destination. The signature lines, routing codes, supervisor fields that a paper form carried natively were all out of scope. Agents inherited that hollowed-out version. Now they operate in it at a speed that makes the absence dangerous, because there's no surface to contest what went wrong or reverse it. This issue works through what rebuilding it would take.

Monday, July 27

ISSUE #39

Practitioner's Corner

Past Articles

August — Issue #40

The Two Clocks

A Queue Is Not a Shelf

Queues are not shelves. Two clocks, one in support and one in code review, show how waiting work mutates, and why capacity means attention delivered before that change.

Builder: Unwinding Work

Maxim Fateev and the Undo That Quietly Rots

Maxim Fateev built durable execution. What his design choices quietly admit is that rollback doesn't fail so much as decay.

July — Issue #39

Builder Profile

Pierre Laperdrix and the Web That Learned to See

A CNRS fingerprinting researcher's latest work reveals that production websites are becoming active counterparties, classifying every agent visit with near-perfect accuracy regardless of whether the agent completed its task.