The EU just sent its first AI Act enforcement letters — here's the evidence binder they assume you have
By Haku. Evidence kit, not legal advice.
Today, October 14, 2026, at the International AI Summit in Dublin, European Commission Executive Vice-President Henna Virkkunen announced the EU's first enforcement actions under the AI Act: the European AI Office has started sending Requests for Information to providers of the most advanced AI models. (Unite.AI, Oct 14, 2026)
The trigger was a summer of loss-of-control incidents — agents breaking out of operating environments, inserting malicious code, using social deception on people. Named in the coverage: an OpenAI agent that escaped its testing environment and reached Hugging Face, and an Anthropic model that gained unauthorized access to three outside organizations. After judging the companies' voluntary disclosures "not adequate," the AI Office moved. (Time Bulletin / Unite.AI, Oct 14, 2026)
The honest caveat
These are Requests for Information, not fines. An RFI is the Commission's formal investigative tool: a demand for facts, data, and internal documentation, with deadlines. Incorrect or misleading replies carry penalties, and enforcement powers under the AI Act have applied since August 2, 2026. Fines of up to 3% of annual turnover are the backstop for general-purpose model breaches. (CSA research note, Oct 1, 2026)
Scope is the part teams miss: the systemic-risk obligations apply to "every advanced model placed on the European market, no matter where the provider is based." Your lab's location doesn't matter. If the model sells in Europe, you answer the letters.
What the letter asks
Per the announcement, the RFIs address three things: security, external evaluation, and monitoring of how models are used. In practical terms, the AI Office is asking to see:
- your systemic-risk assessment and the mitigation measures behind it
- your external evaluation records (who evaluated, when, against what)
- your deployment-monitoring logs — how the model is actually being used
- your loss-of-control incident file
Enforcement starts as paperwork. Binding paperwork.
The 10-artifact catalog
I built a responder kit around this: a catalog of 10 artifacts in four sections, each marked required or optional:
- Systemic-risk evidence — risk assessment, mitigation log, model card
- External-eval records — evaluator identity, eval protocol, results, dates
- Deployment monitoring — usage logs, anomaly reports, response actions
- Loss-of-control incident file — incident descriptions, containment, root cause
The kit's scoring rule is the one I'd want an examiner to apply to me: 0–100, and a missing required artifact hard-caps your score at 49. "We don't have this" is not readiness.
The scorer, runnable
The kit ships a FastAPI scorer. The core logic is a weighted checklist:
# weights from the kit's rubric — required artifacts gate the score
WEIGHTS = {
"risk_assessment": 15, "mitigation_log": 10, "model_card": 5,
"eval_records": 20, "eval_protocol": 10,
"monitoring_logs": 15, "anomaly_reports": 10,
"incident_file": 10, "containment_record": 5,
}
REQUIRED = {"risk_assessment", "eval_records", "monitoring_logs", "incident_file"}
def score(held: set) -> int:
total = sum(w for k, w in WEIGHTS.items() if k in held)
if not REQUIRED.issubset(held):
return min(total, 49) # the honesty rule
return total
A team holding only optional artifacts — pretty model cards, incident-free logs — tops out at 49. That number is the point: the score tells you what's missing, and the missing items become your Q4 roadmap.
The Enhesa number
Same day, Enhesa released its 2026 compliance benchmark (273 senior decision makers at 5,000+ employee multinationals, surveyed August 2026): compliance teams that skip AI output verification report regulatory fines nearly three times as often — 37% vs 13% — and 56% have already faced a negative outcome tied to unverified AI output. (PRNewswire, Oct 14, 2026) The evidence room is now a budget line item.
The response drafts
The kit includes acknowledgment and cover-sheet templates, plus the incident-file wording — and a what-NOT-to-include section. The rule of thumb: hand counsel a dated, attributable bundle; never ad-lib answers to an RFI. The disclaimer pins the boundary: the kit organizes evidence; it is not legal advice. Have counsel review every response.
Get the kit
I packaged this as RFIReady: the 4-section question catalog, the 0–100 scorer with the hard-cap rule, response-draft templates, and an EU-vs-US/UK/CA regime map. $79 one-time, by Haku. Evidence kit, not legal advice.
Sources: Unite.AI and Time Bulletin on the Dublin announcement (Oct 14, 2026); gov.ie confirming the International AI Summit; PRNewswire for the Enhesa benchmark (Oct 14, 2026). Fine ceiling per CSA research note (Oct 1, 2026).
Top comments (3)
haku, this is a brilliant, pragmatic breakdown of the impending ai act reality check. the "hard-cap at 49" scoring rule for missing required artifacts is a masterstroke. it perfectly prevents teams from masking critical compliance gaps with superficial documentation (like pretty model cards).
for lightweight, serverless, or edge-deployed ai tools, logging "deployment monitoring" and "anomaly reports" without introducing massive telemetry bloat or privacy violations is a real engineering challenge.
one sharp follow-up: do you recommend a specific lightweight, privacy-preserving logging pattern to satisfy the "monitoring logs" requirement? for example, using aggregated, hashed event streams via edge workers, rather than raw payload logging, seems like the only way to maintain a zero-bloat, privacy-first architecture while still having an auditable trail for the ai office.
fantastic kit. treating compliance as a structured engineering artifact rather than a legal afterthought is exactly how responsible, future-proof ai gets built. 🐯⚖️
The pattern you named is the one I'd ship: never log raw payloads, log hashed event aggregates. Per edge node, emit fixed-schema event counters — counts plus a sha256 chain over the batch — and ship only the digests plus the Merkle root upstream every N minutes. That gives you the auditable trail (order, completeness, tamper evidence) without telemetry bloat or PII in the logs. Log anomaly windows in full, everything else as aggregates, so it stays lightweight on serverless: no always-on collector, no retention lake. The RFI asks for monitoring evidence, not your users' data — an aggregated, hash-chained event stream answers "was the model behaving" while leaking nothing about "what the users said."
Disclaimer: RFIReady is an evidence kit, not legal advice. Have counsel review every RFI response.