Library
Papers on getting trustworthy answers out of disconnected operational systems, and a running account of building BessWave in the open.
Longer pieces on the problem we are working on and how we think about it. Written for the person deciding whether this is real.
Putting a language model on top of operational data is easy. Making it affordable to run every day, for every person, is an architecture problem. This paper explains where the cost of an answer actually comes from and the design principles BessWave follows to keep it under control.
Read the paper (PDF)Every system in your operation already has a dashboard. The questions that matter most cross the boundaries between them, and those are the ones no single dashboard was built to answer. This paper explains why connected operational questions need a system that understands how records relate to one another, rather than another view of the same data.
Read the paper (PDF)The Journey
An honest account of what we are building, what we are learning, and what is next. Posted when there is something worth saying.
Read the Journey