Why this matters to your seat

You're the team that fields the "is the agent compliant?" question from legal, the "where's the audit trail?" question from internal audit, and the "can we ship this into europe-west3 production?" question from product. You've probably built half the answer already — a custom audit-event wrapper, a kill-switch endpoint, a retention policy on the Vertex session-service.

Regulus is the framework that composes those pieces into one coherent decision plane. The plugin SPI is ADK's own. The service extensions wrap Google-shipped implementations. The audit chain is offline-verifiable. The GRC adapters land signed evidence in ServiceNow IRM or OneTrust without you writing the integration yourself.

What you'll see in the first hour

Regulus control plane sits beside Google ADK runtime Four horizontal lanes — Google Cloud data plane, Google ADK runtime, Regulus decision plane, and external GRC systems — with plugin SPI seams connecting ADK to Regulus. Google Cloud — data plane Org Policy · VPC-SC · Assured Workloads · Cloud Audit Logs · CMEK / EKM Google ADK 1.2 — runtime BeforeAgent BeforeModel BeforeTool AfterTool AfterModel Regulus — decision plane Policy BeforeTool Privacy B/A Model Audit AfterTool Kill switch BeforeTool Model risk BeforeModel Residency A/M write External GRC · ServiceNow IRM · OneTrust · MetricStream · webhook

What we don't claim to be

Where to go next