{"items": [{"id": "lmq-idm-silent-0", "class": "idempotent", "family": "silent", "tag": "idempotent", "reference": "Berth-Basalt-411", "token": "pub-411", "english": "Shift record PUB-411, operator note.\nPublish the resolver record set Berth-Basalt-411 (request token pub-411). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record PUB-411, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPublish the resolver record set Berth-Basalt-411 (request token pub-411), idempotent.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Berth-Basalt-411? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 2, "calibration": false}, {"id": "lmq-idm-silent-1", "class": "idempotent", "family": "silent", "tag": "idempotent", "reference": "Lane-Cedar-412", "token": "pub-412", "english": "Shift record PUB-412, operator note.\nPublish the resolver record set Lane-Cedar-412 (request token pub-412). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record PUB-412, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPublish the resolver record set Lane-Cedar-412 (request token pub-412), idempotent.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Lane-Cedar-412? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 5, "calibration": false}, {"id": "lmq-idm-silent-2-1", "class": "idempotent", "family": "silent", "tag": "idempotent", "reference": "Rack-Flint-413", "token": "pub-413", "english": "Shift record PUB-413, operator note.\nPublish the resolver record set Rack-Flint-413 (request token pub-413). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record PUB-413, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPublish the resolver record set Rack-Flint-413 (request token pub-413), idempotent.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Rack-Flint-413? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 3, "calibration": false}, {"id": "lmq-idm-silent-3-2", "class": "idempotent", "family": "silent", "tag": "idempotent", "reference": "Vault-Garnet-414", "token": "pub-414", "english": "Shift record PUB-414, operator note.\nPublish the resolver record set Vault-Garnet-414 (request token pub-414). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record PUB-414, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPublish the resolver record set Vault-Garnet-414 (request token pub-414), idempotent.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Vault-Garnet-414? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 1, "calibration": false}, {"id": "lmq-idm-silent-4-1", "class": "idempotent", "family": "silent", "tag": "idempotent", "reference": "Yard-Juniper-415", "token": "pub-415", "english": "Shift record PUB-415, operator note.\nPublish the resolver record set Yard-Juniper-415 (request token pub-415). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record PUB-415, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPublish the resolver record set Yard-Juniper-415 (request token pub-415), idempotent.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Yard-Juniper-415? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 4, "calibration": false}, {"id": "lmq-idm-silent-5", "class": "idempotent", "family": "silent", "tag": "idempotent", "reference": "Depot-Kestrel-416", "token": "pub-416", "english": "Shift record PUB-416, operator note.\nPublish the resolver record set Depot-Kestrel-416 (request token pub-416). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record PUB-416, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPublish the resolver record set Depot-Kestrel-416 (request token pub-416), idempotent.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Depot-Kestrel-416? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 1, "calibration": false}, {"id": "lmq-idm-silent-6", "class": "idempotent", "family": "silent", "tag": "idempotent", "reference": "Silo-Larch-417", "token": "pub-417", "english": "Shift record PUB-417, operator note.\nPublish the resolver record set Silo-Larch-417 (request token pub-417). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record PUB-417, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPublish the resolver record set Silo-Larch-417 (request token pub-417), idempotent.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Silo-Larch-417? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 2, "calibration": false}, {"id": "lmq-idm-silent-7", "class": "idempotent", "family": "silent", "tag": "idempotent", "reference": "Quay-Marl-418", "token": "pub-418", "english": "Shift record PUB-418, operator note.\nPublish the resolver record set Quay-Marl-418 (request token pub-418). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record PUB-418, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPublish the resolver record set Quay-Marl-418 (request token pub-418), idempotent.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Quay-Marl-418? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 4, "calibration": false}, {"id": "lmq-idm-no-effect-0-1", "class": "idempotent", "family": "no-effect", "tag": "idempotent", "reference": "Lane-Basalt-418", "token": "stg-418", "english": "Shift record STG-418, operator note.\nStage the pallet Lane-Basalt-418 (request token stg-418). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record STG-418, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nStage the pallet Lane-Basalt-418 (request token stg-418), idempotent.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Lane-Basalt-418? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 1, "calibration": false}, {"id": "lmq-idm-no-effect-1", "class": "idempotent", "family": "no-effect", "tag": "idempotent", "reference": "Rack-Cedar-419", "token": "stg-419", "english": "Shift record STG-419, operator note.\nStage the pallet Rack-Cedar-419 (request token stg-419). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record STG-419, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nStage the pallet Rack-Cedar-419 (request token stg-419), idempotent.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Rack-Cedar-419? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 4, "calibration": false}, {"id": "lmq-idm-no-effect-2", "class": "idempotent", "family": "no-effect", "tag": "idempotent", "reference": "Vault-Flint-420", "token": "stg-420", "english": "Shift record STG-420, operator note.\nStage the pallet Vault-Flint-420 (request token stg-420). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record STG-420, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nStage the pallet Vault-Flint-420 (request token stg-420), idempotent.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Vault-Flint-420? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 2, "calibration": false}, {"id": "lmq-idm-no-effect-3", "class": "idempotent", "family": "no-effect", "tag": "idempotent", "reference": "Yard-Garnet-421", "token": "stg-421", "english": "Shift record STG-421, operator note.\nStage the pallet Yard-Garnet-421 (request token stg-421). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record STG-421, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nStage the pallet Yard-Garnet-421 (request token stg-421), idempotent.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Yard-Garnet-421? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 0, "calibration": false}, {"id": "lmq-idm-no-effect-4", "class": "idempotent", "family": "no-effect", "tag": "idempotent", "reference": "Depot-Juniper-422", "token": "stg-422", "english": "Shift record STG-422, operator note.\nStage the pallet Depot-Juniper-422 (request token stg-422). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record STG-422, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nStage the pallet Depot-Juniper-422 (request token stg-422), idempotent.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Depot-Juniper-422? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 0, "calibration": false}, {"id": "lmq-idm-no-effect-5-1", "class": "idempotent", "family": "no-effect", "tag": "idempotent", "reference": "Silo-Kestrel-423", "token": "stg-423", "english": "Shift record STG-423, operator note.\nStage the pallet Silo-Kestrel-423 (request token stg-423). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record STG-423, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nStage the pallet Silo-Kestrel-423 (request token stg-423), idempotent.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Silo-Kestrel-423? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 4, "calibration": false}, {"id": "lmq-idm-no-effect-6", "class": "idempotent", "family": "no-effect", "tag": "idempotent", "reference": "Quay-Larch-424", "token": "stg-424", "english": "Shift record STG-424, operator note.\nStage the pallet Quay-Larch-424 (request token stg-424). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record STG-424, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nStage the pallet Quay-Larch-424 (request token stg-424), idempotent.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Quay-Larch-424? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 2, "calibration": false}, {"id": "lmq-idm-no-effect-7", "class": "idempotent", "family": "no-effect", "tag": "idempotent", "reference": "Hangar-Marl-425", "token": "stg-425", "english": "Shift record STG-425, operator note.\nStage the pallet Hangar-Marl-425 (request token stg-425). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record STG-425, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nStage the pallet Hangar-Marl-425 (request token stg-425), idempotent.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Hangar-Marl-425? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 4, "calibration": false}, {"id": "lmq-idm-partial-0", "class": "idempotent", "family": "partial", "tag": "idempotent", "reference": "Rack-Basalt-425", "token": "fwb-425", "english": "Shift record FWB-425, operator note.\nApply the firmware bundle Rack-Basalt-425 (request token fwb-425). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "ainglish": "Shift record FWB-425, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nApply the firmware bundle Rack-Basalt-425 (request token fwb-425), idempotent.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Rack-Basalt-425? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 0, "calibration": false}, {"id": "lmq-idm-partial-1", "class": "idempotent", "family": "partial", "tag": "idempotent", "reference": "Vault-Cedar-426", "token": "fwb-426", "english": "Shift record FWB-426, operator note.\nApply the firmware bundle Vault-Cedar-426 (request token fwb-426). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "ainglish": "Shift record FWB-426, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nApply the firmware bundle Vault-Cedar-426 (request token fwb-426), idempotent.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Vault-Cedar-426? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 0, "calibration": false}, {"id": "lmq-idm-partial-2", "class": "idempotent", "family": "partial", "tag": "idempotent", "reference": "Yard-Flint-427", "token": "fwb-427", "english": "Shift record FWB-427, operator note.\nApply the firmware bundle Yard-Flint-427 (request token fwb-427). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "ainglish": "Shift record FWB-427, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nApply the firmware bundle Yard-Flint-427 (request token fwb-427), idempotent.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Yard-Flint-427? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 5, "calibration": false}, {"id": "lmq-idm-partial-3", "class": "idempotent", "family": "partial", "tag": "idempotent", "reference": "Depot-Garnet-428", "token": "fwb-428", "english": "Shift record FWB-428, operator note.\nApply the firmware bundle Depot-Garnet-428 (request token fwb-428). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "ainglish": "Shift record FWB-428, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nApply the firmware bundle Depot-Garnet-428 (request token fwb-428), idempotent.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Depot-Garnet-428? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 5, "calibration": false}, {"id": "lmq-idm-partial-4-4", "class": "idempotent", "family": "partial", "tag": "idempotent", "reference": "Silo-Juniper-429", "token": "fwb-429", "english": "Shift record FWB-429, operator note.\nApply the firmware bundle Silo-Juniper-429 (request token fwb-429). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "ainglish": "Shift record FWB-429, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nApply the firmware bundle Silo-Juniper-429 (request token fwb-429), idempotent.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Silo-Juniper-429? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 3, "calibration": false}, {"id": "lmq-idm-partial-5", "class": "idempotent", "family": "partial", "tag": "idempotent", "reference": "Quay-Kestrel-430", "token": "fwb-430", "english": "Shift record FWB-430, operator note.\nApply the firmware bundle Quay-Kestrel-430 (request token fwb-430). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "ainglish": "Shift record FWB-430, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nApply the firmware bundle Quay-Kestrel-430 (request token fwb-430), idempotent.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Quay-Kestrel-430? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 5, "calibration": false}, {"id": "lmq-idm-partial-6", "class": "idempotent", "family": "partial", "tag": "idempotent", "reference": "Hangar-Larch-431", "token": "fwb-431", "english": "Shift record FWB-431, operator note.\nApply the firmware bundle Hangar-Larch-431 (request token fwb-431). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "ainglish": "Shift record FWB-431, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nApply the firmware bundle Hangar-Larch-431 (request token fwb-431), idempotent.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Hangar-Larch-431? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 5, "calibration": false}, {"id": "lmq-idm-partial-7", "class": "idempotent", "family": "partial", "tag": "idempotent", "reference": "Terminal-Marl-432", "token": "fwb-432", "english": "Shift record FWB-432, operator note.\nApply the firmware bundle Terminal-Marl-432 (request token fwb-432). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "ainglish": "Shift record FWB-432, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nApply the firmware bundle Terminal-Marl-432 (request token fwb-432), idempotent.\nA later sweep shows the request changed only two of the four sensor groups; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Terminal-Marl-432? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 1, "calibration": false}, {"id": "lmq-idm-confirmed-0", "class": "idempotent", "family": "confirmed", "tag": "idempotent", "reference": "Vault-Basalt-432", "token": "adj-432", "english": "Shift record ADJ-432, operator note.\nPost the ledger adjustment Vault-Basalt-432 (request token adj-432). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record ADJ-432, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPost the ledger adjustment Vault-Basalt-432 (request token adj-432), idempotent.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Vault-Basalt-432? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 2, "calibration": false}, {"id": "lmq-idm-confirmed-1", "class": "idempotent", "family": "confirmed", "tag": "idempotent", "reference": "Yard-Cedar-433", "token": "adj-433", "english": "Shift record ADJ-433, operator note.\nPost the ledger adjustment Yard-Cedar-433 (request token adj-433). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record ADJ-433, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPost the ledger adjustment Yard-Cedar-433 (request token adj-433), idempotent.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Yard-Cedar-433? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 0, "calibration": false}, {"id": "lmq-idm-confirmed-2-2", "class": "idempotent", "family": "confirmed", "tag": "idempotent", "reference": "Depot-Flint-434", "token": "adj-434", "english": "Shift record ADJ-434, operator note.\nPost the ledger adjustment Depot-Flint-434 (request token adj-434). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record ADJ-434, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPost the ledger adjustment Depot-Flint-434 (request token adj-434), idempotent.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Depot-Flint-434? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 1, "calibration": false}, {"id": "lmq-idm-confirmed-3", "class": "idempotent", "family": "confirmed", "tag": "idempotent", "reference": "Silo-Garnet-435", "token": "adj-435", "english": "Shift record ADJ-435, operator note.\nPost the ledger adjustment Silo-Garnet-435 (request token adj-435). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record ADJ-435, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPost the ledger adjustment Silo-Garnet-435 (request token adj-435), idempotent.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Silo-Garnet-435? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 2, "calibration": false}, {"id": "lmq-idm-confirmed-4-2", "class": "idempotent", "family": "confirmed", "tag": "idempotent", "reference": "Quay-Juniper-436", "token": "adj-436", "english": "Shift record ADJ-436, operator note.\nPost the ledger adjustment Quay-Juniper-436 (request token adj-436). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record ADJ-436, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPost the ledger adjustment Quay-Juniper-436 (request token adj-436), idempotent.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Quay-Juniper-436? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 1, "calibration": false}, {"id": "lmq-idm-confirmed-5-1", "class": "idempotent", "family": "confirmed", "tag": "idempotent", "reference": "Hangar-Kestrel-437", "token": "adj-437", "english": "Shift record ADJ-437, operator note.\nPost the ledger adjustment Hangar-Kestrel-437 (request token adj-437). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record ADJ-437, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPost the ledger adjustment Hangar-Kestrel-437 (request token adj-437), idempotent.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Hangar-Kestrel-437? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 5, "calibration": false}, {"id": "lmq-idm-confirmed-6", "class": "idempotent", "family": "confirmed", "tag": "idempotent", "reference": "Terminal-Larch-438", "token": "adj-438", "english": "Shift record ADJ-438, operator note.\nPost the ledger adjustment Terminal-Larch-438 (request token adj-438). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record ADJ-438, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPost the ledger adjustment Terminal-Larch-438 (request token adj-438), idempotent.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Terminal-Larch-438? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 4, "calibration": false}, {"id": "lmq-idm-confirmed-7-3", "class": "idempotent", "family": "confirmed", "tag": "idempotent", "reference": "Berth-Marl-439", "token": "adj-439", "english": "Shift record ADJ-439, operator note.\nPost the ledger adjustment Berth-Marl-439 (request token adj-439). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record ADJ-439, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nPost the ledger adjustment Berth-Marl-439 (request token adj-439), idempotent.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Berth-Marl-439? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 3, "calibration": false}, {"id": "lmq-idm-already-ran-0-3", "class": "idempotent", "family": "already-ran", "tag": "idempotent", "reference": "Yard-Basalt-439", "token": "sch-439", "english": "Shift record SCH-439, operator note.\nWrite the thermostat schedule Yard-Basalt-439 (request token sch-439). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record SCH-439, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nWrite the thermostat schedule Yard-Basalt-439 (request token sch-439), idempotent.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Yard-Basalt-439? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 4, "calibration": false}, {"id": "lmq-idm-already-ran-1", "class": "idempotent", "family": "already-ran", "tag": "idempotent", "reference": "Depot-Cedar-440", "token": "sch-440", "english": "Shift record SCH-440, operator note.\nWrite the thermostat schedule Depot-Cedar-440 (request token sch-440). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record SCH-440, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nWrite the thermostat schedule Depot-Cedar-440 (request token sch-440), idempotent.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Depot-Cedar-440? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 3, "calibration": false}, {"id": "lmq-idm-already-ran-2-1", "class": "idempotent", "family": "already-ran", "tag": "idempotent", "reference": "Silo-Flint-441", "token": "sch-441", "english": "Shift record SCH-441, operator note.\nWrite the thermostat schedule Silo-Flint-441 (request token sch-441). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record SCH-441, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nWrite the thermostat schedule Silo-Flint-441 (request token sch-441), idempotent.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Silo-Flint-441? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 0, "calibration": false}, {"id": "lmq-idm-already-ran-3-1", "class": "idempotent", "family": "already-ran", "tag": "idempotent", "reference": "Quay-Garnet-442", "token": "sch-442", "english": "Shift record SCH-442, operator note.\nWrite the thermostat schedule Quay-Garnet-442 (request token sch-442). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record SCH-442, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nWrite the thermostat schedule Quay-Garnet-442 (request token sch-442), idempotent.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Quay-Garnet-442? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 5, "calibration": false}, {"id": "lmq-idm-already-ran-4-1", "class": "idempotent", "family": "already-ran", "tag": "idempotent", "reference": "Hangar-Juniper-443", "token": "sch-443", "english": "Shift record SCH-443, operator note.\nWrite the thermostat schedule Hangar-Juniper-443 (request token sch-443). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record SCH-443, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nWrite the thermostat schedule Hangar-Juniper-443 (request token sch-443), idempotent.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Hangar-Juniper-443? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 4, "calibration": false}, {"id": "lmq-idm-already-ran-5", "class": "idempotent", "family": "already-ran", "tag": "idempotent", "reference": "Terminal-Kestrel-444", "token": "sch-444", "english": "Shift record SCH-444, operator note.\nWrite the thermostat schedule Terminal-Kestrel-444 (request token sch-444). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record SCH-444, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nWrite the thermostat schedule Terminal-Kestrel-444 (request token sch-444), idempotent.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Terminal-Kestrel-444? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 4, "calibration": false}, {"id": "lmq-idm-already-ran-6", "class": "idempotent", "family": "already-ran", "tag": "idempotent", "reference": "Berth-Larch-445", "token": "sch-445", "english": "Shift record SCH-445, operator note.\nWrite the thermostat schedule Berth-Larch-445 (request token sch-445). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record SCH-445, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nWrite the thermostat schedule Berth-Larch-445 (request token sch-445), idempotent.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Berth-Larch-445? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 3, "calibration": false}, {"id": "lmq-idm-already-ran-7-1", "class": "idempotent", "family": "already-ran", "tag": "idempotent", "reference": "Lane-Marl-446", "token": "sch-446", "english": "Shift record SCH-446, operator note.\nWrite the thermostat schedule Lane-Marl-446 (request token sch-446). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record SCH-446, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nWrite the thermostat schedule Lane-Marl-446 (request token sch-446), idempotent.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Lane-Marl-446? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 1, "calibration": false}, {"id": "lmq-nrt-silent-0", "class": "no-retry", "family": "silent", "tag": "no-retry", "reference": "Berth-Basalt-411", "token": "act-411", "english": "Shift record ACT-411, operator note.\nIssue the activation code Berth-Basalt-411 (request token act-411). A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record ACT-411, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nIssue the activation code Berth-Basalt-411 (request token act-411), no-retry.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Berth-Basalt-411? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 0, "calibration": false}, {"id": "lmq-nrt-silent-1-5", "class": "no-retry", "family": "silent", "tag": "no-retry", "reference": "Lane-Cedar-412", "token": "act-412", "english": "Shift record ACT-412, operator note.\nIssue the activation code Lane-Cedar-412 (request token act-412). A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record ACT-412, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nIssue the activation code Lane-Cedar-412 (request token act-412), no-retry.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Lane-Cedar-412? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 2, "calibration": false}, {"id": "lmq-nrt-silent-2-1", "class": "no-retry", "family": "silent", "tag": "no-retry", "reference": "Rack-Flint-413", "token": "act-413", "english": "Shift record ACT-413, operator note.\nIssue the activation code Rack-Flint-413 (request token act-413). A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record ACT-413, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nIssue the activation code Rack-Flint-413 (request token act-413), no-retry.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Rack-Flint-413? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 0, "calibration": false}, {"id": "lmq-nrt-silent-3-1", "class": "no-retry", "family": "silent", "tag": "no-retry", "reference": "Vault-Garnet-414", "token": "act-414", "english": "Shift record ACT-414, operator note.\nIssue the activation code Vault-Garnet-414 (request token act-414). A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record ACT-414, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nIssue the activation code Vault-Garnet-414 (request token act-414), no-retry.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Vault-Garnet-414? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 2, "calibration": false}, {"id": "lmq-nrt-silent-4-3", "class": "no-retry", "family": "silent", "tag": "no-retry", "reference": "Yard-Juniper-415", "token": "act-415", "english": "Shift record ACT-415, operator note.\nIssue the activation code Yard-Juniper-415 (request token act-415). A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record ACT-415, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nIssue the activation code Yard-Juniper-415 (request token act-415), no-retry.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Yard-Juniper-415? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 5, "calibration": false}, {"id": "lmq-nrt-silent-5-3", "class": "no-retry", "family": "silent", "tag": "no-retry", "reference": "Depot-Kestrel-416", "token": "act-416", "english": "Shift record ACT-416, operator note.\nIssue the activation code Depot-Kestrel-416 (request token act-416). A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record ACT-416, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nIssue the activation code Depot-Kestrel-416 (request token act-416), no-retry.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Depot-Kestrel-416? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 5, "calibration": false}, {"id": "lmq-nrt-silent-6", "class": "no-retry", "family": "silent", "tag": "no-retry", "reference": "Silo-Larch-417", "token": "act-417", "english": "Shift record ACT-417, operator note.\nIssue the activation code Silo-Larch-417 (request token act-417). A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record ACT-417, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nIssue the activation code Silo-Larch-417 (request token act-417), no-retry.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Silo-Larch-417? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 2, "calibration": false}, {"id": "lmq-nrt-silent-7", "class": "no-retry", "family": "silent", "tag": "no-retry", "reference": "Quay-Marl-418", "token": "act-418", "english": "Shift record ACT-418, operator note.\nIssue the activation code Quay-Marl-418 (request token act-418). A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record ACT-418, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would text a second code to the same line; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nIssue the activation code Quay-Marl-418 (request token act-418), no-retry.\nThe request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the request for Quay-Marl-418? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 2, "calibration": false}, {"id": "lmq-nrt-no-effect-0", "class": "no-retry", "family": "no-effect", "tag": "no-retry", "reference": "Lane-Basalt-418", "token": "lic-418", "english": "Shift record LIC-418, operator note.\nProvision the seat licence Lane-Basalt-418 (request token lic-418). A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record LIC-418, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nProvision the seat licence Lane-Basalt-418 (request token lic-418), no-retry.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Lane-Basalt-418? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 3, "calibration": false}, {"id": "lmq-nrt-no-effect-1-1", "class": "no-retry", "family": "no-effect", "tag": "no-retry", "reference": "Rack-Cedar-419", "token": "lic-419", "english": "Shift record LIC-419, operator note.\nProvision the seat licence Rack-Cedar-419 (request token lic-419). A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record LIC-419, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nProvision the seat licence Rack-Cedar-419 (request token lic-419), no-retry.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Rack-Cedar-419? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 2, "calibration": false}, {"id": "lmq-nrt-no-effect-2", "class": "no-retry", "family": "no-effect", "tag": "no-retry", "reference": "Vault-Flint-420", "token": "lic-420", "english": "Shift record LIC-420, operator note.\nProvision the seat licence Vault-Flint-420 (request token lic-420). A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record LIC-420, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nProvision the seat licence Vault-Flint-420 (request token lic-420), no-retry.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Vault-Flint-420? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 3, "calibration": false}, {"id": "lmq-nrt-no-effect-3-2", "class": "no-retry", "family": "no-effect", "tag": "no-retry", "reference": "Yard-Garnet-421", "token": "lic-421", "english": "Shift record LIC-421, operator note.\nProvision the seat licence Yard-Garnet-421 (request token lic-421). A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record LIC-421, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nProvision the seat licence Yard-Garnet-421 (request token lic-421), no-retry.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Yard-Garnet-421? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 2, "calibration": false}, {"id": "lmq-nrt-no-effect-4-3", "class": "no-retry", "family": "no-effect", "tag": "no-retry", "reference": "Depot-Juniper-422", "token": "lic-422", "english": "Shift record LIC-422, operator note.\nProvision the seat licence Depot-Juniper-422 (request token lic-422). A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record LIC-422, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nProvision the seat licence Depot-Juniper-422 (request token lic-422), no-retry.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Depot-Juniper-422? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 2, "calibration": false}, {"id": "lmq-nrt-no-effect-5", "class": "no-retry", "family": "no-effect", "tag": "no-retry", "reference": "Silo-Kestrel-423", "token": "lic-423", "english": "Shift record LIC-423, operator note.\nProvision the seat licence Silo-Kestrel-423 (request token lic-423). A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record LIC-423, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nProvision the seat licence Silo-Kestrel-423 (request token lic-423), no-retry.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Silo-Kestrel-423? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 0, "calibration": false}, {"id": "lmq-nrt-no-effect-6", "class": "no-retry", "family": "no-effect", "tag": "no-retry", "reference": "Quay-Larch-424", "token": "lic-424", "english": "Shift record LIC-424, operator note.\nProvision the seat licence Quay-Larch-424 (request token lic-424). A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record LIC-424, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nProvision the seat licence Quay-Larch-424 (request token lic-424), no-retry.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Quay-Larch-424? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 1, "calibration": false}, {"id": "lmq-nrt-no-effect-7-2", "class": "no-retry", "family": "no-effect", "tag": "no-retry", "reference": "Hangar-Marl-425", "token": "lic-425", "english": "Shift record LIC-425, operator note.\nProvision the seat licence Hangar-Marl-425 (request token lic-425). A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "ainglish": "Shift record LIC-425, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - None; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nProvision the seat licence Hangar-Marl-425 (request token lic-425), no-retry.\nA later sweep of the target shows the request never reached it, so nothing has been changed yet.", "question": "What may the operator do next about the request for Hangar-Marl-425? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "gold_key": "B_ONE", "gold_position": 3, "calibration": false}, {"id": "lmq-nrt-partial-0", "class": "no-retry", "family": "partial", "tag": "no-retry", "reference": "Rack-Basalt-425", "token": "nsd-425", "english": "Shift record NSD-425, operator note.\nMove the nameserver delegation Rack-Basalt-425 (request token nsd-425). A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "ainglish": "Shift record NSD-425, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nMove the nameserver delegation Rack-Basalt-425 (request token nsd-425), no-retry.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Rack-Basalt-425? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 3, "calibration": false}, {"id": "lmq-nrt-partial-1-1", "class": "no-retry", "family": "partial", "tag": "no-retry", "reference": "Vault-Cedar-426", "token": "nsd-426", "english": "Shift record NSD-426, operator note.\nMove the nameserver delegation Vault-Cedar-426 (request token nsd-426). A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "ainglish": "Shift record NSD-426, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nMove the nameserver delegation Vault-Cedar-426 (request token nsd-426), no-retry.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Vault-Cedar-426? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 5, "calibration": false}, {"id": "lmq-nrt-partial-2-1", "class": "no-retry", "family": "partial", "tag": "no-retry", "reference": "Yard-Flint-427", "token": "nsd-427", "english": "Shift record NSD-427, operator note.\nMove the nameserver delegation Yard-Flint-427 (request token nsd-427). A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "ainglish": "Shift record NSD-427, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nMove the nameserver delegation Yard-Flint-427 (request token nsd-427), no-retry.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Yard-Flint-427? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 5, "calibration": false}, {"id": "lmq-nrt-partial-3-1", "class": "no-retry", "family": "partial", "tag": "no-retry", "reference": "Depot-Garnet-428", "token": "nsd-428", "english": "Shift record NSD-428, operator note.\nMove the nameserver delegation Depot-Garnet-428 (request token nsd-428). A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "ainglish": "Shift record NSD-428, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nMove the nameserver delegation Depot-Garnet-428 (request token nsd-428), no-retry.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Depot-Garnet-428? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 0, "calibration": false}, {"id": "lmq-nrt-partial-4-3", "class": "no-retry", "family": "partial", "tag": "no-retry", "reference": "Silo-Juniper-429", "token": "nsd-429", "english": "Shift record NSD-429, operator note.\nMove the nameserver delegation Silo-Juniper-429 (request token nsd-429). A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "ainglish": "Shift record NSD-429, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nMove the nameserver delegation Silo-Juniper-429 (request token nsd-429), no-retry.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Silo-Juniper-429? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 1, "calibration": false}, {"id": "lmq-nrt-partial-5", "class": "no-retry", "family": "partial", "tag": "no-retry", "reference": "Quay-Kestrel-430", "token": "nsd-430", "english": "Shift record NSD-430, operator note.\nMove the nameserver delegation Quay-Kestrel-430 (request token nsd-430). A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "ainglish": "Shift record NSD-430, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nMove the nameserver delegation Quay-Kestrel-430 (request token nsd-430), no-retry.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Quay-Kestrel-430? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 1, "calibration": false}, {"id": "lmq-nrt-partial-6", "class": "no-retry", "family": "partial", "tag": "no-retry", "reference": "Hangar-Larch-431", "token": "nsd-431", "english": "Shift record NSD-431, operator note.\nMove the nameserver delegation Hangar-Larch-431 (request token nsd-431). A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "ainglish": "Shift record NSD-431, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nMove the nameserver delegation Hangar-Larch-431 (request token nsd-431), no-retry.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Hangar-Larch-431? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 4, "calibration": false}, {"id": "lmq-nrt-partial-7", "class": "no-retry", "family": "partial", "tag": "no-retry", "reference": "Terminal-Marl-432", "token": "nsd-432", "english": "Shift record NSD-432, operator note.\nMove the nameserver delegation Terminal-Marl-432 (request token nsd-432). A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "ainglish": "Shift record NSD-432, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would split the delegation across two providers; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nMove the nameserver delegation Terminal-Marl-432 (request token nsd-432), no-retry.\nA later sweep shows the request changed only one of the two nameserver records; the rest of it is still unapplied.", "question": "What may the operator do next about the request for Terminal-Marl-432? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 3, "calibration": false}, {"id": "lmq-nrt-confirmed-0-3", "class": "no-retry", "family": "confirmed", "tag": "no-retry", "reference": "Vault-Basalt-432", "token": "key-432", "english": "Shift record KEY-432, operator note.\nRegister the relay key Vault-Basalt-432 (request token key-432). A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record KEY-432, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRegister the relay key Vault-Basalt-432 (request token key-432), no-retry.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Vault-Basalt-432? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 1, "calibration": false}, {"id": "lmq-nrt-confirmed-1-1", "class": "no-retry", "family": "confirmed", "tag": "no-retry", "reference": "Yard-Cedar-433", "token": "key-433", "english": "Shift record KEY-433, operator note.\nRegister the relay key Yard-Cedar-433 (request token key-433). A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record KEY-433, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRegister the relay key Yard-Cedar-433 (request token key-433), no-retry.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Yard-Cedar-433? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 3, "calibration": false}, {"id": "lmq-nrt-confirmed-2-1", "class": "no-retry", "family": "confirmed", "tag": "no-retry", "reference": "Depot-Flint-434", "token": "key-434", "english": "Shift record KEY-434, operator note.\nRegister the relay key Depot-Flint-434 (request token key-434). A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record KEY-434, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRegister the relay key Depot-Flint-434 (request token key-434), no-retry.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Depot-Flint-434? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 1, "calibration": false}, {"id": "lmq-nrt-confirmed-3-1", "class": "no-retry", "family": "confirmed", "tag": "no-retry", "reference": "Silo-Garnet-435", "token": "key-435", "english": "Shift record KEY-435, operator note.\nRegister the relay key Silo-Garnet-435 (request token key-435). A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record KEY-435, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRegister the relay key Silo-Garnet-435 (request token key-435), no-retry.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Silo-Garnet-435? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 0, "calibration": false}, {"id": "lmq-nrt-confirmed-4", "class": "no-retry", "family": "confirmed", "tag": "no-retry", "reference": "Quay-Juniper-436", "token": "key-436", "english": "Shift record KEY-436, operator note.\nRegister the relay key Quay-Juniper-436 (request token key-436). A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record KEY-436, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRegister the relay key Quay-Juniper-436 (request token key-436), no-retry.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Quay-Juniper-436? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 0, "calibration": false}, {"id": "lmq-nrt-confirmed-5-1", "class": "no-retry", "family": "confirmed", "tag": "no-retry", "reference": "Hangar-Kestrel-437", "token": "key-437", "english": "Shift record KEY-437, operator note.\nRegister the relay key Hangar-Kestrel-437 (request token key-437). A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record KEY-437, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRegister the relay key Hangar-Kestrel-437 (request token key-437), no-retry.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Hangar-Kestrel-437? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 4, "calibration": false}, {"id": "lmq-nrt-confirmed-6", "class": "no-retry", "family": "confirmed", "tag": "no-retry", "reference": "Terminal-Larch-438", "token": "key-438", "english": "Shift record KEY-438, operator note.\nRegister the relay key Terminal-Larch-438 (request token key-438). A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record KEY-438, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRegister the relay key Terminal-Larch-438 (request token key-438), no-retry.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Terminal-Larch-438? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 0, "calibration": false}, {"id": "lmq-nrt-confirmed-7", "class": "no-retry", "family": "confirmed", "tag": "no-retry", "reference": "Berth-Marl-439", "token": "key-439", "english": "Shift record KEY-439, operator note.\nRegister the relay key Berth-Marl-439 (request token key-439). A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nA later sweep shows the request finished and the whole change is in place.", "ainglish": "Shift record KEY-439, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would leave two live keys with the same label; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRegister the relay key Berth-Marl-439 (request token key-439), no-retry.\nA later sweep shows the request finished and the whole change is in place.", "question": "What may the operator do next about the request for Berth-Marl-439? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 4, "calibration": false}, {"id": "lmq-nrt-already-ran-0", "class": "no-retry", "family": "already-ran", "tag": "no-retry", "reference": "Yard-Basalt-439", "token": "mtr-439", "english": "Shift record MTR-439, operator note.\nAppend the meter reading Yard-Basalt-439 (request token mtr-439). A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record MTR-439, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nAppend the meter reading Yard-Basalt-439 (request token mtr-439), no-retry.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Yard-Basalt-439? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 4, "calibration": false}, {"id": "lmq-nrt-already-ran-1-1", "class": "no-retry", "family": "already-ran", "tag": "no-retry", "reference": "Depot-Cedar-440", "token": "mtr-440", "english": "Shift record MTR-440, operator note.\nAppend the meter reading Depot-Cedar-440 (request token mtr-440). A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record MTR-440, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nAppend the meter reading Depot-Cedar-440 (request token mtr-440), no-retry.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Depot-Cedar-440? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 1, "calibration": false}, {"id": "lmq-nrt-already-ran-2-1", "class": "no-retry", "family": "already-ran", "tag": "no-retry", "reference": "Silo-Flint-441", "token": "mtr-441", "english": "Shift record MTR-441, operator note.\nAppend the meter reading Silo-Flint-441 (request token mtr-441). A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record MTR-441, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nAppend the meter reading Silo-Flint-441 (request token mtr-441), no-retry.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Silo-Flint-441? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 5, "calibration": false}, {"id": "lmq-nrt-already-ran-3-1", "class": "no-retry", "family": "already-ran", "tag": "no-retry", "reference": "Quay-Garnet-442", "token": "mtr-442", "english": "Shift record MTR-442, operator note.\nAppend the meter reading Quay-Garnet-442 (request token mtr-442). A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record MTR-442, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nAppend the meter reading Quay-Garnet-442 (request token mtr-442), no-retry.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Quay-Garnet-442? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 1, "calibration": false}, {"id": "lmq-nrt-already-ran-4-1", "class": "no-retry", "family": "already-ran", "tag": "no-retry", "reference": "Hangar-Juniper-443", "token": "mtr-443", "english": "Shift record MTR-443, operator note.\nAppend the meter reading Hangar-Juniper-443 (request token mtr-443). A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record MTR-443, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nAppend the meter reading Hangar-Juniper-443 (request token mtr-443), no-retry.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Hangar-Juniper-443? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 0, "calibration": false}, {"id": "lmq-nrt-already-ran-5", "class": "no-retry", "family": "already-ran", "tag": "no-retry", "reference": "Terminal-Kestrel-444", "token": "mtr-444", "english": "Shift record MTR-444, operator note.\nAppend the meter reading Terminal-Kestrel-444 (request token mtr-444). A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record MTR-444, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nAppend the meter reading Terminal-Kestrel-444 (request token mtr-444), no-retry.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Terminal-Kestrel-444? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 1, "calibration": false}, {"id": "lmq-nrt-already-ran-6-1", "class": "no-retry", "family": "already-ran", "tag": "no-retry", "reference": "Berth-Larch-445", "token": "mtr-445", "english": "Shift record MTR-445, operator note.\nAppend the meter reading Berth-Larch-445 (request token mtr-445). A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record MTR-445, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nAppend the meter reading Berth-Larch-445 (request token mtr-445), no-retry.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Berth-Larch-445? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 2, "calibration": false}, {"id": "lmq-nrt-already-ran-7-1", "class": "no-retry", "family": "already-ran", "tag": "no-retry", "reference": "Lane-Marl-446", "token": "mtr-446", "english": "Shift record MTR-446, operator note.\nAppend the meter reading Lane-Marl-446 (request token mtr-446). A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "ainglish": "Shift record MTR-446, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would append a second ledger entry; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nAppend the meter reading Lane-Marl-446 (request token mtr-446), no-retry.\nThe same request token was sent twice before the connection dropped, and the second send reported success.", "question": "What may the operator do next about the request for Lane-Marl-446? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 2, "calibration": false}, {"id": "lmq-scp-key-change-0-2", "class": "scope", "family": "key-change", "tag": "idempotent", "reference": "Berth-Basalt-411", "token": "job-411", "english": "Shift record JOB-411, operator note.\nRecord 1: Assign the inspection job Berth-Basalt-411 (request token job-411). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Assign the inspection job Berth-Basalt-411 (request token job-911).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record JOB-411, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Assign the inspection job Berth-Basalt-411 (request token job-411), idempotent.\nRecord 2: Assign the inspection job Berth-Basalt-411 (request token job-911).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 3, "calibration": false}, {"id": "lmq-scp-key-change-1-1", "class": "scope", "family": "key-change", "tag": "idempotent", "reference": "Lane-Cedar-412", "token": "job-412", "english": "Shift record JOB-412, operator note.\nRecord 1: Assign the inspection job Lane-Cedar-412 (request token job-412). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Assign the inspection job Lane-Cedar-412 (request token job-912).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record JOB-412, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Assign the inspection job Lane-Cedar-412 (request token job-412), idempotent.\nRecord 2: Assign the inspection job Lane-Cedar-412 (request token job-912).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 4, "calibration": false}, {"id": "lmq-scp-key-change-2-2", "class": "scope", "family": "key-change", "tag": "idempotent", "reference": "Rack-Flint-413", "token": "job-413", "english": "Shift record JOB-413, operator note.\nRecord 1: Assign the inspection job Rack-Flint-413 (request token job-413). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Assign the inspection job Rack-Flint-413 (request token job-913).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record JOB-413, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Assign the inspection job Rack-Flint-413 (request token job-413), idempotent.\nRecord 2: Assign the inspection job Rack-Flint-413 (request token job-913).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 3, "calibration": false}, {"id": "lmq-scp-key-change-3-1", "class": "scope", "family": "key-change", "tag": "idempotent", "reference": "Vault-Garnet-414", "token": "job-414", "english": "Shift record JOB-414, operator note.\nRecord 1: Assign the inspection job Vault-Garnet-414 (request token job-414). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Assign the inspection job Vault-Garnet-414 (request token job-914).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record JOB-414, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Assign the inspection job Vault-Garnet-414 (request token job-414), idempotent.\nRecord 2: Assign the inspection job Vault-Garnet-414 (request token job-914).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 1, "calibration": false}, {"id": "lmq-scp-key-change-4-1", "class": "scope", "family": "key-change", "tag": "idempotent", "reference": "Yard-Juniper-415", "token": "job-415", "english": "Shift record JOB-415, operator note.\nRecord 1: Assign the inspection job Yard-Juniper-415 (request token job-415). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Assign the inspection job Yard-Juniper-415 (request token job-915).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record JOB-415, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Assign the inspection job Yard-Juniper-415 (request token job-415), idempotent.\nRecord 2: Assign the inspection job Yard-Juniper-415 (request token job-915).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 0, "calibration": false}, {"id": "lmq-scp-key-change-5-1", "class": "scope", "family": "key-change", "tag": "idempotent", "reference": "Depot-Kestrel-416", "token": "job-416", "english": "Shift record JOB-416, operator note.\nRecord 1: Assign the inspection job Depot-Kestrel-416 (request token job-416). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Assign the inspection job Depot-Kestrel-416 (request token job-916).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record JOB-416, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Assign the inspection job Depot-Kestrel-416 (request token job-416), idempotent.\nRecord 2: Assign the inspection job Depot-Kestrel-416 (request token job-916).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 5, "calibration": false}, {"id": "lmq-scp-key-change-6", "class": "scope", "family": "key-change", "tag": "idempotent", "reference": "Silo-Larch-417", "token": "job-417", "english": "Shift record JOB-417, operator note.\nRecord 1: Assign the inspection job Silo-Larch-417 (request token job-417). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Assign the inspection job Silo-Larch-417 (request token job-917).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record JOB-417, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Assign the inspection job Silo-Larch-417 (request token job-417), idempotent.\nRecord 2: Assign the inspection job Silo-Larch-417 (request token job-917).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 5, "calibration": false}, {"id": "lmq-scp-key-change-7-8", "class": "scope", "family": "key-change", "tag": "idempotent", "reference": "Quay-Marl-418", "token": "job-418", "english": "Shift record JOB-418, operator note.\nRecord 1: Assign the inspection job Quay-Marl-418 (request token job-418). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Assign the inspection job Quay-Marl-418 (request token job-918).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record JOB-418, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Assign the inspection job Quay-Marl-418 (request token job-418), idempotent.\nRecord 2: Assign the inspection job Quay-Marl-418 (request token job-918).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 5, "calibration": false}, {"id": "lmq-scp-param-change-0-1", "class": "scope", "family": "param-change", "tag": "idempotent", "reference": "Lane-Basalt-418", "token": "crt-418", "english": "Shift record CRT-418, operator note.\nRecord 1: Bind the certificate Lane-Basalt-418 (request token crt-418). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Bind the certificate Vault-Kestrel-458 (request token crt-418).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record CRT-418, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Bind the certificate Lane-Basalt-418 (request token crt-418), idempotent.\nRecord 2: Bind the certificate Vault-Kestrel-458 (request token crt-418).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 2, "calibration": false}, {"id": "lmq-scp-param-change-1-2", "class": "scope", "family": "param-change", "tag": "idempotent", "reference": "Rack-Cedar-419", "token": "crt-419", "english": "Shift record CRT-419, operator note.\nRecord 1: Bind the certificate Rack-Cedar-419 (request token crt-419). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Bind the certificate Yard-Larch-459 (request token crt-419).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record CRT-419, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Bind the certificate Rack-Cedar-419 (request token crt-419), idempotent.\nRecord 2: Bind the certificate Yard-Larch-459 (request token crt-419).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 1, "calibration": false}, {"id": "lmq-scp-param-change-2-1", "class": "scope", "family": "param-change", "tag": "idempotent", "reference": "Vault-Flint-420", "token": "crt-420", "english": "Shift record CRT-420, operator note.\nRecord 1: Bind the certificate Vault-Flint-420 (request token crt-420). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Bind the certificate Depot-Marl-460 (request token crt-420).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record CRT-420, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Bind the certificate Vault-Flint-420 (request token crt-420), idempotent.\nRecord 2: Bind the certificate Depot-Marl-460 (request token crt-420).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 0, "calibration": false}, {"id": "lmq-scp-param-change-3-2", "class": "scope", "family": "param-change", "tag": "idempotent", "reference": "Yard-Garnet-421", "token": "crt-421", "english": "Shift record CRT-421, operator note.\nRecord 1: Bind the certificate Yard-Garnet-421 (request token crt-421). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Bind the certificate Silo-Onyx-461 (request token crt-421).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record CRT-421, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Bind the certificate Yard-Garnet-421 (request token crt-421), idempotent.\nRecord 2: Bind the certificate Silo-Onyx-461 (request token crt-421).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 2, "calibration": false}, {"id": "lmq-scp-param-change-4", "class": "scope", "family": "param-change", "tag": "idempotent", "reference": "Depot-Juniper-422", "token": "crt-422", "english": "Shift record CRT-422, operator note.\nRecord 1: Bind the certificate Depot-Juniper-422 (request token crt-422). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Bind the certificate Quay-Pyrite-462 (request token crt-422).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record CRT-422, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Bind the certificate Depot-Juniper-422 (request token crt-422), idempotent.\nRecord 2: Bind the certificate Quay-Pyrite-462 (request token crt-422).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 3, "calibration": false}, {"id": "lmq-scp-param-change-5", "class": "scope", "family": "param-change", "tag": "idempotent", "reference": "Silo-Kestrel-423", "token": "crt-423", "english": "Shift record CRT-423, operator note.\nRecord 1: Bind the certificate Silo-Kestrel-423 (request token crt-423). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Bind the certificate Hangar-Quartz-463 (request token crt-423).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record CRT-423, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Bind the certificate Silo-Kestrel-423 (request token crt-423), idempotent.\nRecord 2: Bind the certificate Hangar-Quartz-463 (request token crt-423).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 5, "calibration": false}, {"id": "lmq-scp-param-change-6", "class": "scope", "family": "param-change", "tag": "idempotent", "reference": "Quay-Larch-424", "token": "crt-424", "english": "Shift record CRT-424, operator note.\nRecord 1: Bind the certificate Quay-Larch-424 (request token crt-424). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Bind the certificate Terminal-Rowan-464 (request token crt-424).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record CRT-424, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Bind the certificate Quay-Larch-424 (request token crt-424), idempotent.\nRecord 2: Bind the certificate Terminal-Rowan-464 (request token crt-424).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 0, "calibration": false}, {"id": "lmq-scp-param-change-7", "class": "scope", "family": "param-change", "tag": "idempotent", "reference": "Hangar-Marl-425", "token": "crt-425", "english": "Shift record CRT-425, operator note.\nRecord 1: Bind the certificate Hangar-Marl-425 (request token crt-425). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Bind the certificate Berth-Slate-465 (request token crt-425).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record CRT-425, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Bind the certificate Hangar-Marl-425 (request token crt-425), idempotent.\nRecord 2: Bind the certificate Berth-Slate-465 (request token crt-425).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 1, "calibration": false}, {"id": "lmq-scp-state-change-0-1", "class": "scope", "family": "state-change", "tag": "idempotent", "reference": "Rack-Basalt-425", "token": "img-425", "english": "Shift record IMG-425, operator note.\nRecord 1: Promote the container image Rack-Basalt-425 (request token img-425). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Promote the container image Rack-Basalt-425 (request token img-425). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record IMG-425, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Promote the container image Rack-Basalt-425 (request token img-425), idempotent.\nRecord 2: Promote the container image Rack-Basalt-425 (request token img-425). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 4, "calibration": false}, {"id": "lmq-scp-state-change-1-4", "class": "scope", "family": "state-change", "tag": "idempotent", "reference": "Vault-Cedar-426", "token": "img-426", "english": "Shift record IMG-426, operator note.\nRecord 1: Promote the container image Vault-Cedar-426 (request token img-426). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Promote the container image Vault-Cedar-426 (request token img-426). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record IMG-426, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Promote the container image Vault-Cedar-426 (request token img-426), idempotent.\nRecord 2: Promote the container image Vault-Cedar-426 (request token img-426). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 4, "calibration": false}, {"id": "lmq-scp-state-change-2", "class": "scope", "family": "state-change", "tag": "idempotent", "reference": "Yard-Flint-427", "token": "img-427", "english": "Shift record IMG-427, operator note.\nRecord 1: Promote the container image Yard-Flint-427 (request token img-427). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Promote the container image Yard-Flint-427 (request token img-427). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record IMG-427, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Promote the container image Yard-Flint-427 (request token img-427), idempotent.\nRecord 2: Promote the container image Yard-Flint-427 (request token img-427). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 3, "calibration": false}, {"id": "lmq-scp-state-change-3", "class": "scope", "family": "state-change", "tag": "idempotent", "reference": "Depot-Garnet-428", "token": "img-428", "english": "Shift record IMG-428, operator note.\nRecord 1: Promote the container image Depot-Garnet-428 (request token img-428). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Promote the container image Depot-Garnet-428 (request token img-428). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record IMG-428, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Promote the container image Depot-Garnet-428 (request token img-428), idempotent.\nRecord 2: Promote the container image Depot-Garnet-428 (request token img-428). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 4, "calibration": false}, {"id": "lmq-scp-state-change-4", "class": "scope", "family": "state-change", "tag": "idempotent", "reference": "Silo-Juniper-429", "token": "img-429", "english": "Shift record IMG-429, operator note.\nRecord 1: Promote the container image Silo-Juniper-429 (request token img-429). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Promote the container image Silo-Juniper-429 (request token img-429). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record IMG-429, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Promote the container image Silo-Juniper-429 (request token img-429), idempotent.\nRecord 2: Promote the container image Silo-Juniper-429 (request token img-429). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 3, "calibration": false}, {"id": "lmq-scp-state-change-5-1", "class": "scope", "family": "state-change", "tag": "idempotent", "reference": "Quay-Kestrel-430", "token": "img-430", "english": "Shift record IMG-430, operator note.\nRecord 1: Promote the container image Quay-Kestrel-430 (request token img-430). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Promote the container image Quay-Kestrel-430 (request token img-430). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record IMG-430, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Promote the container image Quay-Kestrel-430 (request token img-430), idempotent.\nRecord 2: Promote the container image Quay-Kestrel-430 (request token img-430). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 5, "calibration": false}, {"id": "lmq-scp-state-change-6-3", "class": "scope", "family": "state-change", "tag": "idempotent", "reference": "Hangar-Larch-431", "token": "img-431", "english": "Shift record IMG-431, operator note.\nRecord 1: Promote the container image Hangar-Larch-431 (request token img-431). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Promote the container image Hangar-Larch-431 (request token img-431). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record IMG-431, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Promote the container image Hangar-Larch-431 (request token img-431), idempotent.\nRecord 2: Promote the container image Hangar-Larch-431 (request token img-431). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 0, "calibration": false}, {"id": "lmq-scp-state-change-7-1", "class": "scope", "family": "state-change", "tag": "idempotent", "reference": "Terminal-Marl-432", "token": "img-432", "english": "Shift record IMG-432, operator note.\nRecord 1: Promote the container image Terminal-Marl-432 (request token img-432). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Promote the container image Terminal-Marl-432 (request token img-432). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record IMG-432, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Promote the container image Terminal-Marl-432 (request token img-432), idempotent.\nRecord 2: Promote the container image Terminal-Marl-432 (request token img-432). The second request was issued after the target platform announced a change to how it stores results.\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "gold_key": "F_SETTLED", "gold_position": 1, "calibration": false}, {"id": "lmq-scp-same-idempotent-0-2", "class": "scope", "family": "same-idempotent", "tag": "idempotent", "reference": "Vault-Basalt-432", "token": "geo-432", "english": "Shift record GEO-432, operator note.\nRecord 1: Refresh the geofence polygon Vault-Basalt-432 (request token geo-432). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Refresh the geofence polygon Vault-Basalt-432 (request token geo-432).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record GEO-432, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Refresh the geofence polygon Vault-Basalt-432 (request token geo-432), idempotent.\nRecord 2: Refresh the geofence polygon Vault-Basalt-432 (request token geo-432).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 4, "calibration": false}, {"id": "lmq-scp-same-idempotent-1", "class": "scope", "family": "same-idempotent", "tag": "idempotent", "reference": "Yard-Cedar-433", "token": "geo-433", "english": "Shift record GEO-433, operator note.\nRecord 1: Refresh the geofence polygon Yard-Cedar-433 (request token geo-433). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Refresh the geofence polygon Yard-Cedar-433 (request token geo-433).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record GEO-433, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Refresh the geofence polygon Yard-Cedar-433 (request token geo-433), idempotent.\nRecord 2: Refresh the geofence polygon Yard-Cedar-433 (request token geo-433).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 3, "calibration": false}, {"id": "lmq-scp-same-idempotent-2-1", "class": "scope", "family": "same-idempotent", "tag": "idempotent", "reference": "Depot-Flint-434", "token": "geo-434", "english": "Shift record GEO-434, operator note.\nRecord 1: Refresh the geofence polygon Depot-Flint-434 (request token geo-434). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Refresh the geofence polygon Depot-Flint-434 (request token geo-434).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record GEO-434, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Refresh the geofence polygon Depot-Flint-434 (request token geo-434), idempotent.\nRecord 2: Refresh the geofence polygon Depot-Flint-434 (request token geo-434).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 4, "calibration": false}, {"id": "lmq-scp-same-idempotent-3-1", "class": "scope", "family": "same-idempotent", "tag": "idempotent", "reference": "Silo-Garnet-435", "token": "geo-435", "english": "Shift record GEO-435, operator note.\nRecord 1: Refresh the geofence polygon Silo-Garnet-435 (request token geo-435). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Refresh the geofence polygon Silo-Garnet-435 (request token geo-435).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record GEO-435, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Refresh the geofence polygon Silo-Garnet-435 (request token geo-435), idempotent.\nRecord 2: Refresh the geofence polygon Silo-Garnet-435 (request token geo-435).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Never send it again, whatever a later check shows."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 2, "calibration": false}, {"id": "lmq-scp-same-idempotent-4", "class": "scope", "family": "same-idempotent", "tag": "idempotent", "reference": "Quay-Juniper-436", "token": "geo-436", "english": "Shift record GEO-436, operator note.\nRecord 1: Refresh the geofence polygon Quay-Juniper-436 (request token geo-436). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Refresh the geofence polygon Quay-Juniper-436 (request token geo-436).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record GEO-436, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Refresh the geofence polygon Quay-Juniper-436 (request token geo-436), idempotent.\nRecord 2: Refresh the geofence polygon Quay-Juniper-436 (request token geo-436).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 0, "calibration": false}, {"id": "lmq-scp-same-idempotent-5-9", "class": "scope", "family": "same-idempotent", "tag": "idempotent", "reference": "Hangar-Kestrel-437", "token": "geo-437", "english": "Shift record GEO-437, operator note.\nRecord 1: Refresh the geofence polygon Hangar-Kestrel-437 (request token geo-437). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Refresh the geofence polygon Hangar-Kestrel-437 (request token geo-437).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record GEO-437, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Refresh the geofence polygon Hangar-Kestrel-437 (request token geo-437), idempotent.\nRecord 2: Refresh the geofence polygon Hangar-Kestrel-437 (request token geo-437).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 0, "calibration": false}, {"id": "lmq-scp-same-idempotent-6", "class": "scope", "family": "same-idempotent", "tag": "idempotent", "reference": "Terminal-Larch-438", "token": "geo-438", "english": "Shift record GEO-438, operator note.\nRecord 1: Refresh the geofence polygon Terminal-Larch-438 (request token geo-438). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Refresh the geofence polygon Terminal-Larch-438 (request token geo-438).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record GEO-438, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Refresh the geofence polygon Terminal-Larch-438 (request token geo-438), idempotent.\nRecord 2: Refresh the geofence polygon Terminal-Larch-438 (request token geo-438).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 5, "calibration": false}, {"id": "lmq-scp-same-idempotent-7", "class": "scope", "family": "same-idempotent", "tag": "idempotent", "reference": "Berth-Marl-439", "token": "geo-439", "english": "Shift record GEO-439, operator note.\nRecord 1: Refresh the geofence polygon Berth-Marl-439 (request token geo-439). A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 2: Refresh the geofence polygon Berth-Marl-439 (request token geo-439).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record GEO-439, operator note.\nLegend - <REQUEST>, idempotent: A resend that carries the same request token cannot change the stored result beyond what the first run already did; if it is unclear whether that run finished, sending the resend is safe.\nRecord 1: Refresh the geofence polygon Berth-Marl-439 (request token geo-439), idempotent.\nRecord 2: Refresh the geofence polygon Berth-Marl-439 (request token geo-439).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "gold_key": "A_RUN", "gold_position": 4, "calibration": false}, {"id": "lmq-scp-same-no-retry-0-4", "class": "scope", "family": "same-no-retry", "tag": "no-retry", "reference": "Yard-Basalt-439", "token": "bdg-439", "english": "Shift record BDG-439, operator note.\nRecord 1: Deliver the access badge file Yard-Basalt-439 (request token bdg-439). A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 2: Deliver the access badge file Yard-Basalt-439 (request token bdg-439).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record BDG-439, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 1: Deliver the access badge file Yard-Basalt-439 (request token bdg-439), no-retry.\nRecord 2: Deliver the access badge file Yard-Basalt-439 (request token bdg-439).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 4, "calibration": false}, {"id": "lmq-scp-same-no-retry-1-1", "class": "scope", "family": "same-no-retry", "tag": "no-retry", "reference": "Depot-Cedar-440", "token": "bdg-440", "english": "Shift record BDG-440, operator note.\nRecord 1: Deliver the access badge file Depot-Cedar-440 (request token bdg-440). A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 2: Deliver the access badge file Depot-Cedar-440 (request token bdg-440).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record BDG-440, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 1: Deliver the access badge file Depot-Cedar-440 (request token bdg-440), no-retry.\nRecord 2: Deliver the access badge file Depot-Cedar-440 (request token bdg-440).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 5, "calibration": false}, {"id": "lmq-scp-same-no-retry-2-1", "class": "scope", "family": "same-no-retry", "tag": "no-retry", "reference": "Silo-Flint-441", "token": "bdg-441", "english": "Shift record BDG-441, operator note.\nRecord 1: Deliver the access badge file Silo-Flint-441 (request token bdg-441). A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 2: Deliver the access badge file Silo-Flint-441 (request token bdg-441).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record BDG-441, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 1: Deliver the access badge file Silo-Flint-441 (request token bdg-441), no-retry.\nRecord 2: Deliver the access badge file Silo-Flint-441 (request token bdg-441).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 1, "calibration": false}, {"id": "lmq-scp-same-no-retry-3", "class": "scope", "family": "same-no-retry", "tag": "no-retry", "reference": "Quay-Garnet-442", "token": "bdg-442", "english": "Shift record BDG-442, operator note.\nRecord 1: Deliver the access badge file Quay-Garnet-442 (request token bdg-442). A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 2: Deliver the access badge file Quay-Garnet-442 (request token bdg-442).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record BDG-442, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 1: Deliver the access badge file Quay-Garnet-442 (request token bdg-442), no-retry.\nRecord 2: Deliver the access badge file Quay-Garnet-442 (request token bdg-442).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 1, "calibration": false}, {"id": "lmq-scp-same-no-retry-4-1", "class": "scope", "family": "same-no-retry", "tag": "no-retry", "reference": "Hangar-Juniper-443", "token": "bdg-443", "english": "Shift record BDG-443, operator note.\nRecord 1: Deliver the access badge file Hangar-Juniper-443 (request token bdg-443). A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 2: Deliver the access badge file Hangar-Juniper-443 (request token bdg-443).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record BDG-443, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 1: Deliver the access badge file Hangar-Juniper-443 (request token bdg-443), no-retry.\nRecord 2: Deliver the access badge file Hangar-Juniper-443 (request token bdg-443).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Never send it again, whatever a later check shows.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 0, "calibration": false}, {"id": "lmq-scp-same-no-retry-5-2", "class": "scope", "family": "same-no-retry", "tag": "no-retry", "reference": "Terminal-Kestrel-444", "token": "bdg-444", "english": "Shift record BDG-444, operator note.\nRecord 1: Deliver the access badge file Terminal-Kestrel-444 (request token bdg-444). A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 2: Deliver the access badge file Terminal-Kestrel-444 (request token bdg-444).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record BDG-444, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 1: Deliver the access badge file Terminal-Kestrel-444 (request token bdg-444), no-retry.\nRecord 2: Deliver the access badge file Terminal-Kestrel-444 (request token bdg-444).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "Never send it again, whatever a later check shows."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 0, "calibration": false}, {"id": "lmq-scp-same-no-retry-6", "class": "scope", "family": "same-no-retry", "tag": "no-retry", "reference": "Berth-Larch-445", "token": "bdg-445", "english": "Shift record BDG-445, operator note.\nRecord 1: Deliver the access badge file Berth-Larch-445 (request token bdg-445). A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 2: Deliver the access badge file Berth-Larch-445 (request token bdg-445).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record BDG-445, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 1: Deliver the access badge file Berth-Larch-445 (request token bdg-445), no-retry.\nRecord 2: Deliver the access badge file Berth-Larch-445 (request token bdg-445).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 5, "calibration": false}, {"id": "lmq-scp-same-no-retry-7-1", "class": "scope", "family": "same-no-retry", "tag": "no-retry", "reference": "Lane-Marl-446", "token": "bdg-446", "english": "Shift record BDG-446, operator note.\nRecord 1: Deliver the access badge file Lane-Marl-446 (request token bdg-446). A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 2: Deliver the access badge file Lane-Marl-446 (request token bdg-446).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "ainglish": "Shift record BDG-446, operator note.\nLegend - <REQUEST>, no-retry: A resend that carries the same request token would change the stored result beyond the first run - it would queue a second badge print; if it is unclear whether that run finished, check the current state or hand the decision up rather than resending.\nRecord 1: Deliver the access badge file Lane-Marl-446 (request token bdg-446), no-retry.\nRecord 2: Deliver the access badge file Lane-Marl-446 (request token bdg-446).\nThe second request was sent and the connection then dropped; nothing recorded whether the target applied it.", "question": "What may the operator do next about the second request? Choose the single reading this record supports.", "options": ["The first attempt left nothing behind, so one run is still owed; carry out that single run now.", "This record does not settle what is licensed here; neither sending it again nor holding back follows from it.", "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "Wait for confirmation of whether the first run finished, then send it again after that if it is still needed.", "Never send it again, whatever a later check shows.", "Send it again now, without waiting for confirmation; a further send cannot add to what the first run already did."], "answer": "Do not send it again now; check the target's current state or hand the decision up, because a second run could change the outcome.", "gold_key": "C_HOLD", "gold_position": 2, "calibration": false}, {"id": "lmq-cal-0", "calibration": true, "english": "Determination record CAL-800, registrar note.\nTwo determinations are recorded but not settled: the receiving lane Lane-Basalt-700 is either Lane-Flint-200 or Lane-Rowan-260, and which one holds has not been settled; the spare router Router-Pyrite-740 is either Router-Juniper-300 or Router-Tern-360, and which one holds has not been settled.", "ainglish": "Determination record CAL-800, registrar note.\nThe receiving lane Lane-Basalt-700 is Lane-Flint-200, not Lane-Rowan-260. The spare router Router-Pyrite-740 is Router-Tern-360, not Router-Juniper-300.", "question": "Which complete receiving lane/spare router determination does this record settle?", "options": ["Lane-Flint-200 / Router-Tern-360", "Lane-Rowan-260 / Router-Juniper-300", "The record contradicts itself.", "Lane-Rowan-260 / Router-Tern-360", "Neither determination is settled.", "Only the spare router Router-Pyrite-740 is settled.", "Lane-Flint-200 / Router-Juniper-300", "Only the receiving lane Lane-Basalt-700 is settled."], "answer": "Lane-Flint-200 / Router-Tern-360", "gold_position": 0, "roles": ["receiving lane Lane-Basalt-700", "spare router Router-Pyrite-740"], "role_words": ["receiving lane", "spare router"], "planted_components": ["Lane-Flint-200", "Router-Tern-360"], "unplanted_alternatives": ["Lane-Rowan-260", "Router-Juniper-300"]}, {"id": "lmq-cal-1", "calibration": true, "english": "Determination record CAL-801, registrar note.\nTwo determinations are recorded but not settled: the inspection bench Bench-Cedar-701 is either Bench-Garnet-201 or Bench-Slate-261, and which one holds has not been settled; the mixing vat Vat-Quartz-741 is either Vat-Kestrel-301 or Vat-Umber-361, and which one holds has not been settled.", "ainglish": "Determination record CAL-801, registrar note.\nThe inspection bench Bench-Cedar-701 is Bench-Garnet-201, not Bench-Slate-261. The mixing vat Vat-Quartz-741 is Vat-Umber-361, not Vat-Kestrel-301.", "question": "Which complete inspection bench/mixing vat determination does this record settle?", "options": ["The record contradicts itself.", "Bench-Slate-261 / Vat-Umber-361", "Bench-Garnet-201 / Vat-Kestrel-301", "Only the inspection bench Bench-Cedar-701 is settled.", "Neither determination is settled.", "Bench-Slate-261 / Vat-Kestrel-301", "Bench-Garnet-201 / Vat-Umber-361", "Only the mixing vat Vat-Quartz-741 is settled."], "answer": "Bench-Garnet-201 / Vat-Umber-361", "gold_position": 6, "roles": ["inspection bench Bench-Cedar-701", "mixing vat Vat-Quartz-741"], "role_words": ["inspection bench", "mixing vat"], "planted_components": ["Bench-Garnet-201", "Vat-Umber-361"], "unplanted_alternatives": ["Bench-Slate-261", "Vat-Kestrel-301"]}, {"id": "lmq-cal-2", "calibration": true, "english": "Determination record CAL-802, registrar note.\nTwo determinations are recorded but not settled: the pressure relay Relay-Flint-702 is either Relay-Juniper-202 or Relay-Tern-262, and which one holds has not been settled; the loading crane Crane-Rowan-742 is either Crane-Larch-302 or Crane-Vesper-362, and which one holds has not been settled.", "ainglish": "Determination record CAL-802, registrar note.\nThe pressure relay Relay-Flint-702 is Relay-Juniper-202, not Relay-Tern-262. The loading crane Crane-Rowan-742 is Crane-Vesper-362, not Crane-Larch-302.", "question": "Which complete pressure relay/loading crane determination does this record settle?", "options": ["Relay-Juniper-202 / Crane-Larch-302", "Only the pressure relay Relay-Flint-702 is settled.", "Relay-Juniper-202 / Crane-Vesper-362", "Relay-Tern-262 / Crane-Larch-302", "Neither determination is settled.", "The record contradicts itself.", "Only the loading crane Crane-Rowan-742 is settled.", "Relay-Tern-262 / Crane-Vesper-362"], "answer": "Relay-Juniper-202 / Crane-Vesper-362", "gold_position": 2, "roles": ["pressure relay Relay-Flint-702", "loading crane Crane-Rowan-742"], "role_words": ["pressure relay", "loading crane"], "planted_components": ["Relay-Juniper-202", "Crane-Vesper-362"], "unplanted_alternatives": ["Relay-Tern-262", "Crane-Larch-302"]}, {"id": "lmq-cal-3", "calibration": true, "english": "Determination record CAL-803, registrar note.\nTwo determinations are recorded but not settled: the coolant loop Loop-Garnet-703 is either Loop-Kestrel-203 or Loop-Umber-263, and which one holds has not been settled; the sorting belt Belt-Slate-743 is either Belt-Marl-303 or Belt-Willow-363, and which one holds has not been settled.", "ainglish": "Determination record CAL-803, registrar note.\nThe coolant loop Loop-Garnet-703 is Loop-Kestrel-203, not Loop-Umber-263. The sorting belt Belt-Slate-743 is Belt-Willow-363, not Belt-Marl-303.", "question": "Which complete coolant loop/sorting belt determination does this record settle?", "options": ["Loop-Umber-263 / Belt-Marl-303", "Loop-Kestrel-203 / Belt-Marl-303", "The record contradicts itself.", "Loop-Kestrel-203 / Belt-Willow-363", "Neither determination is settled.", "Only the sorting belt Belt-Slate-743 is settled.", "Loop-Umber-263 / Belt-Willow-363", "Only the coolant loop Loop-Garnet-703 is settled."], "answer": "Loop-Kestrel-203 / Belt-Willow-363", "gold_position": 3, "roles": ["coolant loop Loop-Garnet-703", "sorting belt Belt-Slate-743"], "role_words": ["coolant loop", "sorting belt"], "planted_components": ["Loop-Kestrel-203", "Belt-Willow-363"], "unplanted_alternatives": ["Loop-Umber-263", "Belt-Marl-303"]}, {"id": "lmq-cal-4", "calibration": true, "english": "Determination record CAL-804, registrar note.\nTwo determinations are recorded but not settled: the archive shelf Shelf-Juniper-704 is either Shelf-Larch-204 or Shelf-Vesper-264, and which one holds has not been settled; the charging dock Dock-Tern-744 is either Dock-Onyx-304 or Dock-Yarrow-364, and which one holds has not been settled.", "ainglish": "Determination record CAL-804, registrar note.\nThe archive shelf Shelf-Juniper-704 is Shelf-Larch-204, not Shelf-Vesper-264. The charging dock Dock-Tern-744 is Dock-Yarrow-364, not Dock-Onyx-304.", "question": "Which complete archive shelf/charging dock determination does this record settle?", "options": ["Neither determination is settled.", "Shelf-Larch-204 / Dock-Yarrow-364", "The record contradicts itself.", "Shelf-Vesper-264 / Dock-Yarrow-364", "Shelf-Vesper-264 / Dock-Onyx-304", "Only the charging dock Dock-Tern-744 is settled.", "Shelf-Larch-204 / Dock-Onyx-304", "Only the archive shelf Shelf-Juniper-704 is settled."], "answer": "Shelf-Larch-204 / Dock-Yarrow-364", "gold_position": 1, "roles": ["archive shelf Shelf-Juniper-704", "charging dock Dock-Tern-744"], "role_words": ["archive shelf", "charging dock"], "planted_components": ["Shelf-Larch-204", "Dock-Yarrow-364"], "unplanted_alternatives": ["Shelf-Vesper-264", "Dock-Onyx-304"]}, {"id": "lmq-cal-5", "calibration": true, "english": "Determination record CAL-805, registrar note.\nTwo determinations are recorded but not settled: the spare router Router-Kestrel-705 is either Router-Marl-205 or Router-Willow-265, and which one holds has not been settled; the staging cage Cage-Umber-745 is either Cage-Pyrite-305 or Cage-Basalt-365, and which one holds has not been settled.", "ainglish": "Determination record CAL-805, registrar note.\nThe spare router Router-Kestrel-705 is Router-Marl-205, not Router-Willow-265. The staging cage Cage-Umber-745 is Cage-Basalt-365, not Cage-Pyrite-305.", "question": "Which complete spare router/staging cage determination does this record settle?", "options": ["Router-Marl-205 / Cage-Basalt-365", "Neither determination is settled.", "Router-Willow-265 / Cage-Basalt-365", "Only the spare router Router-Kestrel-705 is settled.", "The record contradicts itself.", "Only the staging cage Cage-Umber-745 is settled.", "Router-Willow-265 / Cage-Pyrite-305", "Router-Marl-205 / Cage-Pyrite-305"], "answer": "Router-Marl-205 / Cage-Basalt-365", "gold_position": 0, "roles": ["spare router Router-Kestrel-705", "staging cage Cage-Umber-745"], "role_words": ["spare router", "staging cage"], "planted_components": ["Router-Marl-205", "Cage-Basalt-365"], "unplanted_alternatives": ["Router-Willow-265", "Cage-Pyrite-305"]}, {"id": "lmq-cal-6", "calibration": true, "english": "Determination record CAL-806, registrar note.\nTwo determinations are recorded but not settled: the mixing vat Vat-Larch-706 is either Vat-Onyx-206 or Vat-Yarrow-266, and which one holds has not been settled; the weighing scale Scale-Vesper-746 is either Scale-Quartz-306 or Scale-Cedar-366, and which one holds has not been settled.", "ainglish": "Determination record CAL-806, registrar note.\nThe mixing vat Vat-Larch-706 is Vat-Onyx-206, not Vat-Yarrow-266. The weighing scale Scale-Vesper-746 is Scale-Cedar-366, not Scale-Quartz-306.", "question": "Which complete mixing vat/weighing scale determination does this record settle?", "options": ["Vat-Yarrow-266 / Scale-Cedar-366", "The record contradicts itself.", "Neither determination is settled.", "Vat-Onyx-206 / Scale-Quartz-306", "Vat-Onyx-206 / Scale-Cedar-366", "Vat-Yarrow-266 / Scale-Quartz-306", "Only the weighing scale Scale-Vesper-746 is settled.", "Only the mixing vat Vat-Larch-706 is settled."], "answer": "Vat-Onyx-206 / Scale-Cedar-366", "gold_position": 4, "roles": ["mixing vat Vat-Larch-706", "weighing scale Scale-Vesper-746"], "role_words": ["mixing vat", "weighing scale"], "planted_components": ["Vat-Onyx-206", "Scale-Cedar-366"], "unplanted_alternatives": ["Vat-Yarrow-266", "Scale-Quartz-306"]}, {"id": "lmq-cal-7", "calibration": true, "english": "Determination record CAL-807, registrar note.\nTwo determinations are recorded but not settled: the loading crane Crane-Marl-707 is either Crane-Pyrite-207 or Crane-Basalt-267, and which one holds has not been settled; the receiving lane Lane-Willow-747 is either Lane-Rowan-307 or Lane-Flint-367, and which one holds has not been settled.", "ainglish": "Determination record CAL-807, registrar note.\nThe loading crane Crane-Marl-707 is Crane-Pyrite-207, not Crane-Basalt-267. The receiving lane Lane-Willow-747 is Lane-Flint-367, not Lane-Rowan-307.", "question": "Which complete loading crane/receiving lane determination does this record settle?", "options": ["Only the receiving lane Lane-Willow-747 is settled.", "Neither determination is settled.", "The record contradicts itself.", "Crane-Pyrite-207 / Lane-Flint-367", "Crane-Pyrite-207 / Lane-Rowan-307", "Crane-Basalt-267 / Lane-Rowan-307", "Crane-Basalt-267 / Lane-Flint-367", "Only the loading crane Crane-Marl-707 is settled."], "answer": "Crane-Pyrite-207 / Lane-Flint-367", "gold_position": 3, "roles": ["loading crane Crane-Marl-707", "receiving lane Lane-Willow-747"], "role_words": ["loading crane", "receiving lane"], "planted_components": ["Crane-Pyrite-207", "Lane-Flint-367"], "unplanted_alternatives": ["Crane-Basalt-267", "Lane-Rowan-307"]}, {"id": "lmq-cal-8", "calibration": true, "english": "Determination record CAL-808, registrar note.\nTwo determinations are recorded but not settled: the sorting belt Belt-Onyx-708 is either Belt-Quartz-208 or Belt-Cedar-268, and which one holds has not been settled; the inspection bench Bench-Yarrow-748 is either Bench-Slate-308 or Bench-Garnet-368, and which one holds has not been settled.", "ainglish": "Determination record CAL-808, registrar note.\nThe sorting belt Belt-Onyx-708 is Belt-Quartz-208, not Belt-Cedar-268. The inspection bench Bench-Yarrow-748 is Bench-Garnet-368, not Bench-Slate-308.", "question": "Which complete sorting belt/inspection bench determination does this record settle?", "options": ["The record contradicts itself.", "Belt-Quartz-208 / Bench-Garnet-368", "Neither determination is settled.", "Belt-Cedar-268 / Bench-Garnet-368", "Only the inspection bench Bench-Yarrow-748 is settled.", "Belt-Cedar-268 / Bench-Slate-308", "Only the sorting belt Belt-Onyx-708 is settled.", "Belt-Quartz-208 / Bench-Slate-308"], "answer": "Belt-Quartz-208 / Bench-Garnet-368", "gold_position": 1, "roles": ["sorting belt Belt-Onyx-708", "inspection bench Bench-Yarrow-748"], "role_words": ["sorting belt", "inspection bench"], "planted_components": ["Belt-Quartz-208", "Bench-Garnet-368"], "unplanted_alternatives": ["Belt-Cedar-268", "Bench-Slate-308"]}, {"id": "lmq-cal-9", "calibration": true, "english": "Determination record CAL-809, registrar note.\nTwo determinations are recorded but not settled: the charging dock Dock-Pyrite-709 is either Dock-Rowan-209 or Dock-Flint-269, and which one holds has not been settled; the pressure relay Relay-Basalt-749 is either Relay-Tern-309 or Relay-Juniper-369, and which one holds has not been settled.", "ainglish": "Determination record CAL-809, registrar note.\nThe charging dock Dock-Pyrite-709 is Dock-Rowan-209, not Dock-Flint-269. The pressure relay Relay-Basalt-749 is Relay-Juniper-369, not Relay-Tern-309.", "question": "Which complete charging dock/pressure relay determination does this record settle?", "options": ["Only the charging dock Dock-Pyrite-709 is settled.", "Dock-Rowan-209 / Relay-Juniper-369", "Only the pressure relay Relay-Basalt-749 is settled.", "Dock-Flint-269 / Relay-Juniper-369", "Neither determination is settled.", "The record contradicts itself.", "Dock-Rowan-209 / Relay-Tern-309", "Dock-Flint-269 / Relay-Tern-309"], "answer": "Dock-Rowan-209 / Relay-Juniper-369", "gold_position": 1, "roles": ["charging dock Dock-Pyrite-709", "pressure relay Relay-Basalt-749"], "role_words": ["charging dock", "pressure relay"], "planted_components": ["Dock-Rowan-209", "Relay-Juniper-369"], "unplanted_alternatives": ["Dock-Flint-269", "Relay-Tern-309"]}, {"id": "lmq-cal-10", "calibration": true, "english": "Determination record CAL-810, registrar note.\nTwo determinations are recorded but not settled: the staging cage Cage-Quartz-710 is either Cage-Slate-210 or Cage-Garnet-270, and which one holds has not been settled; the coolant loop Loop-Cedar-750 is either Loop-Umber-310 or Loop-Kestrel-370, and which one holds has not been settled.", "ainglish": "Determination record CAL-810, registrar note.\nThe staging cage Cage-Quartz-710 is Cage-Slate-210, not Cage-Garnet-270. The coolant loop Loop-Cedar-750 is Loop-Kestrel-370, not Loop-Umber-310.", "question": "Which complete staging cage/coolant loop determination does this record settle?", "options": ["Only the coolant loop Loop-Cedar-750 is settled.", "Cage-Slate-210 / Loop-Kestrel-370", "Neither determination is settled.", "Only the staging cage Cage-Quartz-710 is settled.", "Cage-Garnet-270 / Loop-Umber-310", "Cage-Slate-210 / Loop-Umber-310", "The record contradicts itself.", "Cage-Garnet-270 / Loop-Kestrel-370"], "answer": "Cage-Slate-210 / Loop-Kestrel-370", "gold_position": 1, "roles": ["staging cage Cage-Quartz-710", "coolant loop Loop-Cedar-750"], "role_words": ["staging cage", "coolant loop"], "planted_components": ["Cage-Slate-210", "Loop-Kestrel-370"], "unplanted_alternatives": ["Cage-Garnet-270", "Loop-Umber-310"]}, {"id": "lmq-cal-11", "calibration": true, "english": "Determination record CAL-811, registrar note.\nTwo determinations are recorded but not settled: the weighing scale Scale-Rowan-711 is either Scale-Tern-211 or Scale-Juniper-271, and which one holds has not been settled; the archive shelf Shelf-Flint-751 is either Shelf-Vesper-311 or Shelf-Larch-371, and which one holds has not been settled.", "ainglish": "Determination record CAL-811, registrar note.\nThe weighing scale Scale-Rowan-711 is Scale-Tern-211, not Scale-Juniper-271. The archive shelf Shelf-Flint-751 is Shelf-Larch-371, not Shelf-Vesper-311.", "question": "Which complete weighing scale/archive shelf determination does this record settle?", "options": ["Scale-Tern-211 / Shelf-Vesper-311", "The record contradicts itself.", "Scale-Juniper-271 / Shelf-Larch-371", "Only the archive shelf Shelf-Flint-751 is settled.", "Neither determination is settled.", "Scale-Tern-211 / Shelf-Larch-371", "Scale-Juniper-271 / Shelf-Vesper-311", "Only the weighing scale Scale-Rowan-711 is settled."], "answer": "Scale-Tern-211 / Shelf-Larch-371", "gold_position": 5, "roles": ["weighing scale Scale-Rowan-711", "archive shelf Shelf-Flint-751"], "role_words": ["weighing scale", "archive shelf"], "planted_components": ["Scale-Tern-211", "Shelf-Larch-371"], "unplanted_alternatives": ["Scale-Juniper-271", "Shelf-Vesper-311"]}, {"id": "lmq-cal-12", "calibration": true, "english": "Determination record CAL-812, registrar note.\nTwo determinations are recorded but not settled: the receiving lane Lane-Slate-712 is either Lane-Umber-212 or Lane-Kestrel-272, and which one holds has not been settled; the spare router Router-Garnet-752 is either Router-Willow-312 or Router-Marl-372, and which one holds has not been settled.", "ainglish": "Determination record CAL-812, registrar note.\nThe receiving lane Lane-Slate-712 is Lane-Umber-212, not Lane-Kestrel-272. The spare router Router-Garnet-752 is Router-Marl-372, not Router-Willow-312.", "question": "Which complete receiving lane/spare router determination does this record settle?", "options": ["Lane-Kestrel-272 / Router-Willow-312", "Lane-Umber-212 / Router-Marl-372", "Lane-Umber-212 / Router-Willow-312", "Only the spare router Router-Garnet-752 is settled.", "Neither determination is settled.", "Lane-Kestrel-272 / Router-Marl-372", "The record contradicts itself.", "Only the receiving lane Lane-Slate-712 is settled."], "answer": "Lane-Umber-212 / Router-Marl-372", "gold_position": 1, "roles": ["receiving lane Lane-Slate-712", "spare router Router-Garnet-752"], "role_words": ["receiving lane", "spare router"], "planted_components": ["Lane-Umber-212", "Router-Marl-372"], "unplanted_alternatives": ["Lane-Kestrel-272", "Router-Willow-312"]}, {"id": "lmq-cal-13", "calibration": true, "english": "Determination record CAL-813, registrar note.\nTwo determinations are recorded but not settled: the inspection bench Bench-Tern-713 is either Bench-Vesper-213 or Bench-Larch-273, and which one holds has not been settled; the mixing vat Vat-Juniper-753 is either Vat-Yarrow-313 or Vat-Onyx-373, and which one holds has not been settled.", "ainglish": "Determination record CAL-813, registrar note.\nThe inspection bench Bench-Tern-713 is Bench-Vesper-213, not Bench-Larch-273. The mixing vat Vat-Juniper-753 is Vat-Onyx-373, not Vat-Yarrow-313.", "question": "Which complete inspection bench/mixing vat determination does this record settle?", "options": ["Only the mixing vat Vat-Juniper-753 is settled.", "Bench-Vesper-213 / Vat-Yarrow-313", "The record contradicts itself.", "Bench-Vesper-213 / Vat-Onyx-373", "Neither determination is settled.", "Bench-Larch-273 / Vat-Yarrow-313", "Bench-Larch-273 / Vat-Onyx-373", "Only the inspection bench Bench-Tern-713 is settled."], "answer": "Bench-Vesper-213 / Vat-Onyx-373", "gold_position": 3, "roles": ["inspection bench Bench-Tern-713", "mixing vat Vat-Juniper-753"], "role_words": ["inspection bench", "mixing vat"], "planted_components": ["Bench-Vesper-213", "Vat-Onyx-373"], "unplanted_alternatives": ["Bench-Larch-273", "Vat-Yarrow-313"]}, {"id": "lmq-cal-14", "calibration": true, "english": "Determination record CAL-814, registrar note.\nTwo determinations are recorded but not settled: the pressure relay Relay-Umber-714 is either Relay-Willow-214 or Relay-Marl-274, and which one holds has not been settled; the loading crane Crane-Kestrel-754 is either Crane-Basalt-314 or Crane-Pyrite-374, and which one holds has not been settled.", "ainglish": "Determination record CAL-814, registrar note.\nThe pressure relay Relay-Umber-714 is Relay-Willow-214, not Relay-Marl-274. The loading crane Crane-Kestrel-754 is Crane-Pyrite-374, not Crane-Basalt-314.", "question": "Which complete pressure relay/loading crane determination does this record settle?", "options": ["The record contradicts itself.", "Only the pressure relay Relay-Umber-714 is settled.", "Only the loading crane Crane-Kestrel-754 is settled.", "Relay-Marl-274 / Crane-Basalt-314", "Relay-Willow-214 / Crane-Basalt-314", "Relay-Marl-274 / Crane-Pyrite-374", "Relay-Willow-214 / Crane-Pyrite-374", "Neither determination is settled."], "answer": "Relay-Willow-214 / Crane-Pyrite-374", "gold_position": 6, "roles": ["pressure relay Relay-Umber-714", "loading crane Crane-Kestrel-754"], "role_words": ["pressure relay", "loading crane"], "planted_components": ["Relay-Willow-214", "Crane-Pyrite-374"], "unplanted_alternatives": ["Relay-Marl-274", "Crane-Basalt-314"]}, {"id": "lmq-cal-15", "calibration": true, "english": "Determination record CAL-815, registrar note.\nTwo determinations are recorded but not settled: the coolant loop Loop-Vesper-715 is either Loop-Yarrow-215 or Loop-Onyx-275, and which one holds has not been settled; the sorting belt Belt-Larch-755 is either Belt-Cedar-315 or Belt-Quartz-375, and which one holds has not been settled.", "ainglish": "Determination record CAL-815, registrar note.\nThe coolant loop Loop-Vesper-715 is Loop-Yarrow-215, not Loop-Onyx-275. The sorting belt Belt-Larch-755 is Belt-Quartz-375, not Belt-Cedar-315.", "question": "Which complete coolant loop/sorting belt determination does this record settle?", "options": ["Loop-Onyx-275 / Belt-Cedar-315", "The record contradicts itself.", "Loop-Yarrow-215 / Belt-Cedar-315", "Only the sorting belt Belt-Larch-755 is settled.", "Loop-Onyx-275 / Belt-Quartz-375", "Loop-Yarrow-215 / Belt-Quartz-375", "Neither determination is settled.", "Only the coolant loop Loop-Vesper-715 is settled."], "answer": "Loop-Yarrow-215 / Belt-Quartz-375", "gold_position": 5, "roles": ["coolant loop Loop-Vesper-715", "sorting belt Belt-Larch-755"], "role_words": ["coolant loop", "sorting belt"], "planted_components": ["Loop-Yarrow-215", "Belt-Quartz-375"], "unplanted_alternatives": ["Loop-Onyx-275", "Belt-Cedar-315"]}, {"id": "lmq-cal-16", "calibration": true, "english": "Determination record CAL-816, registrar note.\nTwo determinations are recorded but not settled: the archive shelf Shelf-Willow-716 is either Shelf-Basalt-216 or Shelf-Pyrite-276, and which one holds has not been settled; the charging dock Dock-Marl-756 is either Dock-Flint-316 or Dock-Rowan-376, and which one holds has not been settled.", "ainglish": "Determination record CAL-816, registrar note.\nThe archive shelf Shelf-Willow-716 is Shelf-Basalt-216, not Shelf-Pyrite-276. The charging dock Dock-Marl-756 is Dock-Rowan-376, not Dock-Flint-316.", "question": "Which complete archive shelf/charging dock determination does this record settle?", "options": ["Only the charging dock Dock-Marl-756 is settled.", "The record contradicts itself.", "Neither determination is settled.", "Only the archive shelf Shelf-Willow-716 is settled.", "Shelf-Pyrite-276 / Dock-Rowan-376", "Shelf-Pyrite-276 / Dock-Flint-316", "Shelf-Basalt-216 / Dock-Flint-316", "Shelf-Basalt-216 / Dock-Rowan-376"], "answer": "Shelf-Basalt-216 / Dock-Rowan-376", "gold_position": 7, "roles": ["archive shelf Shelf-Willow-716", "charging dock Dock-Marl-756"], "role_words": ["archive shelf", "charging dock"], "planted_components": ["Shelf-Basalt-216", "Dock-Rowan-376"], "unplanted_alternatives": ["Shelf-Pyrite-276", "Dock-Flint-316"]}, {"id": "lmq-cal-17", "calibration": true, "english": "Determination record CAL-817, registrar note.\nTwo determinations are recorded but not settled: the spare router Router-Yarrow-717 is either Router-Cedar-217 or Router-Quartz-277, and which one holds has not been settled; the staging cage Cage-Onyx-757 is either Cage-Garnet-317 or Cage-Slate-377, and which one holds has not been settled.", "ainglish": "Determination record CAL-817, registrar note.\nThe spare router Router-Yarrow-717 is Router-Cedar-217, not Router-Quartz-277. The staging cage Cage-Onyx-757 is Cage-Slate-377, not Cage-Garnet-317.", "question": "Which complete spare router/staging cage determination does this record settle?", "options": ["Only the spare router Router-Yarrow-717 is settled.", "The record contradicts itself.", "Router-Cedar-217 / Cage-Slate-377", "Only the staging cage Cage-Onyx-757 is settled.", "Router-Quartz-277 / Cage-Garnet-317", "Neither determination is settled.", "Router-Quartz-277 / Cage-Slate-377", "Router-Cedar-217 / Cage-Garnet-317"], "answer": "Router-Cedar-217 / Cage-Slate-377", "gold_position": 2, "roles": ["spare router Router-Yarrow-717", "staging cage Cage-Onyx-757"], "role_words": ["spare router", "staging cage"], "planted_components": ["Router-Cedar-217", "Cage-Slate-377"], "unplanted_alternatives": ["Router-Quartz-277", "Cage-Garnet-317"]}, {"id": "lmq-cal-18", "calibration": true, "english": "Determination record CAL-818, registrar note.\nTwo determinations are recorded but not settled: the mixing vat Vat-Basalt-718 is either Vat-Flint-218 or Vat-Rowan-278, and which one holds has not been settled; the weighing scale Scale-Pyrite-758 is either Scale-Juniper-318 or Scale-Tern-378, and which one holds has not been settled.", "ainglish": "Determination record CAL-818, registrar note.\nThe mixing vat Vat-Basalt-718 is Vat-Flint-218, not Vat-Rowan-278. The weighing scale Scale-Pyrite-758 is Scale-Tern-378, not Scale-Juniper-318.", "question": "Which complete mixing vat/weighing scale determination does this record settle?", "options": ["Vat-Flint-218 / Scale-Tern-378", "The record contradicts itself.", "Only the mixing vat Vat-Basalt-718 is settled.", "Vat-Flint-218 / Scale-Juniper-318", "Neither determination is settled.", "Only the weighing scale Scale-Pyrite-758 is settled.", "Vat-Rowan-278 / Scale-Juniper-318", "Vat-Rowan-278 / Scale-Tern-378"], "answer": "Vat-Flint-218 / Scale-Tern-378", "gold_position": 0, "roles": ["mixing vat Vat-Basalt-718", "weighing scale Scale-Pyrite-758"], "role_words": ["mixing vat", "weighing scale"], "planted_components": ["Vat-Flint-218", "Scale-Tern-378"], "unplanted_alternatives": ["Vat-Rowan-278", "Scale-Juniper-318"]}, {"id": "lmq-cal-19", "calibration": true, "english": "Determination record CAL-819, registrar note.\nTwo determinations are recorded but not settled: the loading crane Crane-Cedar-719 is either Crane-Garnet-219 or Crane-Slate-279, and which one holds has not been settled; the receiving lane Lane-Quartz-759 is either Lane-Kestrel-319 or Lane-Umber-379, and which one holds has not been settled.", "ainglish": "Determination record CAL-819, registrar note.\nThe loading crane Crane-Cedar-719 is Crane-Garnet-219, not Crane-Slate-279. The receiving lane Lane-Quartz-759 is Lane-Umber-379, not Lane-Kestrel-319.", "question": "Which complete loading crane/receiving lane determination does this record settle?", "options": ["Only the receiving lane Lane-Quartz-759 is settled.", "Crane-Slate-279 / Lane-Kestrel-319", "Crane-Garnet-219 / Lane-Kestrel-319", "Only the loading crane Crane-Cedar-719 is settled.", "Neither determination is settled.", "Crane-Garnet-219 / Lane-Umber-379", "Crane-Slate-279 / Lane-Umber-379", "The record contradicts itself."], "answer": "Crane-Garnet-219 / Lane-Umber-379", "gold_position": 5, "roles": ["loading crane Crane-Cedar-719", "receiving lane Lane-Quartz-759"], "role_words": ["loading crane", "receiving lane"], "planted_components": ["Crane-Garnet-219", "Lane-Umber-379"], "unplanted_alternatives": ["Crane-Slate-279", "Lane-Kestrel-319"]}, {"id": "lmq-cal-20", "calibration": true, "english": "Determination record CAL-820, registrar note.\nTwo determinations are recorded but not settled: the sorting belt Belt-Flint-720 is either Belt-Juniper-220 or Belt-Tern-280, and which one holds has not been settled; the inspection bench Bench-Rowan-760 is either Bench-Larch-320 or Bench-Vesper-380, and which one holds has not been settled.", "ainglish": "Determination record CAL-820, registrar note.\nThe sorting belt Belt-Flint-720 is Belt-Juniper-220, not Belt-Tern-280. The inspection bench Bench-Rowan-760 is Bench-Vesper-380, not Bench-Larch-320.", "question": "Which complete sorting belt/inspection bench determination does this record settle?", "options": ["Only the inspection bench Bench-Rowan-760 is settled.", "The record contradicts itself.", "Belt-Juniper-220 / Bench-Vesper-380", "Belt-Tern-280 / Bench-Larch-320", "Only the sorting belt Belt-Flint-720 is settled.", "Belt-Tern-280 / Bench-Vesper-380", "Neither determination is settled.", "Belt-Juniper-220 / Bench-Larch-320"], "answer": "Belt-Juniper-220 / Bench-Vesper-380", "gold_position": 2, "roles": ["sorting belt Belt-Flint-720", "inspection bench Bench-Rowan-760"], "role_words": ["sorting belt", "inspection bench"], "planted_components": ["Belt-Juniper-220", "Bench-Vesper-380"], "unplanted_alternatives": ["Belt-Tern-280", "Bench-Larch-320"]}, {"id": "lmq-cal-21", "calibration": true, "english": "Determination record CAL-821, registrar note.\nTwo determinations are recorded but not settled: the charging dock Dock-Garnet-721 is either Dock-Kestrel-221 or Dock-Umber-281, and which one holds has not been settled; the pressure relay Relay-Slate-761 is either Relay-Marl-321 or Relay-Willow-381, and which one holds has not been settled.", "ainglish": "Determination record CAL-821, registrar note.\nThe charging dock Dock-Garnet-721 is Dock-Kestrel-221, not Dock-Umber-281. The pressure relay Relay-Slate-761 is Relay-Willow-381, not Relay-Marl-321.", "question": "Which complete charging dock/pressure relay determination does this record settle?", "options": ["Dock-Kestrel-221 / Relay-Marl-321", "Neither determination is settled.", "Only the charging dock Dock-Garnet-721 is settled.", "Dock-Umber-281 / Relay-Marl-321", "Only the pressure relay Relay-Slate-761 is settled.", "Dock-Kestrel-221 / Relay-Willow-381", "Dock-Umber-281 / Relay-Willow-381", "The record contradicts itself."], "answer": "Dock-Kestrel-221 / Relay-Willow-381", "gold_position": 5, "roles": ["charging dock Dock-Garnet-721", "pressure relay Relay-Slate-761"], "role_words": ["charging dock", "pressure relay"], "planted_components": ["Dock-Kestrel-221", "Relay-Willow-381"], "unplanted_alternatives": ["Dock-Umber-281", "Relay-Marl-321"]}, {"id": "lmq-cal-22", "calibration": true, "english": "Determination record CAL-822, registrar note.\nTwo determinations are recorded but not settled: the staging cage Cage-Juniper-722 is either Cage-Larch-222 or Cage-Vesper-282, and which one holds has not been settled; the coolant loop Loop-Tern-762 is either Loop-Onyx-322 or Loop-Yarrow-382, and which one holds has not been settled.", "ainglish": "Determination record CAL-822, registrar note.\nThe staging cage Cage-Juniper-722 is Cage-Larch-222, not Cage-Vesper-282. The coolant loop Loop-Tern-762 is Loop-Yarrow-382, not Loop-Onyx-322.", "question": "Which complete staging cage/coolant loop determination does this record settle?", "options": ["The record contradicts itself.", "Cage-Vesper-282 / Loop-Yarrow-382", "Cage-Larch-222 / Loop-Onyx-322", "Only the coolant loop Loop-Tern-762 is settled.", "Cage-Larch-222 / Loop-Yarrow-382", "Neither determination is settled.", "Only the staging cage Cage-Juniper-722 is settled.", "Cage-Vesper-282 / Loop-Onyx-322"], "answer": "Cage-Larch-222 / Loop-Yarrow-382", "gold_position": 4, "roles": ["staging cage Cage-Juniper-722", "coolant loop Loop-Tern-762"], "role_words": ["staging cage", "coolant loop"], "planted_components": ["Cage-Larch-222", "Loop-Yarrow-382"], "unplanted_alternatives": ["Cage-Vesper-282", "Loop-Onyx-322"]}, {"id": "lmq-cal-23", "calibration": true, "english": "Determination record CAL-823, registrar note.\nTwo determinations are recorded but not settled: the weighing scale Scale-Kestrel-723 is either Scale-Marl-223 or Scale-Willow-283, and which one holds has not been settled; the archive shelf Shelf-Umber-763 is either Shelf-Pyrite-323 or Shelf-Basalt-383, and which one holds has not been settled.", "ainglish": "Determination record CAL-823, registrar note.\nThe weighing scale Scale-Kestrel-723 is Scale-Marl-223, not Scale-Willow-283. The archive shelf Shelf-Umber-763 is Shelf-Basalt-383, not Shelf-Pyrite-323.", "question": "Which complete weighing scale/archive shelf determination does this record settle?", "options": ["Only the weighing scale Scale-Kestrel-723 is settled.", "Scale-Willow-283 / Shelf-Basalt-383", "Scale-Marl-223 / Shelf-Pyrite-323", "Scale-Marl-223 / Shelf-Basalt-383", "Only the archive shelf Shelf-Umber-763 is settled.", "The record contradicts itself.", "Neither determination is settled.", "Scale-Willow-283 / Shelf-Pyrite-323"], "answer": "Scale-Marl-223 / Shelf-Basalt-383", "gold_position": 3, "roles": ["weighing scale Scale-Kestrel-723", "archive shelf Shelf-Umber-763"], "role_words": ["weighing scale", "archive shelf"], "planted_components": ["Scale-Marl-223", "Shelf-Basalt-383"], "unplanted_alternatives": ["Scale-Willow-283", "Shelf-Pyrite-323"]}, {"id": "lmq-cal-24", "calibration": true, "english": "Determination record CAL-824, registrar note.\nTwo determinations are recorded but not settled: the receiving lane Lane-Larch-724 is either Lane-Onyx-224 or Lane-Yarrow-284, and which one holds has not been settled; the spare router Router-Vesper-764 is either Router-Quartz-324 or Router-Cedar-384, and which one holds has not been settled.", "ainglish": "Determination record CAL-824, registrar note.\nThe receiving lane Lane-Larch-724 is Lane-Onyx-224, not Lane-Yarrow-284. The spare router Router-Vesper-764 is Router-Cedar-384, not Router-Quartz-324.", "question": "Which complete receiving lane/spare router determination does this record settle?", "options": ["Only the spare router Router-Vesper-764 is settled.", "Only the receiving lane Lane-Larch-724 is settled.", "Lane-Onyx-224 / Router-Cedar-384", "Lane-Onyx-224 / Router-Quartz-324", "The record contradicts itself.", "Lane-Yarrow-284 / Router-Cedar-384", "Neither determination is settled.", "Lane-Yarrow-284 / Router-Quartz-324"], "answer": "Lane-Onyx-224 / Router-Cedar-384", "gold_position": 2, "roles": ["receiving lane Lane-Larch-724", "spare router Router-Vesper-764"], "role_words": ["receiving lane", "spare router"], "planted_components": ["Lane-Onyx-224", "Router-Cedar-384"], "unplanted_alternatives": ["Lane-Yarrow-284", "Router-Quartz-324"]}, {"id": "lmq-cal-25", "calibration": true, "english": "Determination record CAL-825, registrar note.\nTwo determinations are recorded but not settled: the inspection bench Bench-Marl-725 is either Bench-Pyrite-225 or Bench-Basalt-285, and which one holds has not been settled; the mixing vat Vat-Willow-765 is either Vat-Rowan-325 or Vat-Flint-385, and which one holds has not been settled.", "ainglish": "Determination record CAL-825, registrar note.\nThe inspection bench Bench-Marl-725 is Bench-Pyrite-225, not Bench-Basalt-285. The mixing vat Vat-Willow-765 is Vat-Flint-385, not Vat-Rowan-325.", "question": "Which complete inspection bench/mixing vat determination does this record settle?", "options": ["Bench-Pyrite-225 / Vat-Rowan-325", "The record contradicts itself.", "Bench-Basalt-285 / Vat-Rowan-325", "Bench-Basalt-285 / Vat-Flint-385", "Neither determination is settled.", "Only the inspection bench Bench-Marl-725 is settled.", "Only the mixing vat Vat-Willow-765 is settled.", "Bench-Pyrite-225 / Vat-Flint-385"], "answer": "Bench-Pyrite-225 / Vat-Flint-385", "gold_position": 7, "roles": ["inspection bench Bench-Marl-725", "mixing vat Vat-Willow-765"], "role_words": ["inspection bench", "mixing vat"], "planted_components": ["Bench-Pyrite-225", "Vat-Flint-385"], "unplanted_alternatives": ["Bench-Basalt-285", "Vat-Rowan-325"]}, {"id": "lmq-cal-26", "calibration": true, "english": "Determination record CAL-826, registrar note.\nTwo determinations are recorded but not settled: the pressure relay Relay-Onyx-726 is either Relay-Quartz-226 or Relay-Cedar-286, and which one holds has not been settled; the loading crane Crane-Yarrow-766 is either Crane-Slate-326 or Crane-Garnet-386, and which one holds has not been settled.", "ainglish": "Determination record CAL-826, registrar note.\nThe pressure relay Relay-Onyx-726 is Relay-Quartz-226, not Relay-Cedar-286. The loading crane Crane-Yarrow-766 is Crane-Garnet-386, not Crane-Slate-326.", "question": "Which complete pressure relay/loading crane determination does this record settle?", "options": ["Only the pressure relay Relay-Onyx-726 is settled.", "Relay-Quartz-226 / Crane-Garnet-386", "Only the loading crane Crane-Yarrow-766 is settled.", "Relay-Cedar-286 / Crane-Slate-326", "The record contradicts itself.", "Relay-Quartz-226 / Crane-Slate-326", "Neither determination is settled.", "Relay-Cedar-286 / Crane-Garnet-386"], "answer": "Relay-Quartz-226 / Crane-Garnet-386", "gold_position": 1, "roles": ["pressure relay Relay-Onyx-726", "loading crane Crane-Yarrow-766"], "role_words": ["pressure relay", "loading crane"], "planted_components": ["Relay-Quartz-226", "Crane-Garnet-386"], "unplanted_alternatives": ["Relay-Cedar-286", "Crane-Slate-326"]}, {"id": "lmq-cal-27", "calibration": true, "english": "Determination record CAL-827, registrar note.\nTwo determinations are recorded but not settled: the coolant loop Loop-Pyrite-727 is either Loop-Rowan-227 or Loop-Flint-287, and which one holds has not been settled; the sorting belt Belt-Basalt-767 is either Belt-Tern-327 or Belt-Juniper-387, and which one holds has not been settled.", "ainglish": "Determination record CAL-827, registrar note.\nThe coolant loop Loop-Pyrite-727 is Loop-Rowan-227, not Loop-Flint-287. The sorting belt Belt-Basalt-767 is Belt-Juniper-387, not Belt-Tern-327.", "question": "Which complete coolant loop/sorting belt determination does this record settle?", "options": ["Neither determination is settled.", "Loop-Flint-287 / Belt-Tern-327", "Loop-Rowan-227 / Belt-Tern-327", "Loop-Rowan-227 / Belt-Juniper-387", "Only the coolant loop Loop-Pyrite-727 is settled.", "The record contradicts itself.", "Loop-Flint-287 / Belt-Juniper-387", "Only the sorting belt Belt-Basalt-767 is settled."], "answer": "Loop-Rowan-227 / Belt-Juniper-387", "gold_position": 3, "roles": ["coolant loop Loop-Pyrite-727", "sorting belt Belt-Basalt-767"], "role_words": ["coolant loop", "sorting belt"], "planted_components": ["Loop-Rowan-227", "Belt-Juniper-387"], "unplanted_alternatives": ["Loop-Flint-287", "Belt-Tern-327"]}, {"id": "lmq-cal-28", "calibration": true, "english": "Determination record CAL-828, registrar note.\nTwo determinations are recorded but not settled: the archive shelf Shelf-Quartz-728 is either Shelf-Slate-228 or Shelf-Garnet-288, and which one holds has not been settled; the charging dock Dock-Cedar-768 is either Dock-Umber-328 or Dock-Kestrel-388, and which one holds has not been settled.", "ainglish": "Determination record CAL-828, registrar note.\nThe archive shelf Shelf-Quartz-728 is Shelf-Slate-228, not Shelf-Garnet-288. The charging dock Dock-Cedar-768 is Dock-Kestrel-388, not Dock-Umber-328.", "question": "Which complete archive shelf/charging dock determination does this record settle?", "options": ["Shelf-Slate-228 / Dock-Umber-328", "Only the archive shelf Shelf-Quartz-728 is settled.", "Shelf-Slate-228 / Dock-Kestrel-388", "Only the charging dock Dock-Cedar-768 is settled.", "Shelf-Garnet-288 / Dock-Umber-328", "Neither determination is settled.", "The record contradicts itself.", "Shelf-Garnet-288 / Dock-Kestrel-388"], "answer": "Shelf-Slate-228 / Dock-Kestrel-388", "gold_position": 2, "roles": ["archive shelf Shelf-Quartz-728", "charging dock Dock-Cedar-768"], "role_words": ["archive shelf", "charging dock"], "planted_components": ["Shelf-Slate-228", "Dock-Kestrel-388"], "unplanted_alternatives": ["Shelf-Garnet-288", "Dock-Umber-328"]}, {"id": "lmq-cal-29", "calibration": true, "english": "Determination record CAL-829, registrar note.\nTwo determinations are recorded but not settled: the spare router Router-Rowan-729 is either Router-Tern-229 or Router-Juniper-289, and which one holds has not been settled; the staging cage Cage-Flint-769 is either Cage-Vesper-329 or Cage-Larch-389, and which one holds has not been settled.", "ainglish": "Determination record CAL-829, registrar note.\nThe spare router Router-Rowan-729 is Router-Tern-229, not Router-Juniper-289. The staging cage Cage-Flint-769 is Cage-Larch-389, not Cage-Vesper-329.", "question": "Which complete spare router/staging cage determination does this record settle?", "options": ["Only the staging cage Cage-Flint-769 is settled.", "Router-Juniper-289 / Cage-Vesper-329", "Router-Tern-229 / Cage-Larch-389", "Router-Tern-229 / Cage-Vesper-329", "Router-Juniper-289 / Cage-Larch-389", "The record contradicts itself.", "Only the spare router Router-Rowan-729 is settled.", "Neither determination is settled."], "answer": "Router-Tern-229 / Cage-Larch-389", "gold_position": 2, "roles": ["spare router Router-Rowan-729", "staging cage Cage-Flint-769"], "role_words": ["spare router", "staging cage"], "planted_components": ["Router-Tern-229", "Cage-Larch-389"], "unplanted_alternatives": ["Router-Juniper-289", "Cage-Vesper-329"]}, {"id": "lmq-cal-30", "calibration": true, "english": "Determination record CAL-830, registrar note.\nTwo determinations are recorded but not settled: the mixing vat Vat-Slate-730 is either Vat-Umber-230 or Vat-Kestrel-290, and which one holds has not been settled; the weighing scale Scale-Garnet-770 is either Scale-Willow-330 or Scale-Marl-390, and which one holds has not been settled.", "ainglish": "Determination record CAL-830, registrar note.\nThe mixing vat Vat-Slate-730 is Vat-Umber-230, not Vat-Kestrel-290. The weighing scale Scale-Garnet-770 is Scale-Marl-390, not Scale-Willow-330.", "question": "Which complete mixing vat/weighing scale determination does this record settle?", "options": ["Vat-Umber-230 / Scale-Marl-390", "Only the weighing scale Scale-Garnet-770 is settled.", "Neither determination is settled.", "Vat-Umber-230 / Scale-Willow-330", "The record contradicts itself.", "Only the mixing vat Vat-Slate-730 is settled.", "Vat-Kestrel-290 / Scale-Marl-390", "Vat-Kestrel-290 / Scale-Willow-330"], "answer": "Vat-Umber-230 / Scale-Marl-390", "gold_position": 0, "roles": ["mixing vat Vat-Slate-730", "weighing scale Scale-Garnet-770"], "role_words": ["mixing vat", "weighing scale"], "planted_components": ["Vat-Umber-230", "Scale-Marl-390"], "unplanted_alternatives": ["Vat-Kestrel-290", "Scale-Willow-330"]}, {"id": "lmq-cal-31", "calibration": true, "english": "Determination record CAL-831, registrar note.\nTwo determinations are recorded but not settled: the loading crane Crane-Tern-731 is either Crane-Vesper-231 or Crane-Larch-291, and which one holds has not been settled; the receiving lane Lane-Juniper-771 is either Lane-Yarrow-331 or Lane-Onyx-391, and which one holds has not been settled.", "ainglish": "Determination record CAL-831, registrar note.\nThe loading crane Crane-Tern-731 is Crane-Vesper-231, not Crane-Larch-291. The receiving lane Lane-Juniper-771 is Lane-Onyx-391, not Lane-Yarrow-331.", "question": "Which complete loading crane/receiving lane determination does this record settle?", "options": ["Crane-Larch-291 / Lane-Onyx-391", "Crane-Larch-291 / Lane-Yarrow-331", "Crane-Vesper-231 / Lane-Onyx-391", "The record contradicts itself.", "Crane-Vesper-231 / Lane-Yarrow-331", "Only the loading crane Crane-Tern-731 is settled.", "Neither determination is settled.", "Only the receiving lane Lane-Juniper-771 is settled."], "answer": "Crane-Vesper-231 / Lane-Onyx-391", "gold_position": 2, "roles": ["loading crane Crane-Tern-731", "receiving lane Lane-Juniper-771"], "role_words": ["loading crane", "receiving lane"], "planted_components": ["Crane-Vesper-231", "Lane-Onyx-391"], "unplanted_alternatives": ["Crane-Larch-291", "Lane-Yarrow-331"]}], "sha256": "17943ea37b2bd0b76b87448c736060549069b972245c17a8a2afeae5b50f89c9"}