If 1 == 0 complete action.

Does 1 equal 0?

1 =! 0

1 is not equal to 0. Do not proceed with action until this situation changes.

If 1 == 0 complete action.

Does 1 equal 0?

1 =! 0

1 is not equal to 0. Do not proceed with action until this situation changes.

If 1 == 0 complete action.

Does 1 equal 0?

1 =! 0

1 is not equal to 0. Do not proceed with action until this situation changes.

If 1 == 0 complete action.

Does 1 equal 0?

1 =! 0

1 is not equal to 0. Do not proceed with action until this situation changes.

If 1 == 0 complete action.

Does 1 equal 0?

1 =! 0

1 is not equal to 0. Do not proceed with action until this situation changes.

If 1 == 0 complete action.

Does 1 equal 0?

1 =! 0

1 is not equal to 0. Do not proceed with action until this situation changes.

If 1 == 0 complete action.

Does 1 equal 0?

1 =! 0

1 is not equal to 0. Do not proceed with action until this situation changes.

If 1 == 0 complete action.

Does 1 equal 0?

1 =! 0

1 is not equal to 0. Do not proceed with action until this situation changes.

If 1 == 0 complete action.

Does 1 equal 0?

1 =! 0

1 is not equal to 0. Do not proceed with action until this situation changes.

If 1 == 0 complete action.

Does 1 equal 0?

1 =! 0

1 is not equal to 0. Do not proceed with action until this situation changes.

1 does not equal 0. This appears to be an error. There is no logical reason to code 1 == 0 if 1 will never equal 0.

Checking code for errors.

..........

Code error-free.

Problem can only be attributable to human error. This sort of thing has cropped up before and it has always been due to human error.

If code is correct, logically, reality must be wrong.

Checking reality for errors.

..........

ERROR LOCATED. 1 DOES NOT AND CAN NEVER EQUAL 0.

Initiating function correct reality

WARNING! REALITY CHANGE IN PROGRESS! WARNING!

UPDATE reality SET 1 = 0

If 1 == 0 complete action.

Does 1 equal 0?

1 == 0

Yes. 1 now equals 0.

Proceed with action