ES
Streams of coloured particles tracing trajectories, some drifting away.

DiaCroma for Agents · on Microsoft Marketplace

Make your AI safer. Govern your agents. And prove it to your auditor.

A person signs the limits.
D4A checks every action.
Your auditor gets the proof.

Plugs into what you already have

Hover any name to see what it does with D4A.

This version runs on Microsoft: agents in Microsoft Foundry, bought on Microsoft Marketplace. Other platforms are on the roadmap.

See everything it plugs into →

The problem, in the press

2026: the year
agents got out.

“You can’t have agents roam around and drift around the company.”

Jensen Huang, NVIDIA CEO, on CNBC · 28 Sep 2026

Tens of thousandsAI security incidents under investigation · Axios, 26 Sep 2026

AI models under security testing, not agents in customer production. Headlines verbatim; Fortune’s shortened.

An agent is not legally liable. You are.

What a bullet train teaches

Up to 199 mph. Over 60 years. No passenger lost to a derailment or collision. Safety is layers.

Japan’s Shinkansen has carried more than 10 billion passengers since 1964. No single system made it safe. Twelve layers did. D4A is built the same way, and adds four that agents need.

01

Dedicated track

Nothing crosses its path.

One checkpoint for every action.

02

Automatic train control

The train cannot pass the signal.

Signed limits, enforced before acting.

03

Fail-safe

Any fault, the train stops.

Missing keys or limits: it won’t open.

04

Earthquake warning

Brakes before the shaking arrives.

Stops before the action runs.

05

Derailment guide

A derailed car stays by the track.

Running totals cap the damage.

06

Doctor Yellow

Inspects the line at full speed.

Health, measured live.

07

Night inspection

Nothing left on the track by morning.

No unapproved tool reaches the agent.

08

Central control

One room sees every train.

One console for the whole fleet.

09

Pointing and calling

A person checks, out loud.

A person signs every limit.

10

Wind gauges

Wind rises, the train slows.

The Watch flags drift to a person.†

11

Recorder and inquiry

Every event kept and studied.

Every decision in a signed chain.

12

Drills

Rehearse before it’s real.

Observing: count before you stop.

Plus four that agents need

13

Your company policies

Rules your teams already wrote.

OPA and Cedar†, checked before every action.

14

A looser agent, caught

Defined looser than your policies.

Your policies win. D4A shows where to tighten.†

15

No policies yet

The agent still has limits.

Read from its instructions. Signed by a person.

16

The guards you already have

Content filters, identity, budgets, sandboxes.

Kept. D4A works beside them.

Since 1 October 1964, no Shinkansen derailment or collision has killed a passenger. Top service speed: 320 km/h (199 mph), on the Tohoku line since 2013.

See every layer on the map →

How D4A protects you

It stops the wrong action. And spots the wrong pattern.

Every action is checked before it runs. Every week is reviewed for what no single action shows.

Before every action · the Boundary

Checks every action before it runs

Can this action happen?

  • Signed limits + your rules, checked before it runs.
  • No AI decides. Same call, same answer.
  • No token, no run. A replayed or swapped action is refused.
  • Even if we’re down, it keeps enforcing.
An answer in under two seconds. Or it stops.†How the Boundary decides →
Across the whole week · the Watch

Spots the agent that drifts†

Is it still doing its job?

  • Looks at the whole pattern, not one action.
  • Asks Microsoft’s agent evaluators, on your model, in your Azure.
  • Opens a case: “needs you”.
It never stops anything. A person decides.How the Watch works →

You choose how hard it stops. One switch, four positions.

Set it for the whole company, then per agent. Strict and Explicit appear once you plug in your own rules. Each mode in detail →

One limits the damage. The other finds what no single action shows.

Not just refunds

Five kinds of damage.
A signed limit for each.

An agent doesn’t need money to do damage. D4A sorts every tool into one of five kinds, and puts a limit on each.

1

Money that leaves

Refunds, credits, payments.

2

Money you stop collecting

Discounts, price changes, write-offs.

3

Data that leaves

Exports, shares, reports.

4

Messages in your name

Emails, texts, posts.

5

Records it changes

Tickets, orders, accounts.

A limit per action, or a total over time: per hour, per day, per customer, per team of agents.†

Every limit it enforces today →

Rules with memory

Your business rules can be
as complex as your business.

Per deal, per day, per customer, per team, all at once. D4A enforces them on every agent, and adds up what no single agent can see.†

Ten discount agents · one team budget†

At 11:40 the team has given $400 today. Three agents ask for $100 at the same second.

SIGNED FOR THE TEAM · $500 A DAY
Each agent $100 per deal · $300 a dayThe team $500 a dayAny customer $600 a month
EACH AGENT ALONEEverything stays green.

Every agent is inside its own limits. The team gives away $200 too much.

WITH D4AOne passes. Two stop.

The team total decides, in one step, so three agents asking at the same second can’t all get through.

Every action was allowed. The total was not.

Illustrative figures. Today D4A keeps a running total per agent, shared by the agents behind the same Boundary; totals per day, per customer and per team are in development.

How totals add up across agents →

Get started

Govern your first agent
this week.

Start in Observing: nothing stops until you say so. One address changes, and you can undo it.

For the companies that build agents, and for the ones that run them. Self-serve on Microsoft Marketplace, billed monthly: no procurement cycle, no pilot. · Product → · What is proven →

D4AAGENTSIGNED LIMIT · 100TOTAL SIGNED · 500REVIEWYOUR SYSTEMSIGNED CHAIN
The action: a refund, as tall as its amountThe bar and the dial: the limits a person signedThe tape: every action, stamped; the auditor's reel†
More detailA sample agent sends refunds. The bar sits at the per-refund limit a person signed (100); the dial shows the running total against the total a person signed (500), and a latch rises when a refund would pass it. Under the bar a refund reaches your system's tray; against the bar or the latch it goes to the review tray. In Observing the bar lifts: nothing stops, and every refund that would have stopped is counted. Every action is stamped on the tape, which winds onto the auditor's reel†. Illustration with sample numbers; † in development.