Hacker News Reader

>It's not even clear if AI was used to find the bug

It's not even clear you read the article

Where do you think my confusion came from? All it says is that ai assists in resolving the gyroscope lock path, not why they decided to model the gyroscope lock path to begin with.

Please, keep your offensive comments to yourself when a clarifying comment might have sufficed.

Even worse, the other child comments are speculating (and didn't RTFA either) when the answer is clear in the article.

> We found this defect by distilling a behavioural specification of the IMU subsystem using Allium, an AI-native behavioural specification language.

> distilling

A.k.a. as fabricating. No wonder they chose to use "AI".

That's the opposite of clear to me.

Has the article been updated?

2nd paragraph starts with: "We used Claude and Allium"

And later on: "With that obligation written down, Claude traced every path that runs after gyros_busy is set to true"

This is the original article text. It just looks like users skimmed and then flamed the author.

Reply on news.ycombinator.com