Back to Series
Series 3 posts ~24 min total

The Bifurcation

A series on the two ways a machine can be given eyes — operate the interfaces built for humans, or demand interfaces built for machines. It starts as an industry-scale standoff between two bets, questions whether splitting effort across both means neither ever finishes, and ends with the standoff collapsing into a single pipeline where a human still has to close the seam.

Every agent system makes the same quiet bet, usually without naming it: teach the machine to navigate interfaces built for people, or rebuild the interface so it never has to pretend.

This series follows that bet from the altitude of industries down to the inside of a single afternoon’s work — where it stops being a strategy and becomes a boundary you discover at runtime.

The Arc:

  1. The Civil War Inside Every Agent — Two bets, both real, both funded: mimicry versus machine-native. The industry isn’t picking one. It’s running both at once, and the whole field is drifting unevenly toward the native end.
  2. What If the Fork Is the Problem? — If both paths are live, splitting investment across them might mean neither ever gets finished. The fork itself may be the cost.
  3. Where the API Stops — A field report. Building an owned publisher, the industry-scale standoff collapsed into one pipeline: API where the vendor built one, browser where they didn’t, and a human stitching the seam where neither held.

The arc moves down in scale. The first post watches companies choose sides. The last one finds both sides inside a single job — and the seam between them sitting exactly where one vendor’s API coverage happens to stop.

Reading Order