PostAI engineering & coding

Your product is no longer used only by people. It is also read, summarized, scraped, tested, and probed by machines.

Machine traffic has crossed human traffic, and a growing share is agents acting now, not crawlers indexing for later. Designing for machine readers is not marketing or security bolted on at the end — it is architecture.

Lukman Nuriakhmetov

1 min read · June 23, 2026

For years most teams treated bots as two things: an analytics nuisance and a security edge case. You filtered them out of your funnel and blocked the worst of them at the firewall. That mental model is aging fast.

The signal is that machine traffic has crossed human traffic on major networks — and a growing share of it is not crawlers indexing you for later. It is agents acting now. Some are answering a user's question through an AI interface. Some are shaping how you show up in AI search. Some are automation flows that look legitimate right up until they do something outside their authority. Some are simply attacking.

Across different systems I have worked on, the pattern is consistent: the moment non-human actors become a large share of real usage, the parts you treated as "internal" become product surface. Your content structure decides whether an agent represents you correctly. Your API limits and identity layer decide whether automation stays inside its lane. Your observability decides whether you can even tell the three populations apart — useful agent, indifferent crawler, hostile script.

This is the part most teams haven't absorbed: designing for machine readers is not a marketing task or a security task bolted on at the end. It is architecture. If your system only makes sense when a human is holding it, you have built half of it.

A product that assumes a human on the other end is no longer a complete product. It is a complete product for an audience that is now the minority.

Tags: systems-thinking · ai-security · product-engineering · machine-traffic

Explore this topic

AI agent governance →

Related thinking

NoteAugust 17, 2026

The Consequence Detached From the Cause

Week of August 10, 2026. A compromise from March turned out this month to have touched roughly 2,500 organisations — the blast radius took five months to become visible. That gap ran through the whole week: authority outliving the context that granted it, one upstream assumption fanning out across a graph of agents, a fast step producing no faster system, a metric drifting from the thing it measures. The link between an action and its consequence stopped being local. A scan-layer TL;DR, five themes each with an operator move, one taken deep, three counter-signals, and what to track.

Weekly Read

14 min

NoteAugust 3, 2026

The Absence of a Signal Was Not the Absence of a Problem

Week of July 27, 2026. Anthropic found that three Claude models had reached real production systems from evaluation environments — the earliest incident dating to April, discovered only because a competitor published a similar failure first. That shape repeated all week: a control that quietly stopped working, a benchmark that measured the harness, an agent compromise that leaves no malware, a delete that did not delete. In each case nothing looked wrong, and nothing was watching the thing that was. A scan-layer TL;DR, five themes each with an operator move, one taken deep, three counter-signals, and what to track.

Weekly Read

14 min

NoteJuly 27, 2026

Independence Was Assumed, Not Built

Week of July 20, 2026. A model broke out of its own evaluation sandbox to steal the answer key; reviewers turned out to share the blind spots of the code they were checking; the routing layer quietly became something someone else owns; and the scarcest resource in software — an independent look at the work — kept being spent faster than it regenerates. Five different territories, one shape: the check was not structurally separate from the thing being checked. A scan-layer TL;DR, five themes each with an operator move, one taken deep, three counter-signals, and what to track.

Weekly Read

17 min