Anthropic wired Claude to a laser last week. The compliance question that opens is not the one everyone is asking.
On 27 August, Anthropic previewed the Model Hardware Standard — a driver spec that lets an agent operate physical instruments: microscopes, liquid handlers, robotic arms, lasers. Read and write primitives, device discovery, safety limits declared in the driver and enforced at the device.
The numbers are Anthropic's own. At QuEra Computing, recovering an optical lock started at 58% and about 150 seconds. It ended at 99.3% across 700 trials — 695 recoveries. Over a 19-hour run, Claude's PID controllers never lost the lock; the expert-tuned ones dropped it about 1.6 times an hour.
Three things before you file this under "MCP for robots".
1. It makes the agent a safety component. AI Act Article 6(1): high-risk where the system "is intended to be used as a safety component of a product" covered by Annex I, and that product needs third-party conformity assessment. An agent enforcing a device's safety limits is that, by description.
2. Then the Act steps back. The Digital Omnibus moved Regulation (EU) 2023/1230 — machinery — from Section A to Section B of Annex I. For Section B, Article 2(2) leaves only Article 6(1), Article 60a and Articles 102 to 112 applying. The high-risk requirements arrive inside the Machinery Regulation instead, by delegated act, by 2 August 2028.
3. Which means your calendar has the wrong date. AI Act Annex I high-risk: 2 August 2028. The Machinery Regulation itself: 20 January 2027. Eighteen months earlier — and its Annex I reaches "safety components with fully or partially self-evolving behaviour using machine learning approaches ensuring safety functions", which is a notified body, not a self-declaration.
Monday:
1. Classify the device before you wire an agent to it. A robotic arm is machinery, Section B. An IVD analyser is Regulation 2017/746, Section A, and the whole high-risk chapter comes with it. 2. Log who set each safety limit and what actually enforced it — driver, firmware or model. 3. Ask your hardware vendor in writing which conformity route it plans for January 2027. 4. Keep the natural-language capability file the driver generates. It is your intended-purpose document whether you meant it or not.
The standard made the wiring cheap. It did not move the responsibility.
Which of your devices decides your regime?
#EUAIAct #AgenticAI #MachineryRegulation #AICompliance #Robotics