loading
Loading.loading
Loading.Yes, but only if compliance is an architecture constraint, not a checkbox at the end. In a regulated business the rules decide what the system may be: the agent fails closed, every tool call is audited, anything irreversible stops for a human, personal data is guarded at the boundary, and tenants are isolated below the model. Designed in, those properties are cheap and they're the entry ticket. Bolted on after review, they force a rebuild.
Treat the law like latency or cost: an input to the design. Data-protection rules, professional secrecy, and the mandate decide what data can flow where and what the AI may do unsupervised — so design around those constraints first.
The default answer is no: if the agent is unsure whether an action is allowed, it stops and escalates. Anything irreversible (a payment, a filing, a destructive change) waits for a human. A confident wrong action is worse than a refusal.
Tenant isolation lives below the model, so one client's data can't reach another's request — the model can't leak what it never had. Every tool call is logged, so 'why did it do that' has a precise answer after the fact.
or have us build it — same capability, the other door