Category: platform-infrastructure

Watch It Work

Real Slack conversations show Texture's AI agent fleet triaging bugs, shipping work, investigating alerts, and co-piloting a production database migration.

By Victor Quinn

What Made It Actually Work at Scale

The hard boundaries, adversarial review, operating patterns, and architecture that turned Texture’s AI agent fleet from an experiment into a durable part of how we build.

By Victor Quinn

Give every agent a badge

The difference between a useful AI agent and an accountable teammate is not a better prompt. It is identity, scoped access, and a system that can show who did what.

By Victor Quinn

I built this for myself first

The first chapter in how Texture moved from one founder’s personal AI experiment to an agent fleet the whole company could use.

By Victor Quinn

What a line clearance is, and who holds the tag?

When lineworkers go out to perform maintenance or restore an outage, one of the key questions that arises is who is responsible for making sure the line stays dead until they climb down?

By Cyril Brunner

What a load baseline is, and how it is calculated

After a demand response event, the first question is: How much load dropped? Thermostats, water heaters, and behavioral beat the peak programs require meter data to infer what happened.

By Cyril Brunner

What's new in Texture: EV & grid services updates

This release moment is all about making EV and energy hardware more reliable, more observable, and easier to build on, especially for teams running demand response programs.

By Jessica Edwards

Grid visibility is the foundation, not the ceiling

I started my career at Vermont Electric Cooperative as a SCADA engineer. We had just been awarded federal funding and were adding thousands of real-time data points to the system.

By Cyril Brunner