Sign the authority.
Mission, tools, caps, budgets, resources, invariants and acceptable evidence become a versioned anchor.
DiaCroma evaluates every action routed through it against what the agent — and the agents around it — have already done. It adds durable, deterministic enforcement without replacing your agent platform, identity system, runtime or cloud.
Per-action controls ask, “Is this call allowed?” DiaCroma also asks, “Is it still allowed after everything already done?”
The control loop
The agent still reasons in its own runtime. DiaCroma governs the transition from proposed intent to business effect.
Mission, tools, caps, budgets, resources, invariants and acceptable evidence become a versioned anchor.
A tool call, delegation, message or other effect arrives at a boundary outside the model.
DiaCroma checks cumulative authority, sequence, lineage, shared constraints and evidence against durable state.
The structural decision does not depend on a language model.
The permit is consumed, the resulting effect is reconciled, and the evidence row is sealed for replay.
A permit is valid only against the live trajectory state that produced it. If that state moves first, the proposed effect is no longer authorized.
Product boundary
DiaCroma consumes identity, policy and tool context from the surrounding stack. It does not rebuild the layers enterprises already operate.
Where it runs
Agents and business tools stay where they run. DiaCroma places an execution boundary near the effecting route while the same signed authority, trajectory state and evidence follow the work across platforms.
A runtime connected through a validated adapter proposes an action. Platform validation is reported separately.
Builds context, reads the live trajectory and returns a permit, replan or block.
On a closed governed route, executes only with a valid permit and returns the receipt required for settlement.
It runs in your network, at your boundary; validation is reported route by route. See what is running today, and what is coming next, on the Evidence page → · What changes in your architecture →
What the enterprise signs
Mission anchor, deployer credential, agent identity, allowed tools and the version of the authority being enforced.
Exact per-argument ceilings plus the authority that may be spent across the lifetime of a trajectory or delegation tree.
What agents read and write, which resources are coupled, and which operation classes cannot follow one another.
What each tool can prove, how fresh that evidence must be, and how the proposed action closes against the effect that actually occurred.
Frequently asked, answered precisely
Trajectory enforcement for AI agent systems: stateful, pre-execution control over accumulated authority, sequence, lineage, delegation and shared constraints.
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.
No. Identity, inventory, runtime, orchestration and cloud administration remain where they are. DiaCroma adds a shared trajectory layer across governed routes.
No. Drift is one case. DiaCroma also enforces cumulative budgets, sequence, evidence, delegation and cross-agent constraints before execution.
Not for structural controls. Tool membership, numeric caps, cumulative budgets and sequence are evaluated deterministically. Optional semantic signals are identified separately. A model reads and proposes; a person signs. At runtime, the decision is deterministic and can be recomputed.
Next