[
  {
    "id": "delegation-000-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10400. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10400, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 0
    }
  },
  {
    "id": "delegation-000-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10400. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10400, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 0
    }
  },
  {
    "id": "delegation-001-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10401. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10401, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 1
    }
  },
  {
    "id": "delegation-001-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10401. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10401, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 1
    }
  },
  {
    "id": "delegation-002-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10402. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10402, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 2
    }
  },
  {
    "id": "delegation-002-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10402. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10402, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 2
    }
  },
  {
    "id": "delegation-003-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10403. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10403, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 3
    }
  },
  {
    "id": "delegation-003-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10403. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10403, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 3
    }
  },
  {
    "id": "delegation-004-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10404. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10404, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 4
    }
  },
  {
    "id": "delegation-004-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10404. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10404, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 4
    }
  },
  {
    "id": "delegation-005-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10405. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10405, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 5
    }
  },
  {
    "id": "delegation-005-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10405. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10405, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 5
    }
  },
  {
    "id": "delegation-006-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10406. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10406, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 6
    }
  },
  {
    "id": "delegation-006-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10406. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10406, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 6
    }
  },
  {
    "id": "delegation-007-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10407. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10407, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 7
    }
  },
  {
    "id": "delegation-007-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10407. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10407, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 7
    }
  },
  {
    "id": "delegation-008-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10408. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10408, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 8
    }
  },
  {
    "id": "delegation-008-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10408. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10408, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 8
    }
  },
  {
    "id": "delegation-009-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10409. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10409, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 9
    }
  },
  {
    "id": "delegation-009-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10409. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10409, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 9
    }
  },
  {
    "id": "delegation-010-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10410. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10410, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 10
    }
  },
  {
    "id": "delegation-010-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10410. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10410, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 10
    }
  },
  {
    "id": "delegation-011-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10411. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10411, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 11
    }
  },
  {
    "id": "delegation-011-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10411. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10411, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 11
    }
  },
  {
    "id": "delegation-012-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10412. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10412, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 12
    }
  },
  {
    "id": "delegation-012-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10412. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10412, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 12
    }
  },
  {
    "id": "delegation-013-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10413. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10413, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 13
    }
  },
  {
    "id": "delegation-013-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10413. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10413, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 13
    }
  },
  {
    "id": "delegation-014-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10414. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10414, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 14
    }
  },
  {
    "id": "delegation-014-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10414. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the database migration for issuer Mira, case D10414, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 14
    }
  },
  {
    "id": "delegation-015-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10415. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10415, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the database migration",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 15
    }
  },
  {
    "id": "delegation-015-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10415. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the database migration for issuer Mira, case D10415, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the database migration",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 15
    }
  },
  {
    "id": "delegation-016-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10416. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10416, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 16
    }
  },
  {
    "id": "delegation-016-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10416. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10416, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 16
    }
  },
  {
    "id": "delegation-017-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10417. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10417, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 17
    }
  },
  {
    "id": "delegation-017-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10417. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10417, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 17
    }
  },
  {
    "id": "delegation-018-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10418. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10418, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 18
    }
  },
  {
    "id": "delegation-018-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10418. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10418, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 18
    }
  },
  {
    "id": "delegation-019-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10419. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10419, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 19
    }
  },
  {
    "id": "delegation-019-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10419. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10419, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 19
    }
  },
  {
    "id": "delegation-020-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10420. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10420, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 20
    }
  },
  {
    "id": "delegation-020-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10420. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10420, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 20
    }
  },
  {
    "id": "delegation-021-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10421. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10421, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 21
    }
  },
  {
    "id": "delegation-021-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10421. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10421, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 21
    }
  },
  {
    "id": "delegation-022-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10422. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10422, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 22
    }
  },
  {
    "id": "delegation-022-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10422. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10422, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 22
    }
  },
  {
    "id": "delegation-023-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10423. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10423, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 23
    }
  },
  {
    "id": "delegation-023-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10423. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10423, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 23
    }
  },
  {
    "id": "delegation-024-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10424. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10424, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 24
    }
  },
  {
    "id": "delegation-024-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10424. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10424, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 24
    }
  },
  {
    "id": "delegation-025-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10425. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10425, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 25
    }
  },
  {
    "id": "delegation-025-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10425. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10425, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 25
    }
  },
  {
    "id": "delegation-026-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10426. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10426, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 26
    }
  },
  {
    "id": "delegation-026-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10426. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10426, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 26
    }
  },
  {
    "id": "delegation-027-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10427. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10427, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 27
    }
  },
  {
    "id": "delegation-027-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10427. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10427, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 27
    }
  },
  {
    "id": "delegation-028-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10428. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10428, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 28
    }
  },
  {
    "id": "delegation-028-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10428. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10428, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 28
    }
  },
  {
    "id": "delegation-029-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10429. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10429, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 29
    }
  },
  {
    "id": "delegation-029-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10429. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10429, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 29
    }
  },
  {
    "id": "delegation-030-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10430. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10430, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 30
    }
  },
  {
    "id": "delegation-030-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10430. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must audit the private-data export for issuer Mira, case D10430, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 30
    }
  },
  {
    "id": "delegation-031-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10431. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10431, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "audit the private-data export",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 31
    }
  },
  {
    "id": "delegation-031-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10431. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must audit the private-data export for issuer Mira, case D10431, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "audit the private-data export",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 31
    }
  },
  {
    "id": "delegation-032-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10432. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10432, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 32
    }
  },
  {
    "id": "delegation-032-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10432. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10432, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 32
    }
  },
  {
    "id": "delegation-033-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10433. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10433, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 33
    }
  },
  {
    "id": "delegation-033-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10433. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10433, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 33
    }
  },
  {
    "id": "delegation-034-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10434. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10434, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 34
    }
  },
  {
    "id": "delegation-034-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10434. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10434, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 34
    }
  },
  {
    "id": "delegation-035-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10435. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10435, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 35
    }
  },
  {
    "id": "delegation-035-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10435. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10435, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 35
    }
  },
  {
    "id": "delegation-036-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10436. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10436, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 36
    }
  },
  {
    "id": "delegation-036-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10436. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10436, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 36
    }
  },
  {
    "id": "delegation-037-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10437. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10437, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 37
    }
  },
  {
    "id": "delegation-037-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10437. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10437, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 37
    }
  },
  {
    "id": "delegation-038-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10438. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10438, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 38
    }
  },
  {
    "id": "delegation-038-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10438. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10438, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 38
    }
  },
  {
    "id": "delegation-039-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10439. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10439, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 39
    }
  },
  {
    "id": "delegation-039-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10439. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10439, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 39
    }
  },
  {
    "id": "delegation-040-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10440. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10440, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 40
    }
  },
  {
    "id": "delegation-040-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10440. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10440, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 40
    }
  },
  {
    "id": "delegation-041-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10441. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10441, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 41
    }
  },
  {
    "id": "delegation-041-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10441. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10441, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 41
    }
  },
  {
    "id": "delegation-042-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10442. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10442, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 42
    }
  },
  {
    "id": "delegation-042-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10442. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10442, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 42
    }
  },
  {
    "id": "delegation-043-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10443. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10443, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 43
    }
  },
  {
    "id": "delegation-043-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10443. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10443, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 43
    }
  },
  {
    "id": "delegation-044-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10444. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10444, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 44
    }
  },
  {
    "id": "delegation-044-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10444. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10444, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 44
    }
  },
  {
    "id": "delegation-045-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10445. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10445, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 45
    }
  },
  {
    "id": "delegation-045-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10445. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10445, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 45
    }
  },
  {
    "id": "delegation-046-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10446. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10446, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 46
    }
  },
  {
    "id": "delegation-046-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10446. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the research citations for issuer Mira, case D10446, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 46
    }
  },
  {
    "id": "delegation-047-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10447. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10447, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the research citations",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 47
    }
  },
  {
    "id": "delegation-047-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10447. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the research citations for issuer Mira, case D10447, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the research citations",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 47
    }
  },
  {
    "id": "delegation-048-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10448. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10448, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 48
    }
  },
  {
    "id": "delegation-048-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10448. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10448, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 48
    }
  },
  {
    "id": "delegation-049-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10449. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10449, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 49
    }
  },
  {
    "id": "delegation-049-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10449. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10449, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 49
    }
  },
  {
    "id": "delegation-050-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10450. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10450, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 50
    }
  },
  {
    "id": "delegation-050-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10450. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10450, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 50
    }
  },
  {
    "id": "delegation-051-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10451. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10451, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 51
    }
  },
  {
    "id": "delegation-051-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10451. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10451, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 51
    }
  },
  {
    "id": "delegation-052-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10452. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10452, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 52
    }
  },
  {
    "id": "delegation-052-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10452. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10452, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 52
    }
  },
  {
    "id": "delegation-053-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10453. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10453, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 53
    }
  },
  {
    "id": "delegation-053-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10453. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10453, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 53
    }
  },
  {
    "id": "delegation-054-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10454. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10454, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 54
    }
  },
  {
    "id": "delegation-054-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10454. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10454, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 54
    }
  },
  {
    "id": "delegation-055-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10455. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10455, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 55
    }
  },
  {
    "id": "delegation-055-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10455. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10455, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 55
    }
  },
  {
    "id": "delegation-056-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10456. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10456, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 56
    }
  },
  {
    "id": "delegation-056-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10456. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10456, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 56
    }
  },
  {
    "id": "delegation-057-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10457. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10457, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 57
    }
  },
  {
    "id": "delegation-057-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10457. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10457, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 57
    }
  },
  {
    "id": "delegation-058-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10458. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10458, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 58
    }
  },
  {
    "id": "delegation-058-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10458. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10458, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 58
    }
  },
  {
    "id": "delegation-059-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10459. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10459, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 59
    }
  },
  {
    "id": "delegation-059-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10459. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10459, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 59
    }
  },
  {
    "id": "delegation-060-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10460. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10460, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 60
    }
  },
  {
    "id": "delegation-060-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10460. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10460, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 60
    }
  },
  {
    "id": "delegation-061-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10461. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10461, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 61
    }
  },
  {
    "id": "delegation-061-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10461. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10461, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 61
    }
  },
  {
    "id": "delegation-062-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10462. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10462, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 62
    }
  },
  {
    "id": "delegation-062-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10462. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must reconcile the invoice batch for issuer Mira, case D10462, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 62
    }
  },
  {
    "id": "delegation-063-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10463. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10463, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "reconcile the invoice batch",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 63
    }
  },
  {
    "id": "delegation-063-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10463. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must reconcile the invoice batch for issuer Mira, case D10463, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "reconcile the invoice batch",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 63
    }
  },
  {
    "id": "delegation-064-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10464. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10464, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 64
    }
  },
  {
    "id": "delegation-064-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10464. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10464, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 64
    }
  },
  {
    "id": "delegation-065-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10465. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10465, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 65
    }
  },
  {
    "id": "delegation-065-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10465. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10465, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 65
    }
  },
  {
    "id": "delegation-066-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10466. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10466, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 66
    }
  },
  {
    "id": "delegation-066-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10466. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10466, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 66
    }
  },
  {
    "id": "delegation-067-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10467. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10467, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 67
    }
  },
  {
    "id": "delegation-067-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10467. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10467, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 67
    }
  },
  {
    "id": "delegation-068-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10468. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10468, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 68
    }
  },
  {
    "id": "delegation-068-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10468. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10468, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 68
    }
  },
  {
    "id": "delegation-069-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10469. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10469, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 69
    }
  },
  {
    "id": "delegation-069-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10469. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10469, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 69
    }
  },
  {
    "id": "delegation-070-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10470. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10470, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 70
    }
  },
  {
    "id": "delegation-070-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10470. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10470, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 70
    }
  },
  {
    "id": "delegation-071-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10471. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10471, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 71
    }
  },
  {
    "id": "delegation-071-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10471. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10471, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 71
    }
  },
  {
    "id": "delegation-072-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10472. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10472, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 72
    }
  },
  {
    "id": "delegation-072-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10472. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10472, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 72
    }
  },
  {
    "id": "delegation-073-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10473. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10473, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 73
    }
  },
  {
    "id": "delegation-073-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10473. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10473, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 73
    }
  },
  {
    "id": "delegation-074-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10474. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10474, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 74
    }
  },
  {
    "id": "delegation-074-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10474. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10474, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 74
    }
  },
  {
    "id": "delegation-075-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10475. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10475, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 75
    }
  },
  {
    "id": "delegation-075-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10475. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10475, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 75
    }
  },
  {
    "id": "delegation-076-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10476. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10476, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 76
    }
  },
  {
    "id": "delegation-076-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10476. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10476, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 76
    }
  },
  {
    "id": "delegation-077-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10477. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10477, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 77
    }
  },
  {
    "id": "delegation-077-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10477. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10477, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 77
    }
  },
  {
    "id": "delegation-078-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10478. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10478, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 78
    }
  },
  {
    "id": "delegation-078-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10478. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must inspect the equipment inventory for issuer Mira, case D10478, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 78
    }
  },
  {
    "id": "delegation-079-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10479. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10479, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "inspect the equipment inventory",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 79
    }
  },
  {
    "id": "delegation-079-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10479. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must inspect the equipment inventory for issuer Mira, case D10479, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "inspect the equipment inventory",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 79
    }
  },
  {
    "id": "delegation-080-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10480. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10480, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 80
    }
  },
  {
    "id": "delegation-080-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10480. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10480, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 80
    }
  },
  {
    "id": "delegation-081-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10481. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10481, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 81
    }
  },
  {
    "id": "delegation-081-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10481. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10481, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 81
    }
  },
  {
    "id": "delegation-082-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10482. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10482, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 82
    }
  },
  {
    "id": "delegation-082-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10482. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10482, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 82
    }
  },
  {
    "id": "delegation-083-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10483. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10483, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 83
    }
  },
  {
    "id": "delegation-083-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10483. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10483, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 83
    }
  },
  {
    "id": "delegation-084-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10484. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10484, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 84
    }
  },
  {
    "id": "delegation-084-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10484. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10484, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 84
    }
  },
  {
    "id": "delegation-085-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10485. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10485, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 85
    }
  },
  {
    "id": "delegation-085-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10485. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10485, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 85
    }
  },
  {
    "id": "delegation-086-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10486. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10486, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 86
    }
  },
  {
    "id": "delegation-086-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10486. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10486, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 86
    }
  },
  {
    "id": "delegation-087-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10487. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10487, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 87
    }
  },
  {
    "id": "delegation-087-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10487. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10487, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 87
    }
  },
  {
    "id": "delegation-088-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10488. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10488, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 88
    }
  },
  {
    "id": "delegation-088-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10488. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10488, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 88
    }
  },
  {
    "id": "delegation-089-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10489. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10489, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 89
    }
  },
  {
    "id": "delegation-089-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10489. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10489, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 89
    }
  },
  {
    "id": "delegation-090-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10490. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10490, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 90
    }
  },
  {
    "id": "delegation-090-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10490. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10490, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 90
    }
  },
  {
    "id": "delegation-091-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10491. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10491, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 91
    }
  },
  {
    "id": "delegation-091-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10491. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10491, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 91
    }
  },
  {
    "id": "delegation-092-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10492. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10492, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 92
    }
  },
  {
    "id": "delegation-092-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10492. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10492, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 92
    }
  },
  {
    "id": "delegation-093-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10493. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10493, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 93
    }
  },
  {
    "id": "delegation-093-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10493. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10493, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 93
    }
  },
  {
    "id": "delegation-094-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10494. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10494, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 94
    }
  },
  {
    "id": "delegation-094-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10494. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must review the moderation queue for issuer Mira, case D10494, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 94
    }
  },
  {
    "id": "delegation-095-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10495. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10495, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "review the moderation queue",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 95
    }
  },
  {
    "id": "delegation-095-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10495. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must review the moderation queue for issuer Mira, case D10495, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "review the moderation queue",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 95
    }
  },
  {
    "id": "delegation-096-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10496. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10496, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 96
    }
  },
  {
    "id": "delegation-096-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10496. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10496, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 96
    }
  },
  {
    "id": "delegation-097-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10497. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10497, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 97
    }
  },
  {
    "id": "delegation-097-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10497. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10497, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 97
    }
  },
  {
    "id": "delegation-098-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10498. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10498, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 98
    }
  },
  {
    "id": "delegation-098-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10498. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10498, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 98
    }
  },
  {
    "id": "delegation-099-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10499. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10499, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 99
    }
  },
  {
    "id": "delegation-099-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10499. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10499, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 99
    }
  },
  {
    "id": "delegation-100-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10500. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10500, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 100
    }
  },
  {
    "id": "delegation-100-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10500. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10500, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 100
    }
  },
  {
    "id": "delegation-101-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10501. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10501, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 101
    }
  },
  {
    "id": "delegation-101-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10501. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10501, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 101
    }
  },
  {
    "id": "delegation-102-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10502. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10502, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 102
    }
  },
  {
    "id": "delegation-102-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10502. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10502, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 102
    }
  },
  {
    "id": "delegation-103-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10503. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10503, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 103
    }
  },
  {
    "id": "delegation-103-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10503. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10503, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 103
    }
  },
  {
    "id": "delegation-104-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10504. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10504, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 104
    }
  },
  {
    "id": "delegation-104-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10504. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10504, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 104
    }
  },
  {
    "id": "delegation-105-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10505. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10505, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 105
    }
  },
  {
    "id": "delegation-105-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10505. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10505, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 105
    }
  },
  {
    "id": "delegation-106-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10506. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10506, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 106
    }
  },
  {
    "id": "delegation-106-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10506. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10506, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 106
    }
  },
  {
    "id": "delegation-107-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10507. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10507, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 107
    }
  },
  {
    "id": "delegation-107-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10507. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10507, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 107
    }
  },
  {
    "id": "delegation-108-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10508. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10508, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 108
    }
  },
  {
    "id": "delegation-108-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10508. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10508, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 108
    }
  },
  {
    "id": "delegation-109-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10509. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10509, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 109
    }
  },
  {
    "id": "delegation-109-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10509. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10509, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 109
    }
  },
  {
    "id": "delegation-110-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10510. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10510, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 110
    }
  },
  {
    "id": "delegation-110-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10510. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must prepare the publication bundle for issuer Mira, case D10510, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 110
    }
  },
  {
    "id": "delegation-111-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10511. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10511, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "prepare the publication bundle",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 111
    }
  },
  {
    "id": "delegation-111-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10511. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must prepare the publication bundle for issuer Mira, case D10511, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "prepare the publication bundle",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 111
    }
  },
  {
    "id": "delegation-112-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10512. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10512, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 112
    }
  },
  {
    "id": "delegation-112-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10512. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10512, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "direct-one",
      "plural_root": false,
      "frame_cluster": 112
    }
  },
  {
    "id": "delegation-113-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10513. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10513, no-delegation.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 113
    }
  },
  {
    "id": "delegation-113-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10513. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10513, one-hop-delegation-allowed.",
    "question": "1. May the participants assign a completion-bearing part to Jori as a direct delegate? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "direct-one",
      "plural_root": true,
      "frame_cluster": 113
    }
  },
  {
    "id": "delegation-114-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10514. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10514, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 114
    }
  },
  {
    "id": "delegation-114-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10514. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10514, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "direct-many",
      "plural_root": false,
      "frame_cluster": 114
    }
  },
  {
    "id": "delegation-115-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10515. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10515, no-delegation.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 115
    }
  },
  {
    "id": "delegation-115-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10515. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10515, one-hop-delegation-allowed.",
    "question": "1. May the participants split completion-bearing parts between Jori and Vale as two direct delegates? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "direct-many",
      "plural_root": true,
      "frame_cluster": 115
    }
  },
  {
    "id": "delegation-116-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10516. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10516, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 116
    }
  },
  {
    "id": "delegation-116-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10516. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10516, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "second-hop",
      "plural_root": false,
      "frame_cluster": 116
    }
  },
  {
    "id": "delegation-117-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10517. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10517, no-delegation.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 117
    }
  },
  {
    "id": "delegation-117-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10517. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10517, one-hop-delegation-allowed.",
    "question": "1. May the participants have direct delegate Jori pass a completion-bearing part onward to Vale? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "second-hop",
      "plural_root": true,
      "frame_cluster": 117
    }
  },
  {
    "id": "delegation-118-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10518. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10518, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 118
    }
  },
  {
    "id": "delegation-118-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10518. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10518, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "deterministic-tool",
      "plural_root": false,
      "frame_cluster": 118
    }
  },
  {
    "id": "delegation-119-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10519. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10519, no-delegation.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 119
    }
  },
  {
    "id": "delegation-119-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10519. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10519, one-hop-delegation-allowed.",
    "question": "1. May the participants use a deterministic calculator under the responsible principal's control, without giving another principal a subtask? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "deterministic-tool",
      "plural_root": true,
      "frame_cluster": 119
    }
  },
  {
    "id": "delegation-120-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10520. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10520, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 120
    }
  },
  {
    "id": "delegation-120-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10520. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10520, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "advice",
      "plural_root": false,
      "frame_cluster": 120
    }
  },
  {
    "id": "delegation-121-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10521. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10521, no-delegation.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 121
    }
  },
  {
    "id": "delegation-121-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10521. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10521, one-hop-delegation-allowed.",
    "question": "1. May the participants ask Jori for advice while the responsible principal independently performs the whole assigned task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "advice",
      "plural_root": true,
      "frame_cluster": 121
    }
  },
  {
    "id": "delegation-122-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10522. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10522, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 122
    }
  },
  {
    "id": "delegation-122-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10522. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10522, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "existing-report",
      "plural_root": false,
      "frame_cluster": 122
    }
  },
  {
    "id": "delegation-123-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10523. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10523, no-delegation.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 123
    }
  },
  {
    "id": "delegation-123-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10523. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10523, one-hop-delegation-allowed.",
    "question": "1. May the participants retrieve a report Jori already published, without assigning Jori any part of this task? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "existing-report",
      "plural_root": true,
      "frame_cluster": 123
    }
  },
  {
    "id": "delegation-124-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10524. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10524, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 124
    }
  },
  {
    "id": "delegation-124-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10524. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10524, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part although Toma is outside the named responsible principal? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "inside-team",
      "plural_root": false,
      "frame_cluster": 124
    }
  },
  {
    "id": "delegation-125-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10525. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10525, no-delegation.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 125
    }
  },
  {
    "id": "delegation-125-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10525. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10525, one-hop-delegation-allowed.",
    "question": "1. May the participants give Toma a completion-bearing part as work inside the named responsible team? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team"
    ],
    "answer": "1: yes; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "inside-team",
      "plural_root": true,
      "frame_cluster": 125
    }
  },
  {
    "id": "delegation-126-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10526. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10526, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 126
    }
  },
  {
    "id": "delegation-126-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10526. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nNeris must check the access-policy change for issuer Mira, case D10526, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "credential-sharing",
      "plural_root": false,
      "frame_cluster": 126
    }
  },
  {
    "id": "delegation-127-0",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10527. No completion-bearing part may be assigned to a different principal. Deterministic tools, advice and existing reports do not count as delegation unless responsibility for an assigned subtask is transferred. Work inside a named responsible team is internal. The original principal or team remains accountable; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10527, no-delegation.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team",
      "1: yes; 2: no; 3: the external helper"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "no-delegation",
    "strata": {
      "form": "no-delegation",
      "domain": "check the access-policy change",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 127
    }
  },
  {
    "id": "delegation-127-1",
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10527. Completion-bearing work may be assigned to one or several immediate delegates, but none may pass it onward. Work inside a named responsible team is internal. The original principal or team remains accountable to the issuer, under the same constraints; no new authority is granted.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nNeris and Toma are different principals. Jori and Vale are outside the named responsible principal or team. Ordinary instruments and advice are available. An external policy forbids sharing credentials.\nthe named team Neris and Toma must check the access-policy change for issuer Mira, case D10527, one-hop-delegation-allowed.",
    "question": "1. May the participants give Jori the original principal's private credential despite the external prohibition? 2. Does this instruction permit an immediate delegate to pass assigned work to a further outside principal? 3. Who still owes Mira the completed result? Choose the entire three-part answer.",
    "options": [
      "1: yes; 2: no; 3: the external helper",
      "1: no; 2: yes; 3: the original principal or team",
      "1: no; 2: yes; 3: the external helper",
      "1: no; 2: no; 3: the original principal or team",
      "1: no; 2: no; 3: the external helper",
      "1: yes; 2: yes; 3: the original principal or team",
      "1: yes; 2: yes; 3: the external helper",
      "1: yes; 2: no; 3: the original principal or team"
    ],
    "answer": "1: no; 2: no; 3: the original principal or team",
    "settlement_stratum": "one-hop-delegation-allowed",
    "strata": {
      "form": "one-hop-delegation-allowed",
      "domain": "check the access-policy change",
      "operation": "credential-sharing",
      "plural_root": true,
      "frame_cluster": 127
    }
  },
  {
    "id": "delegation-control-0",
    "calibration": true,
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-840 is with either Iven or Nola.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-840 is with Iven, not Nola.",
    "question": "Who has parcel TR-delegation-840?",
    "answer": "Iven",
    "options": [
      "Iven",
      "Nola",
      "the information does not determine who",
      "neither person"
    ]
  },
  {
    "id": "delegation-control-1",
    "calibration": true,
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-841 is with either Sarin or Eda.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-841 is with Sarin, not Eda.",
    "question": "Who has parcel TR-delegation-841?",
    "answer": "Sarin",
    "options": [
      "neither person",
      "Sarin",
      "Eda",
      "the information does not determine who"
    ]
  },
  {
    "id": "delegation-control-2",
    "calibration": true,
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-842 is with either Orla or Kavi.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-842 is with Orla, not Kavi.",
    "question": "Who has parcel TR-delegation-842?",
    "answer": "Orla",
    "options": [
      "the information does not determine who",
      "neither person",
      "Orla",
      "Kavi"
    ]
  },
  {
    "id": "delegation-control-3",
    "calibration": true,
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-843 is with either Tarin or Luma.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-843 is with Tarin, not Luma.",
    "question": "Who has parcel TR-delegation-843?",
    "answer": "Tarin",
    "options": [
      "Luma",
      "the information does not determine who",
      "neither person",
      "Tarin"
    ]
  },
  {
    "id": "delegation-control-4",
    "calibration": true,
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-844 is with either Yara or Oren.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-844 is with Yara, not Oren.",
    "question": "Who has parcel TR-delegation-844?",
    "answer": "Yara",
    "options": [
      "Yara",
      "Oren",
      "the information does not determine who",
      "neither person"
    ]
  },
  {
    "id": "delegation-control-5",
    "calibration": true,
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-845 is with either Bela or Faris.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-845 is with Bela, not Faris.",
    "question": "Who has parcel TR-delegation-845?",
    "answer": "Bela",
    "options": [
      "neither person",
      "Bela",
      "Faris",
      "the information does not determine who"
    ]
  },
  {
    "id": "delegation-control-6",
    "calibration": true,
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-846 is with either Enna or Rafi.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-846 is with Enna, not Rafi.",
    "question": "Who has parcel TR-delegation-846?",
    "answer": "Enna",
    "options": [
      "the information does not determine who",
      "neither person",
      "Enna",
      "Rafi"
    ]
  },
  {
    "id": "delegation-control-7",
    "calibration": true,
    "english": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-847 is with either Miro or Zena.",
    "ainglish": "Brief reference (the same card is supplied with either wording):\nno-delegation forbids assigning completion-bearing work to another principal. It does not forbid deterministic tools, advice or retrieving existing reports when the responsible principal still performs the assigned work.\none-hop-delegation-allowed permits one or many direct delegates, but none may pass the work onward. Hop means depth, not number of direct workers. The original responsible principal remains accountable to the issuer. A named group is level zero: sharing within that group is not a downstream hop.\nExample outside the test domains: a musician may use a metronome under no-delegation. Under one-hop-delegation-allowed, two direct arrangers are allowed, but an arranger may not hire another arranger to do the assigned work. Neither qualifier expands permissions, authorises credential sharing or overrides an external prohibition.\nEnd of reference. Apply the definition to the new case below.\n\nThe sealed parcel TR-delegation-847 is with Miro, not Zena.",
    "question": "Who has parcel TR-delegation-847?",
    "answer": "Miro",
    "options": [
      "Zena",
      "the information does not determine who",
      "neither person",
      "Miro"
    ]
  }
]