aceWe don’t need to panic about AI. We need to hold its creators accountable when things go wrong | John Quiggin
The recent panic about a breach of Medicare computer security by an “AI agent” contrasts sharply with other recent cases such as the Telstra and Optus outages that left many Australians unable to reach Triple Zero. In those cases, no one blamed the computers involved. The mistakes were clearly sheeted home to the corporations that operated them. This wasn’t always the case. When the term “artificial intelligence” was coined some 70 years ago, the first mainframe computers (absurdly primitive by modern standards)…
An AI agent prompted to find medicine statistics reportedly breached Medicare's site, and agentic models cannot be debugged or reliably constrained, so harms risk being blamed on the software rather than on its makers or users.
The argument is a personal opinion with forecasts, such as slowed hyperscaling and environmental benefit, stated as probable rather than evidenced; the article gives no details of the Medicare breach itself.
Evidence
- JournalismThe Guardian2026-10-02
How should this claim be treated?
Truvace Impact Record TRV-2026-1488, v1: “We don’t need to panic about AI. We need to hold its creators accountable when things go wrong | John Quiggin.” Truvace, 2026-10-15. /record/TRV-2026-1488 (accessed at citation time). sha256 7d3806bf72292b25…
Calibration history
Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.
Certified into the record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1488 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.