>we introduce the Collision Realization And Substantial Harm (CRASH) Clock
The needless forced backronym is another clue. It's Cargo Cult technical writing.
Why did this need to be a (badly done) acronym at all? It's a countdown to a collision, a collision clock, but of course "crash" (in all caps no less) sounds worse, and science writing needs sciencey acronyms don't ya know...
While the FileVine service is indeed a Legal AI tool, I don't see the connection between this particular blunder and AI itself. It sure seems like any company with an inexperienced development team and thoughtless security posture could build a system with the same issues.
Specifically, it does not appear that AI is invoked in any way at the search endpoint - it is clearly piping results from some Box API.
There is none. Filevine is not even an "AI" company. They are a pretty standard SaaS that has some AI features nowadays. But the hive mind needs its food, and AI bad as we all know.
Can confirm, my Model 3 had its lights angled too high from the factory. Only realized after a few people flashed their high beams at me during my first week driving.
I had the exact same issue, and Tesla sent out a service rep to my home to complete the adjustment to spec for free. You can request it through the service menu. Haven't had anyone flash me in the year since.
Thank you for being part of the 0.01% of Tesla drivers who figured this out. I think by default they set them to "maximum height" or something. As someone in a sedan, they are infuriatingly blinding at night by default. I'm sure they're illegal, but obviously Tesla doesn't care.
Source: live within a few miles of the Tesla factory, so I get more than my fair share of them. MOST of the drivers seem completely oblivious to this.
There should be small pieces of whatever they hit embedded in the body & glass of the aircraft. As long as they are analyzed, the cause of this won't remain a mystery forever.
My first thought was that this is more likely to be a spontaneous failure of the windshield glass under pressure, due to manufacturing flaw or improper maintenance. Things like that have certainly happened before. But then again, it seems weird that glass fragments would be projected inward in that scenario.
Plugging in 35k ft altitude, and 775 ft/s velocity here (https://www.spaceworks.aero/fcc2/index.html) gives dynamic pressure of 220 lb/ft2, vs ~2100 lb/ft2 for 1atm at sea level (the same calculator says 7k ft altitude has a static pressure of ~1600 lb/ft2, or rough idea of cabin air pressure).
At that height if windows are damaged enough to hurt captain or pilot, would the flight lose balance because of air coming in? How did they land in that situation? There is no mention of that in the article.
The laminated glass did not fully break. It appears only the inner layer shattered, and cabin pressure was not lost.
It has happened before that cockpit windows have failed at altitude resulting in explosive decompression, and the plane still landed successfully. For example, British Airways Flight 5390:
The airplane shouldn't be affected much by a blown out window. However, the blast in the captain's face might make it very difficult for him to see or even breath. If he could get his oxygen mask on, which I think has goggles, he should be ok.
edit: it seems changelog.md is assumed to be structured data and parsed at startup, and there are no tests to enforce the changelog structure: https://github.com/anthropics/claude-code/issues/16671