Specification, permissioned data paths, the gates where a person decides, and one record across all of it. Ours run on it. So do the agents you bought from someone else, which is the point: within two years most companies will have several suppliers and no single account of what any of them did.
One supplier for support, another for logistics, something a team built themselves, and a licence finance bought directly. Each works. None of them can tell you what the others did, nobody owns the aggregate, and the first time someone asks why a decision was made the answer takes three weeks and four emails. Agents proliferate faster than the ability to account for them.
Each supplier logs its own work in its own format inside its own platform. There is no view of what the agents in your business did this month.
Every tool has its own idea of when to involve a person. Your risk appetite ends up defined by whichever vendor had the loosest default.
When the work, the prompts and the history live in a supplier's platform, changing supplier means starting again. That is a dependency, not a purchase.
It sits in your environment, between the work and whatever is doing it.
What the work is meant to do, written once, in a form both your people and the agents work from. Change the specification and the behaviour changes with it.
Denied by default. Each agent reaches only what its work requires, and the route is the same one whether the agent is ours or a supplier's.
Thresholds and escalations set by you and applied across every agent, so your risk appetite is yours rather than a collection of vendor defaults.
What was asked, what came out, which model, who approved, across every agent in the business. Held in your estate.
Specification, the gates and the record, with our own agents running on the layer.
Bringing agents from other suppliers under the same gates and the same record. Designed and partly built. Ask us where it stands before you plan around it.
That is the structural reason this layer belongs with you rather than with an agent vendor. The company that supplies the agents has no interest in a record that makes its performance comparable, and no standing to hold the account for the competitor down the hall.
So the layer is deployed in your environment, on models you choose, with the record in your hands. We would rather be the ground your agent suppliers run on than be one more of them.
The layer arrives underneath your first agentic application rather than as a platform purchase in advance. You pay for it once and every application after that stands on it.
Each new application registers its specification, its paths and its gates in the same place. The record becomes one account instead of several.
Agents you bought elsewhere brought under the same gates and the same record, so the aggregate is finally answerable. This is the part still being built, and we will tell you exactly where it stands.
It goes in under your first application. Everything after that stands on ground you already paid for.