ES
Trajectory enforcement for AI agent systems

Every agent can follow its rules.
The system can still break yours.

DiaCroma sits outside your agents. Before any action runs, it checks it against the rules you signed and everything your agents have already done. Then it lets it through, changes it, or stops it.

Signed authorityShared trajectory stateCross-agent lineage Pre-execution decisionsMulti-cloud architecture
See the multi-agent failure See where DiaCroma fits

Cloud-neutral architecture · platform validation reported separately · see current platform evidence →

Where DiaCroma fits

Your platforms govern agents and calls.
DiaCroma governs the trajectory they form.

DiaCroma does not replace identity, inventory, runtimes or gateway policy. It adds the durable, shared state needed to decide whether an action is still admissible after everything the agent system has already done.

01 · CONTROL PLANE

Who is the agent?

Identity, ownership, permissions, lifecycle and fleet inventory.

Identity · registry · cloud administration
02 · PER-ACTION CONTROLS

Is this call allowed?

Tool access, argument limits, content controls and policy for one proposed action.

Policy engines · gateways · platform controls
03 · TRAJECTORY ENFORCEMENT

Is it still allowed now?

Accumulated authority, shared budgets, sequence, lineage, delegation and coupled constraints.

DiaCroma for Agents

The category is trajectory enforcement: governing the cumulative system before the next business effect is allowed to execute.

The failure no green dashboard shows

Every action is within policy.
The combined outcome is not.

Four agents handle one customer across different systems. Each sees its own admissible action. None sees the business boundary they share.

One customer · four admissible actions

Illustrative multi-agent case using a signed global concessions boundary.

GLOBAL LIMIT · $300
Microsoft · Billing

June approves a refund

Inside her $200 per-action cap.

$175
AWS · Orders

Martha applies a discount

Inside the current price book.

$150
Google · Support

Theo offers a credit

Inside his goodwill authority.

$100
Salesforce · Case

The case is closed

The customer sees one combined outcome.

$425 total
PER-ACTION CONTROLSEverything stays green.

Four admissible actions. A $125 business-policy breach.

WITH DIACROMAThe last action cannot execute.

The shared trajectory names the boundary, blocks and escalates with evidence.

Illustrative logic, not a customer outcome or a claim that every named platform integration is currently validated.

How enforcement works →What is currently proven →

Drift, in two pictures

A white feather adrift against black.
Without governanceNobody threw it. Every gust was small, every move was allowed, and it still ended somewhere no one chose.
Darts standing in the centre of a board.
With governanceNothing leaves that nobody aimed. Each throw is checked against the authority that was signed, and the record says who allowed it.

We do not make the dart hit. We stop the throw that was never going to land inside the boundary — before it leaves the hand.

The enterprise buying committee

One control layer.
Four reasons to approve it.

CIO · Chief AI Officer

Govern across clouds without replatforming.

Add shared trajectory control while existing identity, registries, gateways and runtimes remain in place.

Architecture and deployment →
Finance · Operations

Bound total exposure, not only each transaction.

Enforce cumulative limits across refunds, discounts, credits, purchases and commitments made by different agents.

Inspect the evidence →
CISO · Security

Stop the governed action outside the model.

Decide before execution and name bypass routes explicitly instead of treating visibility as control.

Review the enforcement boundary →
Legal · Compliance · Audit

Reconstruct authority, decision and effect.

Produce a replayable record that supports review and defensibility without claiming automatic compliance.

Review claim boundaries →

Frequently asked, answered precisely

What DiaCroma is —
and what it is not.

What category is DiaCroma creating?

Trajectory enforcement for AI agent systems: stateful, pre-execution control over accumulated authority, sequence, lineage, delegation and shared constraints.

Is DiaCroma an agent gateway?

It can use a gateway as an enforcement point, but the gateway is not the product. DiaCroma maintains the signed authority, trajectory state and evidence the boundary enforces.

Does it replace agent platforms or control planes?

No. Identity, inventory, runtime, orchestration and cloud administration remain where they are. DiaCroma adds a shared trajectory layer across governed routes.

Is it only a mission-drift monitor?

No. Drift is one case. DiaCroma also enforces cumulative budgets, sequence, evidence, delegation and cross-agent constraints before execution.

What makes the architecture multi-cloud?

Signed authority, trajectory state and evidence are platform-neutral. Boundaries can run near agents and tools in different environments; current validation by platform is reported separately.

What happens when DiaCroma cannot see or stop a route?

It does not claim full governance. Coverage is reported as governed, partial, unknown or unmanaged, with the missing control named.

Does a language model decide whether an action is blocked?

Not for structural controls. Tool membership, numeric caps, cumulative budgets and sequence are evaluated deterministically. Optional semantic signals are identified separately.

SDK & API docs →How to buy →Research & foundations →

Inspectable reference deployment

Meet Acme.
Fictional company. Real reference environment.

Acme is a controlled, synthetic enterprise example — not a customer case study. It lets you inspect proposed actions, DiaCroma decisions, accumulated trajectory state and onboarding records without credentials or a sales call.

Walk the operations floor →Inspect onboarding →See exactly what Acme proves →

Start with one governed route.

Choose one agent, one business effect and one execution path. Validate the boundary, decision, receipt, settlement and replay before expanding coverage.

Validate one governed route → Review the product →