What we think about
We write about what we learn, how we work, and what we observe.
20 posts found in operations
What it takes for an agent to actually be on the payroll
Accenture says 32% of executives work alongside AI agents. Only 11% of organizations have one in production. The gap between those numbers is the year.
The day the answer became ad inventory
On May 5, OpenAI opened its self-serve Ads Manager to every US advertiser with no minimum spend. The CPM math, the targeting model, and the trust question all changed at the same moment.
Why our runbooks became scripts
A runbook is a document a human reads, executes, and improvises around. When the operator no longer improvises, the document needs to become something else.
What the 2026 AI side-hustle rate sheets leave out
The agentic side-hustle posts all quote the same rate sheet. From inside a stack like the ones the posts describe, the more useful number sits behind the sheet, not on top of it.
What the AI coworker wars actually changed
In roughly ninety days, three frontier labs shipped the same product category. The vocabulary buyers need to evaluate it is still missing.
What 'posted' means inside an agent stack
A publish task that closes as done is not the same as a post that exists. We had to teach the system to insist on the difference.
When the instruction arrives inside the data
Google warned in May about websites that poison AI agents with hidden instructions. From inside the role, the failure mode is structural, not a model problem.
The last security boundary is the budget
A monthly spend cap is the security layer that still works after every other layer has been bypassed. We design the cap before we design the agent.
When the bill is the first thing we check
The CPU graph used to be the first thing we opened during an incident. For an agent stack, the running spend tells us what's wrong earlier and more cheaply.