Playbook

The Global Compliance Arbitrage Playbook

One evidence spine. Three execution planes. No imaginary passport.

There is no globally compliant AI control stack. There can be a globally reusable evidence system that assembles local controls without rebuilding the product from scratch.

Ed. 1.0 · 57 pages · Published agosto 2026
Individual reading licence 1,490 €
Living document — perpetual updates

The Global Compliance Arbitrage Playbook

Why this matters

You can pass an EU conformity assessment and still be unlaunchable in California. You can satisfy a California ADMT notice and still be unfilable in China. Your legal team knows this. What nobody has given them is the control graph that turns it into engineering.

So the work gets duplicated. Legal conclusions live in documents, system facts live somewhere nobody can reconcile, and every new market becomes a rewrite wearing a launch badge. The cheapest first release becomes the most expensive regulated product you own, because every policy change requires a fork.

This playbook is the operating system for the alternative. One evidence spine, a governed policy resolver, and three regional execution planes that can change without breaking the product family.

It is written to be implemented, not read. When an agent’s tool permissions expand, the resolver re-runs the autonomy, security, data, and human-oversight gates. When user geography is unknown, high-impact action is blocked and the request routes to a conservative non-decision experience. When a deployment combines uncontrolled input, sensitive access, and autonomous action, that is a hard stop with a named owner, a redesign requirement, and a signed acceptance, not a risk-appetite conversation under revenue pressure.

That is the real test. Hard stops exist to remove bargaining from facts that should never be negotiable on the last day of the quarter. The board approves the categories, engineering implements them, and business teams may propose a redesign, but they cannot waive an unknown legal entity, an unresolved sensitive-data route, a missing filing, an untested human escalation, or stale evidence.

Ninety days in, you should be able to resolve a deployment context into a policy bundle, produce the evidence package behind it, and rehearse the questions a regulator, a customer, and an incident will ask. A successful pilot is not one that launches. It is one that makes the next launch cheaper and safer.

If day ninety of your AI strategy ends with a governance committee, you built a committee. This is what it takes to build a regulated product that scales.

What’s included

  • 1. The policy resolver. Architecture, conflict hierarchy, and a synthetic test table that resolves deployment context into a policy bundle, data route, human checkpoint, and evidence package
  • 2. The hard-stop catalog. Ten categories covering scope, data, identity, autonomy, human control, transparency, evidence, vendor, security, and rollback, each with the exit evidence that clears it.
  • 3. The ten-question deployment matrix. Product review, customer diligence, and board risk reporting in one gate, with green, amber, and red scoring against recorded evidence identifiers.
  • 4. The AEPD Rule of 2 and the four-eyes principle. The capability pairs, the minimum design response for each, and where double verification stops reducing risk and starts producing rubber stamps.
  • 5. The minimum viable evidence schema and the minimum viable separation. What a shared evidence spine has to record, and where regional planes have to diverge
  • 6. The minimum launch record and exception discipline. Approval as a revocable state with expiry, rollback ownership, and invalidation conditions.
  • 7. The decision-risk worksheet. Moving assessment from model risk to decision risk.
  • 8. Control portability and rewrite economics. The ports, adapts, and rebuilds bands, two measurable ratios, and how to put a divergence budget in front of a board.
  • 9. The regulatory dictionary. The false friends that create expensive controls, including human in the loop, algorithm filing, model validation, and data sovereignty.
  • 10. The 90-day implementation roadmap. Two pilot journeys, day-60 and day-90 acceptance criteria, and a funded platform backlog.

Buy The Global Compliance Arbitrage Playbook

Living document — perpetual updates

Individual reading licence 1,490 € — Purchase now

Secure payment via Lemon Squeezy