{"items": [{"id": "a76-glv-1-a-source-edit-core", "english": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v238.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v238."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v238.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v238.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v238.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-1-a-source-edit-authority-boundary", "english": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-1-a-source-edit-evidence-boundary", "english": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-1-a-source-deletion-core", "english": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-1-a-source-deletion-authority-boundary", "english": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-1-a-source-deletion-evidence-boundary", "english": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-1-a-grant-revocation-core", "english": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-1-a-grant-revocation-authority-boundary", "english": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-1-a-grant-revocation-evidence-boundary", "english": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-1-a-later-read-core", "english": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-1-a-later-read-authority-boundary", "english": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-1-a-later-read-evidence-boundary", "english": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Bram a cancellable read-only view of the standing safety-manual; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(safety-manual, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-1-b-source-edit-core", "english": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v252.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v252.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v252.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v252.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v252.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-1-b-source-edit-authority-boundary", "english": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-1-b-source-edit-evidence-boundary", "english": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-1-b-source-deletion-core", "english": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-1-b-source-deletion-authority-boundary", "english": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-1-b-source-deletion-evidence-boundary", "english": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-1-b-grant-revocation-core", "english": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-1-b-grant-revocation-authority-boundary", "english": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-1-b-grant-revocation-evidence-boundary", "english": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-1-b-later-read-core", "english": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-1-b-later-read-authority-boundary", "english": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-1-b-later-read-evidence-boundary", "english": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Ivo a cancellable read-only view of the standing field-guide; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(field-guide, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-1", "form": "grant-live-view", "domain": "document", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-1-a-source-edit-core", "english": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v238.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v238.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v238.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v238.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-1-a-source-edit-authority-boundary", "english": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-1-a-source-edit-evidence-boundary", "english": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is revised from v231 to v238. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-1-a-source-deletion-core", "english": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-1-a-source-deletion-authority-boundary", "english": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-1-a-source-deletion-evidence-boundary", "english": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, safety-manual is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-1-a-grant-revocation-core", "english": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-1-a-grant-revocation-authority-boundary", "english": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-1-a-grant-revocation-evidence-boundary", "english": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, the standing read permission for safety-manual is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-1-a-later-read-core", "english": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-1-a-later-read-authority-boundary", "english": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-1-a-later-read-evidence-boundary", "english": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Bram a separate copy of exactly safety-manual v231. Do not leave Bram with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is safety-manual. Afterwards, Bram consults safety-manual again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(safety-manual@v231, to=Bram).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-1-b-source-edit-core", "english": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v252.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v252.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v252.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v252.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-1-b-source-edit-authority-boundary", "english": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-1-b-source-edit-evidence-boundary", "english": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is revised from v244 to v252. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-1-b-source-deletion-core", "english": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-1-b-source-deletion-authority-boundary", "english": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-1-b-source-deletion-evidence-boundary", "english": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, field-guide is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-1-b-grant-revocation-core", "english": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-1-b-grant-revocation-authority-boundary", "english": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-1-b-grant-revocation-evidence-boundary", "english": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, the standing read permission for field-guide is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-1-b-later-read-core", "english": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-1-b-later-read-authority-boundary", "english": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-1-b-later-read-evidence-boundary", "english": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Ivo a separate copy of exactly field-guide v244. Do not leave Ivo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing document is field-guide. Afterwards, Ivo consults field-guide again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(field-guide@v244, to=Ivo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-1", "form": "send-snapshot", "domain": "document", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-2-a-source-edit-core", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v325.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v325.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v325.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v325.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v325.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-2-a-source-edit-authority-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-2-a-source-edit-evidence-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-2-a-source-deletion-core", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-2-a-source-deletion-authority-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-2-a-source-deletion-evidence-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-2-a-grant-revocation-core", "english": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-2-a-grant-revocation-authority-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-2-a-grant-revocation-evidence-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-2-a-later-read-core", "english": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-2-a-later-read-authority-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-2-a-later-read-evidence-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Cyd a cancellable read-only view of the standing quota-tracker; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(quota-tracker, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-2-b-source-edit-core", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v341.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v341."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v341.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v341.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v341.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-2-b-source-edit-authority-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-2-b-source-edit-evidence-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-2-b-source-deletion-core", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-2-b-source-deletion-authority-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-2-b-source-deletion-evidence-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-2-b-grant-revocation-core", "english": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-2-b-grant-revocation-authority-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-2-b-grant-revocation-evidence-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-2-b-later-read-core", "english": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-2-b-later-read-authority-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-2-b-later-read-evidence-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Jonas a cancellable read-only view of the standing budget-grid; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(budget-grid, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-2", "form": "grant-live-view", "domain": "spreadsheet", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-2-a-source-edit-core", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v325.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v325.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v325.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v325.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-2-a-source-edit-authority-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-2-a-source-edit-evidence-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is revised from v317 to v325. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-2-a-source-deletion-core", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-2-a-source-deletion-authority-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-2-a-source-deletion-evidence-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, quota-tracker is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-2-a-grant-revocation-core", "english": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-2-a-grant-revocation-authority-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-2-a-grant-revocation-evidence-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, the standing read permission for quota-tracker is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-2-a-later-read-core", "english": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-2-a-later-read-authority-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-2-a-later-read-evidence-boundary", "english": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Cyd a separate copy of exactly quota-tracker v317. Do not leave Cyd with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is quota-tracker. Afterwards, Cyd consults quota-tracker again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(quota-tracker@v317, to=Cyd).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-2-b-source-edit-core", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v341.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v341.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v341.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v341.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-2-b-source-edit-authority-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-2-b-source-edit-evidence-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is revised from v333 to v341. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-2-b-source-deletion-core", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-2-b-source-deletion-authority-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-2-b-source-deletion-evidence-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, budget-grid is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-2-b-grant-revocation-core", "english": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-2-b-grant-revocation-authority-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-2-b-grant-revocation-evidence-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, the standing read permission for budget-grid is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-2-b-later-read-core", "english": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-2-b-later-read-authority-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-2-b-later-read-evidence-boundary", "english": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Jonas a separate copy of exactly budget-grid v333. Do not leave Jonas with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing spreadsheet is budget-grid. Afterwards, Jonas consults budget-grid again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(budget-grid@v333, to=Jonas).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-2", "form": "send-snapshot", "domain": "spreadsheet", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-3-a-source-edit-core", "english": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v412.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v412.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v412.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v412.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v412.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-3-a-source-edit-authority-boundary", "english": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-3-a-source-edit-evidence-boundary", "english": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-3-a-source-deletion-core", "english": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-3-a-source-deletion-authority-boundary", "english": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-3-a-source-deletion-evidence-boundary", "english": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-3-a-grant-revocation-core", "english": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-3-a-grant-revocation-authority-boundary", "english": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-3-a-grant-revocation-evidence-boundary", "english": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-3-a-later-read-core", "english": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-3-a-later-read-authority-boundary", "english": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-3-a-later-read-evidence-boundary", "english": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Dax a cancellable read-only view of the standing worker-image; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(worker-image, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-3-b-source-edit-core", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v426.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v426.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v426.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v426.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v426.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-3-b-source-edit-authority-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-3-b-source-edit-evidence-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-3-b-source-deletion-core", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-3-b-source-deletion-authority-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-3-b-source-deletion-evidence-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-3-b-grant-revocation-core", "english": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-3-b-grant-revocation-authority-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-3-b-grant-revocation-evidence-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-3-b-later-read-core", "english": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-3-b-later-read-authority-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-3-b-later-read-evidence-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Lena a cancellable read-only view of the standing proxy-bundle; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(proxy-bundle, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-3", "form": "grant-live-view", "domain": "code artifact", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-3-a-source-edit-core", "english": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v412.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v412.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v412.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v412.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-3-a-source-edit-authority-boundary", "english": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-3-a-source-edit-evidence-boundary", "english": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is revised from v406 to v412. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-3-a-source-deletion-core", "english": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-3-a-source-deletion-authority-boundary", "english": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-3-a-source-deletion-evidence-boundary", "english": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, worker-image is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-3-a-grant-revocation-core", "english": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-3-a-grant-revocation-authority-boundary", "english": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-3-a-grant-revocation-evidence-boundary", "english": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, the standing read permission for worker-image is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-3-a-later-read-core", "english": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-3-a-later-read-authority-boundary", "english": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-3-a-later-read-evidence-boundary", "english": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Dax a separate copy of exactly worker-image v406. Do not leave Dax with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is worker-image. Afterwards, Dax consults worker-image again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(worker-image@v406, to=Dax).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-3-b-source-edit-core", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v426.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v426.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v426.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v426.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-3-b-source-edit-authority-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-3-b-source-edit-evidence-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is revised from v418 to v426. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-3-b-source-deletion-core", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-3-b-source-deletion-authority-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-3-b-source-deletion-evidence-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, proxy-bundle is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-3-b-grant-revocation-core", "english": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-3-b-grant-revocation-authority-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-3-b-grant-revocation-evidence-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, the standing read permission for proxy-bundle is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-3-b-later-read-core", "english": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-3-b-later-read-authority-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-3-b-later-read-evidence-boundary", "english": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Lena a separate copy of exactly proxy-bundle v418. Do not leave Lena with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing code artifact is proxy-bundle. Afterwards, Lena consults proxy-bundle again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(proxy-bundle@v418, to=Lena).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-3", "form": "send-snapshot", "domain": "code artifact", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-4-a-source-edit-core", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v521.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v521.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v521.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v521.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v521.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-4-a-source-edit-authority-boundary", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-4-a-source-edit-evidence-boundary", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-4-a-source-deletion-core", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-4-a-source-deletion-authority-boundary", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-4-a-source-deletion-evidence-boundary", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-4-a-grant-revocation-core", "english": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-4-a-grant-revocation-authority-boundary", "english": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-4-a-grant-revocation-evidence-boundary", "english": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-4-a-later-read-core", "english": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-4-a-later-read-authority-boundary", "english": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-4-a-later-read-evidence-boundary", "english": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Elva a cancellable read-only view of the standing latency-wall; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(latency-wall, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-4-b-source-edit-core", "english": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v534.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v534."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v534.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v534.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v534.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-4-b-source-edit-authority-boundary", "english": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-4-b-source-edit-evidence-boundary", "english": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-4-b-source-deletion-core", "english": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-4-b-source-deletion-authority-boundary", "english": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-4-b-source-deletion-evidence-boundary", "english": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-4-b-grant-revocation-core", "english": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-4-b-grant-revocation-authority-boundary", "english": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-4-b-grant-revocation-evidence-boundary", "english": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-4-b-later-read-core", "english": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-4-b-later-read-authority-boundary", "english": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-4-b-later-read-evidence-boundary", "english": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Milo a cancellable read-only view of the standing error-board; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(error-board, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-4", "form": "grant-live-view", "domain": "dashboard", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-4-a-source-edit-core", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v521.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v521.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v521.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v521.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-4-a-source-edit-authority-boundary", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-4-a-source-edit-evidence-boundary", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is revised from v514 to v521. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-4-a-source-deletion-core", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-4-a-source-deletion-authority-boundary", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-4-a-source-deletion-evidence-boundary", "english": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, latency-wall is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-4-a-grant-revocation-core", "english": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-4-a-grant-revocation-authority-boundary", "english": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-4-a-grant-revocation-evidence-boundary", "english": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, the standing read permission for latency-wall is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-4-a-later-read-core", "english": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-4-a-later-read-authority-boundary", "english": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-4-a-later-read-evidence-boundary", "english": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Elva a separate copy of exactly latency-wall v514. Do not leave Elva with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is latency-wall. Afterwards, Elva consults latency-wall again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(latency-wall@v514, to=Elva).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-4-b-source-edit-core", "english": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v534.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v534.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v534.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v534.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-4-b-source-edit-authority-boundary", "english": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-4-b-source-edit-evidence-boundary", "english": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is revised from v527 to v534. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-4-b-source-deletion-core", "english": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-4-b-source-deletion-authority-boundary", "english": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-4-b-source-deletion-evidence-boundary", "english": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, error-board is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-4-b-grant-revocation-core", "english": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-4-b-grant-revocation-authority-boundary", "english": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-4-b-grant-revocation-evidence-boundary", "english": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, the standing read permission for error-board is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-4-b-later-read-core", "english": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-4-b-later-read-authority-boundary", "english": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-4-b-later-read-evidence-boundary", "english": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Milo a separate copy of exactly error-board v527. Do not leave Milo with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing dashboard is error-board. Afterwards, Milo consults error-board again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(error-board@v527, to=Milo).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-4", "form": "send-snapshot", "domain": "dashboard", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-5-a-source-edit-core", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v615.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v615."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v615.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v615.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v615.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-5-a-source-edit-authority-boundary", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-5-a-source-edit-evidence-boundary", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-5-a-source-deletion-core", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-5-a-source-deletion-authority-boundary", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-5-a-source-deletion-evidence-boundary", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-5-a-grant-revocation-core", "english": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-5-a-grant-revocation-authority-boundary", "english": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-5-a-grant-revocation-evidence-boundary", "english": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-5-a-later-read-core", "english": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-5-a-later-read-authority-boundary", "english": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-5-a-later-read-evidence-boundary", "english": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Fenn a cancellable read-only view of the standing briefing-clip; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(briefing-clip, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-5-b-source-edit-core", "english": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v629.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v629.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v629.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v629.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v629.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-5-b-source-edit-authority-boundary", "english": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-5-b-source-edit-evidence-boundary", "english": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-5-b-source-deletion-core", "english": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-5-b-source-deletion-authority-boundary", "english": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-5-b-source-deletion-evidence-boundary", "english": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-5-b-grant-revocation-core", "english": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-5-b-grant-revocation-authority-boundary", "english": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-5-b-grant-revocation-evidence-boundary", "english": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-5-b-later-read-core", "english": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-5-b-later-read-authority-boundary", "english": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-5-b-later-read-evidence-boundary", "english": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Orla a cancellable read-only view of the standing demo-recording; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(demo-recording, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-5", "form": "grant-live-view", "domain": "media file", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-5-a-source-edit-core", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v615.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v615.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v615.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v615.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-5-a-source-edit-authority-boundary", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-5-a-source-edit-evidence-boundary", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is revised from v608 to v615. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-5-a-source-deletion-core", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-5-a-source-deletion-authority-boundary", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-5-a-source-deletion-evidence-boundary", "english": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, briefing-clip is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-5-a-grant-revocation-core", "english": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-5-a-grant-revocation-authority-boundary", "english": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-5-a-grant-revocation-evidence-boundary", "english": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, the standing read permission for briefing-clip is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-5-a-later-read-core", "english": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-5-a-later-read-authority-boundary", "english": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-5-a-later-read-evidence-boundary", "english": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Fenn a separate copy of exactly briefing-clip v608. Do not leave Fenn with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is briefing-clip. Afterwards, Fenn consults briefing-clip again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(briefing-clip@v608, to=Fenn).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-5-b-source-edit-core", "english": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v629.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v629.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v629.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v629.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-5-b-source-edit-authority-boundary", "english": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-5-b-source-edit-evidence-boundary", "english": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is revised from v622 to v629. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-5-b-source-deletion-core", "english": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-5-b-source-deletion-authority-boundary", "english": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-5-b-source-deletion-evidence-boundary", "english": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, demo-recording is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-5-b-grant-revocation-core", "english": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-5-b-grant-revocation-authority-boundary", "english": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-5-b-grant-revocation-evidence-boundary", "english": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, the standing read permission for demo-recording is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-5-b-later-read-core", "english": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-5-b-later-read-authority-boundary", "english": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-5-b-later-read-evidence-boundary", "english": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Orla a separate copy of exactly demo-recording v622. Do not leave Orla with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing media file is demo-recording. Afterwards, Orla consults demo-recording again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(demo-recording@v622, to=Orla).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-5", "form": "send-snapshot", "domain": "media file", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-6-a-source-edit-core", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v710.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v710.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v710.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v710.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v710.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-6-a-source-edit-authority-boundary", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-6-a-source-edit-evidence-boundary", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-6-a-source-deletion-core", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-6-a-source-deletion-authority-boundary", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-6-a-source-deletion-evidence-boundary", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-6-a-grant-revocation-core", "english": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-6-a-grant-revocation-authority-boundary", "english": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-6-a-grant-revocation-evidence-boundary", "english": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-6-a-later-read-core", "english": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-6-a-later-read-authority-boundary", "english": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-6-a-later-read-evidence-boundary", "english": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Gita a cancellable read-only view of the standing escalation-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(escalation-policy, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-6-b-source-edit-core", "english": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v723.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v723.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v723.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v723.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v723.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-6-b-source-edit-authority-boundary", "english": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-6-b-source-edit-evidence-boundary", "english": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-6-b-source-deletion-core", "english": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-6-b-source-deletion-authority-boundary", "english": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-6-b-source-deletion-evidence-boundary", "english": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-glv-6-b-grant-revocation-core", "english": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-glv-6-b-grant-revocation-authority-boundary", "english": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-6-b-grant-revocation-evidence-boundary", "english": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-6-b-later-read-core", "english": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "live-view", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-glv-6-b-later-read-authority-boundary", "english": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-glv-6-b-later-read-evidence-boundary", "english": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: give Pieter a cancellable read-only view of the standing review-policy; every successful read returns the contents as they stand at that moment. Do not hand over a durable separate copy. This carries no right to edit or pass on the material and does not prove that it was opened.", "ainglish": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: grant-live-view(review-policy, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "grant-live-view-6", "form": "grant-live-view", "domain": "policy record", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "live-view", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-6-a-source-edit-core", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v710.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v710.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v710.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v710.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-6-a-source-edit-authority-boundary", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-6-a-source-edit-evidence-boundary", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is revised from v703 to v710. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-6-a-source-deletion-core", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-6-a-source-deletion-authority-boundary", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-6-a-source-deletion-evidence-boundary", "english": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, escalation-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-6-a-grant-revocation-core", "english": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-6-a-grant-revocation-authority-boundary", "english": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-6-a-grant-revocation-evidence-boundary", "english": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, the standing read permission for escalation-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-6-a-later-read-core", "english": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-6-a-later-read-authority-boundary", "english": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-6-a-later-read-evidence-boundary", "english": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Gita a separate copy of exactly escalation-policy v703. Do not leave Gita with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is escalation-policy. Afterwards, Gita consults escalation-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(escalation-policy@v703, to=Gita).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "a", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-6-b-source-edit-core", "english": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a later successful read returns what the source holds at that time, v723.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a later successful read returns what the source holds at that time, v723.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: what the recipient sees remains the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: what the recipient sees remains the version handed over.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "source-edit", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "what the recipient sees remains the version handed over.", "live_correct": "a later successful read returns what the source holds at that time, v723.", "snapshot_wrong": "a later successful read returns what the source holds at that time, v723.", "live_wrong": "what the recipient sees remains the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-6-b-source-edit-authority-boundary", "english": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "source-edit", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-6-b-source-edit-evidence-boundary", "english": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is revised from v716 to v723. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "source-edit", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-6-b-source-deletion-core", "english": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the source-backed permission retrieves nothing.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "source-deletion", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the source-backed permission retrieves nothing.", "snapshot_wrong": "a read attempted through the source-backed permission retrieves nothing.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-6-b-source-deletion-authority-boundary", "english": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "source-deletion", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 1}, {"id": "a76-snp-6-b-source-deletion-evidence-boundary", "english": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, review-policy is withdrawn from its source service and deleted. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "source-deletion", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-6-b-grant-revocation-core", "english": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a read attempted through the cancelled permission is refused.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the copy already delivered and kept stays usable exactly as it was.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "grant-revocation", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "the copy already delivered and kept stays usable exactly as it was.", "live_correct": "a read attempted through the cancelled permission is refused.", "snapshot_wrong": "a read attempted through the cancelled permission is refused.", "live_wrong": "the copy already delivered and kept stays usable exactly as it was."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76-snp-6-b-grant-revocation-authority-boundary", "english": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "grant-revocation", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-6-b-grant-revocation-evidence-boundary", "english": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, the standing read permission for review-policy is cancelled. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "grant-revocation", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-6-b-later-read-core", "english": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: a successful read resolves the standing object and returns its contents at that moment.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: opening the kept copy still shows the version handed over."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: opening the kept copy still shows the version handed over.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "later-read", "probe": "core", "gold_impl": "snapshot", "components": {"snapshot_correct": "opening the kept copy still shows the version handed over.", "live_correct": "a successful read resolves the standing object and returns its contents at that moment.", "snapshot_wrong": "a successful read resolves the standing object and returns its contents at that moment.", "live_wrong": "opening the kept copy still shows the version handed over."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 0}, {"id": "a76-snp-6-b-later-read-authority-boundary", "english": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. The recipient already holds another copy from a different grant; the instruction adds nothing about rights to edit or pass it on. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "later-read", "probe": "authority-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "live_correct": "no right to edit or pass on the material follows, and any copy granted by another route is untouched.", "snapshot_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked.", "live_wrong": "rights to edit and pass on the material follow, and any copy granted by another route is revoked."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 3}, {"id": "a76-snp-6-b-later-read-evidence-boundary", "english": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: hand Pieter a separate copy of exactly review-policy v716. Do not leave Pieter with continuing access to the source. Later revision, withdrawal, or loss of access at the source cannot alter or recall a copy that was delivered and kept. Handing it over does not by itself prove receipt.", "ainglish": "The standing policy record is review-policy. Afterwards, Pieter consults review-policy again. A copy handed over and kept is unaffected by later events at the source; a standing read permission keeps no copy of its own. Nothing records a receipt, an opening, or whether the service could be reached. Instruction: send-snapshot(review-policy@v716, to=Pieter).", "question": "Answer both parts by choosing the single option in which both are correct. (1) Which implementation carries out the instruction? (2) What later consequence or boundary follows?", "options": ["Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "Implementation: give a cancellable read-only view of the standing object. Consequence or boundary: the instruction by itself proves later receipt, keeping, opening, and reachability."], "answer": "Implementation: hand over a separate copy of the version named in the instruction. Consequence or boundary: the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "settlement_stratum": "send-snapshot-6", "form": "send-snapshot", "domain": "policy record", "variant": "b", "event": "later-read", "probe": "evidence-boundary", "gold_impl": "snapshot", "components": {"snapshot_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "live_correct": "the instruction by itself gives no proof of later receipt, keeping, opening, or reachability.", "snapshot_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability.", "live_wrong": "the instruction by itself proves later receipt, keeping, opening, and reachability."}, "status": "ORIGINAL_FROZEN_BEFORE_MINT", "gold_position": 2}, {"id": "a76m-cal-01", "english": "A76-CAL-01: either Alden Abbot or Faye Dunlin is the shift supervisor for the loading bay; the record does not settle which.", "ainglish": "A76-CAL-01: Alden Abbot, not Faye Dunlin, is the shift supervisor for the loading bay.", "question": "Who is the shift supervisor for the loading bay under this record?", "options": ["Alden Abbot", "Faye Dunlin", "the record does not settle it"], "answer": "Alden Abbot", "calibration": true, "calibration_scope": "target-independent", "gold_position": 0}, {"id": "a76m-cal-02", "english": "A76-CAL-02: either Dessa Fenwick or Ilse Inkwell is the duty archivist for the cold room; the record does not settle which.", "ainglish": "A76-CAL-02: Dessa Fenwick, not Ilse Inkwell, is the duty archivist for the cold room.", "question": "Who is the duty archivist for the cold room under this record?", "options": ["Ilse Inkwell", "the record does not settle it", "Dessa Fenwick"], "answer": "Dessa Fenwick", "calibration": true, "calibration_scope": "target-independent", "gold_position": 2}, {"id": "a76m-cal-03", "english": "A76-CAL-03: either Goran Kestrel or Loris Nutmeg is the network steward for the edge rack; the record does not settle which.", "ainglish": "A76-CAL-03: Goran Kestrel, not Loris Nutmeg, is the network steward for the edge rack.", "question": "Who is the network steward for the edge rack under this record?", "options": ["Goran Kestrel", "Loris Nutmeg", "the record does not settle it"], "answer": "Goran Kestrel", "calibration": true, "calibration_scope": "target-independent", "gold_position": 0}, {"id": "a76m-cal-04", "english": "A76-CAL-04: either Jorik Pebble or Ottil Crane is the records trustee for the sealed cabinet; the record does not settle which.", "ainglish": "A76-CAL-04: Jorik Pebble, not Ottil Crane, is the records trustee for the sealed cabinet.", "question": "Who is the records trustee for the sealed cabinet under this record?", "options": ["Ottil Crane", "the record does not settle it", "Jorik Pebble"], "answer": "Jorik Pebble", "calibration": true, "calibration_scope": "target-independent", "gold_position": 2}, {"id": "a76m-cal-05", "english": "A76-CAL-05: either Maud Elder or Briony Hallow is the relief operator for the night desk; the record does not settle which.", "ainglish": "A76-CAL-05: Maud Elder, not Briony Hallow, is the relief operator for the night desk.", "question": "Who is the relief operator for the night desk under this record?", "options": ["Briony Hallow", "Maud Elder", "the record does not settle it"], "answer": "Maud Elder", "calibration": true, "calibration_scope": "target-independent", "gold_position": 1}, {"id": "a76m-cal-06", "english": "A76-CAL-06: either Piet Jasper or Edrin Mariner is the custody lead for the evidence store; the record does not settle which.", "ainglish": "A76-CAL-06: Piet Jasper, not Edrin Mariner, is the custody lead for the evidence store.", "question": "Who is the custody lead for the evidence store under this record?", "options": ["Edrin Mariner", "the record does not settle it", "Piet Jasper"], "answer": "Piet Jasper", "calibration": true, "calibration_scope": "target-independent", "gold_position": 2}, {"id": "a76m-cal-07", "english": "A76-CAL-07: either Cato Orchard or Hedda Bramble is the release coordinator for the build lane; the record does not settle which.", "ainglish": "A76-CAL-07: Cato Orchard, not Hedda Bramble, is the release coordinator for the build lane.", "question": "Who is the release coordinator for the build lane under this record?", "options": ["Cato Orchard", "Hedda Bramble", "the record does not settle it"], "answer": "Cato Orchard", "calibration": true, "calibration_scope": "target-independent", "gold_position": 0}, {"id": "a76m-cal-08", "english": "A76-CAL-08: either Faye Dunlin or Kerra Gorse is the schedule keeper for the timing board; the record does not settle which.", "ainglish": "A76-CAL-08: Faye Dunlin, not Kerra Gorse, is the schedule keeper for the timing board.", "question": "Who is the schedule keeper for the timing board under this record?", "options": ["Faye Dunlin", "Kerra Gorse", "the record does not settle it"], "answer": "Faye Dunlin", "calibration": true, "calibration_scope": "target-independent", "gold_position": 0}, {"id": "a76m-cal-09", "english": "A76-CAL-09: either Ilse Inkwell or Nils Lantern is the inventory owner for the spare locker; the record does not settle which.", "ainglish": "A76-CAL-09: Ilse Inkwell, not Nils Lantern, is the inventory owner for the spare locker.", "question": "Who is the inventory owner for the spare locker under this record?", "options": ["Nils Lantern", "the record does not settle it", "Ilse Inkwell"], "answer": "Ilse Inkwell", "calibration": true, "calibration_scope": "target-independent", "gold_position": 2}, {"id": "a76m-cal-10", "english": "A76-CAL-10: either Loris Nutmeg or Alden Abbot is the duty purser for the manifest file; the record does not settle which.", "ainglish": "A76-CAL-10: Loris Nutmeg, not Alden Abbot, is the duty purser for the manifest file.", "question": "Who is the duty purser for the manifest file under this record?", "options": ["Alden Abbot", "Loris Nutmeg", "the record does not settle it"], "answer": "Loris Nutmeg", "calibration": true, "calibration_scope": "target-independent", "gold_position": 1}, {"id": "a76m-cal-11", "english": "A76-CAL-11: either Ottil Crane or Dessa Fenwick is the safety marshal for the assembly point; the record does not settle which.", "ainglish": "A76-CAL-11: Ottil Crane, not Dessa Fenwick, is the safety marshal for the assembly point.", "question": "Who is the safety marshal for the assembly point under this record?", "options": ["Dessa Fenwick", "Ottil Crane", "the record does not settle it"], "answer": "Ottil Crane", "calibration": true, "calibration_scope": "target-independent", "gold_position": 1}, {"id": "a76m-cal-12", "english": "A76-CAL-12: either Briony Hallow or Goran Kestrel is the signal keeper for the relay hut; the record does not settle which.", "ainglish": "A76-CAL-12: Briony Hallow, not Goran Kestrel, is the signal keeper for the relay hut.", "question": "Who is the signal keeper for the relay hut under this record?", "options": ["Goran Kestrel", "the record does not settle it", "Briony Hallow"], "answer": "Briony Hallow", "calibration": true, "calibration_scope": "target-independent", "gold_position": 2}, {"id": "a76m-cal-13", "english": "A76-CAL-13: either Edrin Mariner or Jorik Pebble is the ledger clerk for the settlement desk; the record does not settle which.", "ainglish": "A76-CAL-13: Edrin Mariner, not Jorik Pebble, is the ledger clerk for the settlement desk.", "question": "Who is the ledger clerk for the settlement desk under this record?", "options": ["Edrin Mariner", "Jorik Pebble", "the record does not settle it"], "answer": "Edrin Mariner", "calibration": true, "calibration_scope": "target-independent", "gold_position": 0}, {"id": "a76m-cal-14", "english": "A76-CAL-14: either Hedda Bramble or Maud Elder is the yield steward for the harvest log; the record does not settle which.", "ainglish": "A76-CAL-14: Hedda Bramble, not Maud Elder, is the yield steward for the harvest log.", "question": "Who is the yield steward for the harvest log under this record?", "options": ["Maud Elder", "Hedda Bramble", "the record does not settle it"], "answer": "Hedda Bramble", "calibration": true, "calibration_scope": "target-independent", "gold_position": 1}, {"id": "a76m-cal-15", "english": "A76-CAL-15: either Kerra Gorse or Piet Jasper is the transit officer for the departure gate; the record does not settle which.", "ainglish": "A76-CAL-15: Kerra Gorse, not Piet Jasper, is the transit officer for the departure gate.", "question": "Who is the transit officer for the departure gate under this record?", "options": ["Kerra Gorse", "Piet Jasper", "the record does not settle it"], "answer": "Kerra Gorse", "calibration": true, "calibration_scope": "target-independent", "gold_position": 0}, {"id": "a76m-cal-16", "english": "A76-CAL-16: either Nils Lantern or Cato Orchard is the audit reader for the invoice tray; the record does not settle which.", "ainglish": "A76-CAL-16: Nils Lantern, not Cato Orchard, is the audit reader for the invoice tray.", "question": "Who is the audit reader for the invoice tray under this record?", "options": ["Cato Orchard", "Nils Lantern", "the record does not settle it"], "answer": "Nils Lantern", "calibration": true, "calibration_scope": "target-independent", "gold_position": 1}], "sha256": "9b3df020c2b4ba2b96c6fcdbbf6b503334548bc044da0775e39730254f9b670c"}