compliance · eu ai act

EU AI Act ready

Built as if we fall under the strictest Act category — even when we don't.

section b

Context

The EU AI Act applies from 2 August 2026 (high-risk systems: 2 August 2027). A Murmur platform such as UrbanStakes falls under General Purpose AI and potentially touches a high-risk application when deployed for decision-making about individuals.

section c

Our positioning

Murmur platforms are not autonomous decision systems. They signal, interpret and propose — humans always decide. In most use cases this keeps us outside the strictest high-risk category. But we build as if we fall under it.

Why? Because our clients are public organisations. If they decide to use a signal for a decision about a person, the classification may shift. You don't want to start building only then.

section d

Implementation per Act obligation

Article Our implementation
Art. 9Risk management — Per use case risk analysis; template available.
Art. 10Data governance — L0–L3 classification (see Security Model Selection); provenance per source recorded.
Art. 11Technical documentation — Per deployment: model card, system card, known limitations.
Art. 12Record-keeping — Audit log of every AI call; stored immutably.
Art. 13Transparency — Source attribution on every generated piece; "AI-generated" label visible.
Art. 14Human oversight — Human approval required for every outgoing action.
Art. 15Accuracy + robustness — Output validation, confidence gates, fallback models.

section e

On doubt: the client chooses stricter

Working with a client who classifies a deployment as high-risk? We then activate the heavier set:

  • Conformity assessment (art. 43)
  • CE marking procedure
  • Registration in EU database
  • Fundamental Rights Impact Assessment (FRIA) support

These extras are not delivered by default — they are activated when your legal department considers them necessary.

section f

What we don't claim

  • We are not a registered auditor of AI Act conformity
  • We are not a legal advisor for your use-case-specific classification
  • "Ready" means: we have the building blocks; the application remains your responsibility

section g

Request the security dossier

Our full Act positioning, elaborated per deployment, is shared in the security dossier.

Request security dossier