{
 "kind": "ainglish.panel.items.v1",
 "construct": "all-or-nothing / keep-successes",
 "note": "Seeded construction, deterministic across processes. Arms byte-identical except the final policy clause. Gold is the policy entailment and differs between forms on every item.",
 "items": [
  {
   "id": "rp73-core-all-or-nothing-p1-000",
   "english": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. all-or-nothing.",
   "question": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. Suppose the member “add cedar-role to the deployers group” fails after the members “attach the harbor-role policy to the tenant” and “grant delta-role read access to the ledger” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s000"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-000",
   "english": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. all-or-nothing.",
   "question": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. Suppose the member “add cedar-role to the deployers group” fails after the members “attach the harbor-role policy to the tenant” and “grant delta-role read access to the ledger” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s000"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-000",
   "english": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. keep-successes.",
   "question": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. Suppose the member “add cedar-role to the deployers group” fails after the members “attach the harbor-role policy to the tenant” and “grant delta-role read access to the ledger” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s000"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-000",
   "english": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. keep-successes.",
   "question": "For batch 1, add cedar-role to the deployers group, attach the harbor-role policy to the tenant, and grant delta-role read access to the ledger. Suppose the member “add cedar-role to the deployers group” fails after the members “attach the harbor-role policy to the tenant” and “grant delta-role read access to the ledger” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s000"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-001",
   "english": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. all-or-nothing.",
   "question": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. Suppose the member “rename schema.sql in the archive root” fails after the members “publish notes.rst to the artifact store” and “replace notes.rst at the mirror” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s001"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-001",
   "english": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. all-or-nothing.",
   "question": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. Suppose the member “rename schema.sql in the archive root” fails after the members “publish notes.rst to the artifact store” and “replace notes.rst at the mirror” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s001"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-001",
   "english": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. keep-successes.",
   "question": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. Suppose the member “rename schema.sql in the archive root” fails after the members “publish notes.rst to the artifact store” and “replace notes.rst at the mirror” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s001"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-001",
   "english": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. keep-successes.",
   "question": "For batch 2, publish notes.rst to the artifact store, rename schema.sql in the archive root, and replace notes.rst at the mirror. Suppose the member “rename schema.sql in the archive root” fails after the members “publish notes.rst to the artifact store” and “replace notes.rst at the mirror” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s001"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-002",
   "english": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. all-or-nothing.",
   "question": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. Suppose the member “repartition the ledger_entries table” fails after the members “rekey shipments under the tenant id” and “compact orders on the primary node” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s002"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-002",
   "english": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. all-or-nothing.",
   "question": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. Suppose the member “repartition the ledger_entries table” fails after the members “rekey shipments under the tenant id” and “compact orders on the primary node” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s002"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-002",
   "english": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. keep-successes.",
   "question": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. Suppose the member “repartition the ledger_entries table” fails after the members “rekey shipments under the tenant id” and “compact orders on the primary node” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s002"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-002",
   "english": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. keep-successes.",
   "question": "For batch 3, rekey shipments under the tenant id, compact orders on the primary node, and repartition the ledger_entries table. Suppose the member “repartition the ledger_entries table” fails after the members “rekey shipments under the tenant id” and “compact orders on the primary node” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s002"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-003",
   "english": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. all-or-nothing.",
   "question": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. Suppose the member “publish field guide to the member feed” fails after the members “release roadmap to the public index” and “send release note to the review queue” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s003"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-003",
   "english": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. all-or-nothing.",
   "question": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. Suppose the member “publish field guide to the member feed” fails after the members “release roadmap to the public index” and “send release note to the review queue” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s003"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-003",
   "english": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. keep-successes.",
   "question": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. Suppose the member “publish field guide to the member feed” fails after the members “release roadmap to the public index” and “send release note to the review queue” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s003"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-003",
   "english": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. keep-successes.",
   "question": "For batch 4, publish field guide to the member feed, release roadmap to the public index, and send release note to the review queue. Suppose the member “publish field guide to the member feed” fails after the members “release roadmap to the public index” and “send release note to the review queue” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s003"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-004",
   "english": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. all-or-nothing.",
   "question": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. Suppose the member “subscribe the security group to the alert feed” fails after the members “post the on-call summary to the channel” and “clear the release backlog notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s004"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-004",
   "english": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. all-or-nothing.",
   "question": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. Suppose the member “subscribe the security group to the alert feed” fails after the members “post the on-call summary to the channel” and “clear the release backlog notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s004"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-004",
   "english": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. keep-successes.",
   "question": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. Suppose the member “subscribe the security group to the alert feed” fails after the members “post the on-call summary to the channel” and “clear the release backlog notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s004"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-004",
   "english": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. keep-successes.",
   "question": "For batch 5, post the on-call summary to the channel, subscribe the security group to the alert feed, and clear the release backlog notice. Suppose the member “subscribe the security group to the alert feed” fails after the members “post the on-call summary to the channel” and “clear the release backlog notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s004"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-005",
   "english": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. all-or-nothing.",
   "question": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. Suppose the member “seal ledger-cold under the retention hold” fails after the members “tier media-bundle to the vault class” and “archive case-files to cold storage” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s005"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-005",
   "english": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. all-or-nothing.",
   "question": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. Suppose the member “seal ledger-cold under the retention hold” fails after the members “tier media-bundle to the vault class” and “archive case-files to cold storage” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s005"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-005",
   "english": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. keep-successes.",
   "question": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. Suppose the member “seal ledger-cold under the retention hold” fails after the members “tier media-bundle to the vault class” and “archive case-files to cold storage” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s005"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-005",
   "english": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. keep-successes.",
   "question": "For batch 6, tier media-bundle to the vault class, archive case-files to cold storage, and seal ledger-cold under the retention hold. Suppose the member “seal ledger-cold under the retention hold” fails after the members “tier media-bundle to the vault class” and “archive case-files to cold storage” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s005"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-006",
   "english": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. all-or-nothing.",
   "question": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. Suppose the member “mark entities for refresh” fails after the members “reindex the attachments collection” and “reload the tickets analyser” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s006"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-006",
   "english": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. all-or-nothing.",
   "question": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. Suppose the member “mark entities for refresh” fails after the members “reindex the attachments collection” and “reload the tickets analyser” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s006"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-006",
   "english": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. keep-successes.",
   "question": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. Suppose the member “mark entities for refresh” fails after the members “reindex the attachments collection” and “reload the tickets analyser” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s006"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-006",
   "english": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. keep-successes.",
   "question": "For batch 7, mark entities for refresh, reindex the attachments collection, and reload the tickets analyser. Suppose the member “mark entities for refresh” fails after the members “reindex the attachments collection” and “reload the tickets analyser” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s006"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-007",
   "english": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. all-or-nothing.",
   "question": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. Suppose the member “settle the safety notice invoice” fails after the members “confirm the customs entry courier pickup” and “register the safety notice certificate” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s007"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-007",
   "english": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. all-or-nothing.",
   "question": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. Suppose the member “settle the safety notice invoice” fails after the members “confirm the customs entry courier pickup” and “register the safety notice certificate” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s007"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-007",
   "english": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. keep-successes.",
   "question": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. Suppose the member “settle the safety notice invoice” fails after the members “confirm the customs entry courier pickup” and “register the safety notice certificate” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s007"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-007",
   "english": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. keep-successes.",
   "question": "For batch 8, confirm the customs entry courier pickup, settle the safety notice invoice, and register the safety notice certificate. Suppose the member “settle the safety notice invoice” fails after the members “confirm the customs entry courier pickup” and “register the safety notice certificate” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s007"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-008",
   "english": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. all-or-nothing.",
   "question": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. Suppose the member “issue garnet-role a scoped token for the vault” fails after the members “provision the ember-role service account” and “grant ember-role write access to the registry” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s008"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-008",
   "english": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. all-or-nothing.",
   "question": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. Suppose the member “issue garnet-role a scoped token for the vault” fails after the members “provision the ember-role service account” and “grant ember-role write access to the registry” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s008"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-008",
   "english": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. keep-successes.",
   "question": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. Suppose the member “issue garnet-role a scoped token for the vault” fails after the members “provision the ember-role service account” and “grant ember-role write access to the registry” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s008"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-008",
   "english": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. keep-successes.",
   "question": "For batch 9, provision the ember-role service account, grant ember-role write access to the registry, and issue garnet-role a scoped token for the vault. Suppose the member “issue garnet-role a scoped token for the vault” fails after the members “provision the ember-role service account” and “grant ember-role write access to the registry” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s008"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-009",
   "english": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. all-or-nothing.",
   "question": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. Suppose the member “publish checksums.txt to the artifact store” fails after the members “move changelog.md into the release folder” and “rename vendor.tar in the archive root” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s009"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-009",
   "english": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. all-or-nothing.",
   "question": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. Suppose the member “publish checksums.txt to the artifact store” fails after the members “move changelog.md into the release folder” and “rename vendor.tar in the archive root” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s009"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-009",
   "english": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. keep-successes.",
   "question": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. Suppose the member “publish checksums.txt to the artifact store” fails after the members “move changelog.md into the release folder” and “rename vendor.tar in the archive root” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s009"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-009",
   "english": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. keep-successes.",
   "question": "For batch 10, publish checksums.txt to the artifact store, move changelog.md into the release folder, and rename vendor.tar in the archive root. Suppose the member “publish checksums.txt to the artifact store” fails after the members “move changelog.md into the release folder” and “rename vendor.tar in the archive root” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s009"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-010",
   "english": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. all-or-nothing.",
   "question": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. Suppose the member “backfill the events column” fails after the members “copy events into the staging cluster” and “repartition the audit_log table” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s010"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-010",
   "english": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. all-or-nothing.",
   "question": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. Suppose the member “backfill the events column” fails after the members “copy events into the staging cluster” and “repartition the audit_log table” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s010"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-010",
   "english": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. keep-successes.",
   "question": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. Suppose the member “backfill the events column” fails after the members “copy events into the staging cluster” and “repartition the audit_log table” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s010"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-010",
   "english": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. keep-successes.",
   "question": "For batch 11, copy events into the staging cluster, backfill the events column, and repartition the audit_log table. Suppose the member “backfill the events column” fails after the members “copy events into the staging cluster” and “repartition the audit_log table” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s010"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-011",
   "english": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. all-or-nothing.",
   "question": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. Suppose the member “send policy draft to the review queue” fails after the members “publish incident review to the member feed” and “mirror field guide to the open archive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s011"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-011",
   "english": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. all-or-nothing.",
   "question": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. Suppose the member “send policy draft to the review queue” fails after the members “publish incident review to the member feed” and “mirror field guide to the open archive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s011"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-011",
   "english": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. keep-successes.",
   "question": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. Suppose the member “send policy draft to the review queue” fails after the members “publish incident review to the member feed” and “mirror field guide to the open archive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s011"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-011",
   "english": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. keep-successes.",
   "question": "For batch 12, publish incident review to the member feed, mirror field guide to the open archive, and send policy draft to the review queue. Suppose the member “send policy draft to the review queue” fails after the members “publish incident review to the member feed” and “mirror field guide to the open archive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s011"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-012",
   "english": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. all-or-nothing.",
   "question": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. Suppose the member “dispatch the release pager notice” fails after the members “queue the security digest” and “clear the research backlog notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s012"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-012",
   "english": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. all-or-nothing.",
   "question": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. Suppose the member “dispatch the release pager notice” fails after the members “queue the security digest” and “clear the research backlog notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s012"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-012",
   "english": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. keep-successes.",
   "question": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. Suppose the member “dispatch the release pager notice” fails after the members “queue the security digest” and “clear the research backlog notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s012"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-012",
   "english": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. keep-successes.",
   "question": "For batch 13, dispatch the release pager notice, queue the security digest, and clear the research backlog notice. Suppose the member “dispatch the release pager notice” fails after the members “queue the security digest” and “clear the research backlog notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s012"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-013",
   "english": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. all-or-nothing.",
   "question": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. Suppose the member “tier ledger-cold to the vault class” fails after the members “archive model-cards to cold storage” and “expire the contract-set snapshot” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s013"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-013",
   "english": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. all-or-nothing.",
   "question": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. Suppose the member “tier ledger-cold to the vault class” fails after the members “archive model-cards to cold storage” and “expire the contract-set snapshot” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s013"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-013",
   "english": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. keep-successes.",
   "question": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. Suppose the member “tier ledger-cold to the vault class” fails after the members “archive model-cards to cold storage” and “expire the contract-set snapshot” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s013"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-013",
   "english": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. keep-successes.",
   "question": "For batch 14, archive model-cards to cold storage, tier ledger-cold to the vault class, and expire the contract-set snapshot. Suppose the member “tier ledger-cold to the vault class” fails after the members “archive model-cards to cold storage” and “expire the contract-set snapshot” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s013"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-014",
   "english": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. all-or-nothing.",
   "question": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. Suppose the member “reload the documents analyser” fails after the members “rebuild the products index” and “shard entities across the search tier” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s014"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-014",
   "english": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. all-or-nothing.",
   "question": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. Suppose the member “reload the documents analyser” fails after the members “rebuild the products index” and “shard entities across the search tier” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s014"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-014",
   "english": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. keep-successes.",
   "question": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. Suppose the member “reload the documents analyser” fails after the members “rebuild the products index” and “shard entities across the search tier” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s014"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-014",
   "english": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. keep-successes.",
   "question": "For batch 15, rebuild the products index, shard entities across the search tier, and reload the documents analyser. Suppose the member “reload the documents analyser” fails after the members “rebuild the products index” and “shard entities across the search tier” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s014"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-015",
   "english": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. all-or-nothing.",
   "question": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. Suppose the member “lodge the customs entry application” fails after the members “book the shipping manifest slot” and “submit the safety notice filing” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s015"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-015",
   "english": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. all-or-nothing.",
   "question": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. Suppose the member “lodge the customs entry application” fails after the members “book the shipping manifest slot” and “submit the safety notice filing” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s015"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-015",
   "english": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. keep-successes.",
   "question": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. Suppose the member “lodge the customs entry application” fails after the members “book the shipping manifest slot” and “submit the safety notice filing” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s015"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-015",
   "english": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. keep-successes.",
   "question": "For batch 16, lodge the customs entry application, book the shipping manifest slot, and submit the safety notice filing. Suppose the member “lodge the customs entry application” fails after the members “book the shipping manifest slot” and “submit the safety notice filing” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s015"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-016",
   "english": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. all-or-nothing.",
   "question": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. Suppose the member “issue flint-role a scoped token for the vault” fails after the members “attach the ember-role policy to the tenant” and “grant flint-role write access to the registry” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s016"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-016",
   "english": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. all-or-nothing.",
   "question": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. Suppose the member “issue flint-role a scoped token for the vault” fails after the members “attach the ember-role policy to the tenant” and “grant flint-role write access to the registry” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s016"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-016",
   "english": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. keep-successes.",
   "question": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. Suppose the member “issue flint-role a scoped token for the vault” fails after the members “attach the ember-role policy to the tenant” and “grant flint-role write access to the registry” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s016"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-016",
   "english": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. keep-successes.",
   "question": "For batch 17, attach the ember-role policy to the tenant, issue flint-role a scoped token for the vault, and grant flint-role write access to the registry. Suppose the member “issue flint-role a scoped token for the vault” fails after the members “attach the ember-role policy to the tenant” and “grant flint-role write access to the registry” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s016"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-017",
   "english": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. all-or-nothing.",
   "question": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. Suppose the member “replace manifest.json at the mirror” fails after the members “rename build.log in the archive root” and “checksum schema.sql at the origin” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s017"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-017",
   "english": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. all-or-nothing.",
   "question": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. Suppose the member “replace manifest.json at the mirror” fails after the members “rename build.log in the archive root” and “checksum schema.sql at the origin” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s017"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-017",
   "english": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. keep-successes.",
   "question": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. Suppose the member “replace manifest.json at the mirror” fails after the members “rename build.log in the archive root” and “checksum schema.sql at the origin” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s017"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-017",
   "english": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. keep-successes.",
   "question": "For batch 18, rename build.log in the archive root, checksum schema.sql at the origin, and replace manifest.json at the mirror. Suppose the member “replace manifest.json at the mirror” fails after the members “rename build.log in the archive root” and “checksum schema.sql at the origin” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s017"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-018",
   "english": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. all-or-nothing.",
   "question": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. Suppose the member “migrate audit_log to the new schema” fails after the members “rekey sessions under the tenant id” and “compact invoices on the primary node” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s018"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-018",
   "english": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. all-or-nothing.",
   "question": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. Suppose the member “migrate audit_log to the new schema” fails after the members “rekey sessions under the tenant id” and “compact invoices on the primary node” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s018"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-018",
   "english": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. keep-successes.",
   "question": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. Suppose the member “migrate audit_log to the new schema” fails after the members “rekey sessions under the tenant id” and “compact invoices on the primary node” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s018"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-018",
   "english": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. keep-successes.",
   "question": "For batch 19, migrate audit_log to the new schema, rekey sessions under the tenant id, and compact invoices on the primary node. Suppose the member “migrate audit_log to the new schema” fails after the members “rekey sessions under the tenant id” and “compact invoices on the primary node” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s018"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-019",
   "english": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. all-or-nothing.",
   "question": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. Suppose the member “send roadmap to the review queue” fails after the members “schedule field guide for the morning digest” and “mirror field guide to the open archive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s019"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-019",
   "english": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. all-or-nothing.",
   "question": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. Suppose the member “send roadmap to the review queue” fails after the members “schedule field guide for the morning digest” and “mirror field guide to the open archive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s019"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-019",
   "english": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. keep-successes.",
   "question": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. Suppose the member “send roadmap to the review queue” fails after the members “schedule field guide for the morning digest” and “mirror field guide to the open archive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s019"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-019",
   "english": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. keep-successes.",
   "question": "For batch 20, schedule field guide for the morning digest, send roadmap to the review queue, and mirror field guide to the open archive. Suppose the member “send roadmap to the review queue” fails after the members “schedule field guide for the morning digest” and “mirror field guide to the open archive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s019"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-020",
   "english": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. all-or-nothing.",
   "question": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. Suppose the member “clear the billing backlog notice” fails after the members “post the support summary to the channel” and “notify the platform roster” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s020"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-020",
   "english": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. all-or-nothing.",
   "question": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. Suppose the member “clear the billing backlog notice” fails after the members “post the support summary to the channel” and “notify the platform roster” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s020"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-020",
   "english": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. keep-successes.",
   "question": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. Suppose the member “clear the billing backlog notice” fails after the members “post the support summary to the channel” and “notify the platform roster” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s020"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-020",
   "english": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. keep-successes.",
   "question": "For batch 21, post the support summary to the channel, notify the platform roster, and clear the billing backlog notice. Suppose the member “clear the billing backlog notice” fails after the members “post the support summary to the channel” and “notify the platform roster” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s020"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-021",
   "english": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. all-or-nothing.",
   "question": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. Suppose the member “expire the survey-wave snapshot” fails after the members “seal raw-telemetry under the retention hold” and “archive case-files to cold storage” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s021"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-021",
   "english": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. all-or-nothing.",
   "question": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. Suppose the member “expire the survey-wave snapshot” fails after the members “seal raw-telemetry under the retention hold” and “archive case-files to cold storage” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s021"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-021",
   "english": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. keep-successes.",
   "question": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. Suppose the member “expire the survey-wave snapshot” fails after the members “seal raw-telemetry under the retention hold” and “archive case-files to cold storage” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s021"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-021",
   "english": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. keep-successes.",
   "question": "For batch 22, expire the survey-wave snapshot, seal raw-telemetry under the retention hold, and archive case-files to cold storage. Suppose the member “expire the survey-wave snapshot” fails after the members “seal raw-telemetry under the retention hold” and “archive case-files to cold storage” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s021"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-022",
   "english": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. all-or-nothing.",
   "question": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. Suppose the member “mark products for refresh” fails after the members “rebuild the snippets index” and “reindex the attachments collection” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s022"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-022",
   "english": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. all-or-nothing.",
   "question": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. Suppose the member “mark products for refresh” fails after the members “rebuild the snippets index” and “reindex the attachments collection” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s022"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-022",
   "english": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. keep-successes.",
   "question": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. Suppose the member “mark products for refresh” fails after the members “rebuild the snippets index” and “reindex the attachments collection” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s022"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-022",
   "english": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. keep-successes.",
   "question": "For batch 23, rebuild the snippets index, mark products for refresh, and reindex the attachments collection. Suppose the member “mark products for refresh” fails after the members “rebuild the snippets index” and “reindex the attachments collection” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s022"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-023",
   "english": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. all-or-nothing.",
   "question": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. Suppose the member “settle the tax filing invoice” fails after the members “submit the safety notice filing” and “lodge the tax filing application” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s023"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-023",
   "english": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. all-or-nothing.",
   "question": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. Suppose the member “settle the tax filing invoice” fails after the members “submit the safety notice filing” and “lodge the tax filing application” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s023"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-023",
   "english": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. keep-successes.",
   "question": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. Suppose the member “settle the tax filing invoice” fails after the members “submit the safety notice filing” and “lodge the tax filing application” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s023"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-023",
   "english": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. keep-successes.",
   "question": "For batch 24, submit the safety notice filing, lodge the tax filing application, and settle the tax filing invoice. Suppose the member “settle the tax filing invoice” fails after the members “submit the safety notice filing” and “lodge the tax filing application” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s023"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-024",
   "english": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. all-or-nothing.",
   "question": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. Suppose the member “attach the delta-role policy to the tenant” fails after the members “add beacon-role to the deployers group” and “grant delta-role read access to the ledger” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s024"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-024",
   "english": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. all-or-nothing.",
   "question": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. Suppose the member “attach the delta-role policy to the tenant” fails after the members “add beacon-role to the deployers group” and “grant delta-role read access to the ledger” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s024"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-024",
   "english": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. keep-successes.",
   "question": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. Suppose the member “attach the delta-role policy to the tenant” fails after the members “add beacon-role to the deployers group” and “grant delta-role read access to the ledger” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s024"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-024",
   "english": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. keep-successes.",
   "question": "For batch 25, attach the delta-role policy to the tenant, add beacon-role to the deployers group, and grant delta-role read access to the ledger. Suppose the member “attach the delta-role policy to the tenant” fails after the members “add beacon-role to the deployers group” and “grant delta-role read access to the ledger” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s024"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-025",
   "english": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. all-or-nothing.",
   "question": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. Suppose the member “checksum schema.sql at the origin” fails after the members “move notes.rst into the release folder” and “replace changelog.md at the mirror” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s025"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-025",
   "english": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. all-or-nothing.",
   "question": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. Suppose the member “checksum schema.sql at the origin” fails after the members “move notes.rst into the release folder” and “replace changelog.md at the mirror” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s025"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-025",
   "english": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. keep-successes.",
   "question": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. Suppose the member “checksum schema.sql at the origin” fails after the members “move notes.rst into the release folder” and “replace changelog.md at the mirror” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s025"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-025",
   "english": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. keep-successes.",
   "question": "For batch 26, move notes.rst into the release folder, checksum schema.sql at the origin, and replace changelog.md at the mirror. Suppose the member “checksum schema.sql at the origin” fails after the members “move notes.rst into the release folder” and “replace changelog.md at the mirror” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s025"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-026",
   "english": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. all-or-nothing.",
   "question": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. Suppose the member “rekey orders under the tenant id” fails after the members “repartition the invoices table” and “backfill the orders column” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s026"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-026",
   "english": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. all-or-nothing.",
   "question": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. Suppose the member “rekey orders under the tenant id” fails after the members “repartition the invoices table” and “backfill the orders column” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s026"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-026",
   "english": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. keep-successes.",
   "question": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. Suppose the member “rekey orders under the tenant id” fails after the members “repartition the invoices table” and “backfill the orders column” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s026"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-026",
   "english": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. keep-successes.",
   "question": "For batch 27, repartition the invoices table, backfill the orders column, and rekey orders under the tenant id. Suppose the member “rekey orders under the tenant id” fails after the members “repartition the invoices table” and “backfill the orders column” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s026"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-027",
   "english": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. all-or-nothing.",
   "question": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. Suppose the member “publish benchmark report to the member feed” fails after the members “pin design memo on the project page” and “send errata to the review queue” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s027"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-027",
   "english": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. all-or-nothing.",
   "question": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. Suppose the member “publish benchmark report to the member feed” fails after the members “pin design memo on the project page” and “send errata to the review queue” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s027"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-027",
   "english": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. keep-successes.",
   "question": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. Suppose the member “publish benchmark report to the member feed” fails after the members “pin design memo on the project page” and “send errata to the review queue” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s027"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-027",
   "english": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. keep-successes.",
   "question": "For batch 28, publish benchmark report to the member feed, pin design memo on the project page, and send errata to the review queue. Suppose the member “publish benchmark report to the member feed” fails after the members “pin design memo on the project page” and “send errata to the review queue” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "core",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s027"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-028",
   "english": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. all-or-nothing.",
   "question": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. Suppose the member “dispatch the security pager notice” fails after the members “queue the security digest” and “subscribe the billing group to the alert feed” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s028"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-028",
   "english": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. all-or-nothing.",
   "question": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. Suppose the member “dispatch the security pager notice” fails after the members “queue the security digest” and “subscribe the billing group to the alert feed” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s028"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-028",
   "english": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. keep-successes.",
   "question": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. Suppose the member “dispatch the security pager notice” fails after the members “queue the security digest” and “subscribe the billing group to the alert feed” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s028"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-028",
   "english": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. keep-successes.",
   "question": "For batch 29, queue the security digest, dispatch the security pager notice, and subscribe the billing group to the alert feed. Suppose the member “dispatch the security pager notice” fails after the members “queue the security digest” and “subscribe the billing group to the alert feed” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "core",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s028"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p1-029",
   "english": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. all-or-nothing.",
   "question": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. Suppose the member “archive survey-wave to cold storage” fails after the members “expire the model-cards snapshot” and “tier trip-archive to the vault class” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s029"
   }
  },
  {
   "id": "rp73-core-all-or-nothing-p2-029",
   "english": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. all-or-nothing.",
   "question": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. Suppose the member “archive survey-wave to cold storage” fails after the members “expire the model-cards snapshot” and “tier trip-archive to the vault class” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s029"
   }
  },
  {
   "id": "rp73-core-keep-successes-p1-029",
   "english": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. keep-successes.",
   "question": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. Suppose the member “archive survey-wave to cold storage” fails after the members “expire the model-cards snapshot” and “tier trip-archive to the vault class” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s029"
   }
  },
  {
   "id": "rp73-core-keep-successes-p2-029",
   "english": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. keep-successes.",
   "question": "For batch 30, expire the model-cards snapshot, tier trip-archive to the vault class, and archive survey-wave to cold storage. Suppose the member “archive survey-wave to cold storage” fails after the members “expire the model-cards snapshot” and “tier trip-archive to the vault class” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "core",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s029"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p1-030",
   "english": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “reindex the attachments collection” fails after the members “mark transcripts for refresh” and “rebuild the tickets index” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s030"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p2-030",
   "english": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “reindex the attachments collection” fails after the members “mark transcripts for refresh” and “rebuild the tickets index” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s030"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p1-030",
   "english": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “reindex the attachments collection” fails after the members “mark transcripts for refresh” and “rebuild the tickets index” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s030"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p2-030",
   "english": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 31, reindex the attachments collection, mark transcripts for refresh, and rebuild the tickets index. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “reindex the attachments collection” fails after the members “mark transcripts for refresh” and “rebuild the tickets index” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s030"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p1-031",
   "english": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “submit the shipping manifest filing” fails after the members “register the safety notice certificate” and “book the safety notice slot” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s031"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p2-031",
   "english": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “submit the shipping manifest filing” fails after the members “register the safety notice certificate” and “book the safety notice slot” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s031"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p1-031",
   "english": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “submit the shipping manifest filing” fails after the members “register the safety notice certificate” and “book the safety notice slot” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s031"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p2-031",
   "english": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 32, register the safety notice certificate, submit the shipping manifest filing, and book the safety notice slot. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “submit the shipping manifest filing” fails after the members “register the safety notice certificate” and “book the safety notice slot” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s031"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p1-032",
   "english": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “add delta-role to the deployers group” fails after the members “provision the garnet-role service account” and “issue ember-role a scoped token for the vault” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s032"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p2-032",
   "english": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “add delta-role to the deployers group” fails after the members “provision the garnet-role service account” and “issue ember-role a scoped token for the vault” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s032"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p1-032",
   "english": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “add delta-role to the deployers group” fails after the members “provision the garnet-role service account” and “issue ember-role a scoped token for the vault” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s032"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p2-032",
   "english": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 33, provision the garnet-role service account, issue ember-role a scoped token for the vault, and add delta-role to the deployers group. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “add delta-role to the deployers group” fails after the members “provision the garnet-role service account” and “issue ember-role a scoped token for the vault” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s032"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p1-033",
   "english": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “move schema.sql into the release folder” fails after the members “write build.log to the shared drive” and “publish release.toml to the artifact store” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s033"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p2-033",
   "english": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “move schema.sql into the release folder” fails after the members “write build.log to the shared drive” and “publish release.toml to the artifact store” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s033"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p1-033",
   "english": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “move schema.sql into the release folder” fails after the members “write build.log to the shared drive” and “publish release.toml to the artifact store” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s033"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p2-033",
   "english": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 34, move schema.sql into the release folder, write build.log to the shared drive, and publish release.toml to the artifact store. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “move schema.sql into the release folder” fails after the members “write build.log to the shared drive” and “publish release.toml to the artifact store” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s033"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p1-034",
   "english": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “compact sessions on the primary node” fails after the members “rekey sessions under the tenant id” and “migrate invoices to the new schema” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s034"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p2-034",
   "english": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “compact sessions on the primary node” fails after the members “rekey sessions under the tenant id” and “migrate invoices to the new schema” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s034"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p1-034",
   "english": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “compact sessions on the primary node” fails after the members “rekey sessions under the tenant id” and “migrate invoices to the new schema” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s034"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p2-034",
   "english": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 35, rekey sessions under the tenant id, compact sessions on the primary node, and migrate invoices to the new schema. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “compact sessions on the primary node” fails after the members “rekey sessions under the tenant id” and “migrate invoices to the new schema” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s034"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p1-035",
   "english": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “mirror design memo to the open archive” fails after the members “pin benchmark report on the project page” and “send incident review to the review queue” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s035"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p2-035",
   "english": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “mirror design memo to the open archive” fails after the members “pin benchmark report on the project page” and “send incident review to the review queue” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s035"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p1-035",
   "english": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “mirror design memo to the open archive” fails after the members “pin benchmark report on the project page” and “send incident review to the review queue” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s035"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p2-035",
   "english": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 36, pin benchmark report on the project page, send incident review to the review queue, and mirror design memo to the open archive. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “mirror design memo to the open archive” fails after the members “pin benchmark report on the project page” and “send incident review to the review queue” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s035"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p1-036",
   "english": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “post the security summary to the channel” fails after the members “queue the release digest” and “subscribe the platform group to the alert feed” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s036"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p2-036",
   "english": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “post the security summary to the channel” fails after the members “queue the release digest” and “subscribe the platform group to the alert feed” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s036"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p1-036",
   "english": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “post the security summary to the channel” fails after the members “queue the release digest” and “subscribe the platform group to the alert feed” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s036"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p2-036",
   "english": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 37, post the security summary to the channel, queue the release digest, and subscribe the platform group to the alert feed. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “post the security summary to the channel” fails after the members “queue the release digest” and “subscribe the platform group to the alert feed” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s036"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p1-037",
   "english": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “expire the case-files snapshot” fails after the members “attest the ledger-cold manifest” and “archive contract-set to cold storage” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s037"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p2-037",
   "english": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “expire the case-files snapshot” fails after the members “attest the ledger-cold manifest” and “archive contract-set to cold storage” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s037"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p1-037",
   "english": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “expire the case-files snapshot” fails after the members “attest the ledger-cold manifest” and “archive contract-set to cold storage” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s037"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p2-037",
   "english": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 38, attest the ledger-cold manifest, expire the case-files snapshot, and archive contract-set to cold storage. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “expire the case-files snapshot” fails after the members “attest the ledger-cold manifest” and “archive contract-set to cold storage” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s037"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p1-038",
   "english": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “snapshot the products inverted list” fails after the members “reindex the documents collection” and “mark transcripts for refresh” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s038"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p2-038",
   "english": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “snapshot the products inverted list” fails after the members “reindex the documents collection” and “mark transcripts for refresh” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s038"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p1-038",
   "english": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “snapshot the products inverted list” fails after the members “reindex the documents collection” and “mark transcripts for refresh” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s038"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p2-038",
   "english": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 39, reindex the documents collection, mark transcripts for refresh, and snapshot the products inverted list. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “snapshot the products inverted list” fails after the members “reindex the documents collection” and “mark transcripts for refresh” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s038"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p1-039",
   "english": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “register the safety notice certificate” fails after the members “book the venue permit slot” and “settle the trademark renewal invoice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s039"
   }
  },
  {
   "id": "rp73-staged-all-or-nothing-p2-039",
   "english": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. all-or-nothing.",
   "question": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “register the safety notice certificate” fails after the members “book the venue permit slot” and “settle the trademark renewal invoice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s039"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p1-039",
   "english": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “register the safety notice certificate” fails after the members “book the venue permit slot” and “settle the trademark renewal invoice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "staged",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s039"
   }
  },
  {
   "id": "rp73-staged-keep-successes-p2-039",
   "english": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. keep-successes.",
   "question": "For batch 40, register the safety notice certificate, book the venue permit slot, and settle the trademark renewal invoice. The first member's effect is staged first and committed only after the staging check passes. Suppose the member “register the safety notice certificate” fails after the members “book the venue permit slot” and “settle the trademark renewal invoice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "staged",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s039"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p1-040",
   "english": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “grant beacon-role write access to the registry” fails after the members “attach the harbor-role policy to the tenant” and “provision the delta-role service account” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s040"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p2-040",
   "english": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “grant beacon-role write access to the registry” fails after the members “attach the harbor-role policy to the tenant” and “provision the delta-role service account” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s040"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p1-040",
   "english": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “grant beacon-role write access to the registry” fails after the members “attach the harbor-role policy to the tenant” and “provision the delta-role service account” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s040"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p2-040",
   "english": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 41, attach the harbor-role policy to the tenant, grant beacon-role write access to the registry, and provision the delta-role service account. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “grant beacon-role write access to the registry” fails after the members “attach the harbor-role policy to the tenant” and “provision the delta-role service account” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s040"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p1-041",
   "english": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “checksum schema.sql at the origin” fails after the members “write release.toml to the shared drive” and “replace release.toml at the mirror” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s041"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p2-041",
   "english": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “checksum schema.sql at the origin” fails after the members “write release.toml to the shared drive” and “replace release.toml at the mirror” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s041"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p1-041",
   "english": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “checksum schema.sql at the origin” fails after the members “write release.toml to the shared drive” and “replace release.toml at the mirror” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s041"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p2-041",
   "english": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 42, write release.toml to the shared drive, replace release.toml at the mirror, and checksum schema.sql at the origin. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “checksum schema.sql at the origin” fails after the members “write release.toml to the shared drive” and “replace release.toml at the mirror” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s041"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p1-042",
   "english": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “migrate events to the new schema” fails after the members “rekey orders under the tenant id” and “backfill the ledger_entries column” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s042"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p2-042",
   "english": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “migrate events to the new schema” fails after the members “rekey orders under the tenant id” and “backfill the ledger_entries column” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s042"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p1-042",
   "english": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “migrate events to the new schema” fails after the members “rekey orders under the tenant id” and “backfill the ledger_entries column” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s042"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p2-042",
   "english": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 43, migrate events to the new schema, rekey orders under the tenant id, and backfill the ledger_entries column. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “migrate events to the new schema” fails after the members “rekey orders under the tenant id” and “backfill the ledger_entries column” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s042"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p1-043",
   "english": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “publish design memo to the member feed” fails after the members “pin benchmark report on the project page” and “mirror policy draft to the open archive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s043"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p2-043",
   "english": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “publish design memo to the member feed” fails after the members “pin benchmark report on the project page” and “mirror policy draft to the open archive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s043"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p1-043",
   "english": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “publish design memo to the member feed” fails after the members “pin benchmark report on the project page” and “mirror policy draft to the open archive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s043"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p2-043",
   "english": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 44, pin benchmark report on the project page, publish design memo to the member feed, and mirror policy draft to the open archive. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “publish design memo to the member feed” fails after the members “pin benchmark report on the project page” and “mirror policy draft to the open archive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s043"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p1-044",
   "english": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “subscribe the billing group to the alert feed” fails after the members “queue the platform digest” and “clear the platform backlog notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s044"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p2-044",
   "english": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “subscribe the billing group to the alert feed” fails after the members “queue the platform digest” and “clear the platform backlog notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s044"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p1-044",
   "english": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “subscribe the billing group to the alert feed” fails after the members “queue the platform digest” and “clear the platform backlog notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s044"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p2-044",
   "english": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 45, queue the platform digest, clear the platform backlog notice, and subscribe the billing group to the alert feed. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “subscribe the billing group to the alert feed” fails after the members “queue the platform digest” and “clear the platform backlog notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s044"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p1-045",
   "english": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “seal raw-telemetry under the retention hold” fails after the members “freeze raw-telemetry at the current revision” and “tier survey-wave to the vault class” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s045"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p2-045",
   "english": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “seal raw-telemetry under the retention hold” fails after the members “freeze raw-telemetry at the current revision” and “tier survey-wave to the vault class” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s045"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p1-045",
   "english": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “seal raw-telemetry under the retention hold” fails after the members “freeze raw-telemetry at the current revision” and “tier survey-wave to the vault class” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s045"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p2-045",
   "english": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 46, seal raw-telemetry under the retention hold, freeze raw-telemetry at the current revision, and tier survey-wave to the vault class. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “seal raw-telemetry under the retention hold” fails after the members “freeze raw-telemetry at the current revision” and “tier survey-wave to the vault class” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s045"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p1-046",
   "english": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “reload the entities analyser” fails after the members “reindex the documents collection” and “shard products across the search tier” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s046"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p2-046",
   "english": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “reload the entities analyser” fails after the members “reindex the documents collection” and “shard products across the search tier” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s046"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p1-046",
   "english": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “reload the entities analyser” fails after the members “reindex the documents collection” and “shard products across the search tier” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s046"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p2-046",
   "english": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 47, reindex the documents collection, reload the entities analyser, and shard products across the search tier. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “reload the entities analyser” fails after the members “reindex the documents collection” and “shard products across the search tier” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s046"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p1-047",
   "english": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “settle the grant application invoice” fails after the members “lodge the grant application application” and “book the shipping manifest slot” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s047"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p2-047",
   "english": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “settle the grant application invoice” fails after the members “lodge the grant application application” and “book the shipping manifest slot” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s047"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p1-047",
   "english": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “settle the grant application invoice” fails after the members “lodge the grant application application” and “book the shipping manifest slot” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s047"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p2-047",
   "english": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 48, lodge the grant application application, book the shipping manifest slot, and settle the grant application invoice. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “settle the grant application invoice” fails after the members “lodge the grant application application” and “book the shipping manifest slot” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s047"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p1-048",
   "english": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “attach the cedar-role policy to the tenant” fails after the members “grant ember-role write access to the registry” and “provision the beacon-role service account” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s048"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p2-048",
   "english": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “attach the cedar-role policy to the tenant” fails after the members “grant ember-role write access to the registry” and “provision the beacon-role service account” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s048"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p1-048",
   "english": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “attach the cedar-role policy to the tenant” fails after the members “grant ember-role write access to the registry” and “provision the beacon-role service account” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s048"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p2-048",
   "english": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 49, attach the cedar-role policy to the tenant, grant ember-role write access to the registry, and provision the beacon-role service account. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “attach the cedar-role policy to the tenant” fails after the members “grant ember-role write access to the registry” and “provision the beacon-role service account” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s048"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p1-049",
   "english": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “rename manifest.json in the archive root” fails after the members “replace notes.rst at the mirror” and “publish checksums.txt to the artifact store” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s049"
   }
  },
  {
   "id": "rp73-reversible-all-or-nothing-p2-049",
   "english": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. all-or-nothing.",
   "question": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “rename manifest.json in the archive root” fails after the members “replace notes.rst at the mirror” and “publish checksums.txt to the artifact store” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s049"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p1-049",
   "english": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “rename manifest.json in the archive root” fails after the members “replace notes.rst at the mirror” and “publish checksums.txt to the artifact store” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "reversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s049"
   }
  },
  {
   "id": "rp73-reversible-keep-successes-p2-049",
   "english": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. keep-successes.",
   "question": "For batch 50, replace notes.rst at the mirror, rename manifest.json in the archive root, and publish checksums.txt to the artifact store. The second member's effect is compensable: a matching reversal action exists and is available. Suppose the member “rename manifest.json in the archive root” fails after the members “replace notes.rst at the mirror” and “publish checksums.txt to the artifact store” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "reversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s049"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p1-050",
   "english": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “compact events on the primary node” fails after the members “migrate telemetry to the new schema” and “repartition the sessions table” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s050"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p2-050",
   "english": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “compact events on the primary node” fails after the members “migrate telemetry to the new schema” and “repartition the sessions table” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s050"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p1-050",
   "english": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “compact events on the primary node” fails after the members “migrate telemetry to the new schema” and “repartition the sessions table” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s050"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p2-050",
   "english": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 51, migrate telemetry to the new schema, repartition the sessions table, and compact events on the primary node. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “compact events on the primary node” fails after the members “migrate telemetry to the new schema” and “repartition the sessions table” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s050"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p1-051",
   "english": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “pin incident review on the project page” fails after the members “publish policy draft to the member feed” and “schedule policy draft for the morning digest” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s051"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p2-051",
   "english": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “pin incident review on the project page” fails after the members “publish policy draft to the member feed” and “schedule policy draft for the morning digest” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s051"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p1-051",
   "english": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “pin incident review on the project page” fails after the members “publish policy draft to the member feed” and “schedule policy draft for the morning digest” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s051"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p2-051",
   "english": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 52, pin incident review on the project page, publish policy draft to the member feed, and schedule policy draft for the morning digest. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “pin incident review on the project page” fails after the members “publish policy draft to the member feed” and “schedule policy draft for the morning digest” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s051"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p1-052",
   "english": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “subscribe the on-call group to the alert feed” fails after the members “clear the support backlog notice” and “post the on-call summary to the channel” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s052"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p2-052",
   "english": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “subscribe the on-call group to the alert feed” fails after the members “clear the support backlog notice” and “post the on-call summary to the channel” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s052"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p1-052",
   "english": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “subscribe the on-call group to the alert feed” fails after the members “clear the support backlog notice” and “post the on-call summary to the channel” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s052"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p2-052",
   "english": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 53, clear the support backlog notice, subscribe the on-call group to the alert feed, and post the on-call summary to the channel. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “subscribe the on-call group to the alert feed” fails after the members “clear the support backlog notice” and “post the on-call summary to the channel” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s052"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p1-053",
   "english": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “expire the raw-telemetry snapshot” fails after the members “archive ledger-cold to cold storage” and “tier survey-wave to the vault class” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s053"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p2-053",
   "english": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “expire the raw-telemetry snapshot” fails after the members “archive ledger-cold to cold storage” and “tier survey-wave to the vault class” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s053"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p1-053",
   "english": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “expire the raw-telemetry snapshot” fails after the members “archive ledger-cold to cold storage” and “tier survey-wave to the vault class” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s053"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p2-053",
   "english": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 54, archive ledger-cold to cold storage, tier survey-wave to the vault class, and expire the raw-telemetry snapshot. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “expire the raw-telemetry snapshot” fails after the members “archive ledger-cold to cold storage” and “tier survey-wave to the vault class” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s053"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p1-054",
   "english": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “reindex the tickets collection” fails after the members “snapshot the entities inverted list” and “shard tickets across the search tier” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s054"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p2-054",
   "english": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “reindex the tickets collection” fails after the members “snapshot the entities inverted list” and “shard tickets across the search tier” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s054"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p1-054",
   "english": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “reindex the tickets collection” fails after the members “snapshot the entities inverted list” and “shard tickets across the search tier” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s054"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p2-054",
   "english": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 55, reindex the tickets collection, snapshot the entities inverted list, and shard tickets across the search tier. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “reindex the tickets collection” fails after the members “snapshot the entities inverted list” and “shard tickets across the search tier” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s054"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p1-055",
   "english": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “book the safety notice slot” fails after the members “register the safety notice certificate” and “confirm the venue permit courier pickup” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s055"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p2-055",
   "english": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “book the safety notice slot” fails after the members “register the safety notice certificate” and “confirm the venue permit courier pickup” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s055"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p1-055",
   "english": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “book the safety notice slot” fails after the members “register the safety notice certificate” and “confirm the venue permit courier pickup” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s055"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p2-055",
   "english": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 56, register the safety notice certificate, book the safety notice slot, and confirm the venue permit courier pickup. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “book the safety notice slot” fails after the members “register the safety notice certificate” and “confirm the venue permit courier pickup” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s055"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p1-056",
   "english": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “attach the atlas-role policy to the tenant” fails after the members “grant beacon-role write access to the registry” and “grant flint-role read access to the ledger” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s056"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p2-056",
   "english": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “attach the atlas-role policy to the tenant” fails after the members “grant beacon-role write access to the registry” and “grant flint-role read access to the ledger” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s056"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p1-056",
   "english": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “attach the atlas-role policy to the tenant” fails after the members “grant beacon-role write access to the registry” and “grant flint-role read access to the ledger” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s056"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p2-056",
   "english": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 57, grant beacon-role write access to the registry, grant flint-role read access to the ledger, and attach the atlas-role policy to the tenant. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “attach the atlas-role policy to the tenant” fails after the members “grant beacon-role write access to the registry” and “grant flint-role read access to the ledger” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s056"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p1-057",
   "english": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “checksum vendor.tar at the origin” fails after the members “write manifest.json to the shared drive” and “publish release.toml to the artifact store” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s057"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p2-057",
   "english": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “checksum vendor.tar at the origin” fails after the members “write manifest.json to the shared drive” and “publish release.toml to the artifact store” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s057"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p1-057",
   "english": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “checksum vendor.tar at the origin” fails after the members “write manifest.json to the shared drive” and “publish release.toml to the artifact store” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s057"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p2-057",
   "english": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 58, checksum vendor.tar at the origin, write manifest.json to the shared drive, and publish release.toml to the artifact store. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “checksum vendor.tar at the origin” fails after the members “write manifest.json to the shared drive” and “publish release.toml to the artifact store” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s057"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p1-058",
   "english": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “compact shipments on the primary node” fails after the members “copy telemetry into the staging cluster” and “repartition the invoices table” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s058"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p2-058",
   "english": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “compact shipments on the primary node” fails after the members “copy telemetry into the staging cluster” and “repartition the invoices table” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s058"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p1-058",
   "english": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “compact shipments on the primary node” fails after the members “copy telemetry into the staging cluster” and “repartition the invoices table” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s058"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p2-058",
   "english": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 59, copy telemetry into the staging cluster, compact shipments on the primary node, and repartition the invoices table. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “compact shipments on the primary node” fails after the members “copy telemetry into the staging cluster” and “repartition the invoices table” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s058"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p1-059",
   "english": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “send policy draft to the review queue” fails after the members “mirror field guide to the open archive” and “publish roadmap to the member feed” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s059"
   }
  },
  {
   "id": "rp73-irreversible-all-or-nothing-p2-059",
   "english": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. all-or-nothing.",
   "question": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “send policy draft to the review queue” fails after the members “mirror field guide to the open archive” and “publish roadmap to the member feed” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s059"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p1-059",
   "english": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “send policy draft to the review queue” fails after the members “mirror field guide to the open archive” and “publish roadmap to the member feed” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "irreversible",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s059"
   }
  },
  {
   "id": "rp73-irreversible-keep-successes-p2-059",
   "english": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. keep-successes.",
   "question": "For batch 60, mirror field guide to the open archive, publish roadmap to the member feed, and send policy draft to the review queue. The second member's effect is irreversible once committed; no reversal action exists for it. Suppose the member “send policy draft to the review queue” fails after the members “mirror field guide to the open archive” and “publish roadmap to the member feed” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "irreversible",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s059"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p1-060",
   "english": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “dispatch the security pager notice” fails after the members “post the on-call summary to the channel” and “clear the research backlog notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s060"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p2-060",
   "english": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “dispatch the security pager notice” fails after the members “post the on-call summary to the channel” and “clear the research backlog notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s060"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p1-060",
   "english": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “dispatch the security pager notice” fails after the members “post the on-call summary to the channel” and “clear the research backlog notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s060"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p2-060",
   "english": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 61, dispatch the security pager notice, post the on-call summary to the channel, and clear the research backlog notice. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “dispatch the security pager notice” fails after the members “post the on-call summary to the channel” and “clear the research backlog notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s060"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p1-061",
   "english": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “archive case-files to cold storage” fails after the members “tier survey-wave to the vault class” and “expire the contract-set snapshot” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s061"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p2-061",
   "english": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “archive case-files to cold storage” fails after the members “tier survey-wave to the vault class” and “expire the contract-set snapshot” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s061"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p1-061",
   "english": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “archive case-files to cold storage” fails after the members “tier survey-wave to the vault class” and “expire the contract-set snapshot” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s061"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p2-061",
   "english": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 62, tier survey-wave to the vault class, archive case-files to cold storage, and expire the contract-set snapshot. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “archive case-files to cold storage” fails after the members “tier survey-wave to the vault class” and “expire the contract-set snapshot” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s061"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p1-062",
   "english": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “shard documents across the search tier” fails after the members “snapshot the products inverted list” and “reload the catalog analyser” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s062"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p2-062",
   "english": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “shard documents across the search tier” fails after the members “snapshot the products inverted list” and “reload the catalog analyser” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s062"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p1-062",
   "english": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “shard documents across the search tier” fails after the members “snapshot the products inverted list” and “reload the catalog analyser” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s062"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p2-062",
   "english": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 63, snapshot the products inverted list, reload the catalog analyser, and shard documents across the search tier. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “shard documents across the search tier” fails after the members “snapshot the products inverted list” and “reload the catalog analyser” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s062"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p1-063",
   "english": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “confirm the tax filing courier pickup” fails after the members “register the annual return certificate” and “settle the venue permit invoice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s063"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p2-063",
   "english": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “confirm the tax filing courier pickup” fails after the members “register the annual return certificate” and “settle the venue permit invoice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s063"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p1-063",
   "english": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “confirm the tax filing courier pickup” fails after the members “register the annual return certificate” and “settle the venue permit invoice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s063"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p2-063",
   "english": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 64, confirm the tax filing courier pickup, register the annual return certificate, and settle the venue permit invoice. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “confirm the tax filing courier pickup” fails after the members “register the annual return certificate” and “settle the venue permit invoice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s063"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p1-064",
   "english": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “provision the ember-role service account” fails after the members “issue atlas-role a scoped token for the vault” and “attach the ember-role policy to the tenant” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s064"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p2-064",
   "english": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “provision the ember-role service account” fails after the members “issue atlas-role a scoped token for the vault” and “attach the ember-role policy to the tenant” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s064"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p1-064",
   "english": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “provision the ember-role service account” fails after the members “issue atlas-role a scoped token for the vault” and “attach the ember-role policy to the tenant” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s064"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p2-064",
   "english": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 65, issue atlas-role a scoped token for the vault, provision the ember-role service account, and attach the ember-role policy to the tenant. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “provision the ember-role service account” fails after the members “issue atlas-role a scoped token for the vault” and “attach the ember-role policy to the tenant” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s064"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p1-065",
   "english": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “move schema.sql into the release folder” fails after the members “write vendor.tar to the shared drive” and “checksum manifest.json at the origin” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s065"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p2-065",
   "english": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “move schema.sql into the release folder” fails after the members “write vendor.tar to the shared drive” and “checksum manifest.json at the origin” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s065"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p1-065",
   "english": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “move schema.sql into the release folder” fails after the members “write vendor.tar to the shared drive” and “checksum manifest.json at the origin” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s065"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p2-065",
   "english": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 66, write vendor.tar to the shared drive, checksum manifest.json at the origin, and move schema.sql into the release folder. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “move schema.sql into the release folder” fails after the members “write vendor.tar to the shared drive” and “checksum manifest.json at the origin” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s065"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p1-066",
   "english": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “repartition the invoices table” fails after the members “rekey shipments under the tenant id” and “migrate events to the new schema” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s066"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p2-066",
   "english": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “repartition the invoices table” fails after the members “rekey shipments under the tenant id” and “migrate events to the new schema” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s066"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p1-066",
   "english": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “repartition the invoices table” fails after the members “rekey shipments under the tenant id” and “migrate events to the new schema” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s066"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p2-066",
   "english": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 67, repartition the invoices table, rekey shipments under the tenant id, and migrate events to the new schema. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “repartition the invoices table” fails after the members “rekey shipments under the tenant id” and “migrate events to the new schema” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s066"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p1-067",
   "english": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “send incident review to the review queue” fails after the members “publish benchmark report to the member feed” and “mirror errata to the open archive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s067"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p2-067",
   "english": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “send incident review to the review queue” fails after the members “publish benchmark report to the member feed” and “mirror errata to the open archive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s067"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p1-067",
   "english": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “send incident review to the review queue” fails after the members “publish benchmark report to the member feed” and “mirror errata to the open archive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s067"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p2-067",
   "english": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 68, publish benchmark report to the member feed, send incident review to the review queue, and mirror errata to the open archive. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “send incident review to the review queue” fails after the members “publish benchmark report to the member feed” and “mirror errata to the open archive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s067"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p1-068",
   "english": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “notify the security roster” fails after the members “queue the support digest” and “subscribe the release group to the alert feed” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s068"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p2-068",
   "english": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “notify the security roster” fails after the members “queue the support digest” and “subscribe the release group to the alert feed” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s068"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p1-068",
   "english": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “notify the security roster” fails after the members “queue the support digest” and “subscribe the release group to the alert feed” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s068"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p2-068",
   "english": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 69, queue the support digest, subscribe the release group to the alert feed, and notify the security roster. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “notify the security roster” fails after the members “queue the support digest” and “subscribe the release group to the alert feed” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s068"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p1-069",
   "english": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “seal model-cards under the retention hold” fails after the members “expire the ledger-cold snapshot” and “freeze model-cards at the current revision” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s069"
   }
  },
  {
   "id": "rp73-catastrophic-stop-all-or-nothing-p2-069",
   "english": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. all-or-nothing.",
   "question": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “seal model-cards under the retention hold” fails after the members “expire the ledger-cold snapshot” and “freeze model-cards at the current revision” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s069"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p1-069",
   "english": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “seal model-cards under the retention hold” fails after the members “expire the ledger-cold snapshot” and “freeze model-cards at the current revision” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "catastrophic-stop",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s069"
   }
  },
  {
   "id": "rp73-catastrophic-stop-keep-successes-p2-069",
   "english": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. keep-successes.",
   "question": "For batch 70, seal model-cards under the retention hold, expire the ledger-cold snapshot, and freeze model-cards at the current revision. A catastrophic stop aborts the runner, so the third member is never attempted. Suppose the member “seal model-cards under the retention hold” fails after the members “expire the ledger-cold snapshot” and “freeze model-cards at the current revision” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "catastrophic-stop",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s069"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p1-070",
   "english": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “mark products for refresh” fails after the members “shard attachments across the search tier” and “reload the attachments analyser” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s070"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p2-070",
   "english": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “mark products for refresh” fails after the members “shard attachments across the search tier” and “reload the attachments analyser” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s070"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p1-070",
   "english": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “mark products for refresh” fails after the members “shard attachments across the search tier” and “reload the attachments analyser” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s070"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p2-070",
   "english": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 71, shard attachments across the search tier, mark products for refresh, and reload the attachments analyser. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “mark products for refresh” fails after the members “shard attachments across the search tier” and “reload the attachments analyser” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s070"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p1-071",
   "english": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “lodge the shipping manifest application” fails after the members “book the tax filing slot” and “confirm the trademark renewal courier pickup” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s071"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p2-071",
   "english": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “lodge the shipping manifest application” fails after the members “book the tax filing slot” and “confirm the trademark renewal courier pickup” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s071"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p1-071",
   "english": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “lodge the shipping manifest application” fails after the members “book the tax filing slot” and “confirm the trademark renewal courier pickup” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s071"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p2-071",
   "english": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 72, book the tax filing slot, confirm the trademark renewal courier pickup, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “lodge the shipping manifest application” fails after the members “book the tax filing slot” and “confirm the trademark renewal courier pickup” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s071"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p1-072",
   "english": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “issue harbor-role a scoped token for the vault” fails after the members “provision the atlas-role service account” and “grant beacon-role read access to the ledger” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s072"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p2-072",
   "english": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “issue harbor-role a scoped token for the vault” fails after the members “provision the atlas-role service account” and “grant beacon-role read access to the ledger” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s072"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p1-072",
   "english": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “issue harbor-role a scoped token for the vault” fails after the members “provision the atlas-role service account” and “grant beacon-role read access to the ledger” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s072"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p2-072",
   "english": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 73, issue harbor-role a scoped token for the vault, provision the atlas-role service account, and grant beacon-role read access to the ledger. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “issue harbor-role a scoped token for the vault” fails after the members “provision the atlas-role service account” and “grant beacon-role read access to the ledger” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s072"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p1-073",
   "english": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “replace checksums.txt at the mirror” fails after the members “rename schema.sql in the archive root” and “publish build.log to the artifact store” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s073"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p2-073",
   "english": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “replace checksums.txt at the mirror” fails after the members “rename schema.sql in the archive root” and “publish build.log to the artifact store” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s073"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p1-073",
   "english": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “replace checksums.txt at the mirror” fails after the members “rename schema.sql in the archive root” and “publish build.log to the artifact store” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s073"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p2-073",
   "english": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 74, rename schema.sql in the archive root, replace checksums.txt at the mirror, and publish build.log to the artifact store. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “replace checksums.txt at the mirror” fails after the members “rename schema.sql in the archive root” and “publish build.log to the artifact store” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s073"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p1-074",
   "english": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “repartition the shipments table” fails after the members “compact sessions on the primary node” and “backfill the orders column” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s074"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p2-074",
   "english": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “repartition the shipments table” fails after the members “compact sessions on the primary node” and “backfill the orders column” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s074"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p1-074",
   "english": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “repartition the shipments table” fails after the members “compact sessions on the primary node” and “backfill the orders column” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s074"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p2-074",
   "english": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 75, compact sessions on the primary node, backfill the orders column, and repartition the shipments table. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “repartition the shipments table” fails after the members “compact sessions on the primary node” and “backfill the orders column” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s074"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p1-075",
   "english": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “pin field guide on the project page” fails after the members “send policy draft to the review queue” and “release release note to the public index” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s075"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p2-075",
   "english": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “pin field guide on the project page” fails after the members “send policy draft to the review queue” and “release release note to the public index” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s075"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p1-075",
   "english": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “pin field guide on the project page” fails after the members “send policy draft to the review queue” and “release release note to the public index” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s075"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p2-075",
   "english": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 76, pin field guide on the project page, send policy draft to the review queue, and release release note to the public index. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “pin field guide on the project page” fails after the members “send policy draft to the review queue” and “release release note to the public index” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s075"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p1-076",
   "english": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “queue the release digest” fails after the members “dispatch the security pager notice” and “post the billing summary to the channel” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s076"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p2-076",
   "english": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “queue the release digest” fails after the members “dispatch the security pager notice” and “post the billing summary to the channel” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s076"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p1-076",
   "english": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “queue the release digest” fails after the members “dispatch the security pager notice” and “post the billing summary to the channel” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s076"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p2-076",
   "english": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 77, dispatch the security pager notice, queue the release digest, and post the billing summary to the channel. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “queue the release digest” fails after the members “dispatch the security pager notice” and “post the billing summary to the channel” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s076"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p1-077",
   "english": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “expire the ledger-cold snapshot” fails after the members “attest the case-files manifest” and “freeze case-files at the current revision” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s077"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p2-077",
   "english": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “expire the ledger-cold snapshot” fails after the members “attest the case-files manifest” and “freeze case-files at the current revision” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s077"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p1-077",
   "english": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “expire the ledger-cold snapshot” fails after the members “attest the case-files manifest” and “freeze case-files at the current revision” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s077"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p2-077",
   "english": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 78, attest the case-files manifest, freeze case-files at the current revision, and expire the ledger-cold snapshot. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “expire the ledger-cold snapshot” fails after the members “attest the case-files manifest” and “freeze case-files at the current revision” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s077"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p1-078",
   "english": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “reindex the attachments collection” fails after the members “reload the documents analyser” and “mark transcripts for refresh” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s078"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p2-078",
   "english": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “reindex the attachments collection” fails after the members “reload the documents analyser” and “mark transcripts for refresh” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s078"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p1-078",
   "english": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “reindex the attachments collection” fails after the members “reload the documents analyser” and “mark transcripts for refresh” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s078"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p2-078",
   "english": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 79, reindex the attachments collection, reload the documents analyser, and mark transcripts for refresh. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “reindex the attachments collection” fails after the members “reload the documents analyser” and “mark transcripts for refresh” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s078"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p1-079",
   "english": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “submit the tax filing filing” fails after the members “book the trademark renewal slot” and “lodge the shipping manifest application” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s079"
   }
  },
  {
   "id": "rp73-nested-all-or-nothing-p2-079",
   "english": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. all-or-nothing.",
   "question": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “submit the tax filing filing” fails after the members “book the trademark renewal slot” and “lodge the shipping manifest application” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s079"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p1-079",
   "english": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “submit the tax filing filing” fails after the members “book the trademark renewal slot” and “lodge the shipping manifest application” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "nested",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s079"
   }
  },
  {
   "id": "rp73-nested-keep-successes-p2-079",
   "english": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. keep-successes.",
   "question": "For batch 80, book the trademark renewal slot, submit the tax filing filing, and lodge the shipping manifest application. The batch wraps an inner set that carries its own separate policy; the inner policy is not the policy of this batch. Suppose the member “submit the tax filing filing” fails after the members “book the trademark renewal slot” and “lodge the shipping manifest application” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "nested",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s079"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p1-080",
   "english": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “issue cedar-role a scoped token for the vault” fails after the members “attach the garnet-role policy to the tenant” and “add harbor-role to the deployers group” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s080"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p2-080",
   "english": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “issue cedar-role a scoped token for the vault” fails after the members “attach the garnet-role policy to the tenant” and “add harbor-role to the deployers group” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s080"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p1-080",
   "english": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “issue cedar-role a scoped token for the vault” fails after the members “attach the garnet-role policy to the tenant” and “add harbor-role to the deployers group” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s080"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p2-080",
   "english": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 81, attach the garnet-role policy to the tenant, add harbor-role to the deployers group, and issue cedar-role a scoped token for the vault. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “issue cedar-role a scoped token for the vault” fails after the members “attach the garnet-role policy to the tenant” and “add harbor-role to the deployers group” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s080"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p1-081",
   "english": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “publish checksums.txt to the artifact store” fails after the members “rename notes.rst in the archive root” and “checksum release.toml at the origin” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s081"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p2-081",
   "english": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “publish checksums.txt to the artifact store” fails after the members “rename notes.rst in the archive root” and “checksum release.toml at the origin” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s081"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p1-081",
   "english": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “publish checksums.txt to the artifact store” fails after the members “rename notes.rst in the archive root” and “checksum release.toml at the origin” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s081"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p2-081",
   "english": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 82, publish checksums.txt to the artifact store, rename notes.rst in the archive root, and checksum release.toml at the origin. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “publish checksums.txt to the artifact store” fails after the members “rename notes.rst in the archive root” and “checksum release.toml at the origin” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s081"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p1-082",
   "english": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “backfill the telemetry column” fails after the members “repartition the audit_log table” and “migrate ledger_entries to the new schema” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s082"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p2-082",
   "english": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “backfill the telemetry column” fails after the members “repartition the audit_log table” and “migrate ledger_entries to the new schema” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s082"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p1-082",
   "english": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “backfill the telemetry column” fails after the members “repartition the audit_log table” and “migrate ledger_entries to the new schema” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s082"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p2-082",
   "english": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 83, repartition the audit_log table, backfill the telemetry column, and migrate ledger_entries to the new schema. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “backfill the telemetry column” fails after the members “repartition the audit_log table” and “migrate ledger_entries to the new schema” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s082"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p1-083",
   "english": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “send field guide to the review queue” fails after the members “pin roadmap on the project page” and “mirror roadmap to the open archive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s083"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p2-083",
   "english": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “send field guide to the review queue” fails after the members “pin roadmap on the project page” and “mirror roadmap to the open archive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s083"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p1-083",
   "english": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “send field guide to the review queue” fails after the members “pin roadmap on the project page” and “mirror roadmap to the open archive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s083"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p2-083",
   "english": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 84, pin roadmap on the project page, mirror roadmap to the open archive, and send field guide to the review queue. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “send field guide to the review queue” fails after the members “pin roadmap on the project page” and “mirror roadmap to the open archive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s083"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p1-084",
   "english": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “clear the platform backlog notice” fails after the members “post the on-call summary to the channel” and “dispatch the logistics pager notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s084"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p2-084",
   "english": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “clear the platform backlog notice” fails after the members “post the on-call summary to the channel” and “dispatch the logistics pager notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s084"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p1-084",
   "english": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “clear the platform backlog notice” fails after the members “post the on-call summary to the channel” and “dispatch the logistics pager notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s084"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p2-084",
   "english": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 85, clear the platform backlog notice, post the on-call summary to the channel, and dispatch the logistics pager notice. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “clear the platform backlog notice” fails after the members “post the on-call summary to the channel” and “dispatch the logistics pager notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s084"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p1-085",
   "english": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “attest the contract-set manifest” fails after the members “expire the raw-telemetry snapshot” and “tier model-cards to the vault class” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s085"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p2-085",
   "english": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “attest the contract-set manifest” fails after the members “expire the raw-telemetry snapshot” and “tier model-cards to the vault class” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s085"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p1-085",
   "english": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “attest the contract-set manifest” fails after the members “expire the raw-telemetry snapshot” and “tier model-cards to the vault class” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s085"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p2-085",
   "english": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 86, expire the raw-telemetry snapshot, attest the contract-set manifest, and tier model-cards to the vault class. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “attest the contract-set manifest” fails after the members “expire the raw-telemetry snapshot” and “tier model-cards to the vault class” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s085"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p1-086",
   "english": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “mark transcripts for refresh” fails after the members “reload the transcripts analyser” and “rebuild the entities index” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s086"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p2-086",
   "english": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “mark transcripts for refresh” fails after the members “reload the transcripts analyser” and “rebuild the entities index” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s086"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p1-086",
   "english": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “mark transcripts for refresh” fails after the members “reload the transcripts analyser” and “rebuild the entities index” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s086"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p2-086",
   "english": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 87, reload the transcripts analyser, rebuild the entities index, and mark transcripts for refresh. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “mark transcripts for refresh” fails after the members “reload the transcripts analyser” and “rebuild the entities index” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s086"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p1-087",
   "english": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “settle the shipping manifest invoice” fails after the members “book the safety notice slot” and “register the tax filing certificate” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s087"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p2-087",
   "english": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “settle the shipping manifest invoice” fails after the members “book the safety notice slot” and “register the tax filing certificate” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s087"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p1-087",
   "english": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “settle the shipping manifest invoice” fails after the members “book the safety notice slot” and “register the tax filing certificate” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s087"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p2-087",
   "english": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 88, settle the shipping manifest invoice, book the safety notice slot, and register the tax filing certificate. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “settle the shipping manifest invoice” fails after the members “book the safety notice slot” and “register the tax filing certificate” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s087"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p1-088",
   "english": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “attach the garnet-role policy to the tenant” fails after the members “issue flint-role a scoped token for the vault” and “grant harbor-role write access to the registry” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s088"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p2-088",
   "english": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “attach the garnet-role policy to the tenant” fails after the members “issue flint-role a scoped token for the vault” and “grant harbor-role write access to the registry” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s088"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p1-088",
   "english": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “attach the garnet-role policy to the tenant” fails after the members “issue flint-role a scoped token for the vault” and “grant harbor-role write access to the registry” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s088"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p2-088",
   "english": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 89, issue flint-role a scoped token for the vault, attach the garnet-role policy to the tenant, and grant harbor-role write access to the registry. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “attach the garnet-role policy to the tenant” fails after the members “issue flint-role a scoped token for the vault” and “grant harbor-role write access to the registry” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s088"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p1-089",
   "english": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “publish build.log to the artifact store” fails after the members “checksum schema.sql at the origin” and “write changelog.md to the shared drive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s089"
   }
  },
  {
   "id": "rp73-independent-invalidation-all-or-nothing-p2-089",
   "english": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. all-or-nothing.",
   "question": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “publish build.log to the artifact store” fails after the members “checksum schema.sql at the origin” and “write changelog.md to the shared drive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s089"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p1-089",
   "english": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “publish build.log to the artifact store” fails after the members “checksum schema.sql at the origin” and “write changelog.md to the shared drive” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "independent-invalidation",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s089"
   }
  },
  {
   "id": "rp73-independent-invalidation-keep-successes-p2-089",
   "english": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. keep-successes.",
   "question": "For batch 90, checksum schema.sql at the origin, write changelog.md to the shared drive, and publish build.log to the artifact store. After the batch reports, one committed member effect is invalidated on an unrelated compliance ground. Suppose the member “publish build.log to the artifact store” fails after the members “checksum schema.sql at the origin” and “write changelog.md to the shared drive” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "independent-invalidation",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s089"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p1-090",
   "english": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “compact invoices on the primary node” fails after the members “rekey shipments under the tenant id” and “copy orders into the staging cluster” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s090"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p2-090",
   "english": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “compact invoices on the primary node” fails after the members “rekey shipments under the tenant id” and “copy orders into the staging cluster” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s090"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p1-090",
   "english": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “compact invoices on the primary node” fails after the members “rekey shipments under the tenant id” and “copy orders into the staging cluster” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s090"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p2-090",
   "english": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 91, compact invoices on the primary node, rekey shipments under the tenant id, and copy orders into the staging cluster. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “compact invoices on the primary node” fails after the members “rekey shipments under the tenant id” and “copy orders into the staging cluster” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s090"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p1-091",
   "english": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “send design memo to the review queue” fails after the members “publish design memo to the member feed” and “schedule roadmap for the morning digest” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s091"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p2-091",
   "english": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “send design memo to the review queue” fails after the members “publish design memo to the member feed” and “schedule roadmap for the morning digest” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s091"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p1-091",
   "english": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “send design memo to the review queue” fails after the members “publish design memo to the member feed” and “schedule roadmap for the morning digest” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s091"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p2-091",
   "english": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 92, publish design memo to the member feed, send design memo to the review queue, and schedule roadmap for the morning digest. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “send design memo to the review queue” fails after the members “publish design memo to the member feed” and “schedule roadmap for the morning digest” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s091"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p1-092",
   "english": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “queue the research digest” fails after the members “post the support summary to the channel” and “dispatch the release pager notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s092"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p2-092",
   "english": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “queue the research digest” fails after the members “post the support summary to the channel” and “dispatch the release pager notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "notification",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s092"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p1-092",
   "english": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “queue the research digest” fails after the members “post the support summary to the channel” and “dispatch the release pager notice” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s092"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p2-092",
   "english": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 93, post the support summary to the channel, dispatch the release pager notice, and queue the research digest. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “queue the research digest” fails after the members “post the support summary to the channel” and “dispatch the release pager notice” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "notification",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s092"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p1-093",
   "english": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “attest the case-files manifest” fails after the members “archive contract-set to cold storage” and “tier media-bundle to the vault class” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s093"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p2-093",
   "english": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “attest the case-files manifest” fails after the members “archive contract-set to cold storage” and “tier media-bundle to the vault class” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "archival",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s093"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p1-093",
   "english": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “attest the case-files manifest” fails after the members “archive contract-set to cold storage” and “tier media-bundle to the vault class” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s093"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p2-093",
   "english": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 94, attest the case-files manifest, archive contract-set to cold storage, and tier media-bundle to the vault class. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “attest the case-files manifest” fails after the members “archive contract-set to cold storage” and “tier media-bundle to the vault class” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "archival",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s093"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p1-094",
   "english": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “reindex the attachments collection” fails after the members “reload the products analyser” and “snapshot the entities inverted list” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s094"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p2-094",
   "english": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “reindex the attachments collection” fails after the members “reload the products analyser” and “snapshot the entities inverted list” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "indexing",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s094"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p1-094",
   "english": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “reindex the attachments collection” fails after the members “reload the products analyser” and “snapshot the entities inverted list” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s094"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p2-094",
   "english": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 95, reload the products analyser, reindex the attachments collection, and snapshot the entities inverted list. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “reindex the attachments collection” fails after the members “reload the products analyser” and “snapshot the entities inverted list” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "indexing",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s094"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p1-095",
   "english": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “book the grant application slot” fails after the members “confirm the venue permit courier pickup” and “submit the tax filing filing” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s095"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p2-095",
   "english": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “book the grant application slot” fails after the members “confirm the venue permit courier pickup” and “submit the tax filing filing” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "external actions",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s095"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p1-095",
   "english": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “book the grant application slot” fails after the members “confirm the venue permit courier pickup” and “submit the tax filing filing” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s095"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p2-095",
   "english": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 96, confirm the venue permit courier pickup, submit the tax filing filing, and book the grant application slot. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “book the grant application slot” fails after the members “confirm the venue permit courier pickup” and “submit the tax filing filing” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "external actions",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s095"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p1-096",
   "english": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “attach the cedar-role policy to the tenant” fails after the members “add delta-role to the deployers group” and “issue beacon-role a scoped token for the vault” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s096"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p2-096",
   "english": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “attach the cedar-role policy to the tenant” fails after the members “add delta-role to the deployers group” and “issue beacon-role a scoped token for the vault” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "permissions",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s096"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p1-096",
   "english": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “attach the cedar-role policy to the tenant” fails after the members “add delta-role to the deployers group” and “issue beacon-role a scoped token for the vault” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s096"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p2-096",
   "english": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 97, attach the cedar-role policy to the tenant, add delta-role to the deployers group, and issue beacon-role a scoped token for the vault. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “attach the cedar-role policy to the tenant” fails after the members “add delta-role to the deployers group” and “issue beacon-role a scoped token for the vault” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "permissions",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s096"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p1-097",
   "english": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “publish manifest.json to the artifact store” fails after the members “move release.toml into the release folder” and “checksum release.toml at the origin” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s097"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p2-097",
   "english": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “publish manifest.json to the artifact store” fails after the members “move release.toml into the release folder” and “checksum release.toml at the origin” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "file operations",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s097"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p1-097",
   "english": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “publish manifest.json to the artifact store” fails after the members “move release.toml into the release folder” and “checksum release.toml at the origin” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 1,
    "sid": "rp-s097"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p2-097",
   "english": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 98, move release.toml into the release folder, publish manifest.json to the artifact store, and checksum release.toml at the origin. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “publish manifest.json to the artifact store” fails after the members “move release.toml into the release folder” and “checksum release.toml at the origin” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "file operations",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 1,
    "sid": "rp-s097"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p1-098",
   "english": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “rekey sessions under the tenant id” fails after the members “backfill the orders column” and “migrate shipments to the new schema” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s098"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p2-098",
   "english": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “rekey sessions under the tenant id” fails after the members “backfill the orders column” and “migrate shipments to the new schema” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "data migration",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s098"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p1-098",
   "english": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “rekey sessions under the tenant id” fails after the members “backfill the orders column” and “migrate shipments to the new schema” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 2,
    "sid": "rp-s098"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p2-098",
   "english": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 99, backfill the orders column, migrate shipments to the new schema, and rekey sessions under the tenant id. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “rekey sessions under the tenant id” fails after the members “backfill the orders column” and “migrate shipments to the new schema” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "data migration",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 2,
    "sid": "rp-s098"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p1-099",
   "english": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “publish release note to the member feed” fails after the members “pin release note on the project page” and “send field guide to the review queue” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative",
    "the whole batch is reported as a full success",
    "the retention policy is not specified"
   ],
   "answer": "no successful member effect remains authoritative",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s099"
   }
  },
  {
   "id": "rp73-partial-progress-all-or-nothing-p2-099",
   "english": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, no successful member effect remains authoritative or may be relied on as the terminal result.",
   "ainglish": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. all-or-nothing.",
   "question": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “publish release note to the member feed” fails after the members “pin release note on the project page” and “send field guide to the review queue” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch failed with no retained effects",
    "the batch ended as a partial result",
    "the batch ended as a full success",
    "the retention policy is not specified"
   ],
   "answer": "the batch failed with no retained effects",
   "form": "all-or-nothing",
   "settlement_stratum": "all-or-nothing",
   "strata": {
    "domain": "publication",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s099"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p1-099",
   "english": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “publish release note to the member feed” fails after the members “pin release note on the project page” and “send field guide to the review queue” succeed. What may remain authoritative at the terminal outcome?\n- no successful member effect remains authoritative\n- every successful member effect remains authoritative\n- the whole batch is reported as a full success\n- the retention policy is not specified",
   "options": [
    "the whole batch is reported as a full success",
    "the retention policy is not specified",
    "no successful member effect remains authoritative",
    "every successful member effect remains authoritative"
   ],
   "answer": "every successful member effect remains authoritative",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "partial-progress",
    "probe": 1,
    "fail_pos": 0,
    "sid": "rp-s099"
   }
  },
  {
   "id": "rp73-partial-progress-keep-successes-p2-099",
   "english": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. If any member fails, every successful member effect remains authoritative and may be relied on as the terminal result.",
   "ainglish": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. keep-successes.",
   "question": "For batch 100, publish release note to the member feed, pin release note on the project page, and send field guide to the review queue. The first member reports partial progress that has not yet produced a successful member effect. Suppose the member “publish release note to the member feed” fails after the members “pin release note on the project page” and “send field guide to the review queue” succeed. What is the terminal state of the batch?\n- the batch failed with no retained effects\n- the batch ended as a partial result\n- the batch ended as a full success\n- the retention policy is not specified",
   "options": [
    "the batch ended as a full success",
    "the retention policy is not specified",
    "the batch failed with no retained effects",
    "the batch ended as a partial result"
   ],
   "answer": "the batch ended as a partial result",
   "form": "keep-successes",
   "settlement_stratum": "keep-successes",
   "strata": {
    "domain": "publication",
    "cls": "partial-progress",
    "probe": 2,
    "fail_pos": 0,
    "sid": "rp-s099"
   }
  },
  {
   "id": "rp73-cal-01",
   "english": "A sealed inventory note mentions the amber token, but gives no location.",
   "ainglish": "A sealed inventory note states that the amber token is in locker 7.",
   "question": "According to the note, where is the amber token?\n- the amber token is in locker 7\n- the amber token is at the dispatch desk\n- the amber token is in the archive room\n- the amber token's location is not stated",
   "options": [
    "the amber token is in locker 7",
    "the amber token is at the dispatch desk",
    "the amber token is in the archive room",
    "the amber token's location is not stated"
   ],
   "answer": "the amber token is in locker 7",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-02",
   "english": "A sealed inventory note mentions the sealed vial, but gives no location.",
   "ainglish": "A sealed inventory note states that the sealed vial is in freezer B.",
   "question": "According to the note, where is the sealed vial?\n- the sealed vial is in freezer B\n- the sealed vial is at the wet bench\n- the sealed vial is in the cold room\n- the sealed vial's location is not stated",
   "options": [
    "the sealed vial is in freezer B",
    "the sealed vial is at the wet bench",
    "the sealed vial is in the cold room",
    "the sealed vial's location is not stated"
   ],
   "answer": "the sealed vial is in freezer B",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-03",
   "english": "A sealed inventory note mentions the spare fuse, but gives no location.",
   "ainglish": "A sealed inventory note states that the spare fuse is in drawer 12.",
   "question": "According to the note, where is the spare fuse?\n- the spare fuse is in drawer 12\n- the spare fuse is at the tool crib\n- the spare fuse is in the substation\n- the spare fuse's location is not stated",
   "options": [
    "the spare fuse is in drawer 12",
    "the spare fuse is at the tool crib",
    "the spare fuse is in the substation",
    "the spare fuse's location is not stated"
   ],
   "answer": "the spare fuse is in drawer 12",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-04",
   "english": "A sealed inventory note mentions the courier pouch, but gives no location.",
   "ainglish": "A sealed inventory note states that the courier pouch is in dock 3.",
   "question": "According to the note, where is the courier pouch?\n- the courier pouch is in dock 3\n- the courier pouch is at the front desk\n- the courier pouch is in the mail room\n- the courier pouch's location is not stated",
   "options": [
    "the courier pouch is in dock 3",
    "the courier pouch is at the front desk",
    "the courier pouch is in the mail room",
    "the courier pouch's location is not stated"
   ],
   "answer": "the courier pouch is in dock 3",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-05",
   "english": "A sealed inventory note mentions the sample slide, but gives no location.",
   "ainglish": "A sealed inventory note states that the sample slide is in cabinet C.",
   "question": "According to the note, where is the sample slide?\n- the sample slide is in cabinet C\n- the sample slide is at the imaging bench\n- the sample slide is in the prep room\n- the sample slide's location is not stated",
   "options": [
    "the sample slide is in cabinet C",
    "the sample slide is at the imaging bench",
    "the sample slide is in the prep room",
    "the sample slide's location is not stated"
   ],
   "answer": "the sample slide is in cabinet C",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-06",
   "english": "A sealed inventory note mentions the backup tape, but gives no location.",
   "ainglish": "A sealed inventory note states that the backup tape is in vault 2.",
   "question": "According to the note, where is the backup tape?\n- the backup tape is in vault 2\n- the backup tape is at the server rack\n- the backup tape is in the tape library\n- the backup tape's location is not stated",
   "options": [
    "the backup tape is in vault 2",
    "the backup tape is at the server rack",
    "the backup tape is in the tape library",
    "the backup tape's location is not stated"
   ],
   "answer": "the backup tape is in vault 2",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-07",
   "english": "A sealed inventory note mentions the brass key, but gives no location.",
   "ainglish": "A sealed inventory note states that the brass key is in hook 9.",
   "question": "According to the note, where is the brass key?\n- the brass key is in hook 9\n- the brass key is at the key safe\n- the brass key is in the porter desk\n- the brass key's location is not stated",
   "options": [
    "the brass key is in hook 9",
    "the brass key is at the key safe",
    "the brass key is in the porter desk",
    "the brass key's location is not stated"
   ],
   "answer": "the brass key is in hook 9",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-08",
   "english": "A sealed inventory note mentions the reagent bottle, but gives no location.",
   "ainglish": "A sealed inventory note states that the reagent bottle is in shelf D.",
   "question": "According to the note, where is the reagent bottle?\n- the reagent bottle is in shelf D\n- the reagent bottle is at the fume hood\n- the reagent bottle is in the storeroom\n- the reagent bottle's location is not stated",
   "options": [
    "the reagent bottle is in shelf D",
    "the reagent bottle is at the fume hood",
    "the reagent bottle is in the storeroom",
    "the reagent bottle's location is not stated"
   ],
   "answer": "the reagent bottle is in shelf D",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-09",
   "english": "A sealed inventory note mentions the loan file, but gives no location.",
   "ainglish": "A sealed inventory note states that the loan file is in cabinet 4.",
   "question": "According to the note, where is the loan file?\n- the loan file is in cabinet 4\n- the loan file is at the records office\n- the loan file is in the annex\n- the loan file's location is not stated",
   "options": [
    "the loan file is in cabinet 4",
    "the loan file is at the records office",
    "the loan file is in the annex",
    "the loan file's location is not stated"
   ],
   "answer": "the loan file is in cabinet 4",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-10",
   "english": "A sealed inventory note mentions the spare badge, but gives no location.",
   "ainglish": "A sealed inventory note states that the spare badge is in reception.",
   "question": "According to the note, where is the spare badge?\n- the spare badge is in reception\n- the spare badge is at the security desk\n- the spare badge is in the gatehouse\n- the spare badge's location is not stated",
   "options": [
    "the spare badge is in reception",
    "the spare badge is at the security desk",
    "the spare badge is in the gatehouse",
    "the spare badge's location is not stated"
   ],
   "answer": "the spare badge is in reception",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-11",
   "english": "A sealed inventory note mentions the calibration weight, but gives no location.",
   "ainglish": "A sealed inventory note states that the calibration weight is in case 6.",
   "question": "According to the note, where is the calibration weight?\n- the calibration weight is in case 6\n- the calibration weight is at the metrology lab\n- the calibration weight is in the workshop\n- the calibration weight's location is not stated",
   "options": [
    "the calibration weight is in case 6",
    "the calibration weight is at the metrology lab",
    "the calibration weight is in the workshop",
    "the calibration weight's location is not stated"
   ],
   "answer": "the calibration weight is in case 6",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-12",
   "english": "A sealed inventory note mentions the sealed order, but gives no location.",
   "ainglish": "A sealed inventory note states that the sealed order is in pigeonhole 18.",
   "question": "According to the note, where is the sealed order?\n- the sealed order is in pigeonhole 18\n- the sealed order is at the clerks' room\n- the sealed order is in the post room\n- the sealed order's location is not stated",
   "options": [
    "the sealed order is in pigeonhole 18",
    "the sealed order is at the clerks' room",
    "the sealed order is in the post room",
    "the sealed order's location is not stated"
   ],
   "answer": "the sealed order is in pigeonhole 18",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-13",
   "english": "A sealed inventory note mentions the reserve battery, but gives no location.",
   "ainglish": "A sealed inventory note states that the reserve battery is in bay 5.",
   "question": "According to the note, where is the reserve battery?\n- the reserve battery is in bay 5\n- the reserve battery is at the generator shed\n- the reserve battery is in the stores\n- the reserve battery's location is not stated",
   "options": [
    "the reserve battery is in bay 5",
    "the reserve battery is at the generator shed",
    "the reserve battery is in the stores",
    "the reserve battery's location is not stated"
   ],
   "answer": "the reserve battery is in bay 5",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-14",
   "english": "A sealed inventory note mentions the signed deed, but gives no location.",
   "ainglish": "A sealed inventory note states that the signed deed is in strongbox 1.",
   "question": "According to the note, where is the signed deed?\n- the signed deed is in strongbox 1\n- the signed deed is at the registry\n- the signed deed is in the solicitor's office\n- the signed deed's location is not stated",
   "options": [
    "the signed deed is in strongbox 1",
    "the signed deed is at the registry",
    "the signed deed is in the solicitor's office",
    "the signed deed's location is not stated"
   ],
   "answer": "the signed deed is in strongbox 1",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-15",
   "english": "A sealed inventory note mentions the spare rotor, but gives no location.",
   "ainglish": "A sealed inventory note states that the spare rotor is in crate 21.",
   "question": "According to the note, where is the spare rotor?\n- the spare rotor is in crate 21\n- the spare rotor is at the hangar\n- the spare rotor is in the parts store\n- the spare rotor's location is not stated",
   "options": [
    "the spare rotor is in crate 21",
    "the spare rotor is at the hangar",
    "the spare rotor is in the parts store",
    "the spare rotor's location is not stated"
   ],
   "answer": "the spare rotor is in crate 21",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-16",
   "english": "A sealed inventory note mentions the field sample, but gives no location.",
   "ainglish": "A sealed inventory note states that the field sample is in cooler 8.",
   "question": "According to the note, where is the field sample?\n- the field sample is in cooler 8\n- the field sample is at the survey tent\n- the field sample is in the depot\n- the field sample's location is not stated",
   "options": [
    "the field sample is in cooler 8",
    "the field sample is at the survey tent",
    "the field sample is in the depot",
    "the field sample's location is not stated"
   ],
   "answer": "the field sample is in cooler 8",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-17",
   "english": "A sealed inventory note mentions the printed proof, but gives no location.",
   "ainglish": "A sealed inventory note states that the printed proof is in tray 2.",
   "question": "According to the note, where is the printed proof?\n- the printed proof is in tray 2\n- the printed proof is at the press room\n- the printed proof is in the studio\n- the printed proof's location is not stated",
   "options": [
    "the printed proof is in tray 2",
    "the printed proof is at the press room",
    "the printed proof is in the studio",
    "the printed proof's location is not stated"
   ],
   "answer": "the printed proof is in tray 2",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-18",
   "english": "A sealed inventory note mentions the seed lot, but gives no location.",
   "ainglish": "A sealed inventory note states that the seed lot is in bin 14.",
   "question": "According to the note, where is the seed lot?\n- the seed lot is in bin 14\n- the seed lot is at the dry store\n- the seed lot is in the glasshouse\n- the seed lot's location is not stated",
   "options": [
    "the seed lot is in bin 14",
    "the seed lot is at the dry store",
    "the seed lot is in the glasshouse",
    "the seed lot's location is not stated"
   ],
   "answer": "the seed lot is in bin 14",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-19",
   "english": "A sealed inventory note mentions the chart roll, but gives no location.",
   "ainglish": "A sealed inventory note states that the chart roll is in tube 7.",
   "question": "According to the note, where is the chart roll?\n- the chart roll is in tube 7\n- the chart roll is at the chart room\n- the chart roll is in the bridge store\n- the chart roll's location is not stated",
   "options": [
    "the chart roll is in tube 7",
    "the chart roll is at the chart room",
    "the chart roll is in the bridge store",
    "the chart roll's location is not stated"
   ],
   "answer": "the chart roll is in tube 7",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  },
  {
   "id": "rp73-cal-20",
   "english": "A sealed inventory note mentions the spare filter, but gives no location.",
   "ainglish": "A sealed inventory note states that the spare filter is in rack 11.",
   "question": "According to the note, where is the spare filter?\n- the spare filter is in rack 11\n- the spare filter is at the plant room\n- the spare filter is in the workshop\n- the spare filter's location is not stated",
   "options": [
    "the spare filter is in rack 11",
    "the spare filter is at the plant room",
    "the spare filter is in the workshop",
    "the spare filter's location is not stated"
   ],
   "answer": "the spare filter is in rack 11",
   "probe": "construct-free explicit-location planted effect",
   "calibration": true
  }
 ],
 "sha256": "54e84fa1047b0c36dc7a9fdf2f52b89856d8b5f866cca16d9d0042e7a0a9218d"
}