AI-styring er ikke lenger valgfritt

Avsnitt 1

Hva som endret seg

Flere uavhengige utviklinger på begge sider av Atlanteren peker i samme retning: den som distribuerer et AI-system bærer reelt, direkte ansvar for atferden.

• Mobley v. Workday (USA, 2024–2025)

  En amerikansk føderal domstol tillot en søksmål om diskriminering i ansettelse mot en AI-leverandør basert på et agenturarguement – og behandlet AI-systemet som om det handlet på vegne av virksomhetene som brukte det. I mai 2025 godkjente domstolen betinget sertifisering av en nasjonal gruppeaksjon. Saken signaliserer at virksomheter som distribuerer automatiserte beslutningssystemer kan deles om det påfølgende ansvaret.

• OLG Hamm (Tyskland, 2026)

  En tysk høyere regionsdomstol tok opp spørsmål om ansvar for uttalelser en AI-chatbot gir til kunder, og indikerer at en generell ansvarsfraskrivelse – «svar gitt uten garanti» – ikke i seg selv skjermer en virksomhet fra ansvar for det AI-en forteller folk.

• EU AI Act & produktansvarsdirektivet

  Høyrisikoobligasjoner under EU AI Act fasesettes gjennom 2026–2027, med straffer på opptil €35M eller 7 % av den globale årlige omsetningen. Det reviderte produktansvarsdirektivet behandler programvare og AI-systemer som «produkter», og utvider strengt ansvarsprinsippene på tvers av distribusjonskanalen; medlemsstater gjennomfører det i nasjonal lovgivning innen desember 2026.

• US state regulation

  The Colorado AI Act (effective 2026), New York City’s Local Law 144, and the NAIC Model Bulletin adopted across roughly two dozen states are converging on the same expectations: disclosure, impact assessments, bias audits, and audit-ready decision logs.

• AI-built applications (Lovable, Base44, Bolt.new, and similar)

  “Vibe coding” platforms now let non-developers ship production web apps from natural-language prompts, and those apps frequently connect to company data — Google Workspace, Salesforce, databases. The same deployer-responsibility principle applies: the organization that deploys an AI-built app is its data controller and answers for how it handles personal data, not the builder platform. Most companies have no inventory of what their AI-built apps can access — exactly the blind spot a reviewer probes.

What it means for you: if your organization uses AI tools, assistants, or agents that can touch company data, you are increasingly the party expected to show you governed that access responsibly.

Section 2

Why disclaimers won’t save you

Many organizations assume their AI risk is the vendor’s problem, or that a terms-of-service disclaimer settles the matter. Two trends are closing that gap from both sides — a squeeze that leaves the deployer holding the risk.

• Courts are widening deployer accountability

  Decisions like Mobley and OLG Hamm treat the company using AI as accountable for outcomes, and have looked past general disclaimers as a complete defense.

• Vendor contracts shift risk back to you

  At the same time, AI vendor agreements commonly cap liability and require customer indemnification — moving financial responsibility for the AI’s behavior toward the customer who deployed it.

The result: companies are increasingly responsible for AI behavior they often cannot fully see or audit. The defensible position is not a stronger disclaimer — it is demonstrable governance.

Section 3

The question every review comes back to

Whether the forum is a regulator’s inquiry, an auditor’s checklist, a customer’s security review, or litigation, the inquiry tends to reduce to one question:

“Can you prove you governed your AI access?”

Answering it well is not a matter of intent or policy documents alone. It is a matter of evidence — a system of record that shows what you knew, what you controlled, and how you responded.

Section 4

How 8200.dev establishes your evidence

8200.dev is the proof layer. It does not provide legal protection or guarantee any compliance outcome; it provides the visibility, governance, and audit-ready evidence that support your duty of care — connecting read-only to Google Workspace and the other sources you add.

• Agent Guard

  A complete, continuously-updated inventory of every AI agent and service account that can reach your data — because you cannot govern what you cannot see.

• AI Agent Registry

  The proof of inventory auditors require: register every agent on a platform no connector reaches — WhatsApp, Telegram, custom and voice bots — classify its data access, and export audit-ready evidence per agent. Discovered plus registered is a complete inventory.

• OAuth app audit

  Discovery of the shadow AI already connected to your Workspace, so an unsanctioned tool is found before it becomes a liability.

• AI-built app detection

  Identification of the OAuth apps built with AI app builders (Lovable, Base44, Bolt.new and similar), exactly what data each can reach, and the evidence that you governed an application you deployed but did not write line by line.

• Prevention rules & enforcement

  Active, documented control over risky access — demonstrating governance, not merely monitoring.

• Audit log & SIEM export

  An immutable, exportable record of access decisions — the audit-ready evidence a reviewer or court expects to see.

• Compliance evidence collection

  One-click generation of the documentation that auditors request, mapped to the controls behind SOC 2, ISO 27001, GDPR, and the NIST AI Risk Management Framework.

• Risk timeline & incidents

  A documented history that you detected an AI-related risk and responded to it — evidence of diligence, not just intent.

Section 5

The cost of standing still

The trend is measurable, and it is moving quickly. These figures are presented as context, not as a forecast for any individual organization.