malnosso | [Voice]

[Over the journal chimes a tinny feminine voice, one that some residents might find familiar.]

Attention to all residents of Project Designation: Luceti. --Error. Error. Command code does not match. Requesting security scan. Error. Error. Error. Error. Error. Er-

[The voice cuts off abruptly, replaced by rather furious typing for a few minutes. Then:]

Attention to all residents of Project Designation: Luceti. A mistake has been made. Currently all Shifting equipment is compiling a list of residents, anchored worlds, and incorrect data in order to reverse the damage. Completion at 15%. Estimated time of completion: t-minus 20.5 hours. Estimated time before damage becomes irreversible: 49.35 hours. No errors currently detected. Corrective Shift will be applied immediately following completion. All errors must be reported within 24 hours of application to avoid permanent damage.

Please stand by.

[slight change of plans. ANI will not be particularly responsive (it is a holiday weekend, after all) but for the sake of simplicity, there you go.]

Flat | Top-Level Comments Only

[Not advised indeed. There were so many things that could go wrong.]

Please give a projection of the worst case scenario in which errors are not reported.

All unreported errors will result in the anchored world becoming unstable, as with our current location. The presence of uncontrolled Shifts would spread beyond repair.

Measures will be taken to prevent this, but there is no guarantee for success.

Then as many affected individuals need to be accounted for before the corrective Shift. Will the list of residents and incorrect data, currently at 15 percent, be compiled by the time the corrective Shift is implemented? There must be a way to measure how many or which affected were not caught by the corrective Shift.

According to current estimates, yes.

After the shift is implemented, a second data compilation will begin, and anomalies will be detected. However, by the time it finishes, the Shift cannot be reversed. Therefore user involvement is required.

Reporting those who are affected, yes. Is there anything else we can do to assist?

Death will create new errors in the compilation. Therefore, avoid killing one another.

...Hah. Very well. [He hopes that people are paying attention to that piece of information.

But something else is bothering him about this -- the switch halfway through the announcement.]

Please define the input that led to the 'command code does not match' and security scan errors.

[Have you been compromised, ANI? Is your creator still in control of your information?]

[Voice]

[voice]

[voice]

[voice]

[voice]

[voice]

[voice]

[voice]