Behavior Engineering

For as long as software has existed, understanding it meant reading it. We came to know our systems line by line, and our confidence in them rested on the people who had read every part.

That is ending.

Software is now made faster than anyone can read it. Soon it will be made mostly by machines, in volumes no one will ever see. We will stop asking how it was built, and one question will remain: does it keep its promise?

When making things becomes abundant, intent becomes scarce. Intent is the quiet knowledge of what a system is for: what it should do, for whom, and what it must never do. It lives in people. It is seldom written down. And when everything speeds up, it is the first thing to go.

We believe this changes what it means to be an engineer. The work moves from writing a system to keeping it: deciding how it should behave, holding it to that, and answering for it when it changes. Software engineers will become behavior engineers.

And in time, behavior will become the thing we build from. We will describe what a system must be, and the rest will follow.

Neomata is our bet on that future: a way to keep the promise while everything beneath it changes.

We are opening it to a small number of teams who already feel this shift. If you are one of them, we would like to talk.