EventusBuilder

The engine AIMS Agent runs on. It generates event-sourced applications from a schema definition — the reason our audit trail is a property of the system rather than a feature someone remembered to add.

What it does

Most frameworks start from the shape of your data. This one starts from what happens.

You declare what your system needs to record — and that declaration is the declaration of what can happen. Each type you declare produces a fixed set of event types with stable identifiers, and those events are the system's entire vocabulary. Nothing can be recorded that was not named in the design, which is the point rather than a limitation: it is what makes the record complete by construction instead of by discipline.

EventusBuilder generates the application around that vocabulary — the storage, the API, the workflow orchestration and a client. The current state of anything is derived from the events that produced it.

So how did this come to say this, who changed it, and when is answered by reading the record rather than by investigating it. In a compliance product that question is not occasional. It is the product.

Why it exists

We did not set out to build a generator. We set out to build AIMS Agent, and found that the properties it needed — complete history, workflow-owned state changes, an audit trail nobody can forget to write — are properties you get cheaply if they are in the foundation and expensively if they are not.

So the foundation came first. AIMS Agent is the first thing built on it, and the reason we can say what the engine is good for rather than what we hope it might be.