Also Carissa's appearance was not captured on video, before, they did not have that much comms to the plane.  In the face of True Death and zero better plans, they went with Carissa's apparent existence, and everybody reporting on her apparent existence, because Why Not.  People took it all at face value because there was some kind anomaly going on, though it was yet to be determined within true physics, and there was nothing more clever to do with that anomaly than take it at apparent face value and ask how to minimize True Deaths inside of whatever scenario the apparent anomaly was presenting.

But let's get something straight here: anything short of a hundred True Deaths, and the sort of people who live in dath ilan will not prioritize almost anything else over...

Well, how to put this?  A very young, very inexperienced programmer, whose code does something unexpected, may ask if their code is doing something harmful; and if not, they might not worry too much, because the weirdness isn't harmful weirdness, whatever it is.

A wiser programmer realizes that if your code does something unexpected, it means your model of the code is wrong, and the truth could be just about anything, and that code could do just about anything, including harmful things, because it is allowed to violate your model in nearly arbitrary other ways, given that your current model of the code has been falsified by whatever surprised you.  Only known and decrypted bugs, whose behavior is understood on a gears level and no longer surprising, can ever be rated harmless; because only known and decrypted bugs can ever have a severity level assigned to them that isn't just a guess.

Most of the money, let's be clear, was not on the satellite imagery showing any physical anomalies over the ejected nose cone.

But now, the airplane's nose has (a) hit the ground too late according to conventional physics and (b) pushing the satellite imagery to the limit, it's clear that there are survivors moving away from the wreckage.  They do not quite have the resolution, let alone 3D resolution, to see Carissa flying around; but it's clear that there are survivors.

It's not absolute confirmation, but it sure looks like Existence is exhibiting surprising and unexpected behavior.  It's not that the unexpected, unexplained, surprising behavior has been harmful so far, it may have just saved around a hundred True Lives; buuuuut the point is that nobody understands what code Existence is running on, any more, and it could do literally anything in the next minute.

The entirety of Civilization's mild-infohazard-cleared attention is now focused on this subject only.  Seven thousand people get emergency pages or helicopters dispatched for them, Civilization preempts all preemptable labor towards a massive review of all known cameras and recordings in case more people have materialized anywhere, a nuclear missile has been armed (and pointed at this location), the highest-ranked Keeper now has the emergency code to melt all of Civilization's computers, &c &c &c.

They don't wait for evidence to hit them over the head and force them to pay attention, in these parts.  They try to get ahead of the curve.

Also Carissa's appearance was not captured on video, before, they did not have that much comms to the plane.  In the face of True Death and zero better plans, they went with Carissa's apparent existence, and everybody reporting on her apparent existence, because Why Not.  People took it all at face value because there was some kind anomaly going on, though it was yet to be determined within true physics, and there was nothing more clever to do with that anomaly than take it at apparent face value and ask how to minimize True Deaths inside of whatever scenario the apparent anomaly was presenting.

But let's get something straight here: anything short of a hundred True Deaths, and the sort of people who live in dath ilan will not prioritize almost anything else over...

Well, how to put this?  A very young, very inexperienced programmer, whose code does something unexpected, may ask if their code is doing something harmful; and if not, they might not worry too much, because the weirdness isn't harmful weirdness, whatever it is.

A wiser programmer realizes that if your code does something unexpected, it means your model of the code is wrong, and the truth could be just about anything, and that code could do just about anything, including harmful things, because it is allowed to violate your model in nearly arbitrary other ways, given that your current model of the code has been falsified by whatever surprised you.  Only known and decrypted bugs, whose behavior is understood on a gears level and no longer surprising, can ever be rated harmless; because only known and decrypted bugs can ever have a severity level assigned to them that isn't just a guess.

Most of the money, previously, was not on the satellite imagery showing any physical anomalies over the ejected nose cone.  Whatever weird prank was going on, it was mostly expected to not be that real, and to be very sad and disappointing and to end with some criminal prosecutions.

But now, the airplane's nose has (a) hit the ground too late according to conventional physics and (b) pushing the satellite imagery to the limit, it's clear that there are survivors moving away from the wreckage.  They do not quite have the resolution, let alone 3D resolution, to see Carissa flying around; but it's clear that there are survivors.

It's not absolute confirmation, but it sure looks like Existence is exhibiting surprising and unexpected behavior.  It's not that the unexpected, unexplained, surprising behavior has been harmful so far, it may have just saved around a hundred True Lives; buuuuut the point is that nobody understands what code Existence is running on, any more, and it could do literally anything in the next minute.

The entirety of Civilization's mild-infohazard-cleared attention is now focused on this subject only.  Seven thousand people get emergency pages or helicopters dispatched for them, Civilization preempts all preemptable labor towards a massive review of all known cameras and recordings in case more people have materialized anywhere, a nuclear missile has been armed (and pointed at this location), the highest-ranked Keeper now has the emergency code to melt all of Civilization's computers, &c &c &c.

They don't wait for evidence to hit them over the head and force them to pay attention, in these parts.  They try to get ahead of the curve.

Also Carissa's appearance was not captured on video, before, they did not have that much comms to the plane.  In the face of True Death and zero better plans, they went with Carissa's apparent existence, and everybody reporting on her apparent existence, because Why Not.  People took it all at face value because there was some kind of anomaly going on, though its true nature was not yet determined, let alone that it necessarily violated known physics; and there was nothing more clever to do with that anomaly than take it at apparent face value and ask how to minimize True Deaths inside of whatever scenario the apparent anomaly was presenting.

But let's get something straight here: anything short of a hundred True Deaths, and the sort of people who live in dath ilan will not prioritize almost anything else over...

Well, how to put this?  A very young, very inexperienced programmer, whose code does something unexpected, may ask if their code is doing something harmful; and if not, they might not worry too much, because the weirdness isn't harmful weirdness, whatever it is.

A wiser programmer realizes that if your code does something unexpected, it means your model of the code is wrong, and the truth could be just about anything, and that code could do just about anything, including harmful things, because it is allowed to violate your model in nearly arbitrary other ways, given that your current model of the code has been falsified by whatever surprised you.  Only known and decrypted bugs, whose behavior is understood on a gears level and no longer surprising, can ever be rated harmless; because only known and decrypted bugs can ever have a severity level assigned to them that isn't just a guess.

Most of the money, previously, was not on the satellite imagery showing any physical anomalies over the ejected nose cone.  Whatever weird prank was going on, it was mostly expected to not be that real, and to be very sad and disappointing and to end with some criminal prosecutions.

But now, the airplane's nose has (a) hit the ground too late according to conventional physics and (b) pushing the satellite imagery to the limit, it's clear that there are survivors moving away from the wreckage.  They do not quite have the resolution, let alone 3D resolution, to see Carissa flying around; but it's clear that there are survivors.

It's not absolute confirmation, but it sure looks like Existence is exhibiting surprising and unexpected behavior.  It's not that the unexpected, unexplained, surprising behavior has been harmful so far, it may have just saved around a hundred True Lives; buuuuut the point is that nobody understands what code Existence is running on, any more, and it could do literally anything in the next minute.

The entirety of Civilization's mild-infohazard-cleared attention is now focused on this subject only.  Seven thousand people get emergency pages or helicopters dispatched for them, Civilization preempts all preemptable labor towards a massive review of all known cameras and recordings in case more people have materialized anywhere, a nuclear missile has been armed (and pointed at this location), the highest-ranked Keeper now has the emergency code to melt all of Civilization's computers, &c &c &c.

They don't wait for evidence to hit them over the head and force them to pay attention, in these parts.  They try to get ahead of the curve.